Auto Light Dark
Auto Light Dark
Breadcrumbs

Accessibility

Apwide Booking is built with the Atlassian Design System and runs inside Jira Cloud. We test it against WCAG 2.2 level AA and publish an Accessibility Conformance Report (VPAT® 2.5 INT) on our Trust Center.

Our latest evaluation (November 2026) found barriers that we are working on. They are listed below with ways to work around them.



Accessibility features

  • Keyboard. Booking a resource (with each booking experience: Time Selection, Resource Availability, Time Slots), rescheduling, the setup wizard and the flow editor can be used with the keyboard only (Tab, Shift+Tab, Enter, Space, arrow keys in lists, menus and calendars, Escape to close menus, calendars and the booking dialog).

  • Labels and names. Form fields, pickers and buttons have accessible names that screen readers announce, including the start/end time pickers, the duration selects and the fields of the flow editor.

  • Status messages. The availability result of the booking dialog ("Desk 1 is available…"), resource suggestions, the setup wizard's progress and save errors are announced by screen readers without moving focus.

  • Focus. Focus is always visible, and is kept on the page after an action: after "Next" in the setup wizard focus moves to the new step's title; after moving a resource up or down it stays on the moved row.

  • Light and dark themes. The app follows the theme chosen in Jira (Personal settings > Theme) and uses the Atlassian colour tokens. Text meets 4.5:1 contrast in both themes.

  • Zoom. The booking dialog, the Booking Hub and the flow page's Resources and Timeline tabs work at 200% zoom and at 320 px width without horizontal scrolling. The timeline scrolls horizontally inside its own area.

  • Errors. Invalid input is reported in text (for example "End date must be after Start date").



Compatibility

  • Browsers: the browsers supported by Jira Cloud. Tested with Chrome and Firefox.

  • Assistive technologies: no testing with screen readers (JAWS, NVDA, VoiceOver, TalkBack), speech recognition or switch access has been done yet. The app relies on standard HTML and WAI-ARIA, and on Jira's own frames, dialogs and notifications.



Known limitations and alternatives

  • Timeline. Bookings in the timeline cannot be opened, created or moved with the keyboard, their status is shown by colour only, and their labels are cut off at 200% zoom or with larger text spacing. Alternative: the List tab shows the same bookings in full, with their status in text, and every action; use "+ Book" to create a booking.

  • Reordering. Resource filters and additional booking flows in the flow editor can only be reordered by dragging. Alternative: remove them and add them again in the order you want.

  • Resource availability day view. The quarter-hour grid needs a mouse and its buttons are small. Alternative: type the start and end times in the pickers next to it.

  • Narrow screens. At 320 px width, the flow page's List tab, the setup wizard, the flow editor's Availability, Resources and General tabs and the administration page still scroll horizontally.

  • List tab controls. The reload button is announced as "↻" (it is "Refresh" on the Timeline tab), active filters are shown by a coloured dot only, and the "Book" and "Reschedule" buttons do not say which flow or booking they act on.

  • Form errors and required fields. Errors next to a field are not linked to it and are not announced; required fields are marked by an asterisk that screen readers do not announce. In the booking dialog, an end time earlier than the start time is changed to start + 1 hour without a message: check the end time before booking.

  • Automatic refresh. The List and Timeline tabs reload when bookings change elsewhere (other users, automation), and this cannot be paused.



Feedback

Tell us about accessibility problems or ask for help through the Apwide Customer Portal.