Skip to content
NatureHQ

Accessibility

What is guaranteed, what has been tested, and what has not. The third list matters as much as the first.

What is built in

  • One h1 per page, with headings that descend in order.
  • A skip link as the first focusable element on every page, visible when focused.
  • Every expandable region is a native <details>, so keyboard operation, focus order and assistive-technology semantics come from the browser rather than from us. The evidence layers work with JavaScript disabled.
  • Focus is never removed; a 2px outline with offset is applied globally.
  • Colour is never the only signal. Every evidence badge, verdict and peer-review label pairs its colour with a word.
  • Search results and copy confirmations announce through polite live regions.
  • Wide tables scroll inside their own container; the page body never scrolls sideways.
  • prefers-reduced-motion disables smooth scrolling and collapses transitions.
  • Dark mode follows the system setting, with a separately checked token palette.

What has been tested

An automated audit runs against the built HTML of thirteen routes — one for every page type — on every check. It uses axe-core against WCAG 2.0 and 2.1 at levels A and AA, plus best-practice rules. It currently reports no violations.

That audit is not decoration. On its first run it found seven real defects, including heading levels that skipped from h2 to h4 and duplicate navigation landmarks with identical names — all fixed.

What has not been verified

These are genuinely open, and are not claimed:

  • Colour contrast has not been measured. The automated tool cannot compute used colours without a full rendering engine, so that rule is disabled and reported rather than passing silently. Contrast was chosen from a token palette and reasoned about, not measured.
  • Touch target sizes and scrollable-region focusability — same reason.
  • No screen-reader testing has been performed. Not with VoiceOver, not with NVDA, not with anything.
  • No keyboard-only walkthrough has been recorded by a person.
  • No testing on real mobile devices; responsive behaviour has been checked at breakpoints only.

If something does not work

Accessibility problems are treated as defects, not suggestions. Please report them through the corrections page, describing what you were trying to do and what assistive technology you were using.