Accessibility
— Conformance, Gaps & Feedback —
A reference site is only useful if you can actually read it. Prospector's Almanac targets WCAG 2.1 Level AA, and accessibility checks run automatically as part of the build.
Last updated
Conformance target
We aim to meet WCAG 2.1 Level AA. We describe the site as partially conformant: automated testing covers a representative set of pages on every change, but automated tools cannot catch everything, and no full manual audit has been carried out. Claiming complete conformance would overstate what has been verified.
What we do
- Automated testing in CI. Every build runs axe against representative pages — the homepage, a catalogue, an entry page, and each interactive tool — and fails on any critical or serious violation.
- Semantic HTML first. Pages are built from real
headings, lists, tables, and landmarks rather than styled
divs, so screen readers and keyboard navigation work without special handling. - Keyboard access. Every interactive control — search, sortable tables, the planner — is reachable and operable without a mouse.
- Contrast. Text colours are checked against their backgrounds to meet AA contrast ratios.
- No JavaScript required to read. Content pages are plain HTML. If scripts fail or are blocked, the information is still there.
- Respecting your settings. The site uses relative units so browser zoom and custom text sizes work normally.
Known limitations
Being straight about the gaps is more useful than a blanket claim:
- Wide data tables scroll horizontally on small screens. They're marked up correctly and readable by screen readers, but comparing many columns on a phone is awkward.
- The equipment planner is a complex interactive tool. It's keyboard-operable, but it hasn't been tested end-to-end with every screen reader.
- Game imagery carries descriptive alt text where an image conveys information, but decorative art may be marked decorative rather than described.
- No full manual audit has been done — testing to date is automated plus keyboard spot-checks.
Tell us about a problem
If something on this site is hard or impossible to use, please say so — it's treated as a bug, not a feature request. Telling us the page, what you were trying to do, and what you use to browse (screen reader, keyboard only, magnification) helps most.
We aim to reply within a few days. Accessibility reports are prioritised alongside data corrections.