Legal

Accessibility

Prepared 2 June 2026 · last reviewed 2 June 2026

Vinealto is built to be used by everyone, including people who rely on screen readers, keyboard-only navigation, magnification, captions or reduced motion. We treat accessibility as a build requirement, not an afterthought — the same generous, plain-English posture that governs how we write governs how the product works. This statement explains the standard we build to, where we are on the way to meeting it, and how to tell us if something gets in your way.

Found a barrier? Email elise@vinealto.com and we will aim to reply within five working days. Tell us the page and what went wrong, and we will help — including supplying the information in another accessible format if you need it.

1. The standard we build to

We build to WCAG 2.2 Level AA — the Web Content Accessibility Guidelines published by the W3C. We apply it across every market we serve, because it sits at or above what each regime requires: the Equality Act 2010 in the United Kingdom, the European Accessibility Act and EN 301 549 in the European Union, and the Americans with Disabilities Act in the United States. Meeting it once means meeting all three.

2. What that means in practice

Every meaningful image carries a text alternative; decorative images are marked as decorative.
Audio, including the podcast, carries an accurate transcript; video carries synchronised captions.
Text and essential controls meet AA colour-contrast levels, and colour is never the only way meaning is shown.
Content reflows to a single column and supports text resizing to 200% and zoom to 400% without loss.
Every function works by keyboard alone, with a clear, visible focus indicator and no keyboard trap.
The full-screen navigation menu opens and closes by keyboard, keeps focus inside while open, closes on Escape, and returns focus to where you were.
Forms — the age check, registration, subscription and newsletter — have clear labels, and errors are explained in plain text with a suggested correction.
The page has a "skip to main content" link, a correct heading structure, and link text that makes sense out of context.

3. How we test

We check accessibility before launch and on every significant change, combining automated testing with manual keyboard testing and screen-reader testing (VoiceOver and NVDA), plus a contrast audit of our colour palette. Third-party components we rely on — such as the hosted checkout, our newsletter forms and any embedded audio player — are assessed before use.

4. Honest conformance — where we are

We want to be straight with you about status. We design and build to WCAG 2.2 Level AA, but the site has not yet been through an independent accessibility audit, so we do not yet claim full conformance. We will commission an independent audit once the build is complete and publish the conformance level actually achieved, naming any gaps plainly. We will not describe the site as "fully accessible" before that audit confirms it.

5. Known limitations

The paid subscription flow, the account area and the iOS app are still in build. Each will be tested to WCAG 2.2 Level AA on its own before it goes live. If you meet a barrier anywhere in the meantime, please tell us using the contact below and we will put it right or find another way to give you what you need.

6. Telling us about a problem, or asking for an alternative format

If any part of Vinealto is hard to use, or you would like a page or document in a different accessible format, email elise@vinealto.com. We aim to respond within five working days. Under the Equality Act 2010 we have a duty to make reasonable adjustments, and we take that duty seriously.