Company

Accessibility Statement

How we have approached accessibility on this website, what has actually been built in, where we know the gaps are, and how to tell us about a barrier you run into.

Request a Design Consultation Request a consultation

Our approach

What we are committing to

We have built this site against the Web Content Accessibility Guidelines 2.1 at Level AA as a working target, and we have tested specific things rather than assuming them.

What we are not claiming: that the site is fully conformant, that it has been independently audited, or that it carries any certification. None of those would be true, and an accessibility statement that overstates is worse than none at all.

What we are saying is that the measures below are implemented and were verified, and that we would like to hear about anything that does not work for you.

What has been built in

Measures implemented and verified

Each of these was tested rather than assumed.

Keyboard navigation and focus

Every interactive element on the site is reachable and operable by keyboard. Navigation menus use real buttons with aria-expanded state rather than hover-only behaviour, so they work without a pointing device. The mobile menu traps focus while open, closes on Escape, and is marked inert when closed so its links are not reachable by keyboard while hidden.

Focus indicators are visible: a 2px outline in the site's accent colour, which measures 8.2:1 against the page background — comfortably above the 3:1 minimum WCAG 2.2 sets for focus indicators.

  • All interactive elements are keyboard reachable and operable.
  • Disclosure menus use real buttons with aria-expanded.
  • Mobile menu: focus trap, Escape to close, inert when closed.
  • Visible focus ring measured at 8.2:1 contrast.

Contrast and legibility

Text contrast was measured across fifteen distinct text roles on the site rather than estimated from the palette. All fifteen pass their WCAG AA threshold. The smallest supporting text on the site measures 5.12:1 against its background, against a 4.5:1 requirement; body and heading text sit considerably higher.

  • Fifteen text roles measured; all pass WCAG AA.
  • Smallest text measured at 5.12:1 against a 4.5:1 requirement.
  • Measured with a contrast calculation, not judged by eye.

Forms

Every form field has a real associated <label> element — none rely on placeholder text as a label. Required fields are marked in the label itself as well as with the required attribute. Grouped checkbox options sit inside a <fieldset> with a <legend>. Form inputs render at 16px on mobile, which prevents iOS from zooming on focus and losing the user's place.

  • Every field has a real associated label element.
  • Required state marked in the label and in markup.
  • Grouped options use fieldset and legend.
  • Inputs at 16px on mobile to prevent focus zoom.

Responsive layout and tap targets

Layouts were tested in a browser at 320, 360, 375, 390, 414, 768 and 1440 pixels wide. There is no horizontal scrolling at any of those widths, and no element extends beyond the viewport. Standalone interactive controls measure at least 44px in their smaller dimension.

Links inside a sentence render at line height and are exempt from that target size under WCAG 2.5.8; every standalone control was corrected where measurement found it short.

  • Tested at seven viewport widths; zero horizontal overflow.
  • Standalone controls measure at least 44px.
  • Inline sentence links exempt under WCAG 2.5.8.

Motion and structure

Scroll-triggered fade animations are fully disabled when a visitor's system indicates prefers-reduced-motion, and content is visible without them — the animation is an enhancement, not a requirement for reading the page. Every page has exactly one <h1> and a logical heading order beneath it. FAQ sections are built from native <details> elements, so every answer is readable with JavaScript disabled.

  • prefers-reduced-motion fully honoured; content visible without motion.
  • Exactly one h1 per page, with logical heading order.
  • FAQs are native details elements, readable without JavaScript.
  • All navigation is in the HTML and works without JavaScript.

Being honest

Where we know there are gaps

An accessibility statement that lists only successes is not much of a statement.

No independent audit. The testing described above was carried out by us during the build. It has not been reviewed by an external accessibility specialist and it has not been tested with real assistive technology users, which is the test that matters most.

Screen reader testing has been limited. Semantic structure, labelling and keyboard operation were built and checked deliberately, but we have not run comprehensive testing across the major screen readers.

Third-party content. Some elements of the underlying e-commerce platform are outside our direct control, and we cannot guarantee their conformance.

This site is a work in progress. Pages are still being added. New content is built to the same standards, but each addition is a new opportunity to get something wrong.

Tell us

If something on this site does not work for you

We would genuinely like to know. If you hit a barrier — something unreachable by keyboard, text you cannot read, a form you cannot complete, or anything else — please tell us through the consultation form and describe what happened.

You do not need to be a prospective customer to use it, and you do not need to know the technical cause. Telling us which page and what you were trying to do is enough.

It is currently the only contact route published on this site. When a business email and phone number are published, they will appear here and in the footer as alternatives.

Tell us about a barrier

Start a project

Ready to talk through your space?

If you came here for the accessibility statement and stayed for the screens, the consultation form is the way to start.
Request a Design Consultation