Accessibility
We target WCAG 2.2 Level AA, and accessibility is enforced in our build rather than checked occasionally.
Why this matters especially here
This site is built on identification, and identification content that only works visually fails screen-reader users at exactly the point it matters most.
So: every identification works without seeing the image. Every diagnostic feature that decides an identification is stated in body prose, not only in an image callout. Every diagram carries substantive alternative text describing the same features in words. Our build fails if a species page has diagnostic features only in callouts, or if an identification image lacks substantive alt text.
What is enforced automatically
- Contrast validated at build; the build fails on any AA violation. Body copy never sits on blurred glass, and reading surfaces meet 7:1.
- The identification key is fully operable by keyboard and screen reader, and works completely with JavaScript disabled as a static decision table.
- No drag-only interactions anywhere (2.5.7).
- Targets are at least 24×24 CSS pixels, and 44×44 for touch controls (2.5.8).
- Focus indicators are never removed, and use a double ring over any diagram so they stay visible.
- Anchored headings clear the sticky header (2.4.11).
- Help and contact sit in an identical footer position sitewide (3.2.6).
- The key and calculators keep state in memory only, with no storage APIs (3.3.7).
- The treatment verdict never conveys state by colour alone — icon and explicit text always.
prefers-reduced-motion,prefers-reduced-transparency, andprefers-contrastare fully honoured.- Charts carry a role, a label, and a real data table.
Known gaps
We have not completed manual screen-reader passes with NVDA and VoiceOver on every template. Automated testing catches a great deal but not everything, and we would rather say so than imply a level of assurance we have not reached.
We have not licensed specimen photography. Current diagrams are schematic. When photographs are added, each will carry a substantive diagnostic description and the written identification will remain authoritative.
Reporting a problem
If any part of this site is difficult or impossible to use, tell us through the contact page and describe what happened and what you were using. We will fix it and say when.