UIX
Sign in Start free

Free tool, no sign-in

Check your site’s accessibility

Paste a page address. Get every contrast failure and accessibility problem, each with a fix.

Example

Loading an example result…

How to read this

What the result means.

It checks one web page against the parts of WCAG 2.2 AA a machine can test: text contrast, image alt text, form labels, link and button names, headings, page language, zoom and tap targets. Every problem comes with what it means for people and how to fix it, in plain words.

Contrast ratio
How much the text stands out from what’s behind it, from 1:1 (invisible) to 21:1 (black on white). Pass: 4.5:1 or more for normal text, 3:1 or more for large text (24px, or 18.66px bold). Buttons, field borders and icons need 3:1 too; this check measures text only.
Fix color
A color with the same hue as your text, made lighter or darker until it passes. Swap it in and the pair meets AA.
Must fix
Fails a WCAG 2.2 AA rule: missing alt text, a field with no label, a control with no name, no page language or title, zoom turned off, or text below the contrast minimum.
Check
Probably a problem, but a person should look: headings that skip a level, a missing h1, text on images, or tap targets under 24 × 24 px.
Tap targets
Pass: at least 24 × 24 px at phone width (WCAG 2.2 AA). 44 × 44 px is easier for everyone. Links inside a sentence don’t count.
Places, elements read
Places is how many bits of text share one problem. Elements read is how much of the page we looked at (up to 5,000).
Light mode, dark mode
Next to the site name. The check asks the page for its light look; if your browser passes your dark-mode setting through, you get the dark result instead, and the label says so.

How it works

Three steps, all in your browser.

Your page is fetched once, then measured here. The report isn’t saved anywhere.

What you get back

Two lines of a contrast report in a small window: one failing pair at 2.6 to 1 and its fix at 5.1 to 1, then an AA pass badge.

  1. Paste one page addressYour home page, pricing page or a blog post. Each page is checked on its own.
  2. Press Check pageIt takes 5 to 15 seconds. The page is drawn in your browser with its own CSS and fonts, without running its scripts.
  3. Fix, then copy the listStart with “Must fix”. Copy or download the list as Markdown for your team or your issue tracker.

Questions

Questions people ask.

Short answers about this tool, your data and what it can’t see.

Ask us anything
Is it free?

Yes. Without an account you see the summary, every kind of problem and the first three examples of each, and you can copy or download that. A free UIX account (no card) shows every example, in the page and in the copy or download.

Is this a full WCAG audit?

No. Automated checks find a lot of real problems, contrast most of all, but not all of them. Keyboard use, focus order and how a screen reader actually reads the page need a person to test. Treat a clean result as a good start, not a pass.

What is the example result?

The W3C’s “CityLights” demo page, which the W3C built on purpose to show common accessibility mistakes. Your own result replaces it when you run a check.

How is the fix color picked?

With the same contrast engine UIX uses for every design system: it keeps the hue of your text color and makes it lighter or darker until it reaches the contrast it needs.

Why are some pages almost empty?

Pages that build their content with JavaScript after loading show up mostly empty, because the check doesn’t run the page’s scripts (that keeps it safe). Try a page that shows its content without JavaScript, such as a blog post or a docs page.

Do you store my site or the report?

We fetch the page’s HTML once (cached for up to an hour so a second check is quick). Everything else runs in your browser, and the report isn’t saved anywhere.

Start with one color.

Free to start. Your designers, your developers and your AI agent get one system to follow.

Start free Get the Figma plugin