Website Accessibility Checker
Type a page address. The checker runs Google's automated accessibility test on it, names the WCAG success criterion behind every problem it finds, and adds two checks an Ontario business gets asked about.
Problems found
Two checks for Ontario sites
Check these yourself
No scanner can judge these. Google lists them for a person to test with a keyboard and a screen reader:
A full audit by me covers what no scanner sees and comes with a written list of fixes, from $299, and the fee counts toward the fixes. See the accessibility audit and compliance page.
A score of 100 is a start, not a pass
I built a test page with 18 accessibility faults I knew were there and ran the same rule set over it. It reported 8, marked 1 for a person to review and said nothing about the other 9, among them a menu the keyboard cannot reach, a focus outline that had been removed and three links that all said "click here". The whole test is in the AODA compliance report and your website.
So read the result two ways. Everything in the red list is a real barrier that a scanner can prove, and worth fixing first. An empty red list means the scanner found nothing it can measure, which is why the third box asks you to try the page with the keyboard yourself.
What it found on 36 Toronto web design studios
I ran this checker on the home page of each studio in my GTA price survey on November 17, 2026. The middle score was 96, and 11 studios scored 100.
| Problem | WCAG | Studios |
|---|---|---|
| No link to an accessibility page or statement | Ontario | 31 |
| Text too pale against its background | 1.4.3 | 21 |
| No "skip to content" link for keyboard users | 2.4.1 | 18 |
| Headings that skip a level | best practice | 12 |
| Links a screen reader announces only as "link" | 2.4.4 | 6 |
| Pictures with no text alternative | 1.1.1 | 3 |
Pale text is the one owners notice least, because it looks elegant on a big bright screen. WCAG asks for a contrast of at least 4.5 to 1 for normal text, and the red list shows each element that falls short.
Who in Ontario has to meet WCAG
Count full-time, part-time, seasonal and contract staff in Ontario. Compliance reports for 2026 are due by December 31. Being below a line does not stop a customer who uses a screen reader from leaving, which is why the checks above matter at any size.
Questions about the accessibility checker
Does a score of 100 mean my site meets WCAG?
No. It means the automated rules found nothing on that page. On my test page with 18 known faults, the same rules reported 8. Keyboard use, focus order and how a screen reader reads the page still need a person.
Which WCAG version does Ontario ask for?
WCAG 2.0 Level AA, for organizations with 50 or more employees in Ontario. Newer versions, 2.1 and 2.2, add criteria on top of 2.0, so a site that meets 2.1 AA also meets 2.0 AA.
Is this the same as the Lighthouse accessibility score?
Yes. My server sends the page to Google PageSpeed Insights, which runs Lighthouse on a phone setting, and Lighthouse uses the axe-core rules. The checker then names the WCAG criterion behind each rule and adds the accessibility link and skip link checks.
Does it check my whole website?
One page per check. Problems in a header or footer repeat on every page, so checking the home page finds those; forms and tables need their own pages checked. You can run 12 new checks an hour.
Does the checker change anything on my site?
No. It reads the page the way a visitor's browser does and stores nothing apart from the saved result, kept for 30 minutes so a refresh is instant.
See how this site handles it
My own accessibility statement lists what was tested on these pages and how to report a barrier. The free website audit adds speed, SEO, security and email checks to a few of these.