Accessibility
This is a description of implemented features, not a certified accessibility rating or the outcome of an independent audit.
1. Keyboard operation
A skip link leads to the main content. Navigation uses real links; state changes use native buttons and labelled controls. Keyboard focus has a visible outline. The FAQ uses native disclosure elements that can be opened without a mouse.
The mobile date selector and wide table regions can receive keyboard focus or contain focusable links. On the archive, activating a date-index link clears filters and places focus on the requested record when JavaScript is available.
2. Semantic content
Pages use headings, landmarks and a single main heading. Tables have captions, header groups and column labels; date and Euro-count rows also have row headers. The main-number matrix repeats an explicit number-and-count column pair rather than encoding values by colour.
All eight records, the frequency counts and substantive explanations are present in the HTML. They do not depend on images, scripts or visual number graphics.
3. Filters and draft feedback
Filter controls identify their separate number pools. A status region reports the matching count, including zero, and an empty selection has a written explanation. Draft validation uses text messages and moves focus to an invalid field.
The local drafting tool offers a selectable preview when clipboard access is unavailable. Download and copy messages describe only local actions and never claim that a message was sent.
4. Text, layout and motion
System fonts avoid external font requests. Text can wrap, and content widths change at defined breakpoints. Tables may scroll within labelled regions rather than forcing horizontal scrolling across the entire page.
No animation, autoplay or moving ticker is included. A reduced-motion rule disables animation and transitions if any are introduced through ordinary component styling. Colour is not the only indicator of selected navigation or status.
5. Known implementation limits
Local filtering and file tools require JavaScript. Clipboard permission and file-download behaviour vary by browser. A wide matrix may require horizontal scrolling on a narrow screen, and external source sites have their own accessibility characteristics.
No independent assistive-technology audit is claimed. These features do not by themselves establish conformance to a certified level.
6. Prepare an accessibility note
Use the local feedback-draft page to describe the affected page, control and difficulty. Choose the accessibility topic. Avoid personal or sensitive details.
The draft can be copied or downloaded for your own use. It is not sent to a support team and does not create a support ticket.