Accessibility

What we've built in

• Cognitive load first: one primary action per screen, short plain-English copy, no jargon, and no blank-page-with-a-cursor moments.
• No shame states: no streaks, no guilt, no red “you failed” anywhere — which matters more for cognitive accessibility than most checklists admit.
• Keyboard: every interactive element is reachable and operable by keyboard, with visible focus.
• Screen readers: semantic HTML, labelled controls, and live regions that announce results as they stream in.
• Motion: decorative motion is near-zero by design, and we respect your system's “reduce motion” setting.
• Targets and text: touch targets are at least 44×44px, text contrast meets AA, and layouts work from 390px phones up to large desktops.
• Themes: a light and a midnight theme, both contrast-checked.

Where we're honest about gaps

We test with automated tools and manual keyboard passes. We have not yet completed a full audit with assistive-technology users, and we haven't had an independent accessibility assessment. Some AI-generated content (your steps and plans) is written by a model, so its reading level can vary. Emoji are used decoratively and may be announced by some screen readers.

We'd rather tell you that than claim full conformance we haven't evidenced.

Tell us about a barrier

If something in ADHV is hard or impossible for you to use, please email harryvarvel@gmail.com and say what happened and what you were trying to do. We treat accessibility bugs as real bugs, and we'll reply. If you need information from ADHV in a different format, ask and we'll find a way.

Your rights

Under the Equality Act 2010 we must make reasonable adjustments so disabled people aren't put at a substantial disadvantage. If you think we've fallen short, tell us first — we want to fix it. You can also contact the Equality Advisory and Support Service (EASS).