Accessibility checker

What does the accessibility checker test?

It scans one web page against WCAG 2.2 at level AA: colour contrast, text alternatives for images, names and labels on links, buttons and form fields, heading structure, ARIA and tap target size. Every issue it finds comes with a plain-English fix.

How does the scan work?

Google PageSpeed Insights loads your page in a real Chrome browser and runs Lighthouse's accessibility audit, which is built on axe-core. The checker turns that result into its report. Only the address you enter is scanned.

Is it free?

Yes. It is free to use, with no account to create.

Can it check a page behind a login, or a site on my own computer?

No. Google has to be able to load the page, so it must be reachable on the public web. Password-protected staging sites, intranets and localhost cannot be scanned.

If the scan passes, is my site WCAG compliant?

Not on its own. No automated checker can confirm compliance, because some criteria need a person to judge them: whether alt text actually describes the image, or whether every part of the page works with a keyboard alone. The report lists those checks for you to do by hand.

What is the difference between WCAG AA and AAA?

AA is the level most accessibility laws and policies ask for; AAA is stricter. For colour contrast, AA needs a ratio of at least 4.5:1 for normal text and 3:1 for large text, and AAA needs 7:1 and 4.5:1.

How do I check whether two colours have enough contrast?

Use the contrast checker . Enter a text colour and a background, and it shows whether the pair passes AA and AAA for normal text, large text and interface parts. If it fails, it suggests the nearest colour that passes.

Can it help me build an accessible colour palette?

Yes. The palette generator turns your brand colours into 11-step scales and accessible light and dark themes, with every text and background pair checked against AA or AAA. Copy it to Figma as editable swatches, or as CSS, Tailwind or design tokens.

Rheed MacPherson, founder of Signal Studio

Can’t find your answer?

Book a Discovery call and ask us directly.

Or email hello@signalstudio.co.nz

ACCESSIBILITY-CHECKER.MD ACCESSIBILITY-CHECKER

# Accessibility Checker

Check any web page against WCAG 2.2 AA for free: colour contrast, alt text, labels, headings and more, with a plain-English fix for each issue.

## What it does

Scans one web page against WCAG 2.2: colour contrast, text alternatives, names and labels, headings, ARIA, tap target size and more. Every issue comes with a plain-English fix, and the checks a machine cannot decide are listed to do by hand.

## How it works

The page is loaded in a real browser by Google PageSpeed Insights and checked with Lighthouse's accessibility audit, which runs axe-core. Only the address entered is scanned.

## Palette generator

Turns brand colours into 11-step scales and accessible light and dark themes, with every text and background pair checked against WCAG AA or AAA. Copy the palette to Figma as editable swatches, or as CSS, Tailwind or design tokens.

## Contrast checker

Check any two colours for WCAG AA and AAA, for normal text, large text and interface parts, and get the nearest text or background colour that passes.

## What does the accessibility checker test?

It scans one web page against WCAG 2.2 at level AA: colour contrast, text alternatives for images, names and labels on links, buttons and form fields, heading structure, ARIA and tap target size. Every issue it finds comes with a plain-English fix.

## How does the scan work?

Google PageSpeed Insights loads your page in a real Chrome browser and runs Lighthouse's accessibility audit, which is built on axe-core. The checker turns that result into its report. Only the address you enter is scanned.

## Is it free?

Yes. It is free to use, with no account to create.

## Can it check a page behind a login, or a site on my own computer?

No. Google has to be able to load the page, so it must be reachable on the public web. Password-protected staging sites, intranets and localhost cannot be scanned.

## If the scan passes, is my site WCAG compliant?

Not on its own. No automated checker can confirm compliance, because some criteria need a person to judge them: whether alt text actually describes the image, or whether every part of the page works with a keyboard alone. The report lists those checks for you to do by hand.

## What is the difference between WCAG AA and AAA?

AA is the level most accessibility laws and policies ask for; AAA is stricter. For colour contrast, AA needs a ratio of at least 4.5:1 for normal text and 3:1 for large text, and AAA needs 7:1 and 4.5:1.

## How do I check whether two colours have enough contrast?

Use the [contrast checker](/tools/accessibility-checker/contrast/). Enter a text colour and a background, and it shows whether the pair passes AA and AAA for normal text, large text and interface parts. If it fails, it suggests the nearest colour that passes.

## Can it help me build an accessible colour palette?

Yes. The [palette generator](/tools/accessibility-checker/palette/) turns your brand colours into 11-step scales and accessible light and dark themes, with every text and background pair checked against AA or AAA. Copy it to Figma as editable swatches, or as CSS, Tailwind or design tokens.