How to use HTML Accessibility Hints Checker
- Paste a section or a whole page into the Page HTML box.
- The table appears as soon as the HTML is in the box.
- Read each row: the check, the number of matches and what to do about it.
- Open the sample under a check in the text result, confirm it in the browser, then fix the ones that are real.
Example: HTML Accessibility Hints Checker
Check a small market page before it is published.
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.
Supported inputs and limits
Where your input is processed
This tool processes your input in this browser. Your text and files are not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.
What a markup hint can and cannot tell you
The checks here look at elements and attributes in the HTML you paste. They can prove that an image has no alt attribute, that a link holds no text, or that two elements share an id. They cannot prove that alt text describes an image well, that a label reads clearly, that colour contrast is enough, or that focus moves in a sensible order. Treat a finding as a prompt to look at one element on the real page, and a clear row as the absence of that one problem in the markup you gave the reader. The Web Content Accessibility Guidelines describe the underlying requirements, and a full review needs a browser plus, for anything formal, help from people who use assistive technology.
W3C Web Accessibility Initiative, Images tutorial
Questions about HTML Accessibility Hints Checker
Does a clear result mean my page is accessible?
No. The page runs nine checks over the markup you paste and reports nothing else. Contrast, focus, keyboard order, motion, zoom and the way a screen reader reads the page need a browser and a person, and a serious audit also involves people who use assistive technology.
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.