Assistants
Check a page's accessibility from ChatGPT or Claude — what a screen reader hears, where the keyboard gets stuck, and what an automated WCAG check finds.
On this page
Connect Accessible to ChatGPT or Claude and ask about any public web page in plain language. The assistant loads the page through Accessible and explains what it finds.
What it can do
Accessible gives the assistant four page tools. Each one checks a single public page you name.
| Tool | What it returns |
|---|---|
| Screen reader transcript | The page's accessibility tree in reading order: each element's role, its accessible name and its state, as a screen reader would move through it. |
| Keyboard walkthrough | Every stop when you press Tab from the top of the page, whether focus gets stuck in a loop, and controls that look interactive but that Tab never reaches. |
| Automated WCAG check | An axe-core check against WCAG 2.2 Level AA, with the violations by severity and the elements affected. |
| Form fields | Every field with the name a screen reader announces for it, and the barriers on each: no name, a placeholder as the only label, required fields not exposed to assistive technology, options with no group label, missing autocomplete on personal data, and errors with no message. |
All four read the page and change nothing on it. One check of a page serves all four tools for an hour, so asking a follow-up question about the same page is fast.
After you change the page, ask the assistant to check it again and compare with the earlier report. It loads the page fresh and says what changed: barriers fixed, new ones, a keyboard trap gone.
Every answer links to a full report on accessible.so that you can share with your team. Reports are deleted after 15 days.
Your own sites
If you allow access to your sites when you connect, the assistant also gets five account tools. They reach only the sites of your own organization on Accessible.
| Tool | What it does |
|---|---|
| List my sites | Your sites, with each one's open issue count, whether monitoring is on, and the date of the last scan. |
| Install monitoring | Turns monitoring on for a site and returns the snippet to add to its code, with where it goes. |
| Monitoring status | Whether monitoring is on for a site, when it last received data, and how many sessions it sampled this week. |
| List open issues | A site's open issues from scans, journeys, CI and monitoring. Issues real visitors hit most come first, then by severity. You can filter by page and severity. |
| Get issue | Everything recorded about one issue: the rule, WCAG criteria, page, selectors, markup and fix guidance. |
Install monitoring is the only one that changes anything. No tool changes or closes an issue.
Things to ask
- What would a screen reader announce on https://example.com (opens in a new tab)? Walk me through it the way a blind user would hear it.
- Can someone using only a keyboard get through https://example.com/checkout (opens in a new tab)? Tell me where they'd get stuck.
- Run an accessibility check on https://example.com (opens in a new tab) and list the fixes, most serious first.
- Here's our sign-up form: https://example.com/signup (opens in a new tab). Would a blind user know what each field is for?
- Check the form fields on https://example.com/contact (opens in a new tab). Which ones would confuse a screen reader user?
- I've fixed the labels. Check https://example.com/signup (opens in a new tab) again and tell me what changed since the last report.
- Compare what a screen reader hears on https://example.com/pricing (opens in a new tab) and https://example.com/pricing-new (opens in a new tab).
In Claude Code or Codex, the assistant can go on to fix what it finds: Check https://staging.example.com (opens in a new tab) for accessibility issues, then find and fix the unlabeled buttons in this repo. The page has to be publicly reachable.
What it does not do
- No compliance verdicts. The transcript is a simulation of what assistive technology is given, and automated checks find some barriers, not all. Nothing here certifies conformance to WCAG, the ADA, the EAA or Section 508. See Limits.
- One page at a time. It doesn't crawl a site, sign in to it, type into forms or submit them.
- Public pages only. Addresses on private networks,
localhostand pages behind a login can't be checked.
Limits
Each account can run 20 page checks a day, and each site can be checked a limited number of times a day across everyone. Limits reset at 00:00 UTC. A follow-up about a page checked in the last hour doesn't count again.
Going further
For every page on a schedule, checks on each deploy, journey testing through real tasks like checkout, and monitoring of the barriers real visitors hit, see the rest of Accessible.