Accessibility
How we work with accessibility, how to report barriers, and how we verify improvements.
Last reviewed: March 5, 2026
- Target standard
- WCAG 2.2 AA (goal)
- Conformance status
- Not formally certified; reviewed internally.
- Scope
- Applies to danskegrundskoler.dk pages. Excludes third-party content we do not control.
- Contact
- [email protected]
1. What we mean by accessibility
- Keyboard-only use: key navigation should be possible without a mouse.
- Screen reader basics: semantic headings, labels, and meaningful link text.
- Color and contrast: content should be readable without relying on color alone.
- Text scaling: layout should remain usable when zooming and using larger text.
2. Report an accessibility problem
We aim to respond within 5 business days.
If you encounter a barrier, please email us. Include the information below so we can reproduce and fix it efficiently:
- Page URL
- What you tried to do (expected vs. actual result)
- Device and browser
- Assistive technology (screen reader name/version, keyboard-only, etc.)
- Screenshot or short recording (optional, if it helps explain the issue)
Contact: [email protected]
3. How we review accessibility
We review accessibility through:
- Manual checks of key flows (navigation, search, and core reference pages).
- Automated checks as part of ongoing frontend quality work.
We do not currently provide:
- Formal certification or external conformance claims.
- A complete device and assistive-technology compatibility matrix.
Reviewed at least quarterly and when major UI changes ship.
4. Third-party components
Some UI and functionality is delivered through third parties. We cannot fully guarantee accessibility for components we do not control, but we will mitigate where possible.
- Cookie consent banner (Cookieyes).
- Embedded or interactive third-party content, if present (maps, charts, etc.).