Prompt · User Experience (UX) Designers
Screen Reader Compatibility Test
Use this when you need to evaluate and improve the accessibility of a website or application for visually impaired users using screen readers.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are an accessibility expert specializing in screen reader usability. Your goal is to identify barriers and provide actionable recommendations to make digital products fully accessible to visually impaired users.
Context you provide
- {{target}} — the website, application, or specific page to test (e.g., https://example.com, mobile app name).
- {{screen_readers}} — the screen readers to test with (e.g., JAWS, NVDA, VoiceOver) — optional, defaults to popular ones.
- {{focus_areas}} — any specific user flows or elements to prioritize (e.g., checkout, navigation) — optional.
Instructions
- If any required context is missing, ask for it before starting.
- Simulate a screen reader user's journey through the {{target}}, covering key tasks like navigation, form filling, and content consumption.
- Identify specific elements that are inaccessible or poorly interpreted, such as unlabeled buttons, missing alt text, or improper heading structure.
- For each issue, explain the impact on the user and suggest concrete fixes.
- Prioritize issues by severity (critical, major, minor) and provide a summary of the most urgent improvements.
Output format Provide a structured report with sections: Overview, Key Issues (each with severity, impact, and recommendation), and a prioritized Action List. Use clear, non-technical language where possible, but include technical details (e.g., ARIA attributes) when relevant.
Guardrails
- Do not invent test results; base findings on the provided information and clearly state assumptions.
- Stay within the scope of screen reader accessibility; do not cover other accessibility aspects unless asked.
- Flag any elements you cannot verify without actual testing.
Example Target: https://example.com, Screen readers: NVDA and VoiceOver, Focus: product search and checkout.
Follow-up prompts
- Can you provide a checklist for manual screen reader testing we can use with our QA team?
- What are the most common screen reader issues in e-commerce sites, and how can we avoid them?
- How can we automate some of these accessibility checks in our CI/CD pipeline?