• New UI flows are released and accessibility compliance must be checked.
• Product targets inclusive use across keyboard and screen reader users.
• Team needs evidence against accessibility standards before launch.

• Detect accessibility barriers in structure, interaction, and content readability.
• Output prioritized fixes that improve usability for assistive technology users.
• Reduce legal and product risk caused by inaccessible experience.

1. Select key user journeys and accessibility target level.
2. Check semantic structure, focus order, and keyboard operability.
3. Validate contrast, labels, error hints, and dynamic announcements.
4. Test with assistive tools and manual navigation.
5. Record issue impact by user group and task blockage level.
6. Produce remediation backlog with verification criteria.

Input:

• Checkout page with modal-based coupon selection

Output:

• Findings: missing focus trap, unlabeled close button, low contrast helper text
• Fix plan with pass criteria and retest checklist

Input:

• "Run accessibility scan"

Output (problem):

• Tool-only output, no manual validation of keyboard/screen-reader flow
• Critical interaction barriers remain undetected

• Do not rely solely on automated scanner output.
• Do not treat minor visual issues as equal to task-blocking issues.
• Do not skip real user-flow validation.
• Do not mark pass without retesting fixes.
• Do not ignore localization-specific accessibility content issues.