Test Web App Accessibility with Screen Readers

This skill is a practical guide to testing web applications with screen readers for comprehensive accessibility validation. It's scoped to validating screen reader compatibility, testing ARIA implementations, debugging assistive technology issues, verifying form accessibility, testing dynamic content announcements, and ensuring navigation accessibility. Its working process is to clarify goals, constraints, and required inputs first, apply relevant best practices and validate outcomes, then provide actionable steps and verification - pointing to a companion resources/implementation-playbook.md file when detailed examples or patterns are needed beyond the core guidance.

Use it specifically for screen reader testing tasks - ARIA validation, assistive technology debugging, form and dynamic-content accessibility, navigation checks. It explicitly steps back when the task is unrelated to screen reader testing or needs a different domain or tool outside this scope, rather than stretching to cover adjacent accessibility work it isn't scoped for.

Input is the specific accessibility validation task (ARIA implementation, form, dynamic content, or navigation to test) and any environment-specific constraints. Output is actionable testing steps and verification guidance, with a companion implementation playbook available for more detailed patterns and examples.

Developers and QA testers validating screen reader compatibility and ARIA implementations who need a structured testing approach rather than ad hoc manual checks - with the explicit caveat that its output isn't a substitute for environment-specific validation or expert review, and it stops to ask when required inputs, permissions, safety boundaries, or success criteria are missing.