Accessibility

1. What we aim for

We work towards the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That is a target, not a claim: the site has not yet been audited against it by anybody independent of us.

2. What we do

• Pages are built from real headings, lists, links and buttons, so assistive technology can find its way around them.
• Every form field has a label that is read out with it.
• Buttons, links and form controls are the browser's own, so they can be reached and used with a keyboard.
• The layout adapts to the width of the screen, so zooming in reflows the page into a single column instead of cutting it off.
• Venues can describe each photo they upload, and that description is what a screen reader hears.

3. What we know falls short

• Not every venue has described its photos, and those images are announced by the venue's name alone.
• The map on a venue's page is Google's, embedded as it comes. The written address beside it has the same information.
• There is no “skip to content” link yet, so keyboard users tab through the header on every page.
• Animations do not yet respect a device's reduced-motion setting.

We are working through these, and this list is kept current.

4. Venues themselves

This page is about the website. Whether a court or a restaurant has step-free access, accessible toilets or parking is up to the venue, and we do not inspect venues. If it matters for your visit, ask the venue before you book — their phone number and email are on their page.

5. Telling us about a problem

If something on BooqaPlace is hard or impossible for you to use, please tell us through the contact form or at support@booqaplace.com. Say which page, what you were trying to do, and what you use to browse if you are happy to — a screen reader and its version, for example. We read every message, and if something stands between you and a booking we will help you make it another way.