How Do You Test Accessible Appointment Booking?
Test the complete booking journey: choose a service, select an available date and time, review the details, and confirm or change the appointment. Check each step with a keyboard and a screen reader, including what happens when a slot disappears before submission.
ADASupport · Published and sources checked November 21, 2026

How do you test the date picker?
Start with the date field and complete the task without a mouse. Check that the picker opens from a clearly named control, shows visible focus, communicates the selected date, and returns focus sensibly when closed. If it allows typed dates, expose the format and test whether typing works as an alternative.
W3C’s date-picker dialog is one example of how a custom calendar can manage focus and communicate changes. Its example is not a drop-in compliance solution; test the actual controls in the browsers and assistive technology your audience uses.
How should available times and time zones be presented?
Give each available time a readable label, show the applicable time zone next to the choices, and make the selected slot clear without relying on color. If choosing a date updates the times, verify that people can discover the new options in a predictable place without losing their position.
Test a day with no appointments and another with multiple slots. If the service shows equivalent times in two zones, make it clear which zone is used in the confirmation. Test a date near a daylight-saving change when the service operates across affected zones.
What should happen when a selected slot disappears?
Explain in text that the requested slot is no longer available, keep answers that are still valid, and provide a clear route back to the updated times. Check that a screen reader user learns what changed and can get to a replacement time without starting the entire booking again.
Use two permitted test sessions in staging to check the case where someone else books the same time first. If the page changes without a navigation or move of focus, verify that important feedback is available to assistive technology. Do not announce every small display change.
What should the review and confirmation show?
Before submitting, let the person review the service, date, time zone and location or meeting format, and provide a way to change the selection. After submitting, confirm the result in text and test any links used to retrieve, change or cancel the booking. A selected slot is not a confirmation.
Include the configured third-party scheduler if it handles any step. Use synthetic test information. Record the browser, input method, assistive technology, expected result and actual result, then retest repaired steps. This checklist tests selected barriers; it does not establish full WCAG conformance or legal compliance.
Is checking the calendar enough to test booking accessibility?
No. A person may select a date successfully and still be unable to find an available time, verify the time zone, recover from a booking conflict, or read the confirmation. Include every step in the configured journey, even when the scheduler or confirmation is hosted elsewhere.
Should unavailable slots be distinguished by color alone?
No. If unavailable times are shown, use text or another visible cue as well as color and make the state available to assistive technology. If the interface instead hides unavailable times, clearly explain when there are no choices left and give the user a way to look at another date.