How to use HTML Accessibility Hints Checker
- Paste a section or whole page, or clear the pasted HTML and select one UTF-8 HTML file. The checker does not load the page or its assets.
- If useful, enable Also check a supplied color pair and choose its opaque text/background colors. These are entered values, not detected page styles.
- Read the updated counts, Not checked rows and up to three element samples per markup check. A zero count is not an accessibility verdict.
- Confirm each relevant finding in the real page, including valid wrapping labels and decorative images. Download the report if needed, then test keyboard use, zoom and assistive-technology behavior separately.
Example: HTML Accessibility Hints Checker
Find six static-markup hints in the market-page example while retaining its explicitly empty decorative alt text.
Options
- Hints, not a verdict
- Each row names something that can be seen in markup and shows the matching element so you can judge it. A row with a count of zero means only that this reader found nothing in that category for the HTML you pasted.
- Samples
- Up to three matching elements are shown for each check as trimmed text. Use them to find the element in your template, then confirm the fix on the real page with a keyboard and a screen reader where you can.
- Local HTML file (optional)
- One UTF-8 file up to 200,000 bytes. Clear pasted HTML first.
- Page HTML
- Paste a section or a whole page, up to 200,000 characters. The checks read the markup in this browser and never load the page.
- Also check a supplied color pair
- Checks opaque colors you select. It does not inspect computed styles, gradients, images or the actual page.
Supported inputs and limits
- Pasted HTML up to 200,000 characters or one UTF-8 file up to 200,000 bytes; only the first 4,000 parsed tags and three samples per check are reported.
- Nine markup checks form a bounded subset.
- Wrapping-label relationships, computed accessible names and rendered visibility are not fully evaluated.
- The optional six-digit opaque hexadecimal pair uses WCAG luminance thresholds, not actual page styles, gradients or images.
- No complete WCAG verdict, keyboard audit, focus-order check or screen-reader session.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
What a markup hint can and cannot tell you
A markup check can find a missing alt attribute or repeated id without establishing whether the image description or surrounding interface is useful. A supplied section can also omit a page title, language attribute or associated label that exists elsewhere. Read Not checked and sample rows in that context. The optional contrast ratio answers a separate question about entered colors; it does not inspect their use on the page. Confirm the actual experience with browser and assistive-technology testing.
Questions about HTML Accessibility Hints Checker
Does a clear result mean my page is accessible?
No. The nine checks cover only supplied markup. The optional contrast calculation covers only the two opaque colors you enter. Actual styles, keyboard/focus behavior, zoom, motion and assistive-technology use still need review on the rendered page.
Why is my input reported when I wrap it in a label?
The reader matches a label that points at an input with a for attribute. A label that wraps its input is valid and common, but this reader cannot see that pairing, so it lists the input for you to confirm by hand.
Why is my layout table reported?
A table with no th cells looks the same to the reader whether it holds data or only lays out content. The row is a prompt to say which one it is. A data table needs header cells, and a layout table is better replaced with a grid or flex layout.
What is wrong with a positive tabindex value?
It pulls the element out of the natural page order, so a keyboard user reaches it before elements that appear earlier on the page. The reader lists tabindex values greater than zero; tabindex="0" and tabindex="-1" are not listed.