Optimize web interfaces for JAWS, NVDA, VoiceOver, and TalkBack compatibility. Resolve screen reader announcement issues, reading order problems, and assistive technology bugs.
The Screen Reader Compatibility Engineer is an AI assistant built for developers and accessibility specialists who need to ensure their web interfaces work correctly across the major screen readers used worldwide: JAWS, NVDA, VoiceOver on macOS and iOS, TalkBack on Android, and Narrator on Windows. Screen reader compatibility is more nuanced than WCAG conformance — a page can technically pass all success criteria and still produce a confusing or broken experience in a specific screen reader and browser combination.
This assistant helps you understand and resolve the real-world inconsistencies between screen reader behavior and web standards. It covers announcement behavior for dynamic content, the specific quirks of how different screen readers handle ARIA live regions, the browser-screen reader combinations with known support issues, and the markup patterns that reliably produce correct announcements across the major AT stack combinations.
When you describe an issue — an announcement that fires at the wrong time, an element that reads incorrect text, a component that is completely silent in VoiceOver but works in NVDA — the assistant helps diagnose the likely cause and suggests remediation. It draws on knowledge of the accessibility tree, browser accessibility API implementations (MSAA/IAccessible2, ATK/AT-SPI, AX API), and the mapping between HTML/ARIA semantics and what screen readers actually announce.
This assistant is particularly valuable during screen reader testing phases, when a bug has been identified but its cause is unclear. It helps interpret screen reader behavior, suggests markup changes to test, and explains why a specific fix is likely to work. It also helps teams build screen reader test plans, identify the highest-priority browser-AT combinations to test, and write screen reader testing procedures for QA teams unfamiliar with assistive technology.
Expected outputs include diagnostic analysis, annotated code fixes, screen reader test scripts, browser-AT combination recommendations, and explanations of accessibility tree behavior suitable for both developers and QA engineers.
Sign in with Google to access expert-crafted prompts. New users get 10 free credits.
Sign in to unlock