-
-
Notifications
You must be signed in to change notification settings - Fork 748
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
Improve accessibility #1963
Comments
https://pagespeed.web.dev/ (also part of Lighthouse in Chrome devtools) and https://wave.webaim.org/ are useful accessibility tools. For example, https://pagespeed.web.dev/report?url=https%3A%2F%2Fendoflife.date%2Fpython gives a score of 97 with 1 failed audit: "Links do not have a discernible name" and 10 to check manually. And https://wave.webaim.org/report#/https://endoflife.date/python has 2 errors and 2 alerts. |
The automated checks are not that helpful, we need a better review - things like Color meanings for eg, or strikethrough meaning are entirely missed. |
Two issues on our theme to track: |
As an FYI, in the latest patch I just cut (0.5.2) I've added better accessibility roles/features for buttons. If there are other changes you want to upstream to JtD, would love to do so - accessibility is top-of-mind for me wrt the theme. |
Is your feature request related to a problem? Please describe.
Product pages can be made more accessible.
Describe the solution you'd like
A clear review of accessibility issues, and fixes for the same. Most of this comes from the information we stuff in the table, but might apply elsewhere. This includes:
Adding ARIA annotations for some of the above will be helpful. https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Annotations
The text was updated successfully, but these errors were encountered: