Back to Home

Accessibility Statement

Statement date: August 1, 2026 · Last reviewed: August 1, 2026

1. Our commitment

Bantoor is built so that as many people as possible can use it, including people who rely on assistive technology. We aim to meet Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. These guidelines explain how to make websites easier to use for people with disabilities — including people who are blind or have low vision, are deaf or hard of hearing, or navigate with a keyboard instead of a mouse. Accessibility is ongoing work, and we improve the product as we find and fix issues.

2. What we do

Steps we take to keep Bantoor usable for everyone:

  • Semantic HTML — we use real headings, lists, buttons, and landmarks so screen readers can announce the page structure.
  • Keyboard navigation — you can reach and operate menus, forms, dialogs, and the booking chat using only the keyboard, with a visible focus outline showing where you are.
  • Labels for assistive technology — interactive controls and icons carry accessible names (ARIA labels where a visible label isn't enough) so their purpose is clear when read aloud.
  • Colour contrast — we target the WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text and interface elements) and don't rely on colour alone to convey meaning.
  • Text alternatives for images — decorative images are hidden from screen readers, and we provide alternative text for images that carry meaning.
  • Respecting your settings — the interface honours reduced-motion preferences and scales cleanly when you zoom the page or enlarge text.

3. Known limitations

We want to be honest about the areas we're still working on. These parts of Bantoor may not yet fully meet Level AA, and we're actively improving them:

  • Photo gallery lightbox — the full-screen photo viewer on studio and specialist profiles has known gaps in focus handling and screen-reader announcements. If it's hard to use, the same photos are also reachable in the grid on the profile page.
  • Chat and real-time messages — new incoming messages in the booking chat are not always announced to screen readers as they arrive; you may need to move focus into the conversation to catch up.
  • Map and location views — the interactive map on the explore page is difficult to use without a mouse. The same studios are available as a text list alongside the map.
  • Third-party components — some embedded tools we don't control (for example, the Stripe payment fields) may not meet every AA criterion.

4. Compatibility

Bantoor is designed to work with current versions of major browsers (Chrome, Safari, Firefox, and Edge) and common screen readers, including VoiceOver on Apple devices, NVDA on Windows, and TalkBack on Android. It may not work reliably with browsers or assistive tools more than a few versions out of date.

5. Tell us if something doesn't work

If you hit a barrier using Bantoor, or you need information in a different format, we want to know. Email [email protected] and tell us what happened, the page you were on, and the browser or assistive technology you were using. We aim to reply within 5 business days, and we'll work with you to give you the information or help you need.

6. Keeping this up to date

We review this statement and re-check the product against WCAG 2.1 Level AA on an ongoing basis. The "last reviewed" date at the top of this page shows when we most recently checked it. This statement was first published on August 1, 2026.