Get now

Form control labelling

Agents use field labels to fill in forms. Without them, they have to guess.

Standard
Recommended
30%Top 100 adoption30 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. Includes form_input member tool; fields are targeted via refs from the labelled accessibility tree.

  • 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.' Forms named explicitly: 'interactive elements like buttons, menus, and forms'.

  • 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.

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

What it checks

The extension finds every visible form field on the rendered page: <input> (other than hidden inputs), <select> and <textarea>. A field counts as labelled if it has any of:

  • an aria-label
  • an aria-labelledby reference
  • a title attribute
  • a <label> wrapped around it
  • a <label for> that matches its id

Placeholder text does not count as a label.

Results

Status When
Pass Every form field is labelled
Fail One or more form fields have no label
N/A The page has no form fields
Unmeasured The extension could not read the page (open it in the active tab)

Unlike the other control checks, there is no warning band: a single unlabelled field fails. The result lists locators for each one.

How to fix

Associate a <label> with every field:

<label for="email">Email address</label> <input id="email" name="email" type="email" />

Where a visible label does not suit the design, use aria-label:

<input type="search" name="q" aria-label="Search products" placeholder="Search" />

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. Includes form_input member tool; fields are targeted via refs from the labelled accessibility tree.

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.' Forms named explicitly: 'interactive elements like buttons, menus, and forms'.

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.

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

30 of 100 measured sites implement it

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

9 Oct 2026: 31%12 Oct 2026: 30%23 Oct 2026: 30%
9 Oct 2026 31% → 23 Oct 2026 30%
Sites implementing it30
  1. #3 aws.amazon.com (via amazonaws.com)
  2. #4 facebook.com
  3. #9 microsoft.com
  4. #13 instagram.com
  5. #16 x.com (via twitter.com)
  6. #24 azure.microsoft.com (via azure.com)
  7. #32 github.com
  8. #33 wikipedia.org
  9. #42 bing.com
  10. #43 netflix.com
  11. #48 gandi.net
  12. #50 marketingplatform.google.com (via doubleclick.net)
  13. #57 cloudflare.net
  14. #69 uk.yahoo.com (via yahoo.com)
  15. #76 opera.com
  16. #83 ya.ru (via yandex.net)
  17. #85 ntp.org
  18. #94 blogger.com (via blogspot.com)
  19. #95 mozilla.org
  20. #101 wordpress.com
  21. #106 sentry.io
  22. #110 european-union.europa.eu (via europa.eu)
  23. #112 chatgpt.com
  24. #127 openai.com
  25. #140 android.com
  26. #144 vk.ru
  27. #150 t-online.de
  28. #156 godaddy.com
  29. #159 firebase.google.com (via crashlytics.com)
  30. #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 / 330% 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.