[CI/CD]: Review coverage of accessibility checks in EDU apply-wizard end-to-end tests

[1Copenut]

Feedback framework

• ❗️ Must for if the feedback must be applied
• ⚠️Should if the feedback is best practice
• ✔️ Consider for suggestions/enhancements

Description

Applications must have thorough end-to-end tests that run in our continuous integration/continuous deployment (CI/CD) pipeline. These tests should include thorough axe checks. While auditing the /edu-benefits/edu-apply-wizard folder, I noticed we should be calling the axe check after all radio buttons have been checked and the entire wizard is shown. I'd like the front-end engineering team to review the applications, and update the tests to review this hidden content. Definition of done in acceptance criteria below.

Point of Contact

VFS Point of Contact: Trevor

Environment

• vets-website/src/applications/edu-benefits/edu-apply-wizard/tests
• $ yarn test:e2e src/applications/edu-benefits/edu-apply-wizard/tests

Acceptance Criteria

Definition of done:

• [ ] Front-end team member(s) have reviewed end-to-end tests for axe checks
• [ ] Check all radio buttons to show the entire wizard. Then run the axe check.
• [ ] FE team has consulted with accessibility specialist in cases where there are high numbers of modals, accordions, other hidden content that could slow down e2e test runs.
• [ ] No axe violations appear in the plugin console. These will break the CI/CD build.

WCAG or Vendor Guidance (optional)

• Custom axeCheck helper method
• VSP guidance on writing end-to-end tests

[1Copenut]

@mattpointzxer0 If the team has moved to use the Cypress forms testing, would you mind commenting here and at include me? The Cypress forms tester has axe checks built in and would be a good way to close this issue without additional work.