(Based on WCAG, RGAA, and real user experience)

What if I told you that keyboard accessibility – one of the oldest WCAG rules – is still one of the most broken?

Keyboard accessibility is one of the most fundamental aspects of web accessibility, yet it remains one of the most overlooked. For people who cannot use a mouse, the keyboard is their primary tool to navigate, interact, and accomplish tasks online.

Even as an accessibility professional, I often find testing keyboard navigation surprisingly challenging: focus disappearing, inconsistent behavior across browsers, or having to guess whether Enter or Space should activate an element. These frustrations highlight a critical point: if it’s difficult for trained experts to evaluate keyboard accessibility, imagine the barriers faced by real users who depend on it daily.

Ensuring seamless keyboard navigation is not just a compliance checklist; it’s a way to provide equal access, preserve dignity, and create inclusive experiences for everyone.

Here’s the data:

1. In the 2025 WebAIM Million Report, nearly 95% of home pages have detectable WCAG 2 failures, even though keyboard operability is mandatory since WCAG 2.0 back in 1999.
2. According to accessibility surveys, 25% of screen reader users listed “lack of keyboard accessibility” among their top three web frustrations.
3. The WCAG guideline for no keyboard traps (SC 2.1.2) states clearly that keyboard users must always be able to move focus away from any component, yet trapping still happens too often.

Here are core principles while checking keyboard accessibility:

• Test on multiple browsers (Chrome, Firefox, Safari).
• Native HTML elements (buttons, links, form fields) have reliable default behaviors. If they fail, it’s likely a bug.
• All interactive elements must be keyboard-accessible.
• Standard keyboard keys: Tab → move focus forward | Shift + Tab → move focus backward.
• Focus must always be clearly visible & logical tab order.
• Focus is trapped inside dialogs.
• Arrow navigation works for ARIA patterns

Basic elements & expected behaviors

Element	Keys	Notes
Link (<a>)	Tab + Enter	Space should not activate links.
Button (<button>, input type=”button”)	Tab + Space & Enter	Both should work per WCAG/RGAA.
Checkbox	Tab + Space (toggle)	Enter should do nothing.
Radio button / group	Tab to enter group, arrows to navigate, Space to select	Arrow navigation preferred over Tab.
Select (<select>)	Tab, arrows to navigate, Enter or Space to open/select	Some browsers (Safari) require Alt + Down.
Text input / textarea	Tab for focus, type normally, Enter submits if form	Avoid trapping focus.
Custom ARIA widgets	Follow ARIA role patterns	If role=button, Space and Enter must be supported per ARIA design patterns.

Complex components

Component	Key Behavior	Notes
Menus / Tabs	Arrows to navigate, Tab between items, Esc to close modals	Menus must always be closable via keyboard.
Dialogs / Modals	Focus trapped inside, Esc closes, focus returns to trigger	Crucial to test in every modal.
Accordions, sliders, carousels	Tab, Enter / Space to activate, arrows to navigate	Use proper ARIA attributes.

Improving keyboard accessibility is not just about meeting WCAG or RGAA requirements – it’s about creating a web that works for all users. By applying consistent focus management, proper key interactions, and testing across different browsers and assistive technologies, we can dramatically reduce exclusion and frustration. Investing time in this area brings immediate benefits: users can navigate efficiently, complete tasks independently, and engage confidently with digital services.

Accessibility is an ongoing commitment, and prioritizing keyboard navigation is a concrete, high-impact step that benefits both users and organizations alike.

Reference links for keyboard accessibility checks

WCAG Guidelines:

• WCAG 2.1 – Keyboard Accessible (SC 2.1)
• WCAG 2.1 – No Keyboard Trap (SC 2.1.2)
• WCAG 2.1 – Focus Visible (SC 2.4.7)

RGAA Guidelines (French standard):

• RGAA 4.1 – Keyboard Navigation

Practical testing resource:

• WebAIM – Keyboard Accessibility