Keyboard
clickable-not-focusable
WCAG 2.1.1 Keyboard Level A
Who this affects
This element responds to a mouse click but cannot be reached with a keyboard, so keyboard and screen reader users cannot use it at all.
How to fix it
Use a <button> or <a>. If it must stay a <div>, add role, tabindex="0", and handlers for both Enter and Space.
How much work is it?
Usually a template or design change. That is a rough guide for planning, not an estimate for your codebase. A single content edit repeated across a template is a template change.
What a person still has to check
Passing this rule does not mean 2.1.1 passes. Automation checks part of the criterion, and the rest is a judgement:
Unplug the mouse. Reach and operate every control with the keyboard alone.
Read 2.1.1 Keyboard in plain language
Where this check comes from
This is our own check, not an axe rule. We added it because the failure it catches is common and nothing else was catching it.
Find out whether your site does this
A scan checks this rule on every page it visits, and shows you the code and a screenshot of each place it fires.