We aim for WCAG 2.2 AA across the site and treat accessibility as ongoing work — not a checkbox. If something blocks you, please tell us and we'll fix it.
Our commitment.
CAMUK is committed to making digital and in-person experiences welcoming to disabled people, neurodivergent people, people using assistive technology, and anyone whose needs aren't well served by default. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across this website. Accessibility is not a one-off project — we audit our work regularly and improve as we learn.
What we've done.
- Clear, high-contrast typography across the site, with body type sized for comfortable reading.
- All interactive controls reachable by keyboard, with visible focus styles that don't disappear at zoom.
- Descriptive alternative text on photographs and meaningful images; decorative images marked as such.
- Semantic landmarks (
<header>,<nav>,<main>,<footer>) so screen readers can navigate quickly. - Forms labelled clearly, with helpful error messages and inline guidance.
- Layouts that reflow on small screens and at zoom levels up to 400% without horizontal scrolling.
- Captions on videos hosted on the site, and transcripts on audio recordings.
- Reduced-motion support — animations respect the operating-system preference.
Where we can, we test with real people on real devices — keyboard-only navigation and screen-reader walkthroughs of the primary flows (home, about, events, donate, contact). A formal audit by an external accessibility partner is planned, and we'll publish the findings in full when it's complete.
Where we still fall short.
We don't pretend to be perfect. The known issues we're working through, in priority order:
- Events admin panel — improved screen-reader labelling on the data-entry forms is in progress; target Q3 2026.
- Archival video — captions and transcripts on clips older than 2024 are being added on a rolling schedule.
- Donation form — higher-contrast option for the amount selector on small screens, currently in design.
- PDF reports — older annual reports are scanned images. We're re-typesetting them as accessible PDFs as we go.
At our events.
Most CAMUK events take place in venues that are step-free, well-lit, and on accessible transport routes. Where a venue isn't fully accessible, we say so on the event page so you can plan.
If you have specific access needs — mobility, hearing, vision, sensory, dietary, caring responsibilities — let us know when you RSVP and we'll do everything we can to make the room work for you. We can usually arrange:
- Reserved seating with clear sightlines and easy exit routes.
- Quiet areas for breaks during longer events.
- Live captioning for our larger gatherings.
- BSL interpretation when arranged a few weeks in advance.
- Dietary alternatives — please give us at least 5 working days' notice.
Tell us if something doesn't work.
If you hit a barrier on the site or at one of our events, please write to info@camuk.net with a short description of what happened, the page URL or event involved, and your device or assistive technology if you're comfortable sharing.
We aim to acknowledge within 2 working days and to respond fully within 5. Where we can fix something quickly, we will. Where it'll take longer, we'll tell you when to expect a fix.
Enforcement.
If you contact us about an accessibility issue and aren't satisfied with our response, you can raise it with the Equality Advisory and Support Service (EASS) at equalityadvisoryservice.com.
The Equality Act 2010 (and, for Northern Ireland, the Disability Discrimination Act 1995) requires public bodies to make reasonable adjustments. We hold ourselves to the same standard, even where we're not legally bound.
Technical & testing notes.
This site is built with semantic HTML, progressive enhancement, and minimal JavaScript. It works with assistive technology including:
- VoiceOver on macOS and iOS.
- NVDA and JAWS on Windows, paired with Chrome, Edge, and Firefox.
- TalkBack on Android.
- Browser zoom up to 400% and OS-level larger-text settings.
Automated testing uses axe-core and Lighthouse during build. Manual testing — performed by volunteers, not yet a certified auditor — covers keyboard-only navigation, screen-reader walkthroughs, and reduced-motion scenarios. We're transparent about the limits of self-testing and welcome findings from anyone who runs into a barrier we missed. This statement was last reviewed on 5 May 2026.