Accessibility statement
Held to our own standard
We build the case for accessible systems everywhere. This site is where we prove we mean it.
WeEnable targets WCAG 2.2 AA on every page, and AAA wherever the content allows. Access is designed in from the first draft, never bolted on after the complaints start. We test with real assistive technology, not only automated checkers.
What’s built in
- Full keyboard navigation, with a visible focus indicator on every interactive element.
- Semantic structure and labelling that screen readers can navigate and announce.
- A minimum 4.5:1 contrast ratio between text and its background.
- Text that resizes up to 200% without loss of content or function.
- Captions and transcripts for the audio and video we publish.
- Reduced-motion support that respects your system preference.
Adjust this site to suit you
Every page carries an accessibility panel, opened from the accessibility button in the bottom-right corner. Your choices are remembered on your device and applied the next time you visit. From it you can:
- Increase the text size in steps, up to 140%.
- Turn on a higher-contrast colour mode.
- Add more line and letter spacing for easier reading.
- Highlight every link with an underline.
- Reduce or stop on-screen motion and animation.
- Have the page read aloud with your device's voice.
These controls sit on top of, not instead of, your own assistive technology. The site is built to work with screen readers such as NVDA, JAWS, and VoiceOver, and with your browser and operating system settings.
Where we’re still working
We are honest about the gaps. Some older documents, embedded third-party content, and media published before our current standard do not yet fully meet it. We are working through them, and we prioritise the fixes that remove the most friction for the most people first. Accessibility is a standard we hold, not a box we have finished ticking.
Tell us where we fall short
If you hit a barrier anywhere on this site, we want to know. Email accessibility@weenable.org and tell us what happened and where. We treat access reports as bugs to fix, and we will get back to you.