Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →An aria-label gives an element an accessible name—a short text label assistive technologies can expose when the element needs a name. Use it when a suitable visible or native label is unavailable and the element’s role supports naming. If suitable text is already visible, prefer reusing it with aria-labelledby; for standard form fields, use a native <label>.
What an ARIA label does
An accessible name identifies an element’s purpose, such as “Close dialog” for a button shown only as an ×. The aria-label attribute supplies that name as a string:
As an Amazon Associate I earn from qualifying purchases.
<button type="button" aria-label="Close dialog">×</button>Assistive technologies can expose the resulting name through accessibility APIs. The name should tell users what the element does, not merely describe its appearance. See the WAI-ARIA 1.2 specification.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →When to use aria-label
Use aria-label to fill a genuine naming gap: for example, an icon-only button without another suitable label. It can also be appropriate for certain custom controls that cannot use a native label association, as long as the element’s role permits an accessible name. W3C’s ARIA14 technique describes using aria-label to provide a name when a visible label cannot be used.
#1 Best Overall
- Choose a concise, specific name that communicates the control’s purpose.
- Do not add a naming attribute to roles for which naming is prohibited.
- Do not use a name as a substitute for a longer explanation. Associate additional instructions or context with
aria-describedby.
Choose between a native label, aria-labelledby, and aria-label
| Method | Use it when | Example |
|---|---|---|
Native <label> |
You are naming a standard form control and can associate visible label text with it. | <label for="email">Email address</label> |
aria-labelledby |
Suitable text already exists in the DOM and should provide the accessible name. | aria-labelledby="search-label" |
aria-label |
No suitable visible label is available or usable, and the element’s role supports naming. | aria-label="Close dialog" |
For standard form controls, use a native label where it fits:
<label for="email">Email address</label>
<input id="email" name="email" type="email">If a visible label already exists for a custom control, reference that text rather than maintaining a second string:
<span id="search-label">Search</span>
<button type="button" aria-labelledby="search-label">⌕</button>WAI-ARIA 1.2 says: “If the label text is available in the DOM (Document Object Model) (i.e. typically visible text content), authors SHOULD use aria-labelledby and SHOULD NOT use aria-label.” The WAI-ARIA Authoring Practices Guide on names and descriptions explains the practical preference: visible text is easier to maintain, less likely to diverge from what sighted users see, and avoids duplicated wording and translation work.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How to write an effective accessible name
- Name the action or purpose: “Search” is more useful than “Magnifying glass” for a search button.
- Keep it concise: use the name to identify the control, not to deliver a paragraph of instructions.
- Keep it aligned with visible wording: when visible text exists, reuse it where possible so users do not encounter conflicting names.
- Use a description for extra detail: link longer guidance to the control with
aria-describedby.
How to check the result
After implementing a name, check the element’s computed accessible name in your accessibility inspection workflow. Confirm that it identifies the intended purpose and does not replace useful visible wording. These examples illustrate W3C guidance; they do not claim particular browser or assistive-technology test results.
Common mistakes and fixes
- Adding aria-label to a control that already has a good visible name: use the visible text or reference it with
aria-labelledbyinstead. - Using aria-label on a standard field instead of a native label: associate a visible
<label>with the field when that is suitable. - Writing a name that describes an icon rather than the action: replace “X icon” with a purpose such as “Close dialog.”
- Putting a long explanation in the name: keep the name short and use
aria-describedbyfor additional context. - Assuming aria-label only adds information: it can override a native form label, image alt text, or a link’s own text. Check the computed name so it remains accurate and does not obscure useful content. See W3C’s guidance on ARIA8 and ARIA6.
Or skip the browser setup
If you need a clean screenshot of the page after checking its accessible labels, you can request one with ScreenshotNeo. The API returns a screenshot or PDF from a GET request; see the API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpCookie banners, popups, and chat widgets are removed before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed. An MCP server provides screenshot tools for AI agents. The free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots.
Sign up free for 1,000 screenshots a month, with no card.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Best Value
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
