Get now

Accessible names on controls

An agent picks controls by their names, so it will struggle to use buttons that have none.

Standard
Recommended
78%Top 100 adoption78 of 100 sites implement it8/9OverviewEstablishedWidely supported and widely deployed.

Who supports it

  • ClaudeSupported (announced)

    Published 1 Aug 2026 · last checked 9 Oct 2026: Claude API docs: Browser use toolread_page 'Returns the page's accessibility tree as text' (role + accessible name per element, e.g. button "Search"); Claude also uses screenshots. Date is approximate, taken from the toolset version id browser_toolset_20260801; page shows no date. The same read_page tool is exposed by the Claude in Chrome extension.

  • ChatGPT AtlasSupported (announced)

    Published 1 Sept 2026 · last checked 9 Oct 2026: OpenAI Help Center: Publishers and Developers - FAQHelp Center article shows 'Updated: last month' as of 2026-10-09 (month-only date). Text: 'ChatGPT Atlas uses ARIA tags—the same labels and roles that support screen readers—to interpret page structure and interactive elements.' Explicit: add descriptive labels to interactive elements.

  • Gemini in ChromePartial support

    Published 5 May 2026 · last checked 9 Oct 2026: Chrome for Developers: Accessibility for agents (Lighthouse Agentic browsing)Chrome team guidance for agents in general ('Agents review the accessibility tree to identify interactive elements'; 'Agents rely on the accessibility tree ... as their primary data model', toolkit blog 2026-06-22). It does not name Gemini in Chrome explicitly, hence partial. Explicit on labels: 'missing labels can block users with visual disabilities and agents from completing a task.'

24 others: no evidence yet. See every agent and browser

What it checks

For every visible interactive element on the rendered page (native and non-native, as counted by Native interactive controls), the extension looks for a name in this order:

  1. an aria-label
  2. an aria-labelledby reference
  3. a <label> that wraps the control or points to it with for
  4. the element’s own text
  5. a title attribute
  6. the alt text of the element or of an image inside it
  7. a value attribute

A control with none of these has no accessible name. An agent choosing what to click has nothing to go on.

Results

Status When
Pass Every control has an accessible name
Warn Some controls are unnamed, up to 25% of them
Fail More than 25% of controls are unnamed
N/A The page has no interactive controls
Unmeasured The extension could not read the page (open it in the active tab)

The result lists locators for the unnamed controls.

How to fix

Give every control visible text, or label it. Icon-only buttons are the most common cause:

<!-- Before -->
<button class="search-toggle"><svg>…</svg></button>

<!-- After -->
<button class="search-toggle" aria-label="Search"><svg aria-hidden="true">…</svg></button>

For an image link, put the name in the image’s alt text.

Support by agent and browser

Announced means the vendor’s own docs or announcement say so. Published is the date on the vendor’s own page, where it has one. Checked is the last time our weekly research found that page still saying so.

AgentStatusSource
AI assistants
Claude AnthropicSupported (announced)

Claude API docs: Browser use tool Published · Checked read_page 'Returns the page's accessibility tree as text' (role + accessible name per element, e.g. button "Search"); Claude also uses screenshots. Date is approximate, taken from the toolset version id browser_toolset_20260801; page shows no date. The same read_page tool is exposed by the Claude in Chrome extension.

AI browsers
ChatGPT Atlas OpenAISupported (announced)

OpenAI Help Center: Publishers and Developers - FAQ Published · Checked Help Center article shows 'Updated: last month' as of 2026-10-09 (month-only date). Text: 'ChatGPT Atlas uses ARIA tags—the same labels and roles that support screen readers—to interpret page structure and interactive elements.' Explicit: add descriptive labels to interactive elements.

Gemini in Chrome GooglePartial support

partial Chrome for Developers: Accessibility for agents (Lighthouse Agentic browsing) Published · Checked Chrome team guidance for agents in general ('Agents review the accessibility tree to identify interactive elements'; 'Agents rely on the accessibility tree ... as their primary data model', toolkit blog 2026-06-22). It does not name Gemini in Chrome explicitly, hence partial. Explicit on labels: 'missing labels can block users with visual disabilities and agents from completing a task.'

No evidence yet24
  • ChatGPT
  • Gemini
  • Perplexity
  • Copilot
  • Meta AI
  • Comet
  • Dia
  • Edge Copilot Mode
  • Claude Code
  • Cursor
  • Codex
  • GitHub Copilot
  • Windsurf
  • CCBot
  • Applebot
  • Amazonbot
  • Bytespider
  • Cohere
  • Mistral
  • DuckAssist
  • Chrome
  • Edge
  • Firefox
  • Safari

