Conformance target

We target Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. That is the standard this site is built and tested against.

Measures we have taken

Semantic structure. Pages use real headings in order without skipped levels, landmark regions, lists for lists, and tables with proper header associations.
Keyboard operation. Every interactive element can be reached and operated by keyboard. Focus indicators are visible and high contrast. A skip link is the first focusable item on every page.
Contrast. Every text and background pair, and every non-text interface element, is validated to AA contrast ratios across the whole color system before a component ships.
Works without JavaScript. Content and navigation remain reachable with JavaScript disabled. The FAQ accordions use native disclosure elements, and the service request form submits without client-side scripting.
Touch targets. Interactive elements are at least 44 by 44 pixels.
Forms. Every field has an associated label. Required and invalid states are conveyed programmatically, not by color alone. Errors are announced through a live region and describe how to fix the problem.
Motion. The site respects the reduced motion preference. There is no auto-playing or auto-rotating content.
Dragging alternatives. No function requires a dragging gesture.
Reflow. The layout works down to 320 pixels wide with no horizontal scrolling. Wide tables scroll inside their own container rather than forcing the page sideways.

Known limitations

We want to be straightforward about where gaps remain.

Embedded maps. The Google Maps embed on the contact page and in the footer is a third-party component whose internal accessibility we do not control. The full address is provided as text immediately adjacent to it, and directions are described in writing, so no information is available only through the map.
Photography. Photographic galleries are not yet published. When they are, every image will carry descriptive alternative text.
Third-party spam prevention. The form uses a spam prevention widget from an external provider. If it presents a barrier, call the shop and we will take your details by phone.

Assessment approach

This site is assessed through automated testing during development and manual keyboard and screen reader testing. Automated testing catches roughly a third of accessibility issues, which is why manual testing is part of the process rather than an optional extra.

Alternatives

Everything on this site can be handled by phone. If any part of the site prevents you doing what you came to do, call the shop during opening hours and we will help directly.

Feedback

If you encounter an accessibility barrier here, please tell us. Include the page address and what happened. We treat accessibility reports as bugs and prioritize them accordingly, and we will acknowledge your report and tell you what we intend to do about it.

Accessibility Statement