[Epic][AP] Accessibility support and testing - Githubissues

department-of-veterans-affairs / va.gov-cms

Editor-centered management for Veteran-centered content.

https://prod.cms.va.gov

GNU General Public License v2.0

99 stars 69 forks source link

[Epic][AP] Accessibility support and testing #14457

Open timcosgrove opened 1 year ago

timcosgrove commented 1 year ago

Requirements & Goals

### How will we know we've achieved our goal?
- [x] All checking of a11y compliance is set to WCAG 2.1 AA standards
- [x] The Next Build repo is instrumented with checks for a11y standard compliance in CI and in local repository testing
- [ ] Ongoing a11y checks of VA.gov content are set up so that CMS content can be checked for a11y compliance.

Work

### Issues or tasks to be turned into issues
- [ ] https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16117
- [ ] https://github.com/department-of-veterans-affairs/va.gov-cms/issues/17776
- [ ] https://github.com/department-of-veterans-affairs/va.gov-cms/issues/17777
- [ ] https://github.com/department-of-veterans-affairs/va.gov-cms/issues/18450

Supporting material

We have accessibility testing in the next-build repo available through axe-core, both in jest and e2e tests.

We should implement these additional things:

run the e2e suite in CI
run the a11y test spec in CI separately, on a set cadence (daily / weekly)
output the results of that weekly scan in a readable format (interested parties shouldn't need to scroll GHA logs) -- location of that output should be on a reachable and VA-sharable location, and should be browsable (HTML report)

timcosgrove commented 1 year ago

AMP scans? Talk to Laura, as the landscape may be changing.