Create account
Interfaces and CSSChecked through WebDiag API

Link and Button Accessible Name Analyzer

Get a bounded static inventory of interactive elements and find missing, generic, or ambiguous names.

  • Links and buttons
  • Text, alt, and ARIA
  • Custom-role signals
Online tool

Try the tool

Enter a URL: WebDiag will run a safe network check and show the result.

Page URL

Network check through backend

For HTTP/SEO tools, the URL is sent to the WebDiag API, where SSRF protection, DNS/IP policy, and redirect limits are applied.

Reviewed: 2026-07-17
01

How to use it

  1. 1

    Enter a public page URL.

  2. 2

    Run the source-HTML analysis.

  3. 3

    Review unnamed, generic, nested, and custom-role findings.

02

What the tool can do

  • Native a/button/input/area and explicit role=link/role=button.
  • Names from aria-label, aria-labelledby, text, img alt, input value, and title.
  • Generic names, nested interactive elements, duplicate IDs, javascript: href, and tabindex signals.
03

Common use cases

  • Finding icon-only buttons without aria-label.
  • Reviewing 'Read more' links with different destinations.
  • Finding div role=button elements without a focus signal.
04

How it works inside

Generic-name detection uses a transparent limited dictionary and requires manual context review.

tabindex=0 is only a static signal; the tool does not prove Enter/Space handlers exist.

05

Questions and answers

Does text inside SVG count as a name?

It may appear in the static text inventory, but the final result must be confirmed in the browser accessibility tree.

Why is title-only reported separately?

Title is not a reliable replacement for visible text or an explicit ARIA relationship in every scenario.