Closed dmtrek14 closed 2 years ago
@GeraldMit et al lets hold this one a bit. I'm cleaning up the other workflows at the moment.
@dmtrek14 thanks again also for contribution here! Once we get this merged, if you're available would love to have you join us to discuss this PR during our Hacktoberfest Demo Day. and if you can't make it live would love to be able to get some quick thoughts from you on it that we can refer to during the event.
Let me know if you're interested either way and I can follow up.
@demilolu As noted in the other PR, I'd love to join you all!
Signed-off-by: Danielle Mayabb dmmayabb@gmail.com
Contributes to #216
What did you do?
Added an action similar to the build action that runs just the accessibility tests for the UI
Added a a11y.spec.js file with a skeleton of what a test for a11y could look like if jest-axe is used
Why did you do it?
Axe is one of the best libraries for testing a11y. Automated tests for a11y can be tricky and have pros/cons as noted in this article: https://www.a11y-collective.com/blog/automated-accessibility-testing-a-few-scenarios/.
How have you tested it?
Yes.
Were docs updated if needed?
[ ] No
[ ] Yes
[X ] N/A
Type of change
Checklist: