Accessibility statement

Our goal

This website targets WCAG 2.1 Level AA, the technical standard commonly adopted in settlement agreements under the Americans with Disabilities Act. We do not use accessiBe, UserWay, AudioEye or any similar overlay — overlays do not make a site conformant, and we would rather put the work into the pages themselves.

What we have done

• The first focusable element on every page is a "Skip to main content" link, so keyboard users do not have to tab through the whole navigation.
• Every interactive element can be reached with Tab and operated with Enter or Space. The focus ring is a navy-and-amber double ring, clearly visible on light cards and on the dark header alike.
• When the mobile menu opens, focus moves into it and Tab cycles inside it rather than escaping to something you cannot see. Esc closes it and returns focus to the Menu button.
• Pages use header / nav / main / footer, have exactly one h1, and never skip a heading level.
• Body text meets a contrast ratio of at least 4.5:1; form borders, icons and other interface components meet at least 3:1.
• Every form field has a real label, and required versus optional is stated in words — not by colour or an asterisk alone. When something is wrong, the explanation appears next to that field in plain words, with a warning glyph so the message never depends on colour alone.
• The contact form uses no image CAPTCHA. Spam is handled with honeypot fields, a timing trap and rate limiting; only submissions flagged as suspicious see a challenge, and that challenge is written in plain text a screen reader can read.
• The background video on the home page is silent and has a pause button in the corner that works with a keyboard. When your system asks for reduced motion we switch off entrance animations that move things around, and looping motion — but the video and ordinary hover effects keep working. Turning every animation off makes a page harder to use, which is not what accessibility means to us.
• Pages do not scroll horizontally or overlap at 200% zoom.
• Every page declares its own language in the HTML (lang="en", lang="es", lang="zh-Hans" and so on), and the Arabic pages also set dir="rtl", so screen readers use the right voice and the right reading direction.

We know it is not perfect

Accessibility is ongoing work, not a one-time sign-off. Automated tools catch roughly a third of real problems; the rest we only learn about from the people who hit them. If anything on this site gets in your way — a screen reader that cannot read something, a keyboard trap, contrast you cannot see, a layout that breaks when you zoom — please tell us and we will treat it as a real defect.

How to report a barrier

Please include the address of the page, the device and assistive technology you were using (for example iPhone with VoiceOver, or Windows with NVDA), and what happened.

Scope of this statement

This statement covers all pages on appt247.com in every language we publish. The booking widget your customers see on a shop's own website is served by the booking system, which we are also working to improve; if you ran into a problem on a shop's booking page, please report it the same way.

Last updated: 11 August 2026