Accessibility
Reading and operating the catalogue
1. Keyboard controls
The implementation uses ordinary links, buttons, inputs and selects rather than simulated clickable panels. A skip link leads to main content, and interactive elements have visible focus outlines. FAQ answers use native details and summary controls, which can be opened with the keyboard.
The numbered balls in Lucky Number Reveal are buttons operated with Enter or Space. A revealed ball stays available to keyboard focus with its result in its accessible label. Try another resets the balls and returns focus to the first one. The cookie banner is a labelled, non-modal region; it does not trap keyboard focus or prevent reading the page. Cookie settings in the footer reopens it.
2. Headings, labels and tables
Each page has a single main heading and labelled navigation. Form fields have visible labels. Frequency tables have captions, column headings and row headings. Main and Euro numbers are identified in text, not by colour alone. Matching-record counts and draft status messages use live status regions.
Revealed numbers are also announced in a live status region with their source record. Decorative stars and celebration particles are hidden from assistive technology; their colours convey no required information.
3. Readable layouts and motion
Wide catalogue columns stack on smaller screens. Long text can wrap, and table regions allow local horizontal scrolling if needed without removing columns. System fonts avoid external font requests. The build has no autoplay sound, flashing lights or continuous animation. Short button, card and number animations respond to interaction.
The reduced-motion preference disables animation and transitions. The reveal activity then shows the number immediately without a shake, moving flip, bouncing counter or celebration particles. Revealed values and source links remain available.
4. Content without JavaScript
All eight archive records, source links, guides, questions and answers, and frequency values are in the HTML. Filters, exports and correction-draft preparation need JavaScript and are disabled when it is unavailable. Clipboard permission or download restrictions may require manual copying from the prepared-text field.
The optional Lucky Number Reveal activity, shared favicon enhancement and cookie banner are added by the shared script. Without JavaScript, the activity and banner are absent and no banner choice is stored. The underlying catalogue remains readable.
5. Assessment limits and issue notes
No certified accessibility level or completed independent audit is claimed. Browser and assistive-technology combinations may behave differently, so implemented features are not a guarantee of an issue-free experience.
The local feedback-draft tool includes an Accessibility issue topic. You can describe a page, control and observed problem without personal information. This prepares a note on your device; it does not send a support ticket or promise a response.