Accessibility Statement

Our commitment

Buying a supplement should not require a mouse, perfect eyesight, or a steady hand. Everything we sell is sold on this website, so if the website is hard to use, the product is unavailable — that is the standard we hold ourselves to.

Accessibility is part of how pages get built here, not a remediation project bolted on afterwards. That means it is also never finished: the honest position is that parts of this site meet the bar today, parts have not been verified yet, and we would rather tell you which is which than publish a badge.

The standard we target

We target the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the W3C. WCAG 2.2 is the current version and adds criteria that matter for a store — visible focus that is not obscured, targets large enough to hit reliably, and not making people re-enter information they already gave you.

We do not claim full conformance, and we have not commissioned a third-party accessibility audit. Claiming certified conformance we cannot evidence would be exactly the kind of unverifiable badge we avoid everywhere else on this site. What follows is a description of measures we have actually implemented, and of the gaps we are aware of.

What we have built

Structure a screen reader can navigate

Pages are built from real HTML landmarks — a banner header, a main region, a footer — with one h1 per page and headings that nest in order, so you can jump through a long policy or product page by heading instead of reading it top to bottom. Lists are marked up as lists, tables use proper row and column headers with a caption, and the page language is declared so a screen reader chooses the right pronunciation.

Breadcrumbs that announce themselves

Every breadcrumb trail is a labelled navigation region containing an ordered list, with the current page marked so a screen reader says so rather than leaving you to guess. The same component emits both the visible trail and its structured data, so what you hear and what search engines read can never diverge.

Keyboard operation

Navigation is built from real links, not click handlers on generic elements, so Tab, Enter and the browser’s own back button behave the way you expect. Interactive shop filters are real buttons and checkboxes. The cart drawer and the navigation panel stay in the page structure rather than being conditionally destroyed, which keeps their contents reachable.

Visible focus

We do not strip the browser’s focus indicator to make the design look tidier. Where a control replaces the default outline — form fields, for instance — it substitutes a clearly visible sage ring plus a border colour change, so the focused element is never ambiguous.

Reduced motion, honoured globally

If your operating system is set to reduce motion, our global stylesheet short-circuits the entire animation vocabulary of the site in one rule — every animation and transition on every element, including the homepage carousel and the fade-and-float effects. This is not a per-component opt-in that a new page could forget to apply; it is a single switch that applies to markup we have not written yet.

Images and text alternatives

Meaningful images carry descriptive alternative text, and purely decorative graphics are hidden from assistive technology so they are not read out as noise. Content that only makes sense visually is paired with text — for example, live status messages are announced politely rather than appearing silently.

Colour and contrast

Body copy is dark charcoal on white or cream, and link and label colours are chosen to be legible rather than merely on-brand. Colour is never the only way we convey information: state is also carried by text, position, or an icon.

Responsive and zoom-friendly

Layouts are built mobile-first with relative units and flexible grids, so magnifying the page or increasing your operating system’s text size reflows the content instead of clipping it. Wide content such as tables scrolls inside its own container rather than forcing the whole page sideways.

Assistive technology we aim to support

We aim for the site to work with current versions of the following, used with a current version of Chrome, Safari, Firefox or Edge:

• VoiceOver on macOS and iOS
• NVDA and JAWS on Windows
• TalkBack on Android
• Keyboard-only navigation, with no pointing device at all
• Voice control software, including Voice Control on Apple devices and Dragon
• Browser zoom up to 200%, and operating-system text-size settings
• Operating-system settings for reduced motion, increased contrast and dark mode

If you use something not on this list and it does not work, that is worth telling us about — the list describes our targets, not a limit on who we want to help.

Known limitations

Stated plainly, because a statement that lists only successes is not much use to someone trying to work out whether they can shop here.

• No skip-to-content link yet. Keyboard and screen-reader users currently have to tab through the header — including the search field and navigation — before reaching the main content of each page. Landmark navigation works as a workaround for screen-reader users, but that is not a substitute. This is our highest-priority fix.
• No independent audit. We have not had this site tested by a third-party accessibility specialist, and we have not published a formal conformance report. Our own testing will have blind spots.
• Contrast is not fully verified. Primary body text and interactive text are chosen for legibility, but we have not completed a component-by-component contrast audit. Some secondary, muted or decorative text — and some uses of our brighter brand green on white — may not yet reach the 4.5:1 ratio WCAG asks for at Level AA.
• Screen-reader testing is not exhaustive. The shop filters, the cart drawer and the checkout flow have been built to be keyboard operable, but they have not been verified against every screen reader and browser combination listed above.
• Payment happens on a page we do not control. Checkout is completed on a page hosted by our payment processor. We do not control its markup or its accessibility. If you hit a barrier there, tell us and we will work with you to get your order placed.
• Manufacturer product photography. Product and label images come from our manufacturer and may contain text — ingredient panels, serving directions — that is not always repeated in the surrounding page copy. If you need the contents of a label read to you, ask us and we will send it as plain text.
• Email and text messages. Our emails are built as HTML with text alternatives, but their rendering depends on your mail client and we cannot guarantee behaviour in every one.

Report a barrier

If any part of this site stops you doing something, please tell us. You are not complaining — you are giving us a bug report we cannot generate ourselves.

Email support@betterlynutrition.com with “Accessibility” in the subject line, or use our contact form. If you can, include:

• The page you were on — the web address, or just what it was called.
• What you were trying to do, and what happened instead.
• The browser, operating system, and any assistive technology you were using, with versions if you know them.

Other ways to reach us

You never have to use a form on this site to get help. Email support@betterlynutrition.com for anything, or support@betterlynutrition.com about a specific order. We are happy to send product information, ingredient panels or order details as plain text, and to handle a return by email rather than through the returns page.

If you need to check an order and the tracking page is not working for you, email us the order reference and we will look it up and reply with the status in plain text.

How we review

• New pages and components are checked with keyboard-only navigation before they ship — every interactive element reachable, operable, and visibly focused.
• Markup is reviewed for landmark structure, heading order and text alternatives as part of code review, rather than in a separate pass that can be skipped.
• Reduced-motion and zoom behaviour are checked whenever the layout or motion system changes.
• We re-read this statement whenever we ship a significant change to the site, and update the limitations above as we close them or find new ones.
• Reported barriers are treated as bugs with owners and dates, not as feedback filed away.

An independent audit is on our roadmap. When one has been completed, this page will say so and say what it found — including anything unflattering.

Related policies

Read our privacy policy for what happens to the information you send us, and our terms of service for the terms covering orders, subscriptions and returns. For anything else, our contact page is the fastest route to a person.