Accessibility statement

eudr.dev register · last reviewed 9 October 2026 (every page given a main landmark and a skip link; the landing page's heading restored after hydration; all eighteen application screens walked by keyboard)

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

9 October 2026 (every page given a main landmark and a skip link; the landing page's heading restored after hydration; all eighteen application screens walked by keyboard)

§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 every page a skip-to-content link is the first tab stop. On /app the primary navigation is twenty links, all reachable in order.
Structure — semantic landmarks (header, nav, main, footer), a single h1 per page and an ordered heading outline, and a declared page language. Until 9 October 2026 the main landmark was missing from the thirty-eight pages rendered by the server, and the landing page lost its heading the moment JavaScript replaced the shell; both are fixed and held by tests.
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, GeoJSON, WKT or spreadsheet 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.
The application's main menu (/app) could not be reached by keyboard until 29 September 2026: its items were not links, a Level A failure (WCAG 2.1.1, 4.1.2). A reviewer found it; the items are now real links with an address each, and the keyboard path through /app's home screen was re-measured on 9 October 2026 — sixty-one stops, nothing unreachable, nothing focusable but invisible.
All eighteen application screens were walked on 9 October 2026 and what the walk found is fixed: the portfolio table's rows opened on a click and took no focus; form fields across six screens carried a label that named nothing — <label>EORI</label> beside the field rather than pointing at it, which reads correctly and associates nothing — or had no label at all; the language tabs on /try were text, not buttons. Two gates now hold these — one reads the source on every push, one drives a browser against the live site.
Not yet walked: the field-visit app a scout opens from an SMS link (its labels were corrected from source, but the running app has not been measured), and the supplier intake form. And nothing anywhere has been tested with an actual screen reader — the checks above read the accessibility tree, which is not the same thing as hearing a page read out. Please tell us about anything you cannot reach.
Third-party map tiles & fonts are self-hosted or avoided so no external, potentially inaccessible, widget is embedded.

§3How we tested

Three ways, none of which replaces the others. An automated colour-contrast audit computes 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 it after any change to the palette. A keyboard walk drives a real browser against the live site, pressing Tab and recording what takes focus, which is how the missing landmarks and the lost heading were found; it also reports controls that respond to a click but not to a key, controls with no programmatic name, images with no alternative text, and the heading outline. And manual review of each page's structure. What none of this does is use the service with a screen reader, so §2 says where that is still owed.

§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.