Screen Reader Experience Audit of an Article Page
Check reading order, headings, links and images.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit how an article page would be read by a screen reader. Page text with headings, links, image alt text, tables and embedded media: [PAGE_CONTENT]. The reader's goal: [READER_GOAL]. Assistive technology I can test with, if any: [TOOLS_AVAILABLE]. Check heading hierarchy, landmark use, link text that makes sense out of context, meaningful alt text and decorative images, table headers, captions for media, abbreviations, and the order in which content is announced. Be clear about what the text alone cannot prove. Return findings graded red, amber or green with the quoted evidence, rewrites for the five worst alt texts and links, and a manual test plan with expected announcements. Standards and legal duties are [VERIFY] for [JURISDICTION]. Add a list of questions to ask a screen reader user if I can arrange a paid session, covering how they scan headings, how they find the main content and which parts were confusing. Offer a respectful way to invite and compensate testers.
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.