WCAG Web Accessibility Tools

PX to REM converter, WCAG contrast checker and accessible button generator. Free tools for developers.

How it works

It gathers the accessibility checks you repeat most while building interfaces into one page: a contrast checker that computes the ratio between text and background colours and tells you whether it passes AA or AAA, a pixel-to-rem converter for scalable typography, and accessible button examples with visible focus states and correct ARIA labels. Everything is calculated in your browser as you type, with no reloads and nothing sent to a server.

Benefits

No need to install extensions or juggle three separate tools to validate one component. Results follow WCAG 2.1 criteria, so you can justify design decisions to a client or a team. It behaves the same in light and dark mode, which lets you confirm your palette passes contrast in both themes before shipping.

Use cases

Validating a brand palette before turning it into design tokens, reviewing a form that failed an audit, switching font sizes to rem so browser zoom keeps working, or showing a junior team why light grey on white is unreadable. It also works as a quick checklist before handing off a landing page.

Tips

Target AA as your floor (4.5:1 for body text, 3:1 for large text) and keep AAA for critical content. Never rely on colour alone to signal an error: pair it with an icon and text. Define sizes in rem instead of px so users can scale text. And confirm every interactive element is reachable with the Tab key.

Frequently asked questions

Is the web accessibility kit free?

Yes, it's free and needs no sign-up. You can use every utility as many times as you like.

What contrast ratio do I need?

WCAG asks for 4.5:1 on body text and 3:1 on large text at level AA. Level AAA raises that to 7:1 and 4.5:1.

Are my colours sent to a server?

No. Every calculation runs in your browser, so no palette or value ever leaves your machine.

Why should I use rem instead of px?

Because rem scales with the user's font-size preference. With fixed px, people who need larger text can't enlarge it properly.

Does it replace a full accessibility audit?

No. It covers contrast, typography and button patterns, but a full audit also includes keyboard navigation, screen readers and the semantic structure of the whole site.

Ants in similar Web Dev projects