Legal

Accessibility statement

VERSION 1.0 LAST UPDATED: 18 JUNE 2026 TARGET: WCAG 2.2 AA

1.Our commitment & scope

This statement applies to the Supername website (the pages under supername.com). Supername Ltd wants everyone to be able to research, buy and run campaigns here — including people using screen readers, keyboard-only navigation, magnification, voice control, or reduced-motion settings.

Accessibility for us isn’t a compliance checkbox: our customers are local business owners of every age and ability, often on old phones in the back of a shop. The site is built for them first.

🟢The plain-English versionEverything on this domain should work for everyone — that’s the bar, and it’s a product decision, not just a legal one. (If this summary and the statement ever disagree, the statement wins.)

2.Conformance status

We aim for conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 level AA. This website is partially conformant: most content meets the standard by design, but it has not yet been formally audited by an independent third party and some known limitations remain (section 4). We intend to commission an independent audit and will update this statement with its findings.

🟢The plain-English versionBuilt to AA on purpose, not yet certified by an outside auditor — and we say so rather than rounding up. (If this summary and the statement ever disagree, the statement wins.)

3.What’s built in

Works without JavaScript. All content is visible and readable with scripts disabled or failed; animations and interactive extras are progressive enhancements, never gatekeepers.
Keyboard operable. Menus, accordions, calculators and forms are reachable and usable by keyboard, with a visible focus indicator (a high-contrast outline) on every interactive element.
Reduced motion respected. Every animation — scrolling tickers, marquees, pulses, reveals — is disabled when your system sets prefers-reduced-motion, with scrolling alternatives where content moves.
Semantic structure. Proper landmarks, heading hierarchy, native disclosure elements (<details>), labelled form fields, and aria-expanded/aria-label on toggles and icon buttons.
Readable by design. Scalable rem typography that honours browser text-size settings, generous line-height, and a colour system designed against AA contrast on body text.
Subtitled video, as policy. Creator videos produced through our campaigns are required to carry subtitles as part of the quality bar — it’s a payout condition, not a nice-to-have.

🟢The plain-English versionNo-JS safe, keyboard-friendly, motion-respecting, screen-reader-structured — and the campaign videos themselves must be subtitled before a creator gets paid. (If this summary and the statement ever disagree, the statement wins.)

4.Known limitations

Decorative emoji. We use emoji as visual texture; most are marked decorative, but some may still be announced by screen readers. We are sweeping these to aria-hidden where they carry no meaning.
Placeholder media. Video slots currently show placeholders; when real campaign videos are embedded, each will require captions and a text alternative before going live.
Small-text contrast. A small number of muted monospace labels may fall below AA at their smallest sizes on tinted backgrounds — under review as part of the audit.
Third-party surfaces. WhatsApp, Stripe checkout and any embedded scheduling tools are outside our control; we link to providers with their own accessibility commitments and offer alternatives (email, phone) for every third-party step.
Charts. Data visualisations carry text alternatives via aria-label and surrounding copy, but not yet full data tables, which we plan to add.

🟢The plain-English versionEmoji chatter, captionless placeholders, a few tiny labels, other people’s widgets, and charts without tables — the honest snag list, each with a plan. (If this summary and the statement ever disagree, the statement wins.)

5.How we test

Current practice: manual keyboard-only passes on every new page, prefers-reduced-motion testing, no-JavaScript rendering checks (automated across the whole site on every change), and colour-contrast checks during design. Planned: automated WCAG scanning (for example, axe or Pa11y) in the build pipeline, screen-reader passes with NVDA and VoiceOver, and the independent audit noted above.

🟢The plain-English versionToday: human keyboard testing plus automated no-JS checks on every page. Next: scanners in the pipeline and a proper outside audit. (If this summary and the statement ever disagree, the statement wins.)

6.Feedback & alternative formats

If anything here is hard to use with your setup, we genuinely want the report: [email protected]. We aim to respond within 5 working days and to fix verified issues on a published timeline. If you need information from this site in another format — large print, plain text, or a walkthrough over the phone — ask and we’ll provide it.

🟢The plain-English versionTell us what’s broken and we’ll fix it; tell us what format you need and we’ll send it. (If this summary and the statement ever disagree, the statement wins.)

7.Enforcement

In the UK, the Equality Act 2010 protects your right to access services without discrimination. If you contact us about an accessibility problem and aren’t happy with our response, the Equality Advisory and Support Service (EASS) can advise you on your options.

🟢The plain-English versionIf we let you down and don’t fix it, EASS is the independent next step. (If this summary and the statement ever disagree, the statement wins.)

8.About this statement

Prepared on 18 June 2026; last reviewed 18 June 2026. It will be reviewed at least annually and after any significant redesign. Supername Ltd, 71–75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom.