Accessibility
Accessibility
The standard this site is built to, what we have tested, what we know is imperfect, and how to tell us about a barrier.
Prefer to talk it through? Book a strategy call
The standard we build to
This site targets WCAG 2.2 Level AA. That is the standard we hold our client work to, and it would be difficult to argue for it while not applying it here.
We have not commissioned an independent audit, so we are not claiming certified conformance. What we have done is build to the standard from the start rather than retrofitting: semantic HTML, a visible skip link, keyboard operability throughout, focus indicators that are never removed, colour contrast checked against the palette, reduced-motion support, and text that resizes without breaking layout.
What has been tested
- Full keyboard navigation, including the main menu and every interactive control
- Visible focus on every focusable element
- Colour contrast for text, interface elements and states against the brand palette
- Heading structure and landmark regions
- Behaviour with prefers-reduced-motion enabled
- Text scaling to 200 per cent without loss of content or function
Reported barriers
What happens when something here does not work for you
A statement is worth roughly what follows a report of a barrier. This is the whole of that: we handle a barrier as a defect, and anything we cannot fix quickly gets said out loud instead.
Is it in something we have already tested?
Yes: Then it is a regression in work we said was checked, and it is fixed rather than explained.
No: It is a gap we did not know about. Reports from assistive technology users are the most useful input we get.
Can it be fixed quickly?
Yes: It is fixed. On a site that keeps growing this is maintenance rather than a milestone.
No: We tell you what we are doing in the meantime, rather than letting the report go quiet.
Does it change what this page can claim?
Yes: The limitation is written here. Listing known failures is worth more than claiming full conformance.
No: The claim stands as it is: built to WCAG 2.2 Level AA, with no independent audit behind it.
If something is not working
Tell us. Email hello@tryboostd.com with the page and what happened, and we will treat it as a defect rather than a suggestion. If a fix will take time, we will tell you what we are doing in the meantime.
Accessibility on a site that keeps growing is maintenance, not a milestone. Reports from people actually using assistive technology are the most valuable input we get.
Last updated · Published on owner authorisation by Zubair Afzal