Tool
Free website accessibility checker
Updated Oct 8, 2026
Accessibility Check reads a page's code for the problems that stop disabled people using it, and says what to fix.
What it checks
Up to 1 in 4 adults in the US has a disability (CDC), and many use a screen reader, a keyboard or zoom.
- Forms
Boxes with no label, so a screen reader can't say what to type.
- Links and buttons
Ones with no words (often an icon), and "click here" links.
- Zoom
Pages that stop people pinching to zoom on a phone.
- Structure
Page language and title, a main heading, headings in order, tables with headers.
- Surprises
Sound that plays by itself, and a jumbled Tab order.
Each rule matches part of WCAG (the Web Content Accessibility Guidelines, the standard US accessibility rules point to). We read the page's code, which catches many problems but not all. Color contrast, and anything added by scripts after the page loads, need the page drawn, which this check doesn't do; for contrast, try your colors in Color check. What the law asks: for businesses and for town, city and county websites.
Try it on Wrenfield's contact page, a sample website we break on purpose.
See the site here (new tab).
Check the official rules. Rules and dates change, so check them with the official sources before you rely on them: ADA.gov (the US Department of Justice), the W3C's WCAG pages and Section508.gov. PageKiwi helps you find problems and get closer to meeting the rules. It can't promise a website meets them, it isn't legal advice, and we can't take responsibility for decisions made from it.
New to this? Website accessibility: where to start, with the tools that help and what the law asks.
How to use it
- Type or paste your website's address, like YourWebsite.com. Any page works: copy it from the bar at the top of your browser.
- Press the button and leave the page open. It takes about a minute; the bar shows how far it's got.
- Your report opens by itself. The worst problems are at the top.
- Send the report's link to whoever fixes your site. They see exactly what you see, for 90 days.
- Once they've fixed things, check again to make sure.
What your results mean
- Problem
- What kind of fault it is. Every problem name, explained.
- Where
- The link, picture or words it's about, and where on the page (the menu, the footer, the page itself).
- What to tell your web person
- The fix, in words you can copy into an email. If you edit the site yourself, it's your to-do list.
- Nothing to fix
- We didn't find anything in what we checked. It doesn't promise the whole site is perfect: we check one page's code against 13 rules. Color contrast, and anything added by scripts, need the page drawn, which this check doesn't do, and some problems only a person can judge.
- Fix first
- Someone can't use that part of the page at all.
- When you can
- People can get past it, but it's slow or confusing.
When to use it
- Before you launch or redesign, when fixes cost least.
- Someone tells you they couldn't use a form or a page.
- Before you write or update your accessibility statement.
- Your web person says a problem is fixed. Check before you sign it off.
- Town, county, library or school: regularly, as you work toward the ADA rule's dates.
Why it matters
- Some of your visitors use a screen reader, the keyboard instead of a mouse, or zoom. A form box with no label or a button with no words can stop them completely.
- Most fixes help everyone: clear labels, link words that say where they go, a page that still works zoomed in.
- The ADA applies to many websites, and state and local governments have a rule with dates. Fixing what this finds gets you closer to it.
Go deeper: WCAG explained. What WCAG is, what A, AA and AAA mean, and how far automated checks go.