Interactive elements carry accessible names for AI agents

This check is about agent operability, not search citation. AI agents that operate a browser on a user's behalf navigate your UI the way screen readers do. OpenAI's developer guidance is explicit: "ChatGPT Atlas uses ARIA tags—the same labels and roles that support screen readers—to interpret page structure and interactive elements. To improve compatibility, follow WAI-ARIA best practices." Google's generative-AI guide likewise describes browser agents "inspecting the DOM structure, and interpreting the accessibility tree." An icon-only button with no accessible name is invisible to those agents: a user who asks their assistant to sign up, check pricing, or run your product hits a wall your human visitors never see. The same fix serves disabled users — accessibility work now does double duty.

Give every interactive element an accessible name. Native semantics count — <button>Submit</button> is already named; the failures are icon-only buttons, unlabeled inputs, and clickable divs.

// Icon-only button: name it
<button aria-label="Copy audit prompt">
  <CopyIcon aria-hidden="true" />
</button>

// Input: associate a label
<label htmlFor="email">Email</label>
<input id="email" type="email" />

For full coverage (roles, states, keyboard interaction), the Accessibility WCAG audit goes much deeper — this check covers only the naming floor agents need.