MyClawn WCAG Audit › Accessibility checker
Website accessibility checker: what fails on your page, and how to fix it
Paste a page address and the checker loads it in a real browser, tests it against WCAG 2.2 Level A and AA rules, and shows each failure on a screenshot of your page with the fix. This page explains what it tests, what no checker can test, and how to use the result.
What the check does
- Opens your page in a real browser, with scripts running, the way a visitor gets it. Checking only the raw HTML misses menus, pop-ups and anything a script builds.
- Runs the WCAG rule set with an open-source rule engine: text alternatives, form labels, names of buttons and links, heading structure, page language, ARIA used correctly, and more.
- Measures contrast between text and what is actually behind it on the rendered page, and reports the ratio.
- Walks the page with the Tab key to see whether focus is visible and can reach the controls.
- Shows you the result: how many problems, which criteria fail, where each one is on a screenshot of your page, and the corrected code for the first ones.
One page, about a minute, no signup: check your site.
What no automatic checker can tell you
A rule can see that an image has alt text. It cannot see that the text says 'image123'. Published estimates of what automated rules catch range from about a quarter of the WCAG criteria to 30 to 40 percent of issues. The rest needs a browser being driven like a person would drive it, or a person.
| Question | Rule check | Our full audit | Person with a screen reader |
|---|---|---|---|
| Is there a label, an alt attribute, enough contrast? | Yes | Yes | Yes |
| Can every control be reached and used by keyboard, with no trap? | No | Yes, by a scripted Tab walk | Yes |
| Does the page survive 200% zoom and a 320px screen? | No | Yes | Yes |
| Is the alt text or link text meaningful? | No | Reviewed, with a suggested rewrite | Yes |
| Does a complex widget make sense when read aloud? | No | Listed as a human check, with steps | Yes |
Paste your address and see what fails WCAG 2.2 AA, where, and the code that fixes it. Starter $39/mo · Pro $129/mo. Refund within 14 days if it misses.
Check my siteHow to use the result
- Fix by pattern, not by instance. Eleven low-contrast links are usually one CSS colour. The result groups failures so you see that.
- Start with what blocks people: unlabeled form fields, controls with no name, keyboard traps. Then contrast and alt text.
- Fix the template. A header or footer failure repeats on every page; fix it once.
- Check again after the change, and keep the dated results. That record is what owners in our data ask auditors for: proof that the work was done.
The free check covers one page. The monthly audit covers up to 10 pages on Starter and 25 on Pro, writes every fix, and retests each month.
Other checkers worth knowing
Free tools are good for a developer's daily work, and we would rather you use them than nothing:
- WAVE by WebAIM: a browser extension that marks errors on the page.
- Accessibility Insights by Microsoft: automated checks plus a guided manual assessment.
- The W3C's evaluation tools list: a catalogue of checkers for web pages, PDFs and more.
- Built-in checkers in Word, PowerPoint and Acrobat for documents, which our audit does not cover.
What they leave to you is the work around the scan: choosing pages, driving the keyboard tests, writing the fixes for your code, keeping the record. That is the part we sell.
Questions
Is the accessibility check free?
The check of one page is free, with no signup. The full audit of your key pages with all fixes, an accessibility statement and a monthly retest starts at $39 a month.
Does a clean scan mean my site is accessible?
No. It means the rules a machine can decide found nothing on that page. Keyboard use, zoom, meaningful alt text and screen-reader behaviour still have to be tested.
Which standard does the checker test against?
WCAG 2.2 Level A and AA, which includes the requirements of WCAG 2.1 AA and 2.0 AA.
Does it work for Shopify, WordPress, Wix or Squarespace sites?
Yes. It tests the page as delivered to the browser, whatever built it. The full audit adds notes on where to apply each fix on those platforms.
Can it check PDFs or a page behind a login?
No. It checks public web pages. For PDFs use Acrobat's checker or PAC; pages behind a login are outside the audit, and we never ask for passwords.
Paste your address and see what fails WCAG 2.2 AA, where, and the code that fixes it. Starter $39/mo · Pro $129/mo. Refund within 14 days if it misses.
Check my siteMore about WCAG Audit
Sources (checked 2026-11-11): www.w3.org/WAI/test-evaluate/tools/list/ · accessible.org/wcag-audit-questions/ · testpros.com/accessibility/wcag-audit/ · accessibility.huit.harvard.edu/auto-tools-testing