Designers
ToolsDocsProAll the Possibles

All 141 tools / Accessibility checks

Read a page as a linear script of what a screen reader would announce, with problems flagged inline.

Screen reader scriptFreeFor developers and designers

30/day

free runs a day, no sign-in.

Before: what you give it

The example input, as typed in. You give it a page address.

<!doctype html><html lang="en"><head><title>Join the studio</title></head><body><header><nav aria-label="Main"><a href="/work">Work</a><a href="/about">About</a></nav></header><main><h1>Join the studio</h1><p>We hire twice a year.</p><h3>Roles</h3><ul><li><a href="/jobs/1">Read more</a></li><li><a href="/jobs/2">Senior designer</a></li></ul><form><label for="e">Email</label><input id="e" type="email" required><input type="text" placeholder="Your name"><button><img src="x.svg" alt=""></button></form><img src="team.jpg"></main><nav><a href="/privacy">Privacy</a></nav></body></html>

After: what comes back

The first lines of a real run on that input. Nothing here is edited by hand.

Screen reader script (approximation)
Source: pasted HTML, title "Join the studio", language en
This is a linear approximation built from the markup's accessibility tree. It is not a recording of NVDA, JAWS or VoiceOver, which differ in wording, verbosity settings and how they treat CSS, script and live regions.

01  banner landmark
02    navigation landmark "Main"
03      link: "Work"
04      link: "About"
05  main landmark
06    heading level 1: "Join the studio"
07    text: "We hire twice a year."
08    heading level 3: "Roles"
        PROBLEM: skipped heading level (h1 to h3)
09    list, 2 items
... full output on the tool page

What you get

Numbered lines for landmarks, headings, links, fields and images, with a PROBLEM note under each fault

What it cannot do

An approximation from static markup, not a recording of NVDA, JAWS or VoiceOver; it runs no script and applies no CSS, and stops at 250 nodes.

Who it is for

  • Developers
  • Designers

Free and Pro

Free30 runs a day per IP address, up to 200,000 characters a run.
ProNo daily limit, 300 requests a minute, up to 200,000 characters a run.

What each plan includes

Use it from your assistant

The tool is called screen_reader_script. Connect the server once, then ask for it by name or just describe the job. Install steps for each app.

claude mcp add --transport http designers https://designers.allthepossibles.com/mcp
curl -X POST https://designers.allthepossibles.com/api/screen-reader-script -H 'content-type: application/json' -d '{"html":"<!doctype html><html lang=\"en\"><head><title>Join the studio</title></head><body><header><nav aria-label=\"Main\"><a href=\"/work\">Work</a><a href=\"/about\">About</a></nav></header><main><h1>Join the studio</h1><p>We hire twice a year.</p><h3>Roles</h3><ul><li><a href=\"/jobs/1\">Read more</a></li><li><a href=\"/jobs/2\">Senior designer</a></li></ul><form><label for=\"e\">Email</label><input id=\"e\" type=\"email\" required><input type=\"text\" placeholder=\"Your name\"><button><img src=\"x.svg\" alt=\"\"></button></form><img src=\"team.jpg\"></main><nav><a href=\"/privacy\">Privacy</a></nav></body></html>"}'

Try it here

The form starts with the same example input, so you can run it first and then swap in your own.

More in accessibility checks

All accessibility checks tools