Name every control

A control should explain itself before anyone presses it.

Is Agenticis-agentic.com
The score is an at-a-glance summary; the individual checks and evidence are the useful part of the report.
MethodologyRead docs ↗

Notes from the Is Agentic checks and report format.

Read the interface as an agent

Ask both sides which control sends the invoice.

Visual hints onlyBad
Invoice #1042•••

Accessible tree
aria-label="button"
Specific namesGood
Invoice #1042Draft

Accessible tree
<button>Send invoice to Acme</button>
<label for="due-date">Due date</label>
<input id="due-date" name="dueDate" type="date">

<button type="submit">
  Send invoice to Acme
</button>

Why it matters, pros and cons

Why it matters

Agents operate through the same semantics assistive technology uses. Good names also remove hesitation for everyone else.

Pros

  • Intent is clear before activation.
  • Native controls bring keyboard behavior for free.
  • Automation becomes less brittle.

Cons

  • An aria-label cannot repair a confusing workflow.
  • Names must stay specific when the state changes.
  • Icon-only controls still need a visible clue when possible.