Accessibility
Built to be usable by everyone on the road.
A platform about reaching people shouldn’t exclude any of them. This statement describes what this website actually implements today — not aspirations, and not a certificate we don’t hold.
Our target: WCAG 2.2 AA
We design and build this site against the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We test with keyboards, reduced-motion settings and semantic checks as part of building each page. We have not yet commissioned a formal third-party audit or certification, and we won’t claim one until we have — what we can do is state plainly what’s built, and fix what you report.
What this site implements
- Skip link on every page — the first focusable element jumps keyboard users straight past the navigation to the main content.
- Visible focus, always — every interactive element shows a 2px Sunset Orange focus ring with a 3px offset. If you can tab to it, you can see where you are.
- Reduced motion respected — with “reduce motion” set in your OS, every animation, floating element, scroll reveal and counter is disabled. Content simply appears.
- Semantic structure — one h1 per page, labeled landmark sections, definition lists for stats, real tables with captions and scoped headers, and ordered lists for sequences.
- Meaningful alternative text — photography carries descriptive alt text; purely decorative art is marked aria-hidden with empty alt so screen readers skip it.
- 44px touch targets — buttons, toggles, links in navigation and form controls meet a 44px minimum target size.
- Readable without JavaScript — scroll effects are progressive enhancement. With scripts off, every page renders its full content immediately.
- Native controls where it matters — FAQs use native disclosure elements, toggles carry aria-pressed / aria-selected, and empty states announce via role="status".
Where we’re honest about gaps
Some pages use simulated dashboard and phone interfaces as illustrations; these are marked decorative and summarized in text, but they are dense, and we keep refining their descriptions. If any part of this site is hard to use with your assistive technology, that’s a bug — please tell us.
Found a barrier? Report it.
Email us with the page, what you were trying to do, and the assistive technology or setting involved. A person reads every report, and accessibility fixes don’t sit at the back of the queue.
Email support@hitdahiway.comThis statement covers the marketing website at hitdahiway.com. Last reviewed July 2026.