Names and marks belong to their owners and are used only to identify products. None of these vendors is affiliated with Sitebulb. Spotted something out of date? Send a correction.

Adoption on the top 100 sites

78 of 100 measured sites implement it

Scanned 23 Oct 2026 with the Sitebulb Labs extension, against the Tranco list (tranco-56Z8N).

9 Oct 2026: 78%12 Oct 2026: 76%23 Oct 2026: 78%
9 Oct 2026 78% → 23 Oct 2026 78%
Sites implementing it78
  1. #1 google.com
  2. #2 cloudflare.com
  3. #3 aws.amazon.com (via amazonaws.com)
  4. #4 facebook.com
  5. #9 microsoft.com
  6. #11 youtube.com (with warnings)
  7. #12 apple.com
  8. #13 instagram.com
  9. #15 mail.ru (with warnings)
  10. #16 x.com (via twitter.com)
  11. #18 linkedin.com
  12. #20 dzen.ru (with warnings)
  13. #24 azure.microsoft.com (via azure.com)
  14. #26 m365.cloud.microsoft (via office.com)
  15. #32 github.com
  16. #33 wikipedia.org
  17. #37 fastly.com (via fastly.net)
  18. #39 whatsapp.com (via whatsapp.net)
  19. #42 bing.com
  20. #43 netflix.com
  21. #44 triplinkintl.com (with warnings)
  22. #48 gandi.net
  23. #50 marketingplatform.google.com (via doubleclick.net)
  24. #55 wordpress.org
  25. #56 teams.live.com (via skype.com)
  26. #57 cloudflare.net
  27. #60 digicert.com
  28. #67 domains.google (via googledomains.com)
  29. #68 zoom.com (via zoom.us) (with warnings)
  30. #69 uk.yahoo.com (via yahoo.com) (with warnings)
  31. #70 sso.myfritz.net (via myfritz.net) (with warnings)
  32. #71 endpoints.news (with warnings)
  33. #72 api.whatsapp.com (via wa.me)
  34. #75 roblox.com (with warnings)
  35. #76 opera.com
  36. #80 baidu.com (with warnings)
  37. #83 ya.ru (via yandex.net)
  38. #84 nginx.org
  39. #85 ntp.org (with warnings)
  40. #86 msn.com
  41. #87 qq.com (with warnings)
  42. #90 vimeo.com
  43. #91 primevideo.com (via amazonvideo.com)
  44. #93 bunny.net (via b-cdn.net) (with warnings)
  45. #94 blogger.com (via blogspot.com)
  46. #95 mozilla.org
  47. #96 f5.com (with warnings)
  48. #98 telegram.org (via t.me) (with warnings)
  49. #99 store.epicgames.com (via epicgames.com) (with warnings)
  50. #101 wordpress.com (with warnings)
  51. #103 reddit.com
  52. #106 sentry.io (with warnings)
  53. #107 letsencrypt.org (via lencr.org) (with warnings)
  54. #109 ui.com (with warnings)
  55. #110 european-union.europa.eu (via europa.eu)
  56. #112 chatgpt.com
  57. #116 bitly.com (via bit.ly) (with warnings)
  58. #117 ipify.org
  59. #120 samsung.com (with warnings)
  60. #122 intuit.com
  61. #127 openai.com
  62. #128 one.one.one.one (via cloudflare-dns.com) (with warnings)
  63. #130 registrar-servers.com
  64. #131 pages.github.com (via github.io) (with warnings)
  65. #132 dropbox.com
  66. #135 discord.com (via discord.gg) (with warnings)
  67. #136 developer.adobe.com (via adobe.io)
  68. #139 apache.org (with warnings)
  69. #140 android.com
  70. #141 nih.gov
  71. #144 vk.ru
  72. #150 t-online.de (with warnings)
  73. #153 webex.com
  74. #154 snapchat.com (with warnings)
  75. #156 godaddy.com (with warnings)
  76. #158 kaspersky.co.uk (via kaspersky.com) (with warnings)
  77. #159 firebase.google.com (via crashlytics.com)
  78. #160 tumblr.com

Overview

8/9

Established

Widely supported and widely deployed.

How this rating is worked out8 of 9 points
FactorPointsWhy
Vendor support2 / 32 vendors supporting, 1 partly or planned
Top-100 adoption3 / 378% of measured sites
Spec maturity3 / 3Published standard

8 or more points is Established, 5 to 7 is Gaining traction, 2 to 4 is Speculative and under 2 is Stalled. A feature is also Stalled when more vendors have said no than yes. Read the spec.

Community insights

No community insights for this feature yet.

Quotes are from public posts, checked against the original before they appear here. Suggest an insight, or ask for yours to be removed.