What is the problem that we want to solve?
The accessibility review found meaningful user-facing barriers across az_quickstart, but the project does not yet have a shared policy for what must be tested before release. Without an agreed page matrix and verification bar, the team can fix individual issues while still missing real-world user journeys.
Why this matters to users
Users do not experience Quickstart one component at a time. They experience full pages and complete tasks. If the project only tests isolated widgets, people can still run into accessibility blockers in the places they actually use every day.
Outcome we want
Create a documented verification policy that tells the team:
- Which representative pages must pass before release.
- Which assistive-technology combinations must be used for manual checks.
- What level of verification is required for patch versus minor releases.
- Which issues must block release if they remain unresolved.
Scope
- Representative page matrix
- Assistive-technology matrix
- Verification expectations by release type
- Recommendation for the first implementation wave
Out of scope
- CI implementation work
- Component remediation work
Recommended discussion points
- Should patch releases require a smaller but mandatory accessibility check set?
- Which pages best represent the highest-risk Quickstart user journeys?
- Which flows need manual testing every time versus only when changed?
Conditions of satisfaction
What is the problem that we want to solve?
The accessibility review found meaningful user-facing barriers across az_quickstart, but the project does not yet have a shared policy for what must be tested before release. Without an agreed page matrix and verification bar, the team can fix individual issues while still missing real-world user journeys.
Why this matters to users
Users do not experience Quickstart one component at a time. They experience full pages and complete tasks. If the project only tests isolated widgets, people can still run into accessibility blockers in the places they actually use every day.
Outcome we want
Create a documented verification policy that tells the team:
Scope
Out of scope
Recommended discussion points
Conditions of satisfaction