Legal
Accessibility statement
Our target is WCAG 2.1 Level AA. This page says how far we have actually got, and how we know — including the parts we have not tested.
Partial conformance
We do not claim full WCAG 2.1 AA conformance, because we have not verified it. Accessibility has been built into this site deliberately, and 5 of the 8 areas below have been checked and hold up. The rest have not been tested.
The most significant gap is the honest one to lead with: this site has never been tested with a screen reader. Its markup was written and reviewed for it, but that is a reasonable expectation rather than a result, and we are not going to describe it as one.
Area by area
The evidence column is the point of this table. A claim without a method behind it is not a claim we will make.
| Area | Status | How we know |
|---|---|---|
| Semantic structure | Verified | Every page checked in the served HTML for one <h1>, headings that descend without skipping, and correct landmarks. Article body headings are forced to h2–h6 so an author cannot break the outline from the editor. |
| Colour contrast | Verified by design | Body text and controls use a fixed token palette checked against 4.5:1 (and 3:1 for large text and control borders). White-on-gold is banned outright at the design-system level because it measures about 2:1 — gold buttons carry rich-black text. |
| Information not carried by colour alone | Verified | Error states pair colour with an icon and text. Product badges and order statuses are words, not colour swatches. |
| Form labelling and errors | Verified by inspection | All forms use one shared field component: labels bound with htmlFor/id, never a placeholder standing in for a label; error regions always mounted with aria-live so a message that appears after render is announced; focus moved to the first error on a failed submit. |
| Reduced motion | Verified | A global prefers-reduced-motion rule collapses transitions and removes image hover zoom. Transitions sit in the 150–250ms band. There is no autoplaying media and no infinite scroll anywhere. |
| Keyboard operation | Not verified | The code is written for it — a visible focus ring on every control, focus moved to the first error, disclosures built on native <details> so the browser provides keyboard behaviour rather than us reimplementing it. But nobody has tabbed through the site. No browser automation is installed and this has never been done by hand. |
| Screen readers | Not verified | No testing with NVDA, JAWS or VoiceOver has been carried out on any page of this site. Markup has been inspected repeatedly and follows the patterns that usually produce good results, but inspecting markup is not the same as listening to it, and we are not going to present it as though it were. |
| Zoom and reflow at 320px | Not verified | Layouts are single-column below the tablet breakpoint and use relative units, and one real 320px overflow bug was found and fixed by measurement during Epic 1. The full range of pages has not been re-checked at that width since. |
What happens next
A screen-reader pass with NVDA and VoiceOver, and a keyboard pass across the main flows, are the outstanding work. This page will be updated with what they find — including anything that turns out to be worse than expected.
We are not putting a date on that, because we have not committed to one and a date here that slipped would be its own broken promise.
If something blocks you
Tell us what you were trying to do and what got in the way, and what you are using to browse — that last part is usually the most useful thing. We will work around it for you in the meantime, by phone or message, rather than leaving you waiting for a fix.