Back to home

Accessibility Statement

Last updated: 20 May 2026

1. Our commitment

CHAIR SOFTWARE LTD(“CHAIR”) wants the platform to be usable by everyone, regardless of ability or the assistive technology they use. We aim to meet WCAG 2.1 Level AA as a minimum standard, and we treat accessibility issues with the same urgency as functional bugs.

2. What we've built in

  • Keyboard navigation: all primary flows (browse, book, sign up, dashboard) can be operated with Tab / Shift+Tab / Enter / Esc — no mouse required.
  • Light and dark themes: the colour palette is designed to meet WCAG AA contrast ratios in both modes. The platform respects your system preference and remembers your choice.
  • Responsive layout: the platform reflows down to a 320px viewport and supports zoom up to 200% without horizontal scrolling on the main flows.
  • Semantic HTML: headings are in logical order, links and buttons are real <a> / <button> elements, and form fields have associated <label>s.
  • Reduced motion: non-essential animations are toned down when your system reports prefers-reduced-motion.
  • Focus indicators: every interactive element has a visible focus ring.

3. Known issues

We're honest that the platform is not fully conformant yet. Areas we know need work, and are tracking:

  • Some calendar / week-view interactions on the professional dashboard rely on drag-and-drop with no keyboard-only equivalent.
  • A handful of icon-only buttons in the dashboard are missing visible text labels (they have aria-labels but a sighted user without icon-vocabulary may struggle).
  • Charts and analytics widgets do not yet expose underlying data as an accessible table for screen reader users.
  • Some third-party embeds (Stripe Checkout, Google OAuth screens) follow their own accessibility standards, which we cannot directly modify.

If you hit an issue not listed here, please tell us — it almost certainly belongs on this list.

4. Compatibility

The platform is tested against:

  • The latest two versions of Chrome, Safari, Firefox, and Edge.
  • VoiceOver on macOS and iOS.
  • NVDA on Windows.
  • iOS and Android system zoom and font-size accessibility settings.

Older browsers may render the platform correctly but are not actively tested for assistive technology compatibility.

5. Reporting a problem

If you find something that doesn't work for you, or that we should improve, email [email protected]. To help us reproduce the issue, please include:

  • The page or flow where you hit the problem (a URL is ideal).
  • What you were trying to do.
  • Your browser and assistive technology (if any), including versions.

We aim to acknowledge accessibility reports within 2 working days and to give a fix or workaround within 10 working days. Reports that block someone from using a core feature get jumped to the top of the queue.

6. Enforcement

If you contact us about an accessibility issue and you're not happy with our response, you can contact the Equality Advisory and Support Service (EASS) — they handle complaints under the UK Equality Act 2010.

7. How this statement was prepared

This statement was prepared on 20 May 2026. The platform is assessed by a mix of automated tooling (axe, Lighthouse) on every deployment, and periodic manual checks using keyboard-only navigation and screen readers (VoiceOver, NVDA). We are not yet independently audited; an external WCAG audit is on our roadmap.