Statement

Accessibility

Last audited: 29 June 2026

Snippets is for total beginners — and that includes making the website itself as easy to use as the kits. We design and build to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. This page describes what we've done, what we're still working on, and how to tell us when something isn't working for you.

What we've done

Structure and semantics

Every page uses semantic HTML — one <h1>, logically ordered headings, landmarks ( <main>, <nav>, <footer>), and lists where content is genuinely list-like.
A visible skip link appears at the top of every page when focused, so keyboard users can jump straight to main content.
The <html> element carries lang="en".

Keyboard navigation

Every interactive element — links, buttons, form fields, accordions — is reachable and operable by keyboard alone.
Focus order follows the visual reading order.
Focus rings are always visible: a solid pattern-blue outline appears on any focused element. We never suppress the focus indicator with outline: none without a styled replacement.

Color and contrast

Body text (#1B2235 ink on #FBF9F4 tissue) meets the 4.5:1 minimum contrast ratio for normal text.
Our amber accent color (#E5A23A thread) is used only for large graphic/decorative elements and the stitch-line divider — never for body text on light backgrounds, where it would fail contrast.
Information is never conveyed by color alone.

Images and media

All meaningful images carry specific, truthful alt text that describes what's actually in the frame.
Purely decorative images and SVG illustrations are hidden from assistive technology (aria-hidden="true" or empty alt).
The site uses no auto-playing audio or video.

Motion and animation

All animation — scroll reveals, the stitch-line draw, the smooth scroll — respects your operating system's Reduce Motion preference.
Under reduced motion, animations degrade gracefully to static states. Hero content is always visible immediately and never gated behind a JS animation completing.
Nothing on the site flashes more than three times per second.

Forms

Every form field has a visible, programmatically associated label.
Inline error messages are linked to their field via aria-describedby and marked with aria-invalid.
Success and error states are announced to screen readers.

No accessibility overlay widgets

We do not use, and will not use, third-party accessibility overlay or toolbar widgets (such as accessiBe, UserWay, AudioEye, and similar products). These tools often introduce new barriers rather than removing them, and they are not a substitute for building accessibly from the start. Our accessibility work is done in the code itself.

Ongoing audits

Before each release, this site is audited with axe-core (automated WCAG checks) at both desktop (1440 px) and mobile (390 px) viewport widths, and reviewed manually for keyboard operability and screen reader behavior. The date above reflects the most recent completed audit. Audits are ongoing and updated with each significant release.

Known limitations

This is a pre-launch site. The interactive stitch demo ("Wonky is impossible") includes a keyboard-operable alternative for reduced-motion users; its full mouse/touch interaction is being iteratively improved for touch-based assistive input. We'll update this section as issues are resolved.

Tell us if something's hard to use

If you find any part of this site difficult to use, we want to know and we'll work to fix it. You can reach us:

Contact form: use the form on this site and describe the barrier you encountered.
Email: [hello@snippets — placeholder; confirm before launch]

We aim to acknowledge accessibility reports within two business days and to address critical barriers as quickly as possible.