Accessibility

The target is WCAG 2.1 Level AA. That is a target, not a claim — this site has not been audited, and nobody has yet put a screen reader through a checkout. Below is what is genuinely built in, what is genuinely missing, and how to tell us when we have got it wrong.

What we are aiming at

WCAG 2.1 AA, the version most public-sector and commercial guidance points at. We are not claiming conformance to it. Conformance is something you demonstrate by testing — automated checks, keyboard passes, assistive-technology runs — and none of that has been done here yet. A store that has never taken an order has not earned the word “conformant”.

What is in place today

Each of these is a decision already made in the code, not an intention:

Motion respects your system setting. If your device asks for reduced motion, every animation and transition on the site is switched off, and the one carousel that advances on its own never starts — it holds its first frame rather than cutting between images.
Form controls cannot fall below 16px. Every input, select, textarea and button on the site inherits a 16px floor. Below 16px, iOS Safari zooms the viewport when a field takes focus, which mid-checkout reads as the page lurching sideways and losing your place. The floor is written so a control added later inherits it without anyone remembering it exists.
Real semantics, not styled divs. One main landmark per page, a declared page language, genuine table markup with row headers on the size and care tables, and the checkout and contact fields wrapped in real labels rather than leaning on a placeholder to name them.
Images say what they are, or say nothing on purpose. Product photographs carry the product name; decorative and duplicate images carry an empty alt so a screen reader skips them instead of reading a filename.
Icon-only controls are labelled. The gallery thumbnails, the quantity buttons and the popup close button all carry text labels for assistive technology, and star ratings announce “4 out of 5” rather than a row of glyphs.
Search suggestions are a real combobox. The search field exposes the standard combobox and listbox roles with the active option marked, so the suggestion list is navigable rather than being a visual-only dropdown.
One contrast budget was measured rather than eyeballed. The email-capture panel sits on photographs, so its background opacity was set against the darkest frame behind it to keep body text at 4.69:1 — above the 4.5:1 minimum, with the working shown in the stylesheet.
The cookie banner does not trap you. It is a labelled region rather than a modal dialog, with no scrim: the shop stays fully usable while the question is open, and there is a permanent way back to the choice in the footer.

What is missing, and we know it

These are real, current gaps. They are listed because knowing about them changes what you do next, and because a statement that only lists strengths is marketing.

There is no skip link. Tabbing into a page walks you through the header and the navigation before it reaches the content, on every page. This is the first thing on the list to fix.
There is no site-wide focus style. A handful of components draw their own focus ring; everywhere else you get the browser’s default, which on some of these backgrounds is faint. A single visible focus indicator across the whole site is the second thing to fix.
Nothing has been audited. No automated scan, no keyboard-only pass, no screen reader, no zoom or 400% reflow test, no voice-control test. We have not run them, so we do not know what they would say.
Contrast has been measured in one place, not everywhere. The palette was chosen with contrast in mind and checked properly at the hardest spot; it has not been swept token by token.
There is no dark or high-contrast theme. The single light palette is a deliberate design decision documented in the stylesheet — several surfaces are dark objects photographed on light paper and stop reading as objects if the page inverts — but it does mean a visitor who relies on a dark or forced-colours mode does not get one here, and forced-colours mode is untested.

Telling us about a problem

The contact form — pick “Something else” and say which page and what happened. You do not need to know the standard or name the failure; “the keyboard gets stuck here” is a perfect bug report and more useful than a success criterion number.

That form is not connected to an inbox yet.

Adrenaline has no monitored support address at the moment, and the contact page says so rather than accepting a message and dropping it. Naming a reporting route that nobody reads would make this statement worse than not having one, so we are naming the gap instead.

What is needed: a monitored mailbox for this store. It is the same blocker the contact page and the returns process are waiting on, and it is on the launch checklist ahead of taking money.

When there is one, this page will carry the reply time we actually hold to, and the two fixes named above will be dated rather than described.

The honest summary