Accessibility statement
What we have done, and what we have not.
Dayspan aims to meet WCAG 2.2 Level AA. Aiming is not the same as arriving, so this page lists the specific work that exists today and, below it, the parts that are still missing.
Done, and checkable in the code
Text contrast was measured, not eyeballed
Our muted body colour was failing: at #6d7686 on the bone background it measured 4.32:1, under the 4.5:1 AA floor. It was darkened to #5b6473 to clear it. The figure is recorded in the stylesheet next to the value so nobody quietly reverts it.
Touch targets are at least 44px
Navigation links, menu controls, form buttons, and footer links all carry a minimum height of 44 pixels rather than relying on text size, which is the AAA target size and comfortably clears AA.
Charts are described, not just drawn
Every diagram carries a role and a text description of what it shows — the temperature curve, the saturation curve, the shelf grid, the dose charts. Each one also states its point in the prose beside it, so no argument on this site exists only inside a picture.
Wide charts stay legible instead of shrinking
Squeezing an 880-unit chart into a phone column renders its labels at under 5 pixels. Those charts scroll horizontally at close to full size instead, with a visible swipe cue, and the breakpoint was chosen from the measured label size rather than guessed.
Colour is never the only signal
Where a chart distinguishes a result that held from one that did not, it also changes shape — a filled marker against a hollow dashed one — and says which in words.
Structure is semantic
Real headings in order, real lists, real figures with captions, labelled landmarks and form fields, and page sections tied to their headings so a screen reader can navigate by structure.
Not done, stated plainly
No independent audit has been done
Everything above is our own work checked against our own reading of the guidelines. No third party has audited this site, and there is no VPAT. Self-assessment is weaker evidence than an audit, and we would rather label it that way than call ourselves compliant.
Assistive-technology testing is limited
The site has not been tested across a full matrix of screen readers, magnifiers, and voice control. Issues that only appear in that testing almost certainly remain.
The feedback channel is not live yet
An accessibility statement is supposed to give you somewhere to report a barrier. Ours does not have a staffed inbox yet — the same gap the privacy notice records. It publishes before the first campaign email is sent. Publishing an address nobody reads would be worse than admitting this.
Why this page is shaped like this
Most accessibility statements claim conformance and stop. A claim is cheap; the list of what is missing is the part that tells you whether anyone actually looked. This page is held to the same standard as the rest of the site — if we have not done the work, it says so.