Accessibility Statement

The standard we build to

This site targets the Web Content Accessibility Guidelines version 2.2 at Level AA. That includes the newer criteria on focus visibility, dragging alternatives and minimum target size, not only the older 2.1 set.

Accessibility is checked as part of the build rather than audited once and forgotten. Automated checks run against every page, and the color system fails the build if any text or interface pair drops below the required contrast ratio.

What that means in practice

Page content renders and is readable with JavaScript disabled. Navigation, the full text of every page, and the frequently asked question answers are all present in the markup rather than injected by script.

Every interactive element is reachable and operable by keyboard, with a visible focus outline that meets contrast requirements against both light and dark backgrounds. A skip to content link is the first focusable element on every page.

Touch targets are at least forty four by forty four pixels and form fields are at least forty eight pixels tall. Form labels are properly associated, errors are announced through a live region, and required and invalid states are exposed programmatically rather than only through color.

• Readable with JavaScript disabled
• Full keyboard operation with visible focus
• Skip to content as the first focusable element
• Touch targets at least forty four pixels
• Errors announced, not signaled by color alone
• Motion respects the reduced motion preference
• No horizontal page scroll at any viewport width

Known limitations

The embedded map in the footer and on the contact page is a third party iframe. Its internal controls are outside our ability to modify. Every piece of information that map conveys, meaning the address, the hours and the phone number, is also present as plain text on the same page, and the Open in Maps link gives a direct route out to the full mapping application.

Photography slots on the gallery pages currently render as described placeholders. Each one carries a full text description of what belongs in it, so a screen reader user gets the same information a sighted user does.

How to report a barrier

If any part of this site prevents you from getting what you need, call the shop and tell us. We will handle whatever you were trying to do by phone immediately, and we will fix the underlying issue on the site.

Reports about a specific page are most useful if you can tell us the page address and what you were trying to do. Reports about assistive technology are most useful if you can tell us which one you use.