-
Notifications
You must be signed in to change notification settings - Fork 6
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
♿ #1084 Check borders after accessibility changes #463
♿ #1084 Check borders after accessibility changes #463
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #463 +/- ##
========================================
Coverage 96.46% 96.46%
========================================
Files 505 505
Lines 18255 18255
========================================
Hits 17609 17609
Misses 646 646 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
dda7ee7
to
798e448
Compare
Some elements still do need a bigger accessibility contrast with a different color |
18acea9
to
9ca7f72
Compare
22057d2
to
38a18fc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -13,12 +13,12 @@ | |||
} | |||
|
|||
&__list-item { | |||
border-bottom: var(--border-width) solid var(--color-mute); | |||
border-bottom: var(--border-width) solid var(--color-gray); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, you are right, I think this should become 1px as well; i will add to it.
@vaszig Do you mean you think that there should be an extra border there? |
Yes, anything that is -actually- needed for accessibility ("Interface Components" and "Graphical Objects" such as form elements etc.) still needs that darker border, so i did not change it for the elements that still need it. I you feel like looking deeper into this, look at my Stackoverlflow question-with-answer linked in the description of this PR. |
No, I mean the |
Ah, I see, you mean the voting-labels; well spotted! |
Thanks @vaszig for the detailed check! 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only two small remarks ant I think it's ready to be merged. @alextreme can tell us his opinion as well.
@@ -12,16 +12,38 @@ | |||
color: var(--color-primary); | |||
cursor: default; | |||
} | |||
&#negative { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes that is not the way it should be, eventually, but I want to collect that in a new ticket for all accessibility issues that are not quite on par yet.
@vaszig My opinion is that we'll likely have to iterate on this, we won't be able to get this exactly according to the design in one go but I'm happy with these and other steps being taken. |
Some borders need to be reverted to original design, because: The 'Toegankelijkheidsaudit' does not explicitly ask for borders around these areas + This Level AA requirement reads: "...Incidental: Text[...]that are part of an inactive user interface component, that are pure decoration,[...], have no contrast requirement..."
"pure decoration" in the definition of WCAG = "serving only an aesthetic purpose, providing no information, and having no functionality"
https://taiga.maykinmedia.nl/project/open-inwoner/task/1084
Answer to my question on Stack Overflow: https://stackoverflow.com/questions/75379770/do-borders-that-visually-group-related-content-have-a-contrast-requirement
“... WCAG does not require you to have a border around the grouped elements. […] there aren't any WCAG requirements for the contrast. 1.4.11 Non-text Contrast comes close but that requirement is for "Interface Components" and "Graphical Objects". Your tile might contain "Interface Components" (such as a link) but the tile itself is not an "Interface Component" so 1.4.11 does not apply. That doesn't mean you shouldn't try to have better contrast, but it's not required by WCAG.”