Accessibility Statement

Our commitment

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. These guidelines explain how to make web content more accessible to people with disabilities, including those who use screen readers, keyboard-only navigation, or other assistive technologies.

We review this site periodically and make improvements as we identify them. This statement was last updated on October 5, 2026.

What we have done

We have taken the following steps to improve accessibility on this site:

• Added a skip to main content link at the top of every page so keyboard users can bypass the navigation.
• Ensured visible keyboard focus indicators on all interactive elements, including navigation links, buttons, and form fields.
• Used semantic HTML throughout: one <h1> per page, logical heading order, and landmark regions (<header>, <main>, <nav>, <footer>).
• Provided descriptive alt text on all meaningful images.
• Associated every form field with a visible label, marked required fields, and linked hint text to inputs with aria-describedby.
• Added ARIA live regions so screen readers announce form submission success and error messages.
• Made the mobile navigation menu operable by keyboard and screen reader, with dynamic open/close announcements.
• Set the page language to English (lang="en") so screen readers use the correct pronunciation rules.

Known limitations

The following areas have not yet been verified through end-to-end testing with assistive technologies:

• Screen reader announcements: Live region announcements on form submission (success, error, and validation failure) have been implemented but not verified with NVDA, JAWS, or VoiceOver.
• Keyboard navigation end-to-end: Skip-link focus behavior, mobile menu keyboard operation, and focus management after form validation failure have been implemented but not tested with keyboard-only navigation in a browser.
• Touch target sizes: Interactive elements are designed to meet the 24×24 CSS pixel minimum (WCAG 2.2 §2.5.8), but computed sizes have not been verified in browser DevTools.
• iOS date inputs: The booking form uses type="date" inputs, which render as native date pickers on iOS. VoiceOver compatibility has not been tested on an iOS device.
• Third-party content: Embedded content or widgets provided by third parties (such as Instagram links) may not fully conform to WCAG 2.2 AA. We do not control the accessibility of third-party services.

Important notice

This statement describes the steps we have taken and the issues we are aware of. It is not a certification of full ADA or WCAG compliance. Accessibility conformance requires ongoing testing with real users and assistive technologies. We have not conducted a formal third-party audit. If you encounter a barrier, please tell us — your feedback directly shapes our improvements.

How to report an accessibility problem

If you have difficulty using this website, please email [email protected]. Include the page address, a description of the problem, and how we can best assist you. We will review your message and work with you to provide the information or assistance you need in an accessible format.

Continuous improvement

Accessibility is an ongoing effort. We review this site when we make significant changes and act on feedback we receive. We welcome suggestions even if you are not experiencing a specific barrier — if you think something could work better for more people, we want to hear it.