Skip to content

    Accessibility

    Everyone should be able to book a table.

    Forage is built to meet WCAG 2.2 at level AA. This page says what that means in practice, what we check on every release, and where the gaps still are. Last reviewed October 2026.

    What works

    • Every page can be used with a keyboard alone. A visible focus ring follows you, and a "Skip to content" link is the first thing on every page.
    • Buttons, links and form controls are at least 44 by 44 pixels on phones, and never smaller than 24 by 24 anywhere.
    • Text keeps a contrast ratio of at least 4.5 to 1 against its background. Nothing is conveyed by colour alone.
    • Images of venues carry their name and cuisine as alternative text. Decorative images are hidden from screen readers.
    • Dialogs trap focus, announce their title, and close on Escape. Live updates such as a confirmed booking are announced politely.
    • Search is a proper combobox. Results in the three pane layout are a listbox you can move through with the arrow keys.
    • Text can be zoomed to 200 percent and the layout reflows at 320 pixels wide without sideways scrolling.
    • Motion is reduced when your device asks for it: the hero video does not play and animations are shortened.
    • Dates, times and money are written out in full so they read correctly aloud.

    How we test

    Every change runs an automated audit with axe-core across every public page and the booking flow, on a desktop and a phone sized browser, before it can be released. The same suite checks that every interactive element meets the target size rule (WCAG 2.5.8) and shows a visible focus indicator (WCAG 2.4.11). We also use VoiceOver on iOS and macOS and NVDA on Windows by hand for the booking dialog, the Passport and the search page.

    Known limits

    • The map is an alternative view of the same results. Everything on it is also in the list, which is the accessible route.
    • Venue photos are supplied by venues. Where a venue has not written a description, we use the venue name and cuisine instead.
    • Payments for deposits, experiences and gift cards happen on Stripe's hosted checkout, which has its own accessibility statement.
    • QR codes for bookings and gift cards are images; the reference or code is always printed next to them as text.

    If something is in the way

    Tell us. Email hello@crumbs.vip with the page and what happened, and we will reply within five working days. If you cannot book online, any venue on Forage can take the same booking by phone: the number is on its page.

    You can also manage a booking without an account, and the venue is told straight away.

    The standard

    Forage aims to conform with the Web Content Accessibility Guidelines version 2.2, level AA, published by the W3C. Forage is a product of Crumbs OS. This statement follows the format recommended by the UK Government Digital Service.