Create intermediate Works with: Any AI

Accessibility Testing Plan for a Web App

Table output

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.

Combine automated and manual accessibility testing for a web application. App description and main user journeys: [APP_AND_JOURNEYS]. Stack and release process: [STACK_AND_RELEASES]. Target standard: [STANDARD]. Team and budget: [TEAM_AND_BUDGET].

Tables:
1. Coverage: Layer | What is tested | Tool or method | Frequency | Owner. Include linting in the editor, component tests with an automated checker, end-to-end checks on key pages, manual keyboard testing, screen reader testing on two combinations, zoom and reflow, color and contrast, reduced motion, and user testing with disabled people.
2. Journeys: Journey | Steps | Keyboard-only result | Screen reader result | Zoom 200 percent result | Issues.
3. Manual test script: 15 numbered checks any team member can run in 30 minutes.
4. Defect handling: severity levels, response times, and who fixes; a policy that serious issues block release.
5. Metrics: open defects by severity, time to fix, regressions per release, and coverage of journeys.
6. Training and tooling needs.

Explain what automated tools can and cannot find (a minority of issues), include a pull request checklist for developers, and a report template. Mention that legal conformance claims need a specialist's judgement.

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 Any AI or another assistant.

Related prompts