Accessibility statement

We’re targeting WCAG 2.2 Level AA across the whole platform. That’s the conformance bar the UK Government Digital Service uses for public-facing services, and it’s the right level for a marketplace that carries payments and sensitive profile data.

We’re honest that hitting AA perfectly on day one of a build is rare. The list of known gaps below is the live picture, not a marketing claim.

• Keyboard navigation

  Every interactive control (nav, search, booking wizard, messaging, dispute flow) is reachable and operable with Tab / Shift+Tab / Enter / Space. A visible focus ring is present on every focusable element.

• Screen readers

  Headings follow a proper hierarchy (h1 per page, no skipped levels). Form fields have associated labels. Buttons have accessible names. Images have alt text, or are marked decorative.

• Colour contrast

  Body copy and UI text meet or exceed 4.5:1 contrast against the background in both light and dark themes. The brand amber (#B45309) is used for accents that are also distinguishable without colour (underlines, icons, text labels).

• Reduced motion

  Framer Motion entrances and Lenis smooth scroll respectprefers-reduced-motion. If your OS is set to reduce motion, the platform drops eased animations in favour of instant transitions.

• Dark mode

  A true dark theme is available via the navbar toggle and respects the OSprefers-color-schemeon first visit. Contrast was independently verified in dark mode, not just light.

• Zoom & reflow

  Pages reflow cleanly up to 200% browser zoom and down to 320px viewport width without horizontal scrolling or truncated content.

• Map view on /listings

  The Mapbox map is interactive with a mouse but doesn’t yet expose every pin to screen readers. The parallel list view (default) has the same data and is fully accessible; a keyboard-equivalent map interaction pattern is on the roadmap.

• Image carousels

  Listing detail photo galleries expose next/previous controls, but the swipe interaction on touch devices does not currently announce photo index changes to screen readers. The visible counter is correct.

• Some older third-party widgets

  Stripe Checkout (hosted by Stripe) and the Supabase magic link email confirm button are rendered outside our app. Their conformance is the responsibility of those providers, though both are well above AA in our testing.

• Auto-playing video

  None — we deliberately don’t use auto-playing video anywhere on the platform, so this isn’t a concern. Listed here so the absence is explicit.

• Automated

  axe-core DevTools sweep on every major page in both themes; keyboard-only tab-order walk-through before any release tagged on the changelog.

• Screen readers

  Spot-checked with VoiceOver on macOS/iOS Safari and NVDA on Windows Firefox. We haven’t yet run a full TalkBack (Android) pass.

• Manual review

  Contrast spot-checks via the Stark Chrome extension; zoom & reflow tested manually at 200% on desktop and 320px viewport width on mobile.

If something on DrivewayNights isn’t working with your assistive technology, please tell us. The quickest way is the contact form — or email support@drivewaynights.co.uk with “Accessibility” in the subject line. Include the page URL, what you were trying to do, and which assistive technology you’re using if you’re able to. We aim to reply within one working day and fix confirmed issues within two weeks unless the change is a larger rebuild.

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Equality Act 2010 in the UK as it applies to private-sector services. If you contact us about a problem and you’re unhappy with how we respond, you’re entitled to escalate to the EHRC. We’d rather just fix the problem — but the escalation path is yours.

This statement was last substantively reviewed on 16 April 2026. We review it at least every six months, and any time a major feature ships that changes the interactive surface (new booking flow, new messaging surface, new host onboarding flow).