Focused checks, useful next steps

HTML Accessibility Checker

Find common accessibility issues in the HTML you provide. Review labels, image alternatives, links and buttons, then jump to the source and export your findings.

Start with your markup

Find issues in the source.

Paste HTML or upload a UTF-8 file, up to 512 KiB and 5,000 elements. Include any labels referenced by ID. Uploaded files replace the input.

Your HTML stays in this browser. It is read as text; scripts, images, stylesheets and embedded pages are never run or loaded by the checker.

How to use the result

Start with the markup. Continue with people.

Paste HTML or upload a UTF-8 file. Checks examine supplied markup for common labeling, image-alternative, link, button and ID issues. Findings include source locations and separate likely source issues from items needing judgment.

This does not fetch a website, run scripts, inspect CSS or reproduce a browser’s full accessibility tree. Name checks are approximations. Hidden-state and labeling behavior can differ in the live page, especially with dynamic components or CSS. A result with no detected issues is not an accessibility pass or WCAG conformance claim.

Continue with keyboard navigation, visible focus, screen-reader checks, zoom and reflow, color contrast and a review of whether labels and image descriptions are meaningful. Use the Color Contrast Checker for a focused color-pair check.

Processing stays in this browser tab. HTML is read as inert text and is not executed, fetched, uploaded or saved by the tool. Limits are 512 KiB of UTF-8 input and 5,000 elements. The interface shows up to 200 matching findings; exports contain the complete bounded report.

Form & Intake Planner · Markdown & HTML Converter

W3C: evaluating accessibility ↗ · How these tools work