Accessibility

1. Keyboard operation

Every page starts with a "Skip to main content" link. Navigation, filters, buttons, FAQ disclosures and links are native HTML controls reachable with Tab and operable with Enter or Space. Table wrappers that can scroll sideways are focusable so their content can be moved with arrow keys. Buttons are used for actions and links for navigation; there are no placeholder links.

The storage notice that appears on a first visit is a small non-modal panel added at the end of the page. It does not trap focus or block the content behind it, and both of its buttons are ordinary buttons reachable with Tab.

2. Focus visibility

Focused elements show a 3px amber outline with an offset, visible on both the grey and white backgrounds. Headings and record sheets carry scroll-margin-top so that anchors and the sticky filter rail do not hide the target.

3. Structure, tables and labels

• One H1 per page; landmarks for header, navigation, main, aside and footer; breadcrumb navigation on inner pages.
• Tables use caption, thead, tbody, tfoot and scope on header cells. The frequency tables list every number from 1 to 50 and 1 to 12, including zero counts.
• Every form control has a visible label. Error messages are text placed next to the field and announced through a live region; they do not rely on colour alone.
• Number pools are ordered lists with descriptive labels, and the Euro pool is distinguished by both text and an amber rule.
• Body text is 18px on desktop and 16px on small screens with line-height around 1.6; long prose is limited to roughly 68 characters per line.

4. Motion and colour

The only transitions are 150ms colour and underline changes on links and buttons. Under prefers-reduced-motion: reduce they are disabled. No content starts hidden, and there are no animated counters, tickers, autoplaying media or scroll effects. The retro visual style uses hard shadows and bevelled borders, which are decorative; text and background colours (black and navy on grey and white, amber accents in their darker shade for text) were chosen to meet a 4.5:1 contrast ratio for normal text.

5. Without JavaScript

All records, tables, guides and legal text are present in the HTML. Filters, CSV download and the contact draft need JavaScript; where they do, a visible note says so, and the underlying information remains readable. The storage notice is added by script and is simply absent without it, which is safe because nothing is stored without your pressing its OK button.

6. Known limitations

• No independent assistive-technology audit has been carried out on this build; screen-reader behaviour of the live regions should be confirmed by the deployment team.
• The 50-row frequency table is long; a summary of non-zero counts is not provided separately, though the totals row is.
• The <details> FAQ relies on native browser behaviour, which varies slightly between browsers.
• The storage notice is positioned in a page corner and, on very small screens, may cover the bottom of the content until it is closed with either of its buttons.

7. Reporting a problem

Use the local feedback-draft tool and choose the topic "Accessibility issue". The tool prepares text on your device and does not send a message; it is not a support ticket. A real reporting channel is a pre-launch dependency for the site operator.