Full keyboard navigation
Every function is accessible — without a mouse. Essential for screen reader users, helpful for everyone else.
What does "Full keyboard navigation" mean?
Keyboard navigation means: every interactive function of a website is accessible with tab, Enter, Space, arrow keys and Esc Operable. No mouse dependencies, no function that only works via hover or click. Hover effects are allowed, but must not be the only way to interact.
Obligation and Benefit — WCAG 2.1.1.
WCAG 2.1.1 (Keyboard) Level A accessibility is mandatory — without keyboard input, a site is unusable for screen reader users, people with motor impairments, and power users. Plus: 2.1.2 (No Keyboard Trap) — Focus must be restored from every area. Carousels, modals, and custom dropdowns are the most common pitfalls.
How we will solve it specifically.
- All buttons are
or<a href="/en/…/">(not<div onclick>). - Tab order corresponds to the reading order — not arbitrary
tabindex. - Carousels: Arrow keys + ESC Pause; Modals: Focus Trap with ESC Close + Focus Return.
- Hover menus have a keyboard-activated click trigger.
- Keyboard walkthrough test before each release — see verification checklist.
Related building blocks of our module suite
-
AAA contrasts, tested per component
WCAG 1.4.6≥ 7:1 for text, ≥ 4.5:1 for large font — tested per component, not per page sample.
-
Plain language (AI-supported)
WCAG 3.1.5Content simplified at the touch of a button — for people with reading difficulties, language learners and those in a hurry.
-
AI alt text generator
WCAG 1.1.1No more "image without a description". AI provides the first draft — editorial team refines it.
-
Heading Hygiene & Structure Manager
WCAG 1.3.1Clean outline for screen readers and search engines — one H1 per page, no jumps.
Do you need this exact module?
15-minute initial consultation — we'll clarify whether it's relevant for your site.
Further information:
BFSG overview ·
Performance overview ·
BAFA funding ·
FAQs
