Accessibility statement
Last updated 24 September 2026
What we test, and what we know is still wrong. If something on this site doesn’t work for you, tell us.
The standard we aim for
Level AA of the Web Content Accessibility Guidelines, version 2.2, known as WCAG 2.2 AA. It applies to every page, in English and in Georgian.
What this statement covers
This website, in both of its languages: the shop and the destination pages, checkout, sign-in, your account and order pages, the help centre and the legal pages. Card details are entered on our payment provider’s own page, which we don’t build and haven’t tested. We don’t have an app.
How we check it
- Automated accessibility tests using axe run against our interface components and pages. A test fails on any serious or critical problem it finds.
- Keyboard and focus: controls show a visible outline when they have keyboard focus, dialogs move focus inside when they open and hand it back when they close, and every page starts with a link that skips straight to its content.
- Touch targets: on a phone-sized screen, buttons, menus and links that stand on their own are at least 44 pixels tall, and an automated check refuses any control whose minimum height on a phone is set lower. A link inside a sentence is the size of the text around it. On wider screens, where a mouse is more likely, some header controls and links are shorter than 44 pixels.
- Contrast: every pair of text and background colours in our design system is measured against the WCAG ratios: 4.5 to 1 for text, and 3 to 1 for the edges of controls and the focus outline. If a pair falls short, a check fails.
- Motion: if your device is set to reduce motion, animation stops rather than slowing down.
- Languages: English and Georgian are checked the same way, and a test fails if a message exists in one language but not the other.
- On 23 September 2026 we ran axe in a browser against the WCAG 2.2 A and AA rules on our main pages, at desktop and phone widths and in both languages. It found no violations.
What we know is not right yet
- We haven’t yet tested with screen readers such as VoiceOver and TalkBack, or on real phones and tablets. So far our checks are automated or done in a desktop browser.
- No independent accessibility audit has been carried out.
- The site has a light appearance only. It doesn’t follow a dark mode setting on your device.
- If you open an address that doesn’t exist, the page telling you so appears only once JavaScript has run. Without JavaScript it is blank.
Tell us about a problem
Email us about any problem you meet on this site.
Include the web address of the page, what you were trying to do, and the device, browser and any assistive technology you use.
How the site is built
The pages are HTML and CSS, with JavaScript for the parts that respond as you use them, and WAI-ARIA where plain HTML can’t describe a control on its own. Most pages are put together on our server, so their content arrives as HTML.