What it is
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. Custom components lack correct ARIA. Misread by AT/agents. Apply correct ARIA roles/states.
Why does aria misused/missing on custom widgets matter for AI search?
Misread by AT/agents.
How do you fix it?
Apply correct ARIA roles/states.
How do you find it on your site?
- Inspect custom widgets for appropriate ARIA roles, states and properties.
- Flag missing or incorrect ARIA.
- Apply the correct patterns, preferring native elements where possible.
- Test with assistive technology.
Which ranking and citation factors does it touch?
Correct ARIA makes custom components understandable to assistive tech and agents. Misused ARIA can be worse than none.
What is the impact?
Low-medium. Direct (WAI-ARIA).
What is the evidence?
Correct ARIA for custom widgets. W3C, WAI-ARIA Authoring Practices; W3C, Web Content Accessibility Guidelines (WCAG) 2.2
Sources
Frequently asked questions about aria misused/missing on custom widgets
What does "ARIA misused/missing on custom widgets" mean?
Custom components lack correct ARIA.
How do you fix aRIA misused/missing on custom widgets?
Apply correct ARIA roles/states.