Accessibility

Our commitment

We build this site to the principles of WCAG 2.2 Level AA. Accessibility is treated as part of the build rather than a retrofit.

What we have done

• Semantic HTML throughout, with a single h1 per page and no skipped heading levels — both checked automatically on every build.
• Full keyboard operability, including the mega menu, which uses buttons with aria-expanded rather than hover-only interaction. Escape closes and returns focus.
• A visible, high-contrast focus indicator on every interactive element.
• A skip link to the main content as the first focusable element.
• The FAQ accordions use native <details>, so answers are present in the DOM and operable without JavaScript.
• All form controls have real labels, with errors announced via a live region and linked with aria-describedby.
• Every animation is disabled under prefers-reduced-motion: reduce, and content is never revealed only by an animation's end state.
• Touch targets meet a 44px minimum.
• Colour contrast meets AA; primary buttons measure approximately 14.8:1.

Known limitations

• Embedded third-party content — a booking calendar or video player — is outside our control and may not fully meet AA.
• The interactive automation and voice demos are visual by nature. Their content is available as text, and we would welcome feedback on whether that is sufficient.
• This statement reflects our own testing. It has not been independently audited.

Reporting a problem

If something on this site is difficult or impossible to use, tell us at Pending: EMAIL and describe what you were trying to do. We treat accessibility reports as defects rather than requests, and will tell you what we are doing about it.