Retrievability and UX · Branch R.D, Semantic UI and structured data
R-09 Interactive UI must be understood through semantic HTML and accessibility trees
Links, buttons, labels, dialogs and form controls must be usable by both people and browser agents through native semantic HTML or appropriate ARIA.
- Scope
- All public content
- Priority
- Optimisation.
- Quality bucket
- Retrievability and UX
- Legacy coverage
- GEO-20
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.
How to implement
- Replace clickable divs and spans with real button and a href elements.
- Attach a real label to every form input.
- Add the correct semantics or ARIA to modals, dialogs and menus.
- Walk through the site by keyboard and fix the focus order.
- Remove ARIA that duplicates what native HTML already provides.
- Re-test with an accessibility checker and a browser-agent flow.
Checklist
- Use a real button element for buttons and an a element with href for links.
- Connect a real label to every input.
- Mark modal, dialog and menu states with the correct semantics or ARIA.
- Test keyboard navigation and focus order.
- Do not use ARIA unnecessarily in place of native HTML.
How to audit
- Inspect the accessibility tree.
- Run accessibility tests such as axe or WAVE.
- Test a real browser-agent flow.
How UltimateSEO checks this automatically
Automated. Checked automatically on a sample: 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.1, revised 2026-10-07. Evidence states, control states and the publish gate are explained on the hub.