-
Notifications
You must be signed in to change notification settings - Fork 65
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
Icon A11y improvements #4215
Comments
from #4194
|
@StephDriver to find a list of all icons we actually use. |
A search of the codebase showed up 126 icons, which I have grouped below as some are variations on each other.
|
backlog refinement
This issue needs to scale back in order to meet the WCAG target - so just marking as decorative/ adding aria labels so that the icons currently in use are accessible, and making notes of the process for future work on the design system. Prioritise typesetting. |
Icons are not being handled accessibly.
Icons are non-text content as per WCAG 1.1.1.
The key technique is H86
They must also be semantically identified, as per ARIA24 Technique.
Most of our icons come from Font Awesome, but there are a few others, such as the ORCiD logo, that need individual handling.
For Font Awesome:
The text was updated successfully, but these errors were encountered: