4.6 Agentic readiness (Lever 9) ✦MediumVerified

ARIA misused/missing on custom widgets

Custom widgets, menus, tabs, modals, need correct ARIA roles and states to be understood by assistive tech and agents. Missing or wrong ARIA makes them opaque or misleading.

What it is

Custom components lack correct ARIA.

Why it matters

Misread by AT/agents.

How to fix it

Apply correct ARIA roles/states.

How to find it on your site

  1. Inspect custom widgets for appropriate ARIA roles, states and properties.
  2. Flag missing or incorrect ARIA.
  3. Apply the correct patterns, preferring native elements where possible.
  4. Test with assistive technology.

Cross-reference to ranking and citation factors

Correct ARIA makes custom components understandable to assistive tech and agents. Misused ARIA can be worse than none.

Impact

Low-medium. Direct (WAI-ARIA).

Evidence

Correct ARIA for custom widgets. W3C, WAI-ARIA Authoring Practices; W3C, Web Content Accessibility Guidelines (WCAG) 2.2

← No machine-readable product/availability for agentsllms.txt present →