Honest status
WCAG 2.2 Level AA is our design target. We are not claiming full WCAG conformance yet because the final independent accessibility audit, complete assistive-technology testing and production device/browser pass are still outstanding.
Our accessibility target
DesperateMinds aims to make its public content and interactive assessments perceivable, operable, understandable and robust. New components are designed against WCAG 2.2 Level AA where applicable, with the understanding that conformance must be demonstrated by testing rather than claimed from a checklist alone.
What we build for
- keyboard access to interactive controls;
- visible focus states and logical control order;
- semantic headings, landmarks and form labels;
- text alternatives for meaningful images;
- sufficient contrast and no critical meaning conveyed by color alone;
- responsive layouts that remain usable on narrow screens and at increased zoom;
- reduced-motion behavior where animation is not necessary;
- clear validation and error messaging for assessments and forms;
- plain-language explanations around complex psychology and care-navigation topics.
How we test
Development QA checks markup, heading structure, mobile behavior, runner visibility, action spacing, broken links and common regressions. We also use targeted manual browser checks during development. Automated checks are useful but do not replace keyboard, screen-reader, zoom and real-device testing.
Current limitations
The revamp is still in development. A full independent accessibility audit has not yet been completed, and not every supported assistive-technology/browser combination has been tested. Some legacy pages also use an older site shell while the new platform is being prepared.
These are accessibility requirements, not reasons to hide known barriers. If we identify a material accessibility defect, we will prioritize a fix and document the correction through the normal QA process.
Report an accessibility barrier
If you cannot access content, complete an assessment or use a control, please contact us with the page URL, what you were trying to do, and the browser or assistive technology involved if you are comfortable sharing it. Do not include sensitive health details that are not necessary to reproduce the issue.
Third-party services
Some future payments, email, analytics or external booking experiences may be provided by third parties. We will consider accessibility when selecting and configuring those services, but their interfaces can have separate accessibility behavior and policies.
Reference standard
Our design target is based on the World Wide Web Consortium's Web Content Accessibility Guidelines (WCAG) 2.2. W3C notes that accessibility evaluation requires a combination of testable criteria and human evaluation.