-
-
Notifications
You must be signed in to change notification settings - Fork 766
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
Accessibility Audit #1347
Comments
OverviewThere are more than 100 accessibility testing tools. Figuring out which ones to use can be a black hole. For guidance we recommend this article: Which accessibility testing tool should you use? Summary of ArticleThe author recommends using the tools in the following order fixing as you go along, since no one tool catches all the relevant issues aXe But if you want to test your site with other tools, here is a bigger list |
The review could be done now and just ignore the alt text flags. |
We are going to make one issue using this template Ask QiQi how often we should do it Checking the board to see if the feasibility is good (meaning there are either not a lot of outstanding issues or they are all of a specific type). |
@GLRJr brought up a good point for using an accessibility linter. We could use a vs code extension from deque systems like this |
@qiqicodes Can you talk to us about how often an accessibility audit should be made, in your opinion? So far, we plan to perform an audit after the current slew of accessibility issues are completed. Afterwards, should an audit be performed at a regular interval? Let me know, because if so, we can create a GHA to create an automated issue. |
Dependency
Overview
Accessibility Audit to follow the WCAG 2.0/2.1 guidelines
Action Items
- [ ] Improve current project card’s headings and links’ descriptions
- [ ] test with keyboard tab to see focusable elements
- [ ] test with a blur filter along side with screen reader and voiceover
Resources/Instructions
Guidelines/Law:
- WCAG 2.0 & 2.1
- Quick Reference
- Tools & Guidance
Tool Extensions:
Here are some of the sample errors we currently have for Hack for LA website:
Hack for LA Web Accessibility Results
The text was updated successfully, but these errors were encountered: