Accessibility

Accessibility statement

BK ClinicQ aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA on every screen a patient or a clinic's staff use. This page says how close it is, how that is checked and what is not yet tested.

Last reviewed: 27 September 2026

How accessible it is

BK ClinicQ partially conforms to WCAG 2.2 level AA. Every page and journey that has been tested meets AA; the limitations below are the parts not yet tested, or not yet tested by a person.

Joining a queue, checking a ticket's place in line and cancelling a ticket all work with a keyboard alone, with the focus visible at every step and never trapped.

What is checked, and how

Before each release, automated WCAG 2.2 A and AA checks run in a real browser on every page below, in the light and the dark theme. A failure stops the release.

Who uses itWhat is checked
PatientsThe front page, this page, the privacy notice and terms, clinic search, a clinic's page, every step of joining, the app's home and sign-in, a ticket and its cancel question, and the consent page; on a phone-sized screen
Clinic staffThe front desk, walk-ins, ticket lookup, the room view, priority overrides, the reports, the audit trail and every clinic settings screen; on a desk-sized screen, as the role that uses each
The waiting roomThe board in its three themes with a call on it, the pairing screen and the check-in kiosk

What was fixed

  • Text on the front desk that was below 4.5:1 contrast now meets it.
  • The choices in the dialog for moving a patient are now large enough to tap, with room between them.
  • A list's quick view can now be scrolled with the keyboard.
  • A clinic's page refreshes every 30 seconds; the focus now stays on Join the queue through a refresh.
  • After cancelling a ticket, the focus moves to the answer, which a screen reader reads out.
  • A ticket's place in line is announced by a screen reader when it changes.
  • The clinic switcher, an address choice and the breadcrumbs now show a focus ring.

Known limitations

  1. No person has yet used BK ClinicQ with a screen reader. The joining steps were recorded with the keyboard alone, together with what the browser tells a screen reader at each step. Before the pilot's first patient, the joining, checking and cancelling journeys will be run with TalkBack on Android and VoiceOver on an iPhone.
  2. Automated checks find only part of WCAG. They cannot judge whether a label makes sense or an error is understandable. The screen-reader runs cover this for patients, and a review of the clinic dashboard's forms follows in user testing.
  3. The clinic dashboard has not been measured at 200% zoom. It is designed for a desk screen; the patient pages are tested at 320 pixels wide.
  4. The Chromecast receiver page is not checked. It frames the board, which is checked, and will be checked on a device when casting is released.
  5. The platform team's own administration consoles are not in this audit. They will be audited before any clinic staff are given access to them.
  6. English only. Other South African languages are planned.
  7. The waiting-room board has not yet been read on a real screen at 5 metres. Its contrast and text size have been measured.

Telling us about a problem

If something in BK ClinicQ is hard or impossible to use with your device, your assistive technology or your way of working, tell the clinic's front desk, or contact the operator of this service (named in the privacy notice). We answer every report, and a problem that stops someone joining a queue is fixed first.