AccName & ARIA Inspector
Inspect HTML elements to compute their exact accessible name, role, and screen reader announcements following the W3C Accessible Name and Description Computation (AccName 1.2) specification.
Live Element Rendering
Computed Accessibility Tree
WCAG Conformance Checks
How accessible names work
Every button, link and form field needs an accessible name, the text a screen reader announces for it. Browsers compute that name with the Accessible Name and Description Computation (AccName) algorithm. It looks at, in order of precedence, aria-labelledby, aria-label, the native label or content of the element and, as a last resort, the title attribute.
Most accessible name bugs come from a missing name (an icon-only button with no label), a name that does not match the visible text, or ARIA that conflicts with native HTML. The first rule of ARIA is to use a native element, such as a real <button>, whenever one exists, because native elements carry the right role, name and keyboard behavior for free.
Paste an HTML snippet into this tool to see the computed name, role and state, a plain-language preview of what a screen reader would announce, and warnings for common anti-patterns.
Frequently asked questions
What is an accessible name?
The text alternative a browser gives assistive technology for a control or image, such as the label of a button or form field. It is what a screen reader reads aloud.
Does aria-label replace the visible text?
For name computation, yes, aria-label takes precedence over the element's content. But WCAG criterion 2.5.3 Label in Name expects the accessible name to include the visible label text, so voice control users can say what they see.
What is the first rule of ARIA?
If a native HTML element or attribute already has the semantics and behavior you need, use it instead of adding ARIA. No ARIA is better than bad ARIA.
Which WCAG criteria involve accessible names?
Mainly 4.1.2 Name, Role, Value, 1.1.1 Non-text Content, 2.4.4 Link Purpose and 3.3.2 Labels or Instructions.
Want every page of your site checked, not just one? Request a free WCAG 2.2 AA audit, or read our accessibility guides.