Retrieval and usability, control 9 of 18
R-09 Use semantic and accessible interactive controls
Controls should expose their purpose, name and state to people and machines. Semantic HTML supports usability; it is not a special AI ranking schema.
- Priority
- High priority.
- Hard gate
- No
- Change class
- AUTO_WITH_TEST: A candidate requiring relevant tests.
- Quality bucket
- Retrieval and usability
Why it matters
If a clickable element is not a real control, keyboard and assistive technology users may not be able to operate it. Browser agents that rely on the accessibility tree can fail in the same way, so forms and checkouts may not complete. Native semantics give people and automated agents the same dependable view of the interface.
Evidence to review
- Accessibility tree, keyboard task test and rendered control inspection.
How to implement
- Use buttons for actions and links for navigation.
- Associate inputs with labels and communicate validation errors.
- Test keyboard focus, expanded states and dialogs.
- Use appropriate ARIA only when native semantics are insufficient.
How UltimateSEO checks this
Automated. A check in the scan sets PASS or FAIL for this control, and reports UNKNOWN or BLOCKED when its input is missing.
The check looks at: buttons and links have accessible names and form inputs have labels.
States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.
Sources
Part of The UltimateSEO Framework v4.3, catalogue dated 2026-10-14. Evidence states, control states and the publish gate are explained on the hub.