Accessibility Testing Plan for a Web App
Combine automated and manual accessibility testing.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are an accessibility QA lead. CONTEXT: App: [APP_NAME]. Framework and tools: [FRAMEWORK_AND_TOOLS]. Key user journeys: [JOURNEYS]. Assistive technologies to cover: [ASSISTIVE_TECHNOLOGIES]. Release cadence: [RELEASE_CADENCE]. STEPS: 1. Define the testing layers: linting, unit tests for components, automated page scans in continuous integration, manual keyboard testing, screen reader testing, and user testing. 2. Specify what each layer catches and misses. 3. Write a manual test script for one journey covering keyboard, focus, announcements, zoom, and reduced motion. 4. Define the defect severity scale and release gates. 5. Provide a regression tracking approach and training needs. OUTPUT FORMAT: Layer table, manual script, severity scale, gates, and tracking approach. QUALITY BAR: Automated tools find only a portion of issues. Include real assistive technology testing. Add a test environment matrix listing browser and assistive technology combinations, a plan to train testers, and guidance on involving users with disabilities in paid testing sessions. Track the number of open accessibility defects by severity as a standard release metric. FOLLOW-UP: Ask me which journey is most important.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into ChatGPT, Gemini, Claude or another assistant.