FFCheck is built to be usable by everyone — including people who navigate by keyboard, use screen readers, have low vision, color-vision differences, or motor disabilities. This statement describes what we target, what's known to be imperfect, and how to tell us when something's broken.
Target conformance level
We aim to meet WCAG 2.1 Level AA across every page on ffcheck.nl. This is the conformance level expected of EU public-sector sites under Directive 2016/2102 and increasingly expected of private-sector sites under the European Accessibility Act (EAA, applicable from June 28, 2025 for many digital services).
What that means in practice
- Color contrast: body text and interactive controls meet at least 4.5:1 contrast against their background (3:1 for large text and non-text components).
- Keyboard navigation: every interactive element is reachable and operable with Tab / Shift+Tab / Enter / Space, with visible focus indicators throughout.
- Screen reader compatibility: semantic HTML (
<nav>,<main>,<button>, headings in order); ARIA used only where native semantics fall short; live regions announced where content updates without page reload. - Text alternatives: every meaningful image, icon, and SVG has an
altattribute oraria-label. Decorative graphics are markedaria-hidden. - Reduced motion: the cookie banner, hover animations, and weather visuals respect
prefers-reduced-motion. - 200% zoom: all pages remain usable at 200% browser zoom without horizontal scrolling on a 1280×1024 viewport.
- No autoplay: no audio or video starts automatically. No flashing content above WCAG 2.3.1 thresholds.
Known limitations
- The 3D Amsterdam map on Wat Nu? requires WebGL2 and is fundamentally a visual experience. Screen-reader users get the same underlying data via the bottom drawer's tabbed lists (Live · Alerts · Transit · Parking · Crowds · Community). Map controls (tilt, locate, reset) are keyboard-reachable but they don't communicate visual state through the screen reader — a known limitation we'd like to fix.
- The Buienradar precipitation chart is rendered as inline SVG bars. Screen readers will hear the dataset summary ("dry for the next 2 hours") but not the per-5-minute granularity. Audio description / table fallback is on the roadmap.
- Some third-party embeds (e.g., Google Analytics opt-out controls, social-link icons) may inherit color contrast we don't control directly.
Date of last review
This statement was last reviewed on 20 May 2026 through internal audit using browser DevTools, axe-core, NVDA on Windows, and VoiceOver on macOS / iOS.
How to report a problem
If something is unusable for you — at any level — please tell us. The fastest way:
Include: which page, which device + browser, which assistive technology (if any), and what you tried to do. We aim to respond within 5 business days and to ship a fix or a workaround within 4 weeks.
Alternative formats
Any document or data on ffcheck.nl can be provided in plain-text or a different format upon request. Email toegankelijkheid@ffcheck.nl.