-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add accessibility testing #37
Comments
@upkarlidder @demilolu This issue needs the ms-cohort-claimed label |
pa11y-ci
|
Google Lighthouse CI
|
axe
|
Discussing with our accessibility experts. Feel free to pick one if you don't hear back by Friday (03.04). |
@kayleekimberly adding another on to the mix for your investigation - https://www.npmjs.com/package/accessibility-checker Edit - @tombrunet added more details in the comment below. Thank you 🙏🏽 |
IBM Equal Access Accessibility Checker - https://www.ibm.com/able/toolkit/tools/#develop
|
Additional notes on the IBM Equal Access Accessibility Checker:
|
Conclusions from the above investigation: All of the tools that were investigated appear to be quality, popular choices for automated accessibility testing. My top recommendations would be the IBM Equal Access Accessibility Checker or the pa11y-ci. I think either tool would be a good fit for the project. CC: @upkarlidder |
Thank you for the detailed investigation @kayleekimberly. With the final two recommendations, let's go with |
Remaining tasks for this issue
The jest boilerplate documentation is a great place to start. |
Is your feature request related to a problem? Please describe.
There is currently no accessibility testing
Describe the solution you'd like
We would like to add an accessibility testing library/framework to the project
Describe alternatives you've considered
Other forms of testing (unit/integration)
Additional context
N/a
The text was updated successfully, but these errors were encountered: