We want eudr.dev to be usable by everyone who has to meet the Deforestation Regulation, however they browse. This statement records, honestly, where the service stands against the standard — and how to tell us when we fall short.
Standard
EN 301 549 · WCAG 2.1 Level AA
Status
Partial conformance — most of the service meets AA; the map has known limits with a text alternative (below)
Last reviewed
5 August 2026
§1What conforms
Colour contrast✓ AA — every text/background pair was measured; body text is 14:1, the lightest caption 4.8:1, all links and marks ≥ 4.5:1 in both the light and dark register.
Keyboard — the site is operable without a mouse; every interactive control takes focus and shows a visible focus ring; on the main application pages a skip-to-content link is the first tab stop.
Structure — semantic landmarks (header, nav, main, footer), a single h1 per page and an ordered heading outline, and a declared page language.
Motion — all ambient animation stops under prefers-reduced-motion; nothing flashes.
Forms & status — inputs have programmatic labels; the assistant panel is a labelled dialog and announces replies via a polite live region; errors are shown in text, not colour alone.
Zoom & reflow — content reflows to a single column and remains usable at 200% and on small viewports.
§2Known limitations & text alternatives
The plot map (drawing a polygon by pointer) is not fully keyboard-operable — a limitation of the mapping library. Text alternative: you can enter a plot entirely without the map by typing latitude/longitude or by uploading a KML, KMZ or GeoJSON file; the verdict is identical.
The printable due-diligence report is a paper/PDF document optimised for print and audit, not a web page; its accessibility follows document (PDF/UA) practice rather than WCAG for web. The same facts are available on screen.
Third-party map tiles & fonts are self-hosted or avoided so no external, potentially inaccessible, widget is embedded.
§3How we tested
Assessed by manual keyboard and structure review across every page, and by an automated colour-contrast audit computing the WCAG relative-luminance ratio for each token pair against the AA thresholds (4.5:1 normal text, 3:1 large text and UI). We re-run the contrast audit after any change to the palette.
§4Tell us about a barrier
If something blocks you, email avijeet@vortx.ai with the page and what happened, and we will fix it and reply. If you are not satisfied with our response, you can escalate to the accessibility-enforcement body in your EU member state.