| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Review requested:
|
Sorry, something went wrong.
The current use of color only to differentiate links fails WCAG A accessibility standards. Possible solutions are: 1. Using a text indicator to show that the text is a link. 2. Using additional cues (such as underlining). 3. Providing color contrast of 3:1 or greater with surrounding text (not the background--the adjacent text!) along with visual cues on hover. The solution here implements the second option. Ref: https://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html Ref: https://www.w3.org/WAI/WCAG21/Techniques/failures/F73 Ref: https://www.w3.org/WAI/WCAG21/Techniques/general/G182
There was a problem hiding this comment.
This seems such a trivial enough change, that it definitely brings more benefits as outlined by Rich, even tho these API docs are due to a redeisgn.
Thanks for the effort of making this change and bringing relevant docs, Rich!
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
We may want to revise this later to improve the aesthetics, but I think it's better to make it accessible first and then figure out how to make it look better. In a lot of cases, adding the underlining looks just fine: But it can be a bit much when everything is a link: (Or maybe all that underlining is fine. I don't know.) |
Sorry, something went wrong.
The current use of color only to differentiate links fails WCAG A accessibility standards. Possible solutions are: 1. Using a text indicator to show that the text is a link. 2. Using additional cues (such as underlining). 3. Providing color contrast of 3:1 or greater with surrounding text (not the background--the adjacent text!) along with visual cues on hover. The solution here implements the second option. Ref: https://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html Ref: https://www.w3.org/WAI/WCAG21/Techniques/failures/F73 Ref: https://www.w3.org/WAI/WCAG21/Techniques/general/G182 PR-URL: #50481 Refs: https://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html Refs: https://www.w3.org/WAI/WCAG21/Techniques/failures/F73 Refs: https://www.w3.org/WAI/WCAG21/Techniques/general/G182 Reviewed-By: Claudio Wunder <cwunder@gnome.org> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Tierney Cyren <hello@bnb.im> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
The current use of color only to differentiate links fails WCAG A accessibility standards. Possible solutions are: 1. Using a text indicator to show that the text is a link. 2. Using additional cues (such as underlining). 3. Providing color contrast of 3:1 or greater with surrounding text (not the background--the adjacent text!) along with visual cues on hover. The solution here implements the second option. Ref: https://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html Ref: https://www.w3.org/WAI/WCAG21/Techniques/failures/F73 Ref: https://www.w3.org/WAI/WCAG21/Techniques/general/G182 PR-URL: #50481 Refs: https://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html Refs: https://www.w3.org/WAI/WCAG21/Techniques/failures/F73 Refs: https://www.w3.org/WAI/WCAG21/Techniques/general/G182 Reviewed-By: Claudio Wunder <cwunder@gnome.org> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Tierney Cyren <hello@bnb.im> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
The current use of color only to differentiate links fails WCAG A accessibility standards. Possible solutions are: 1. Using a text indicator to show that the text is a link. 2. Using additional cues (such as underlining). 3. Providing color contrast of 3:1 or greater with surrounding text (not the background--the adjacent text!) along with visual cues on hover. The solution here implements the second option. Ref: https://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html Ref: https://www.w3.org/WAI/WCAG21/Techniques/failures/F73 Ref: https://www.w3.org/WAI/WCAG21/Techniques/general/G182 PR-URL: #50481 Refs: https://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html Refs: https://www.w3.org/WAI/WCAG21/Techniques/failures/F73 Refs: https://www.w3.org/WAI/WCAG21/Techniques/general/G182 Reviewed-By: Claudio Wunder <cwunder@gnome.org> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Tierney Cyren <hello@bnb.im> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
| Back | FazBrowse Home | New Git URL |
The current use of color only to differentiate links fails WCAG A accessibility standards.
Possible solutions are:
The solution here implements the second option.
Ref: https://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html
Ref: https://www.w3.org/WAI/WCAG21/Techniques/failures/F73
Ref: https://www.w3.org/WAI/WCAG21/Techniques/general/G182