Accessibility
Last updated: [DATE]
What we aim for
This site was built to meet WCAG 2.2 Level AA. That is the standard we designed and coded against, from colour contrast to keyboard order to the way form errors are announced.
We do not claim the site is fully compliant or usable by everyone. No site can honestly claim that. What we can tell you is what we built to, how we tested it, and what to do when something gets in your way.
How we test
Every page template is scanned automatically for accessibility problems on each release, at desktop and phone widths, and the scan has to come back clean before anything ships.
Automated scanning catches only a minority of real problems, so we also check by hand: moving through each page with the keyboard alone, with motion reduced, with scripts disabled, and with a screen reader. [CONFIRM: which screen readers and browsers, and the date of the last manual pass.]
We have not yet had an independent audit. When we do, the result will be summarised here.
What we know is not right yet
[LIST KNOWN BARRIERS.] Keeping this list honest and current matters more than keeping it short. If it is empty at launch, that is because nothing is known, not because nothing was looked for.
The accessibility widget
The toolbar on this site can enlarge text, increase contrast, stop animations and adjust spacing. It is there for comfort. It is not the basis of our accessibility claim, and the site is built to work properly with it switched off and with your own browser or operating system settings instead.
Tell us about a barrier
If something here stopped you doing what you came to do, we want to hear about it, and we will tell you what we are going to do rather than just thanking you for the feedback.
Email [ACCESSIBILITY EMAIL] or call [PHONE]. Tell us the page and what happened. We aim to reply within [N] business days, and if we cannot fix something quickly we will offer another way to get it done — including taking your order over the phone.
