Accessibility
Accessibility at Assembly
Assembly exists for families who are being failed by systems that weren't designed around them. An inaccessible website would be a strange way to start. Here's what we do, and, further down, our contrast working shown live rather than asserted.
Our commitment
We aim for WCAG 2.2 level AA across this site, and we track the perceptual contrast model (APCA) that underpins the emerging WCAG 3 alongside it. Where the two standards disagree, we say so openly below instead of quietly picking whichever suits us.
Keyboard first
Every page works with a keyboard alone: a skip-to-content link, visible focus rings, and menus that open, close and return focus predictably (Escape included).
Semantic structure
Proper landmarks on every page, one main, labelled navs, real headings in order, so screen readers get the same map sighted visitors do.
Motion is optional
Scroll animations respect prefers-reduced-motion. Turn it on and content simply appears; nothing is hidden behind an animation.
Readable by design
Body text at 18–20px on long-form pages, line lengths capped near 66 characters, and text that zooms to 200% without breaking.
Found something that doesn't work for you, a screen reader snag, a contrast problem, a keyboard trap? Email info@helloassembly.com and we'll fix it. Accessibility reports get the same priority as bugs, because they are bugs.
The contrast lab
Colour contrast has two rulebooks right now. WCAG 2.2 uses a luminance ratio designed in the 2000s: simple, testable, and famously wrong about one thing, it over-rewards dark text on saturated mid-tone colours, which is why it insists the world's orange buttons should carry black text that no design team believes is more readable. APCA (the Accessible Perceptual Contrast Algorithm, the candidate model for WCAG 3) models how vision actually responds to polarity, font size and weight.
Below, every colour pair on this site is measured in your browser, right now, against both. Nothing is precomputed, flip your system to dark mode and the numbers remeasure.
| Component | Sample | WCAG 2.2ratio · AA verdict | APCALc · verdict |
|---|---|---|---|
| The live measurements need JavaScript, this table measures the rendered colours in your browser rather than quoting precomputed numbers. With scripts off, the short version: every text/background pair on this site passes WCAG 2.2 AA at the level it's used at, including the peach call-to-action, whose story is told openly in the next section. | |||
Measured from computed styles in this browser session. WCAG 2.2 AA requires 4.5:1 for normal text and 3:1 for large text (≥24px, or bold ≥18.7px). APCA verdicts use the draft bronze thresholds: Lc 75 for body text, Lc 60 for large/bold text, Lc 45 for very large display text.
The peach button, honestly
Our primary call-to-action used to be white text on a warmer peach. WCAG 2.2's formula scores that around 2.3:1, a hard fail, and scores near-black text on the same peach around 8:1, a resounding pass. APCA measures the same two options and finds them nearly equivalent, and in fact the "compliant" black text fails the perceptual model, because the old formula dramatically overestimates how readable dark-on-orange really is. That disagreement, times every orange button on the internet, is a big part of why WCAG 3 is replacing the formula.
We refused to pretend the black-on-peach button was the accessible one, and we also refused to keep a button that failed both rulebooks. So we did the work and shipped the third option: a slightly deeper peach with large bold white type that satisfies both standards. All three, with their scores measured live in your browser:
Where we started
Get startedWhat WCAG 2.2 asks for
Get startedToday's button, passes both
Get startedThe third button is the one live across this site and the Assembly app (shipped July 2026). It keeps the brand where the brand lives, a warm peach pill with confident white type, while clearing WCAG 2.2 AA's large-text threshold (3:1 at bold ≥18.7px) and APCA's level for large bold text, which is why every CTA renders its label at 19px bold. Standards met, soul intact. The change is also pinned by an automated contrast gate over our colour tokens, so it can't quietly regress.
Where we stand
This statement covers the marketing site at assemblyhealth.co.uk and was last reviewed in July 2026. We test with keyboard-only navigation, screen readers and automated tooling as part of development, not as a yearly audit. The Assembly app has its own accessibility work, held to the same bar. If anything here doesn't match your experience, we want to know: info@helloassembly.com .