Skip to content

Accessibility

Booking should work for everyone.

Our accessibility statement for Developing Today Appointments: the standard we aim for, how we test against it, and what we know still falls short. Last reviewed 29 September 2026.

The standard

We aim for Developing Today Appointments to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, on this website, on the booking pages your customers use, and in the screens you use to run your business. The site has a light and a dark theme, follows your device's choice until you pick one, and the public pages reflow to a 320 pixel wide screen without scrolling sideways.

Conformance status

Developing Today Appointments partially conforms to WCAG 2.2 AA: most of it does, and the known exceptions are listed below.

How we test

  • Every page, public and signed-in, is checked by two automated checkers, axe-core and IBM Equal Access, against WCAG 2.2 AA, in both the light and the dark theme. That includes the states that are easy to miss: open dialogs, open menus and a service chosen on the booking page.
  • These checks run on every change before it can be released. A new problem stops the change. Known problems are listed, and the list can only get shorter: fixing one means removing it.
  • Tests book an appointment with the keyboard alone, and check that dialogs take focus when they open and give it back when they close.
  • The public pages are checked at 320 pixels wide for content that would need sideways scrolling.
  • Page changes are announced to screen readers.

Automated checkers find many problems, but not all of them. If something gets in your way that isn't listed here, we'd like to hear about it.

Known issues

These are the problems our checkers still report, in plain terms:

  • Booking page. One field's autocomplete setting isn't a value browsers recognize. On the link that covers every location, the location picker's list doesn't fully follow the pattern screen readers expect, and some of its parts lack a programmatic label.
  • Edit dialogs in the admin screens (business hours, holidays, appointments): some fields lack a programmatic label, or have it after the field, and the day-of-week list has the same picker issue as above.
  • Appointments screen. The calendar's grid structure isn't complete for assistive technology, and some button names don't match their visible text.
  • Admin screens generally. Some pages repeat an internal element identifier, which can confuse assistive technology that relies on it.

Feedback

If you have trouble using any part of Developing Today Appointments, or need something in a different format, please email [email protected]. Tell us the page and what happened, and what you use to browse if you're happy to, and we'll work on it.

Our sister product, Developing Today Accessibility, is the accessibility auditing platform we build.