Accessibility (BFSG / WCAG 2.1 AA) – Checklist for your website
This checklist sums up the key requirements of WCAG 2.1 Level AA / EN 301 549 in practical terms – the benchmark for Germany's Accessibility Reinforcement Act (BFSG, in force since 28 June 2025). It doesn't replace a full audit, but it helps you work through the biggest barriers systematically. Go through it in order and get expert support for final conformance.
- 1. Full keyboard operability
Every function must be reachable and usable without a mouse – menus, dropdowns, forms, sliders, pop-ups. The focus order is logical, there are no keyboard traps, and focus returns sensibly after dialogs close.
- 2. Visible focus
The currently focused element is always clearly identifiable (a distinct outline with sufficient contrast). Never remove the focus indicator in CSS without replacing it with a better one.
- 3. Sufficient colour contrast
Normal text at least 4.5:1, large text (from ~24px, or 19px bold) at least 3:1. Controls and graphics also need enough contrast. Don't rely on colour alone to convey meaning (e.g. don't mark errors only in red).
- 4. Scalability & responsive layout
Content stays usable at 200% zoom without text being cut off or requiring horizontal scrolling. Use relative units and avoid fixed pixel heights that trap text.
- 5. Text alternatives for images & graphics
Informative images get a meaningful alt text; decorative ones stay empty (alt=""). Functional icons need an accessible label. Complex graphics/charts need a text description.
- 6. Clean structure & semantics
A sensible heading hierarchy (exactly one H1, then H2/H3 in order), real HTML elements (buttons, links, lists) instead of faux DIVs, clear landmarks (header, nav, main, footer) and a skip link to the content.
- 7. Accessible forms
Each field has a visible, associated label (not just a placeholder). Required fields are marked, error messages are clear, placed at the field and announced to screen readers (role="alert"/aria-live). Sensible autocomplete attributes ease input.
- 8. Accessible multimedia
Videos need captions, audio needs a transcript; purely visual videos need audio description or an alternative. Media doesn't autoplay with sound and can be paused.
- 9. Motion & time under control
Automatic motion (sliders, animations, auto-scroll) can be paused and respects the system 'reduce motion' setting. No flashing content (seizure risk) and no tight time limits without an option to extend.
- 10. Understandability & consistency
Clear, plain language; the page language is set in the HTML (lang). Navigation and controls are consistent across pages. Important information isn't hidden only as image text.
- 11. Test with real assistive technology
Automated tools (e.g. axe-core, Lighthouse) catch only part of the issues. Also test manually: full keyboard operation and a run-through with a screen reader (e.g. VoiceOver, NVDA).
- 12. Publish an accessibility statement
Provide a statement with conformance status, known limitations, the standard applied and a feedback/contact route for reporting barriers. Date it and keep it current.
Next steps: Start with an audit, fix the highest-impact items first (keyboard, contrast, forms, structure) and publish an accessibility statement. Not sure whether you're affected or where you stand? Reach out at info@rocket-monkeys.com for a no-pressure intro call.
⚠️ Important note: This content is for general information and is not legal advice. Whether you are affected and which measures are required depends on your specific case. For a binding legal assessment, consult qualified advisors.