Website Accessibility Checker

A website accessibility checker scans a page for barriers that stop people using screen readers, keyboards or zoom, and maps each one to WCAG 2.2. Paste a page's HTML below to find missing alt text, unlabeled fields, empty buttons and links, heading problems, disabled zoom and low contrast, with a fix for each. It runs in your browser, so nothing is uploaded.

Paste your HTML

A full page (from View Source or DevTools > Copy outerHTML) gets every check. A snippet skips the whole-page checks (language, title, h1, main).

What automated checks miss

  • Checks the HTML you paste, not CSS files: contrast is checked only where text and background colors are set inline.
  • Event handlers attached by JavaScript frameworks (React, Vue) are not visible in HTML, so mouse-only clicks there are not detected.
  • It cannot judge whether alt text or labels are meaningful, or test focus visibility, animations and captions. Test those by hand.

The 19 checks and the WCAG rule behind each

Image has no alt attribute

WCAG 1.1.1 Non-text Content (A)

Add alt text that says what the image shows or does. Use alt="" only for purely decorative images.

Form field has no label

WCAG 4.1.2 Name, Role, Value (A)

Add a <label for="id">, wrap the field in a <label>, or add aria-label / aria-labelledby.

Button has no accessible name

WCAG 4.1.2 Name, Role, Value (A)

Add visible text, or aria-label="Close" (or similar) on icon-only buttons.

Link has no accessible name

WCAG 2.4.4 Link Purpose (A)

Put descriptive text inside the link, or aria-label on icon links; give linked images alt text.

Link text is vague

WCAG 2.4.4 Link Purpose (A)

Say where the link goes: "Read the pricing guide" instead of "Read more".

Page has no lang attribute

WCAG 3.1.1 Language of Page (A)

Add the language to the root element, for example <html lang="en">.

Page has no title

WCAG 2.4.2 Page Titled (A)

Add a unique, descriptive <title> inside <head>.

Heading is empty

WCAG 2.4.6 Headings and Labels (AA)

Add text to the heading or remove it.

Heading level skipped

WCAG 1.3.1 Info and Relationships (A)

Go down one level at a time. Style headings with CSS instead of picking a level for its size.

Page has no <h1>

WCAG Best practice (1.3.1, 2.4.6)

Give every page one <h1> that names the page.

Page has no <main> landmark

WCAG Best practice (2.4.1 Bypass Blocks)

Wrap the primary content in <main>, and add a "Skip to content" link.

Zoom is disabled

WCAG 1.4.4 Resize Text (AA)

Use <meta name="viewport" content="width=device-width, initial-scale=1"> with no zoom limits.

Clickable element is not keyboard accessible

WCAG 2.1.1 Keyboard (A)

Use a real <button> or <a href>. If you cannot, add role="button", tabindex="0" and a key handler.

Positive tabindex

WCAG 2.4.3 Focus Order (A)

Use tabindex="0" (or none) and fix the order in the HTML instead.

Focusable element is hidden from screen readers

WCAG 4.1.2 Name, Role, Value (A)

Remove aria-hidden, or take the element out of the Tab order (tabindex="-1", or disabled).

Frame has no title

WCAG 4.1.2 Name, Role, Value (A)

Add a title that says what the frame contains, for example title="Product demo video".

Label or ARIA reference points to a missing id

WCAG 1.3.1 Info and Relationships (A)

Fix the id, or add the element it should point to.

Duplicate id

WCAG Best practice (breaks labels and ARIA)

Make every id on the page unique.

Low text contrast

WCAG 1.4.3 Contrast (Minimum) (AA)

Darken the text or lighten the background until the ratio passes.

Accessibility checker FAQ

What does a website accessibility checker test?

It looks for barriers that stop disabled people from using a page: images without alt text, form fields without labels, buttons and links with no name, missing page language and title, skipped heading levels, disabled zoom, mouse-only click handlers, and low text contrast. Each problem is mapped to the WCAG success criterion it fails.

Is this accessibility checker free and private?

Yes. It is free with no signup, and the HTML you paste is checked entirely in your browser. Nothing is uploaded or stored, so you can check staging pages and internal tools safely.

Can an automated checker make my site WCAG or ADA compliant?

No. Automated tools catch only some WCAG issues; judgment calls such as whether alt text is accurate need a person. You still need to test with a keyboard (Tab, Shift+Tab, Enter, Escape), zoom to 200%, try a screen reader such as VoiceOver or NVDA, and check that alt text and labels actually make sense. Use the checker to clear the obvious problems first.

How do I check a whole website, not just one snippet?

Open the page, press Ctrl+U (Cmd+Option+U on a Mac) to view its source, select all and paste it here. For pages built with JavaScript, open DevTools, right-click the <html> element, choose Copy > Copy outerHTML, and paste that instead so you check what the browser actually rendered. Repeat for each page template.

What is the WCAG contrast ratio requirement?

WCAG 2.2 level AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text (24px, or 18.66px bold). This tool checks colors set in inline styles; for colors from stylesheets, test the pair in our Color Contrast Checker.

Related free tools

Let an AI assistant run the checks for you

NitroClaw hosts a dedicated OpenClaw assistant you can message on Telegram, WhatsApp or Discord to review pages, draft alt text and fix markup. No server or setup needed.

Explore NitroClaw