Accessibility
This page describes what we've actually tested, not an aspirational commitment. As coverage grows, this page will be updated to match.
What we aim for
We build CocktailHQ to be usable with a keyboard alone, with a screen reader, and at browser zoom levels up to 200%, broadly targeting the WCAG 2.1 AA success criteria — not a claim of full conformance, but the standard we test against.
What's been tested
Every major page type — recipe pages, search, discovery tools, calculators, MocktailHQ, favourites, comparisons, and practical guides — has been checked with automated axe-core scans for serious and critical WCAG violations, plus real Lighthouse accessibility audits. Interactive components (the age gate, cookie-consent banner, mobile menu, feedback form) have been manually checked for keyboard operability and focus handling, including focus trapping in modal dialogs and visible focus outlines throughout.
Known limitations
Automated and manual testing catches a meaningful share of issues but not everything — we haven't run a full assistive-technology audit with real screen-reader users across every page. If you hit a problem, we'd genuinely like to know about it.
Reporting a problem
You can report an accessibility issue using the feedback button available on every page, or via the Contact page. Please include the page you were on and what went wrong — that's the same detail the feedback form already collects automatically.