Our commitment

local-hotel.com aims to be usable by everyone, including people with visual, hearing, motor, or cognitive impairments. We build the site against WCAG 2.2 AA and run automated accessibility tests on every code change to catch regressions before they land.

Conformance status

We aim for WCAG 2.2 Level AA conformance across the site, with selected areas (the booking flow, forms, and emails) meeting Level AAA. Our build pipeline runs axe-core against the components users touch most often; failures block merges.

Specific measures we've implemented:

• Skip-to-content link on every page for keyboard + screen-reader users
• Visible focus indicators on every interactive element
• Form labels associated to inputs; required fields announced via aria-required
• Error messages linked to their input via aria-describedby; announced live
• Modal dialogs trap keyboard focus and restore it on close
• All decorative SVGs hidden from screen readers; meaningful images carry descriptive alt
• prefers-reduced-motion honoured — animation is suppressed when the OS requests it
• iOS focus-zoom prevented by setting inputs to 16px on mobile
• Touch targets at least 44 × 44 px (WCAG 2.5.5 AAA)
• Transactional emails ship plain-text fallbacks and pass automated a11y checks

Known limitations

Some third-party widgets we embed don't expose a fully accessible surface. Where this is the case we've documented the limitation and, where possible, provided an alternative path to complete the same action.

• Interactive map (Leaflet) — marker keyboard navigation is limited. The list view on the same page provides full keyboard access to every hotel shown on the map.
• Payment widget (Stripe Embedded Checkout) — the card-entry iframe is owned by Stripe; its accessibility is governed by their team. Stripe publishes its own conformance statement.

Compatible technology

We test against current versions of the following browsers + assistive technologies:

• Safari + VoiceOver (macOS, iOS)
• Chrome + NVDA (Windows)
• Firefox + Orca (Linux)
• Keyboard-only navigation on all of the above

JavaScript is required for the search and booking flow. Static content (legal pages, destinations directory) works without it.

Found a problem? Tell us.

We want to hear about it — your report directly fixes the next person's experience.

Email: accessibility@local-hotel.com

Please include: the page URL, what you were trying to do, what happened, the browser + assistive technology you were using, and a screenshot if you can. We aim to respond within 5 working days and to fix or work around the issue within 30 days for high-impact items.

Enforcement

If you're not satisfied with our response, you can escalate to the relevant national body — for UK consumers, the Equality and Human Rights Commission; for EU consumers, your national accessibility-enforcement authority under the European Accessibility Act.

How we assessed

We use a combination of:

• Automated checks via axe-core, run on every code change in CI
• Lighthouse a11y audits during release verification
• Manual keyboard and screen-reader walk-throughs of the booking flow
• Chrome DevTools vision-deficiency simulation (protanopia, deuteranopia, tritanopia, achromatopsia)