Skip to main content

A store you can't reach isn't open.

We build FaStart to WCAG 2.1 AA and are moving to 2.2 AA. It isn't certified or audited: it's work we keep doing, and you can tell us where it fails.

The statement

What an accessibility statement should tell you, in one place.

Standard
WCAG 2.1 AA today, moving to 2.2 AA
Conformance
Partial: the core patterns are in place, some flows are still improving
Assessed by
Our own review and automated axe checks; no third-party audit
Formal report
A criterion-by-criterion report is planned, not published yet
Last reviewed
October 2026

In place today

Checked with axe on every page rebuilt since October 2026, in both languages, on phone and desktop. Older pages are being brought up to the same bar.

  • Keyboard and visible focus

    Menus, forms and buttons work from the keyboard, and the focused element always shows a ring.

  • A skip link

    Every page starts with a link that skips past the menu to the content.

  • Headings, regions and labels

    Pages are built from real headings and regions, with labels where a screen reader needs them.

  • Contrast

    Text and background colours are paired and measured for contrast in both the light and the dark scheme.

  • Reflow and zoom

    Pages fit a phone without sideways scrolling and reflow when you enlarge the text.

  • Motion you control

    With reduced motion set on your device, pages show still pictures, and pages that move have a pause button.

  • Live

    Accessibility and performance thresholds

    Accessibility, layout and page-size checks that were run for this site. They don't yet run on every release by themselves.

Commerce should work for everyone.

You can't choose who visits your store. Someone on a keyboard, listening to a screen reader or zooming the text should be able to finish the purchase too.

Three habits for your own store

  • Keep the contrast

    When you change colours, keep text far from its background; avoid pale text on a pale field.

  • Describe your pictures

    Give every product photo a short alt text; screen readers and search both read it.

  • Keep words out of images

    Put prices and offers in text, so they stay readable when someone zooms in.

Tell us where it fails

Write to accessibility@fastart.co. Name the page, what stopped you, and the device and assistive technology you use.

accessibility@fastart.co
  • What happens next

    We treat each barrier like a bug: we reproduce it, and fix first the ones that stop the most people.

  • Another format

    Ask for this statement in large print, plain text or simpler language, and we'll send it.

Questions about accessibility

Is FaStart certified as accessible?
No. We work to WCAG 2.1 AA and assess it ourselves; there's no third-party audit or certificate.
Does it work with screen readers?
We build for them with real headings, regions and labels, and some flows are more mature than others. If something is skipped or unclear, tell us.
When will the formal report come?
A criterion-by-criterion report is planned. We'll publish it here when it's done, not before.

Every shopper should reach the checkout.

If you couldn't, write to accessibility@fastart.co and tell us where.