Documentation Update | Add "column" for pass/fails in documentation - Non text contrast - Githubissues

w3c / wcag

Web Content Accessibility Guidelines

https://w3c.github.io/wcag/guidelines/22/

Other

1.14k stars 256 forks source link

Documentation Update | Add "column" for pass/fails in documentation - Non text contrast #3987

Closed Gcamara14 closed 3 months ago

Gcamara14 commented 4 months ago

Problem:

We have a data table with examples on accessibility. But makes it very difficult to convey if they "Pass/Fail."

Solution:

When we have examples. Clearly state whethere they Pass or Fail.

Benefits:

This will save people time understanding what passes/fails. If accessibility testers can save time here, they can finish more work and make the world more accessible...
This is more beginner friendly.
It's better UX

Example:

On the user interface examples data table. Add a new column that states whether they pass/fail.

Image:

Screenshot of the non-text contrast WCAG requirement. The data tables convey examples such as link text example, but does not convey whether it passes or fails.

URL:

https://www.w3.org/WAI/WCAG22/Understanding/non-text-contrast.html#:~:text=have%20sufficient%20contrast.-,User%20Interface%20Component%20Examples,-Type

fstrr commented 4 months ago

We have a pull request that is waiting for approval that does something similar to what you're asking for. There's a demo page (not with the current design) where:

We've split passing and failing examples into two tables.
We've re-written the contents of the figcaption elements so they all start with "pass" or "fail".

Hopefully that's what you're looking for.