Processing boundary
Input is processed only in the active browser tab's memory and is not sent to a ByteQuant server.
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. ARIA Accessible-Name Inventory limitation: 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.
- Input
- For ARIA Accessible-Name Inventory, provide an HTML fragment containing buttons, links, images, and form controls that needs no script execution. The requested outcome is to inventory buttons, links, and form controls with their accessible names and find unnamed controls.
- Output
- When ARIA Accessible-Name Inventory finishes, it returns an inventory with element type, selector hint, computed name source, and unnamed or suspicious-control status, organised around the goal to inventory buttons, links, and form controls with their accessible names and find unnamed controls.
- Method
- ARIA Accessible-Name Inventory uses this disclosed method to inventory buttons, links, and form controls with their accessible names and find unnamed controls: 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.
- Verification
- Before accepting a ARIA Accessible-Name Inventory result, complete focusing every interactive element by keyboard and comparing name, role, state, and error message in a real screen reader and accessibility tree; the evidence should support the goal to inventory buttons, links, and form controls with their accessible names and find unnamed controls.
TOOL-SPECIFIC RUN PLAN
Go to the workbench ↓See exactly what ARIA Accessible-Name Inventory expects and returns
ARIA Accessible-Name Inventory uses the contract below to complete “Pre-release form audit: local analysis with ARIA Accessible-Name Inventory” in particular. Confirm the shape with the example first; use real data only when the fields and expected result are clear.
- Use this shape
1 · Prepare the input
ARIA Accessible-Name Inventory — For ARIA Accessible-Name Inventory, provide an HTML fragment containing buttons, links, images, and form controls that needs no script execution. The requested outcome is to inventory buttons, links, and form controls with their accessible names and find unnamed controls.. Load the example or fill the clearly labelled fields for your scenario. Expected format for ARIA Accessible-Name Inventory: For ARIA Accessible-Name Inventory, provide an HTML fragment containing buttons, links, images, and form controls that needs no script execution. The requested outcome is to inventory buttons, links, and form controls with their accessible names and find unnamed controls..
- Method applied
2 · Run the operation
ARIA Accessible-Name Inventory — ARIA Accessible-Name Inventory uses this disclosed method to inventory buttons, links, and form controls with their accessible names and find unnamed controls: 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. Run the check on-device and review metrics, warnings, and recommended corrections together. ARIA Accessible-Name Inventory applies this method: ARIA Accessible-Name Inventory uses this disclosed method to inventory buttons, links, and form controls with their accessible names and find unnamed controls: 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.
- Expected output
3 · Read the result
ARIA Accessible-Name Inventory — When ARIA Accessible-Name Inventory finishes, it returns an inventory with element type, selector hint, computed name source, and unnamed or suspicious-control status, organised around the goal to inventory buttons, links, and form controls with their accessible names and find unnamed controls.. Icon-button review: validating the ARIA Accessible-Name Inventory output
- Acceptance check
4 · Accept or correct
ARIA Accessible-Name Inventory — Before accepting a ARIA Accessible-Name Inventory result, complete focusing every interactive element by keyboard and comparing name, role, state, and error message in a real screen reader and accessibility tree; the evidence should support the goal to inventory buttons, links, and form controls with their accessible names and find unnamed controls.. Validate the result in the real target environment and record its assumptions. Acceptance check for ARIA Accessible-Name Inventory: Before accepting a ARIA Accessible-Name Inventory result, complete focusing every interactive element by keyboard and comparing name, role, state, and error message in a real screen reader and accessibility tree; the evidence should support the goal to inventory buttons, links, and form controls with their accessible names and find unnamed controls..
A tool-specific example path
1. Pre-release form audit: local analysis with ARIA Accessible-Name Inventory → 2. Icon-button review: validating the ARIA Accessible-Name Inventory output → 3. Preparing WCAG task tests: checking the limits of ARIA Accessible-Name Inventory
Tip: when an example-data button is available, run it first. Do not use the result in a live process unless it passes the acceptance check.
Persistent storage
Input and output are not stored. The optional usage counter keeps only tool identity and count, never content.
Verification
Output comes from disclosed rules or browser APIs and needs independent review before high-impact use.
APPLICATION AND DECISION GUIDE
✓ REVIEWEDUse ARIA Accessible-Name Inventory with the right input, acceptance check, and next step
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. The notes below help you do more than produce a result: they show how to test whether ARIA Accessible-Name Inventory fits the task and when to stop before a weak output travels further.
ARIA Accessible-Name Inventory uses this disclosed method to inventory buttons, links, and form controls with their accessible names and find unnamed controls: 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. Code is not executed; only static patterns and contracts are inspected. No finding does not prove the absence of a vulnerability.
For ARIA Accessible-Name Inventory, provide an HTML fragment containing buttons, links, images, and form controls that needs no script execution. The requested outcome is to inventory buttons, links, and form controls with their accessible names and find unnamed controls. Confirm the shape first with a small example containing no personal data.
When ARIA Accessible-Name Inventory finishes, it returns an inventory with element type, selector hint, computed name source, and unnamed or suspicious-control status, organised around the goal to inventory buttons, links, and form controls with their accessible names and find unnamed controls. — Before accepting a ARIA Accessible-Name Inventory result, complete focusing every interactive element by keyboard and comparing name, role, state, and error message in a real screen reader and accessibility tree; the evidence should support the goal to inventory buttons, links, and form controls with their accessible names and find unnamed controls.
Three practical use cases
Pre-release form audit: local analysis with ARIA Accessible-Name Inventory
Action: Start with a small synthetic fixture that represents this need. Expected input: For ARIA Accessible-Name Inventory, provide an HTML fragment containing buttons, links, images, and form controls that needs no script execution. The requested outcome is to inventory buttons, links, and form controls with their accessible names and find unnamed controls..
Acceptance signal: The fixture should reproduce “Pre-release form audit: local analysis with ARIA Accessible-Name Inventory” without real personal data.
Icon-button review: validating the ARIA Accessible-Name Inventory output
Action: Keep that fixture unchanged and run the on-device method: ARIA Accessible-Name Inventory uses this disclosed method to inventory buttons, links, and form controls with their accessible names and find unnamed controls: 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.
Acceptance signal: Identical input should return the same result, with no network or file action assumed beyond the disclosed method.
Preparing WCAG task tests: checking the limits of ARIA Accessible-Name Inventory
Action: Retain the output record before moving it into the target workflow: When ARIA Accessible-Name Inventory finishes, it returns an inventory with element type, selector hint, computed name source, and unnamed or suspicious-control status, organised around the goal to inventory buttons, links, and form controls with their accessible names and find unnamed controls..
Acceptance signal: Acceptance requires Before accepting a ARIA Accessible-Name Inventory result, complete focusing every interactive element by keyboard and comparing name, role, state, and error message in a real screen reader and accessibility tree; the evidence should support the goal to inventory buttons, links, and form controls with their accessible names and find unnamed controls.; otherwise do not move the result forward.
Do not use the result for a decision beyond this boundary: ARIA Accessible-Name Inventory limitation: 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.
Move the result to another tool or live process only after Before accepting a ARIA Accessible-Name Inventory result, complete focusing every interactive element by keyboard and comparing name, role, state, and error message in a real screen reader and accessibility tree; the evidence should support the goal to inventory buttons, links, and form controls with their accessible names and find unnamed controls.. Keep this limit visible in the decision record: ARIA Accessible-Name Inventory limitation: 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.
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.
A result in three steps
- 01
Load the example or fill the clearly labelled fields for your scenario. Expected format for ARIA Accessible-Name Inventory: For ARIA Accessible-Name Inventory, provide an HTML fragment containing buttons, links, images, and form controls that needs no script execution. The requested outcome is to inventory buttons, links, and form controls with their accessible names and find unnamed controls..
- 02
Run the check on-device and review metrics, warnings, and recommended corrections together. ARIA Accessible-Name Inventory applies this method: ARIA Accessible-Name Inventory uses this disclosed method to inventory buttons, links, and form controls with their accessible names and find unnamed controls: 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.
- 03
Validate the result in the real target environment and record its assumptions. Acceptance check for ARIA Accessible-Name Inventory: Before accepting a ARIA Accessible-Name Inventory result, complete focusing every interactive element by keyboard and comparing name, role, state, and error message in a real screen reader and accessibility tree; the evidence should support the goal to inventory buttons, links, and form controls with their accessible names and find unnamed controls..
When is this tool useful?
- ✓ Pre-release form audit: local analysis with ARIA Accessible-Name Inventory
- ✓ Icon-button review: validating the ARIA Accessible-Name Inventory output
- ✓ Preparing WCAG task tests: checking the limits of ARIA Accessible-Name Inventory
Tool-specific limitation
ARIA Accessible-Name Inventory limitation: 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
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 →Safe Release Operations: From Performance Budgets to Restore Evidence
Turn performance, dependencies, backups, and change information into one reversible release decision instead of isolated checks.
Read guide →ABOUT THIS TOOL
Frequently asked questions
What input does ARIA Accessible-Name Inventory accept?+
For ARIA Accessible-Name Inventory, provide an HTML fragment containing buttons, links, images, and form controls that needs no script execution. The requested outcome is to 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.
What does ARIA Accessible-Name Inventory return?+
When ARIA Accessible-Name Inventory finishes, it returns an inventory with element type, selector hint, computed name source, and unnamed or suspicious-control status, organised around the goal to inventory buttons, links, and form controls with their accessible names and find unnamed controls. 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?+
Before accepting a ARIA Accessible-Name Inventory result, complete focusing every interactive element by keyboard and comparing name, role, state, and error message in a real screen reader and accessibility tree; the evidence should support the goal to inventory buttons, links, and form controls with their accessible names and find unnamed controls. 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 this tool send or store input on a server?+
No. Processing runs in this browser tab and tool input is not persisted. Copying, downloading, or transferring happens only when you choose it.