-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix critical accessibility issues #595
Comments
Radio/RadioGroup |
Hey @kaikdi , when I manually set the background color in storybook to the same background color we use in Figma (hsl(216 9% 10% / 1), at least some contrast violations disappeared for the RadioGroup. Could you try out to change the default background color for the dark mode in storybook? |
@thrbnhrtmnn I applied custom |
Checked everything again and the only open topic is for the NumberInput and maybe the Tooltip once the refactored version is merged. |
As decided today all open issues will be done in a follow up task after alpha release |
Description / User Story
After #187 this is the task to fix the most critical accessibility issues. Preparing this task is part of #187 .
TIMEBOX: 1 iteration
Requirements
Acceptance Criteria
NumberInputBackground information
Incomplete tests from #187
TextButton: Elements must have sufficient color contrast (disabled=true & theme=light)Checkbox: Form field must not have multiple label elements (hasLabel=true)Radio: ARIA attributes must conform to valid values (disabled=true / hasError=true)Violations from #187
IconButton: Elements must only use allowed ARIA attributes (disabled=true)TextButton:id attribute value must be unique (all states & variants)ARIA commands must have an accessible name (loading=true)Elements must have sufficient color contrast (disabled=true & theme=light / variant=secondary / variant=encourage)> Follow up tasks were created: TextButton - resolve contrast violation in disabled state #660 & TextButton - encourage variant does not reach contrast minimum in light theme #661Checkbox:Form elements must have labels (hasLabel=false / checkInputId="" / hasLabel=true & label="")Elements must have sufficient color contrast (theme=dark & hasError=true / theme=dark & showHint=true)Radio:Form elements must have labels (label="" / optionId="")> this is just using the component wrong, we should not invest too much effort in preventing users to do that, there will almost always be a way to break thingsElements must have sufficient color contrast (disabled=true / theme=dark & showHint=true / theme=dark & hasError=true)RadioGroup:ARIA attributes must conform to valid values (hasError=true)Elements must have sufficient color contrast (theme=dark & hasError=true / theme=dark & showHint=true)Select: Elements must have sufficient color contrast (> error state contrast needs to be fixed by design, a follow up task will be createdtheme=dark & showHint=true /theme=dark & hasError=true)TextInput:theme=dark & hasError=true /theme=dark & showHint=true) ~ > error state contrast needs to be fixed by design, a follow up task will be createdForm elements must have labels (placeholder="")TextArea: Elements must have sufficient color contrast (theme=dark & hasError=true / theme=dark & showHint=true / theme=dark & showCounter=true & warningState=true / theme=dark & showCounter=true & errorState=true / showCounter=true & size=md)ToggleSwitch: Elements must have sufficient color contrast (theme=dark & showHint=true)FormCaption (currently still named FormHint): Elements must have sufficient color contrast (theme=dark)FormCaptionGroup (currently still named FormInfo): Elements must have sufficient color contrast (theme=dark)FormLabel:Elements must have sufficient color contrast (theme=dark & variant=error)id attribute value must be unique (all states & variants)ButtonGroup:ARIA commands must have an accessible name (all states & variants)Elements must have sufficient color contrastthis only happens due to the "labels" next to the component, should be fixed with documentation taskFollow-Up Task
Some components received new errors while this issue was in progress, these issues will be fixed in a follow-up task. This includes the following components:
Incomplete tests:
Components that need to be checked as well after refactoring tasks:
The text was updated successfully, but these errors were encountered: