Accessibility statement.

What we aim for

We aim to meet Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA — the international standard for web accessibility. Where we fall short, we say so on this page and we work on fixes in priority order.

Although as a private social initiative we are not legally required to meet a specific accessibility standard, we apply the same standards required of UK public sector bodies under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018. The audience we serve makes that the right baseline.

What’s compatible

The site has been built and tested to be usable with:

• Screen readers — we test against NVDA, VoiceOver (macOS, iOS), and TalkBack (Android).
• Keyboard-only navigation — every interactive element is reachable via Tab and operable via Enter/Space.
• Browser zoom up to 400% without loss of content or function.
• System-level prefers-reduced-motion (we respect this and disable transitions automatically).
• System-level prefers-color-scheme (we provide a dark variant).
• Screen magnifier software (ZoomText, macOS Zoom).

Built-in user controls

Click the “Accessibility” button in the top right of any page (or use the keyboard skip-link “Accessibility settings” at the very top of every page) to open a panel where you can change:

• Text size — Medium / Large / Extra-large.
• Contrast — Auto / High / Dark.
• Motion — On / Off (forces reduced motion regardless of OS settings).
• Dyslexia font — Off / On (swaps the body font for a high-readability typeface).
• Bandwidth — Default / Low (strips webfonts and decorative images for slow connections).

Settings persist on your device via local storage. They affect your visit only and apply nowhere else.

Known limitations

We’re honest about where we fall short. As of April 2026:

• Some block-pattern complex sections (FAQs, stat grids) use core HTML in the editor, which means an editor swapping content can accidentally break heading structure. Mitigation: we audit page heading order before any post goes live.
• The newsletter signup forms are embedded via the MailerLite plugin. The default MailerLite markup hits WCAG AA but we’ve not customised the error-message wording — that’s on the next-fixes list.
• Embedded third-party content (any YouTube embeds, Twitter cards) inherits the third party’s accessibility level, which is variable. We avoid embeds where we can and provide text alternatives where we can’t.
• The site is currently English-only. We’re aware that’s a barrier for the populations we serve. Translation is on the roadmap.

Tell us when we get it wrong

If you find a barrier on the site, please email hello@callingforhelp.org with the URL of the page and a description of the problem. We aim to respond within 5 working days and to fix accessibility issues at higher priority than feature work.

If you’ve reported an issue and aren’t satisfied with the response, you can also contact the Equality Advisory and Support Service (EASS) (UK) or the Information Commissioner’s Office if your issue concerns access to your own personal data.

How we test

We run the following before publishing any new template or major page revision:

• Automated checks via axe DevTools and Lighthouse Accessibility audit.
• Manual keyboard navigation through every interactive element.
• Manual screen reader pass with VoiceOver (the developer’s primary stack).
• Colour contrast verification for every brand colour combination using WebAIM’s contrast checker.
• Live testing of the user-control panel (text size, contrast, motion, dyslexia font, bandwidth) on each new template.

---

This statement was last reviewed on 30 April 2026. The site was last tested on 30 April 2026 against WCAG 2.2 AA. Material changes to this site since that date are reviewed against the same standard before publication.