HTML is parsed as an inert document with DOMParser. Visible text, label relations, aria-labelledby, aria-label, alt, and title are reviewed in accessible-name priority order.
334
Code & file security
ARIA Accessible-Name Inventory
Inspects pasted HTML without executing it and reports visible text, aria-label, aria-labelledby, label[for], alt, and title sources in priority order. The result is not an assistive-technology test; dynamic states still require accessibility-tree review.
✓ Free✓ No account✓ In-browser
QUICK ANSWER
What does this tool do?
Inventory buttons, links, and form controls with their accessible names and find unnamed controls.
APPLICATION AND DECISION GUIDE
ARIA Accessible-Name Inventory: method and usage
Inspects pasted HTML without executing it and reports visible text, aria-label, aria-labelledby, label[for], alt, and title sources in priority order. The result is not an assistive-technology test; dynamic states still require accessibility-tree review.
an HTML fragment containing buttons, links, images, and form controls that needs no script execution Confirm the shape first with a small example containing no personal data.
an inventory with element type, selector hint, computed name source, and unnamed or suspicious-control status
Practical steps
- Load the example or fill the clearly labelled fields for your scenario.
- Run the check on-device and review metrics, warnings, and recommended corrections together.
- Validate the result in the real target environment and record its assumptions.
focusing every interactive element by keyboard and comparing name, role, state, and error message in a real screen reader and accessibility tree
A static HTML inventory cannot fully observe CSS-hidden text, Shadow DOM, runtime states, or screen-reader behaviour; it is not a WCAG conformance report.
Suitable use cases
- Pre-release form audit
- Icon-button review
- Preparing WCAG task tests
Worked decision record
Practical scenario: Pre-release form audit. Inventory buttons, links, and form controls with their accessible names and find unnamed controls.
Scan a small HTML sample containing a text link, an icon button with `aria-label`, an email field with an associated `label`, and a second unnamed icon button.
Acceptance record: focusing every interactive element by keyboard and comparing name, role, state, and error message in a real screen reader and accessibility tree. Keep the result-card metrics and warnings together with the retained example.
Do not publish in this state: A static HTML inventory cannot fully observe CSS-hidden text, Shadow DOM, runtime states, or screen-reader behaviour; it is not a WCAG conformance report.
LEARN THE WORKFLOW
Guides for this tool
Mobile UI Quality: Layers, Touch Targets, and Accessible Names
Accept headers, menus, modals, and tool actions through overlap, touch, keyboard, and screen-reader tasks—not appearance alone.
Read guide →Accessible HTML Publishing: Language, Headings, Forms, and Accessible Names
Go beyond visual polish and validate language, heading flow, control names, keyboard use, and errors through real tasks.
Read guide →ABOUT THIS TOOL
Frequently asked questions
What input does ARIA Accessible-Name Inventory accept?+
an HTML fragment containing buttons, links, images, and form controls that needs no script execution Scan a small HTML sample containing a text link, an icon button with `aria-label`, an email field with an associated `label`, and a second unnamed icon button.
What does ARIA Accessible-Name Inventory return?+
an inventory with element type, selector hint, computed name source, and unnamed or suspicious-control status Acceptance record: focusing every interactive element by keyboard and comparing name, role, state, and error message in a real screen reader and accessibility tree. Keep the result-card metrics and warnings together with the retained example.
How should I validate ARIA Accessible-Name Inventory output?+
focusing every interactive element by keyboard and comparing name, role, state, and error message in a real screen reader and accessibility tree Do not publish in this state: A static HTML inventory cannot fully observe CSS-hidden text, Shadow DOM, runtime states, or screen-reader behaviour; it is not a WCAG conformance report.
Does ARIA Accessible-Name Inventory send or store input on a server?+
Tool input is processed in the active tab. Saving to the Workstation or transferring to another tool is a separate choice. Consider browser extensions and shared devices separately; the privacy page explains advertising and network connections.