Statement

Accessibility at Cantlepost

We want the catalog to be usable by every rider who wants to read it — keyboard, screen reader, magnification, voice control, or just plain mouse and a small phone on a hayloft. This page is written so a screen reader makes sense of it: real headings, a list where a list belongs, and a real link to a real inbox.

1. Our target

We aim to meet WCAG 2.1 Level AA across the pages we publish directly — the catalog, the fit request, the checkout flow, the policy pages you're reading now, and the pages that sit behind sign-in.

In practice that means:

  • Text and background combinations hit at least a 4.5:1 contrast ratio (we lean on the design tokens in the site theme to keep this consistent).
  • Every interactive element is reachable from a keyboard, with a visible focus state.
  • Form fields carry real labels, so screen readers announce them clearly.
  • Images carry descriptive alt text; decorative images are marked as such.
  • The page doesn't trap you — you can get back to where you came from.

2. What's in scope

Our direct scope is the Cantlepost site — the markup, the styles, the interactions we control. The catalog is a moving target: each maker and supplier brings their own product descriptions, photography, and detail copy, and the fit-form answers are entered by individual riders. Where we can, we set the expectations and provide scaffolding; where a supplier's content sits outside our direct control, we'll work with them to bring it in line — but we can't promise third-party content is perfect on day one.

With that honest caveat, here's what we test before shipping:

  • Keyboard-only navigation through the catalog, fit form, and checkout.
  • Screen-reader run-throughs (VoiceOver and NVDA) of the public pages.
  • Zoom and reflow up to 200% without content falling off the page.
  • Form errors announced and recoverable without losing entries.

3. Known limits and things we're working on

We're a small team. Where the site doesn't quite meet the bar, we'd rather say so than wave it off. Today:

  • Supplier-uploaded product photography and long-form descriptions may not yet carry alt text or structured headings; we tag the gaps as we find them and work back through the catalog.
  • Some older PDF fit guides were authored before our current standards; we keep them available as-is while we reissue.
  • The fit request form uses inline validation; we're keeping an eye on how that reads with assistive tech and refining the messaging as it surfaces.

4. Tell us when something's in the way

If a page is hard to use on your setup, we'd genuinely like to hear about it. Send the URL, what you were trying to do, and the assistive tech or browser you were using — we'll dig in.

Email cantlepost@polsia.app.

5. Effective date

This statement applies to the Cantlepost site as of the date below. We revisit it each time we add a new public surface or a new maker comes online with content we publish.

Last updated: 2026-07-21