Accessibility.

Text sits over a moving field, not a flat colour, so contrast is held against the brightest part of that field and not against its average. Measured there, with a sample placed on the worst patch the field produces, the faintest tone in the type ramp comes back at 4.8:1 at night and 5.0:1 in daylight, and body text at 7.5:1 and 10.3:1. WCAG AA asks for 4.5:1. Those are the hard-case figures. Against the flat ground, away from the field’s brightest moment, every one of them is higher.

Both themes are designed. Neither is the other one inverted, and the site opens in whichever you last chose.

A skip link is the first thing the Tab key reaches on every page, and it moves focus as well as the viewport. You land in the content instead of watching it scroll past while focus stays behind.

Interactive components are reachable and operable without a pointer. The capability strip on the homepage takes the arrow keys, Home and End, announces which plate is current, and hands the scroll back to the page at either end instead of trapping it.

If your system asks for reduced motion, the site listens: the background field stops animating, scroll reveals resolve immediately, and in-page links jump instead of gliding. There is no carousel that advances on its own, nothing flashes, and nothing moves faster than the page you are scrolling.

Every page is static HTML and readable with scripts disabled. Content that would otherwise fade in on scroll is rendered in its final state instead, so nothing is hidden waiting for an animation that will not run.

One exception, and it is an interaction rather than an animation: the capability panels on the instrument page are an accordion, so with scripts off you get every panel’s name and number and the body of the one that opens by default. The same material is on this site as running prose elsewhere.

This site has not had an independent accessibility audit, and it has not been tested end to end with a screen reader by someone who uses one daily. The measurements above are ours. Saying so is cheaper than claiming a conformance nobody has checked, which is more or less the argument the rest of this site makes about datasets.

If something here does not work for you, write to accessibility@staticsignal.co.uk. We reply within seven working days, and a report that names the page and what you were using is the fastest route to a fix.