Open YedidaZalik opened 2 years ago
I think we can icebox this one. We will be listing the critical a11y issues that remain unresolved in our Accessibility statement, and we can look to provide the full audit to public servants/teams that request it
Description
As a user of Notify, I need to be able to find and read the accessibility audit so that I can understand what steps Notify has taken to create an accessible product.
WHY are we building? So that our work is in the open, including our work to make our product accessible. WHAT are we building? A link to publicly host our accessibility audit. VALUE created by our solution Individual users can read about the particular accessibility issues on Notify that are relevant to them.
Acceptance Criteria** (Definition of done)
To be refined through discussion with the team
Given a user wants to know specific details on how Notify was tested for accessibility, they'll be able to find and read that information.
If this user story emerged from User Research insights:
[ ] Link research insight back to hypothesis from Epic or Objective in Airtable
[ ] Once change/fix/feature is implemented, mark insight as "resolved" in Airtable
[ ] Once change/fix/feature is implements, link insight to design artifacts (Figma) in Airtable
A11y
Measuring success and metrics
QA Steps