TanodTools
EN

HTML accessibility checker

Check pasted or saved HTML for missing alt text, labels, link names and ARIA problems with axe-core, in your browser. Its scripts never run.

Your HTML never leaves your device

Up to 5 MiB. Scripts in it never run and nothing it links to is loaded.

One HTML document at a time, up to 5 MiB and 20,000 elements, with a 60-second limit. Scripts, linked stylesheets, images and fonts are not loaded, so colour contrast and other rules that need them are not checked.

Check HTML for accessibility problems

  1. Paste the HTML of a page or part of one, or choose a saved .html file.
  2. Select Check HTML. The problems are grouped by rule, with a count, a short help line, the WCAG criteria and the elements involved.
  3. Fix what is listed, then test what the tool cannot: keyboard use, focus order, contrast and a screen reader on the live page.

Reading the report

Problems are rules that failed. Needs review lists elements axe-core could not decide, such as an ARIA value it cannot confirm, so check those by hand. Each rule shows how many elements it found and up to 50 of them, with the markup as you wrote it (for example <img src="logo.png">) and what to fix. Not checked lists what a static copy cannot show. Nothing is reported as passed.

The JSON export has the same groups, the axe-core version, the time of the check and what was removed before checking. axe-core is used unchanged under the Mozilla Public License 2.0. These tools are open source (MIT).

Questions

Does a clean report mean the page meets WCAG?

No. Automated rules catch only some problems. Keyboard use, focus order, contrast and what a screen reader announces cannot be judged from markup alone; the report lists them under Not checked.

Is it safe to check HTML I don't trust?

The HTML is parsed as inert text first. Scripts, event handlers, refreshes, base and link elements, frames and attributes such as src that load files are removed. The rest is checked in a sandboxed frame that cannot reach this page. Styles stay, because they decide what is hidden, and the frame's policy refuses any file they point to.

Which rules run?

axe-core 4.14.0 with its default rules, which cover WCAG A and AA and some best practices. Rules that need the page's real styles, layout, media or frames are off: colour contrast, link-in-text-block, target size, scrollable regions, orientation lock, frames and autoplay audio.

Is my HTML uploaded?

No. Each check runs in a fresh frame in this tab that loads axe-core from this site. No request carries your HTML or file name, and this tool stores neither. Clear removes the report; closing the tab releases the memory. The separate paid PDF check API receives a file only if you choose to call it.