BetterYou+ is built to be readable. This page says what we actually do, what we measure, and where we know we fall short.
What is built in
- Text scales with the viewport. Body type, captions and credits are sized in fluid ranges rather than fixed pixels, so a phone and a large display each get a comfortable size instead of the same one.
- Contrast is a floor, not an aspiration. Small text roles such as image credits are held above the WCAG AA minimum; the credit role currently measures 7.4:1.
- Touch targets are at least 24 × 24 pixels, including the small homepage hero controls, whose visible dots are deliberately smaller than the area you can hit.
- Reduced motion is honoured. If your system asks for reduced motion, the homepage hero stops rotating rather than merely slowing down.
- The hero is operable by keyboard, with previous and next controls, a labelled list of stories, and visible focus outlines.
- A skip link takes you straight to the article.
- Images carry alternative text that states what matters about the image; decorative images are marked as decorative so a screen reader passes over them.
- Light and dark are both first-class and follow your system setting unless you choose one.
What we measure, and how
Before an article is published it is rendered and measured at 360, 390, 768, 1024 and 1440 pixels wide, in light and dark. We check contrast, horizontal overflow, layout shift, whether credits are actually visible rather than merely present in the markup, and whether interactive targets meet the size floor. An article that fails is not published.
Where we know we fall short
We have not yet run a full audit with screen-reader users, and we do not claim formal WCAG 2.1 AA conformance across the whole site. Parts of the site inherited from our underlying theme have not been rebuilt to the standard above. We would rather say that than claim a level we have not tested for.
Tell us
If something here is hard to read, hard to operate, or does not work with your assistive technology, please tell us — including what you were using. Specific reports get fixed; we cannot fix what we do not know about.