Now that we've (almost?) shipped the axe-core 4.1.1 update, I'd like to write best practice documentation for e2e accessibility testing.
Tasks
[ ] Update the Cypress best practices on VSP document with a new section on "what makes a good accessibility test in Cypress"
Acceptance Criteria
The documentation updates should include the following:
[ ] Pages should be fully rendered before an axe check is run
[ ] Consider axe checks for forms before they are filled out, and after
[ ] Consider opening accordions and / or modal dialogs and running a second axe check
[ ] Re-enable the color-contrast check for 1-2 tests per product
How to configure this issue
[ ] Attached to a Milestone (when will this be completed?)
[ ] Attached to an Epic (what body of work is this a part of?)
[x] Labeled with Team (product support, analytics-insights, operations, service-design, tools-be, tools-fe)
[x] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
[x] Labeled with Type (bug, request, discovery, documentation, etc.)
pjhill
commented
2 years ago
Issue Description
Now that we've (almost?) shipped the axe-core 4.1.1 update, I'd like to write best practice documentation for e2e accessibility testing.
Tasks
Acceptance Criteria
The documentation updates should include the following:
How to configure this issue
product support,analytics-insights,operations,service-design,tools-be,tools-fe)backend,frontend,devops,design,research,product,ia,qa,analytics,contact center,research,accessibility,content)bug,request,discovery,documentation, etc.)