Policies
Our commitment to accessibility
Written By Why.Help. Last reviewed . 1 min read.
The short answer
why.help is built to meet WCAG 2.1 Level AA accessibility standards, because people reaching out for addiction help are already dealing with enough friction - this site shouldn't add more, whether someone uses a screen reader, navigates by keyboard only, or needs high-contrast text.
Key points
- Target standard: WCAG 2.1 Level AA across the site.
- Every page uses semantic headings and is fully operable by keyboard alone.
- Text resizes up to 200 percent without breaking layout or losing content.
- No content auto-plays, and animations respect your reduced-motion setting.
- Report an issue to [contact email] and expect a response within [N] business days.
What we've built in
- Full keyboard navigation, including the FAQ accordions and the navigation menu.
- Descriptive alt text on all images.
- Minimum 4.5:1 color contrast throughout.
- Visible focus indicators for keyboard users.
- A skip-to-content link on every page.
- No content or navigation that relies on color alone.
Ongoing work
Accessibility isn't a one-time checklist - we test this site periodically and welcome direct feedback if something isn't working for you.
What are the known limitations?
Video content embedded from YouTube on our video page runs inside YouTube's own player, which we do not control directly. YouTube's player has its own accessibility features and its own gaps, and we cannot guarantee it meets the same standard as the rest of this site. We link out to YouTube's own accessibility information where relevant and continue to evaluate whether embedded video meets our bar.
How do you test for this?
We test using a combination of automated scanning tools, manual keyboard-only navigation, and screen reader checks on new and updated pages before they publish. This is an ongoing process rather than a single audit, since new content is added regularly and needs the same scrutiny as the original site.
What do you do if something is broken?
If you find a page, feature, or piece of content that is not accessible to you, email [contact email] with the page URL and a description of the problem, including what device or assistive technology you were using if relevant. We aim to respond within [N] business days and will work to fix confirmed issues as quickly as we reasonably can.
Frequently asked questions
You do not have to explain yourself to get help.
Start with the page that matches where you are right now.
See your options