We want everyone to be able to read about our vinegar and buy it, including people using a screen reader, a keyboard, magnification, or a browser tuned to their own needs.
Last updated 13 August 2026.
The standard we build to
We aim to meet WCAG 2.2 Level AA. We treat that as the working standard for new work on the site, not as a badge — where we fall short of it, we would rather say so than claim otherwise. This statement covers pomevinegar.com.
What we have done
- The site is built from semantic HTML with a proper heading order, so a screen reader can navigate it by structure.
- Everything works by keyboard, and the focus outline is deliberately visible — including on dark sections, where a default outline would disappear.
- A skip link takes you straight to the main content.
- Colour is never the only thing carrying meaning. Each vinegar has an accent colour, but the product is always named in text as well.
- Body text meets AA contrast against its background, and the type is set at a comfortable size and measure rather than a fashionable one.
- Images that carry information have alternative text describing what is actually in them. Decorative images are marked so a screen reader skips them.
- Text reflows and stays readable when you zoom or use a small screen; nothing depends on hovering.
- Form fields have real labels, and errors are described in words rather than by turning a box red.
Where we know we fall short
An honest statement needs this section.
- The payment fields at checkout are hosted by Stripe and rendered inside their frames. We can style them, but we do not control their markup or their behaviour with assistive technology. If you hit a barrier there, please tell us — we will report it to Stripe and help you complete your order another way in the meantime.
- The site is young and still being built. Some photography is still being commissioned, and pages added later may not yet have had the same review as the ones here today.
- We have not yet completed a full independent audit or testing with a broad range of assistive technologies. Our checks so far are our own.
Tell us when we get it wrong
If any part of this site is hard to use, we want to hear about it — it is the fastest way for us to find the problems our own testing misses. Use our contact page and tell us what you were trying to do, which page you were on, and what got in the way. If you can tell us the browser and any assistive software you were using, that helps us reproduce it.
We read every one of these and will reply. If something we have built is stopping you from ordering, say so and we will take the order directly rather than leave you stuck.