Semantic Buttons and Links Check
Ensure interactive controls use native buttons and links with the correct behavior and accessible semantics.
Check your websiteWhy this check matters
Native controls provide keyboard behavior, focus handling, names, and roles automatically. Clickable generic elements often exclude keyboard and assistive-technology users.
Passing evidence
<button type="button">Open filters</button>
<a href="/pricing">View pricing</a>Common failing evidence
<div onclick="openFilters()">Open filters</div>Possible false positives
- A custom component can render a correct native element internally.
- Non-interactive styled content should not be counted as a control.
How to fix it safely
- Use button for actions and anchor for navigation.
- Preserve visible keyboard focus.
- Give icon-only controls a concise accessible name.
How to verify the fix
- Operate every control using only the keyboard.
- Confirm role, name, state, and focus in the accessibility tree.
Related Accessibility checks
Run the complete audit
Check this signal together with the related category evidence on the current public page.
Open the accessibility audit tool
