Open pacerwow opened 2 months ago
Hey @bacitracin responding to the questions above:
Scope: I broke up the tickets by form section. Representative sample: Not sure how to answer this one. Page traffic: I prioritized the subtasks by page traffic, focusing on the most heavily used pages first https://analytics.google.com/analytics/web/#/analysis/p419143770/edit/BtqeUqzLR3y7cFsUETgZwQ
Adding more context to this ticket that Rueben shared in DSVA slack. It helps sum up the future opportunities for shaping the 5103 work beyond what is scoped for Sprint 10.
Issue Description
As a T-REX team member, I want a full accessibility audit of the online 21-526ez form so that I know more about how accessible our product is and I am able to identify future opportunities for accessibility improvements.
This work will help further the related OCTO objective "Our digital experiences are the best way to access VA health care and benefits."
Evaluation methods
Environments evaluated
Bugs/violations will be recorded in an Google Sheets spreadsheet with specific WCAG violation, severity level and an general estimated "level of effort"
Note: VPAT could be split out into its own ticket Final result will be an Accessibility Conformance Report (ACR) using the Voluntary Product Accessibility Template (VPAT)
VPAT will show conformance against the following standards
Tasks
Acceptance Criteria
Outstanding questions