Accessible front-end development
Accessible front ends meet WCAG 2.2 AA and can be used entirely by keyboard and screen reader.
Background
The BFSG, Germany's implementation of the European Accessibility Act, has applied since 28 June 2025. It covers digital services for consumers, such as online shops and customer accounts. Market surveillance authorities can impose fines. Public bodies are bound by the BITV 2.0. The benchmark is EN 301 549. We develop to WCAG 2.2 AA, which also covers the newer criteria.
What we implement
Semantic HTML: correctly structured headings, landmarks, lists and forms
Keyboard operation: logical focus order, visible focus and no keyboard traps
Targeted ARIA: for dialogues, menus and accordions
Contrast: at least 4.5:1 for body text, reflowing at up to 400% zoom
Forms and media: visible labels, alt text and captions
New in WCAG 2.2
Among other things, version 2.2 sets a minimum target size of 24 × 24 pixels. Focus must not be hidden, and dragging needs an alternative. Log-in steps must not require users to remember or calculate anything.
Approach
Accessibility is planned in from the design stage, which costs far less than rebuilding later. We test every component automatically with axe and Lighthouse, and by hand with a keyboard, VoiceOver and NVDA.
For existing websites, we produce a WCAG audit report with prioritised actions. The results are documented so you can present them to market surveillance authorities and customers.