True You TogetherCIC

how this site works for everyone

Accessibility statement.

This is the public statement of how True You Together CIC has built its website to be accessible, what we’ve tested, what we know isn’t yet right, and how to tell us about a barrier.

Last updated: 21 May 2026. [REVIEW: refresh each time we make a substantive accessibility change.]

Our commitment.

True You Together CIC supports neurodivergent people, parents and communities. Many of the people we serve have access needs. We treat accessibility as part of the service, not an afterthought.

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at AA level as a baseline, with some AAA-level provisions where they matter most for our audience.

What we’ve done.

The site is built with the following accessibility decisions baked in:

  • Three reading modes. A small control in the top-right of every page lets you choose Paper (the warm cream default), Dusk (warm dark, easier on light-sensitive eyes and migraine), or High Contrast (off-white on near-black for low vision). Your choice persists across visits.
  • Text-size control. A three-step A / A+ / A++ button in the top-right scales the whole page, not just the body text. Headings, captions, and labels all scale together. Your choice persists across visits.
  • Atkinson Hyperlegible fonts. The body typeface was designed by the Braille Institute specifically for low-vision and dyslexic readers. Distinct letter shapes, clear figures, generous default line-height.
  • High contrast text. Body text on the default Paper background is at roughly 13:1 contrast, well above WCAG AAA. Dusk and High Contrast modes maintain or improve this.
  • Reduced-motion support. If your device is set to “Reduce Motion”, we honour it. No animations or transitions will play.
  • Keyboard navigation. Every link, button, form field and interactive control is reachable and operable from the keyboard alone. We use a visible 3-pixel focus ring in leaf blue (or yellow on High Contrast).
  • Skip-to-content link. The first focusable item on every page is a “Skip to content” link, so keyboard and screen-reader users can bypass the header navigation.
  • Forced-colours support. If your operating system has high-contrast mode enabled (Windows for example), we step aside and let your system palette through.
  • Semantic HTML. Landmarks (header, main, footer, complementary) are properly marked up so screen-reader users can jump between regions. Headings follow a logical order.
  • Image alt text. Every meaningful image carries a description. Purely decorative images are explicitly marked as decorative.
  • Crisis signposting on every page. The safety strip at the top of every page carries Samaritans, Shout (text) and NHS 111 details. Text-based crisis support (Shout 85258) is included specifically because many neurodivergent people find phone calls inaccessible.
  • Plain language. We try to write the way we’d speak. We avoid jargon. We don’t use deficit-led words like “disorder” or “sufferer”.
  • No autoplay. No video, audio, or motion starts without you choosing to start it.

What we know isn’t yet right.

Honest list of known gaps, with rough timelines to address each. We update this every time we publish a fix.

  • [REVIEW: We will run a full WCAG 2.1 AA audit against the live pages before formally launching. Note any specific issues found, with an estimated timeline.]
  • The Dusk-mode logo currently uses a placeholder image. A proper Dusk variant is being prepared.
  • Resource articles in the library are currently placeholder cards. We’ll publish real articles with proper structured content before promoting Home to the front page.
  • We do not yet provide audio descriptions or captions, because we have no video content yet. Any future video will include both.

How we test.

  • Automated checks using axe DevTools in the browser, and the Lighthouse accessibility audit.
  • Manual keyboard-only walkthroughs of each page.
  • Manual screen-reader checks using VoiceOver on macOS. [REVIEW: add NVDA and JAWS testing once available.]
  • Reading mode and text-size combinations tested across Safari, Chrome, Firefox and Edge.
  • [REVIEW: add real-user testing with neurodivergent volunteers once we have a small panel established.]

How to report a problem.

If you find anything on this site that isn’t accessible to you, please tell us. We treat accessibility reports seriously and act quickly.

Email Info@trueyoucic.co.uk with the following if you can:

  • The page or feature where you hit the problem
  • What you were trying to do
  • What happened (or didn’t)
  • What assistive tech or settings you use, if you’re comfortable sharing

We’ll reply within seven working days, often sooner. If a fix is needed, we’ll tell you when to expect it.

Enforcement.

If you contact us about an accessibility problem and you’re not happy with how we respond, you can complain to the Equality and Human Rights Commission (EHRC), which enforces the Equality Act 2010.

www.equalityadvisoryservice.com

Technical detail.

For the technically-minded, this site is built on a custom WordPress block theme called True You Together. The theme is open-source-friendly and the source code is on GitHub. The accessibility patterns we use are documented in the theme repository’s README. Specific commits relating to accessibility are tagged in the change log.