Designers

All 141 tools / Accessibility checks

Scan one page's HTML for accessibility problems and see the WCAG criterion behind each one.

Page accessibilityFreeFor developers and designers

20/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.

https://allthepossibles.com

After: what comes back

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

"All the Possibles: tools that check themselves before they ship": 13 headings, 0 images, 21 links, 3 buttons, 1 form controls
0 high, 0 medium, 0 low

No static findings.

Static HTML only. It does not render the page, so it cannot test colour contrast (use the contrast tool), focus order, keyboard traps, ARIA behaviour in script-built interfaces, captions, or reading order. Passing this audit does not mean a page is accessible; automated tools find roughly a third of WCAG failures.

What you get

Issues ranked high, medium and low, each with its WCAG criterion and an example element

What it cannot do

Reads static HTML only: it cannot test contrast, focus order, keyboard traps or script-built interfaces.

Who it is for

  • Developers
  • Designers

Free and Pro

Free20 runs a day per IP address.
ProNo daily limit, 300 requests a minute.

What each plan includes

Use it from your assistant

The tool is called audit_page_accessibility. 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/a11y-page -H 'content-type: application/json' -d '{"url":"https://allthepossibles.com"}'

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