Kapi FormsAccessibility
Kapi Forms
Accessibility conformance report
For the pages people use to answer Kapi Forms: a form's steps, Check your answers and the thank-you page; booking, the booking page and its ticket; joining a queue and its ticket page; and Report this form. Written against WCAG 2.2 levels A and AA.
- Status
- Draft, for review before launch
- Standard
- WCAG 2.2, levels A and AA
- Date
- 2 November 2026
- Checked by
- Kapi's automated tests of these pages, which run in a simulated browser
No one has yet tested these pages with a screen reader or other assistive technology. That review is planned before launch, and this report will change with it.
Supports: every criterion in the group has been checked and holds. Partially supports: a criterion in the group falls short somewhere. Not yet evaluated: not every criterion in the group has been checked, and the remarks say what has.
| Guideline and criteria | Conformance | Remarks |
|---|---|---|
| 1.1 Text alternatives1.1.1 | Not yet evaluated | The organisation's mark, welcome photo and background picture are shown as decoration, with empty alt text, and its name is in words beside its mark. Not yet checked: any other picture an organisation adds. |
| 1.2 Time-based media1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5 | Not yet evaluated | A question may show a YouTube or Vimeo video the organisation adds. Its captions and audio description come from the organisation, and are not yet checked. |
| 1.3 Adaptable1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5 | Not yet evaluated | Automated tests check that each question is a named group or field, that its heading carries the question and its count, and that name, email, phone, website, organisation and job title fields say what they collect, for autofill (1.3.5). Not yet checked: reading order, orientation, wording about shape or position, and the newer question kinds. |
| 1.4 Distinguishable1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13 | Not yet evaluated | Colours come from each organisation's design. Kapi's code chooses the text and button colours so words read at 4.5:1 or better and lines and controls at 3:1 against the page; the button colours have automated tests. Not yet checked on the pages themselves, nor zoom, reflow, text spacing or content shown on hover. |
| 2.1 Keyboard accessible2.1.1, 2.1.2, 2.1.4 | Not yet evaluated | Automated tests answer forms with the keyboard: Enter continues, Back keeps the answers, letter keys pick a choice and are announced as shortcuts, and keys typed while the next question opens reach it. Not yet checked: bookings, queues, files and the newer question kinds by keyboard, and whether the letter keys need a way to turn them off (2.1.4). |
| 2.2 Enough time2.2.1, 2.2.2 | Not yet evaluated | Automated tests check that a quiz with a time limit shows the time left and announces it at 5 minutes and at 1 minute, and that a booking shows how long its places are held before it is made. Not yet checked: whether each time limit can be extended, and the queue ticket's page, which updates itself. |
| 2.3 Seizures and physical reactions2.3.1 | Not yet evaluated | Not yet checked. |
| 2.4 Navigable2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.11 | Not yet evaluated | Automated tests check that each step's heading takes focus, that the page title names the question and begins with Error: when there is a problem, that problems link to their fields, and that focus shows on the problems a script moves it to, as on buttons. Not yet checked: skipping repeated content (2.4.1), the purpose of each link, and focus hidden by other content (2.4.11). |
| 2.5 Input modalities2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8 | Not yet evaluated | Automated tests check that a signature can be typed instead of drawn. Not yet checked: target sizes, dragging in ranking questions, pointer cancellation and labels in names. |
| 3.1 Readable3.1.1, 3.1.2 | Not yet evaluated | An automated test checks that an English form's page states its language. Every page takes its language from the form's, and a right-to-left language turns the page right to left. Not yet checked: words in another language within a page (3.1.2). |
| 3.2 Predictable3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6 | Not yet evaluated | Automated tests check that choosing an answer keeps the person on the question until they continue, with Continue, Enter or a choice's letter key, which each choice shows, and that a form's footer names whose form it is and who to ask (3.2.6). Not yet checked: the rest of this group. |
| 3.3 Input assistance3.3.1, 3.3.2, 3.3.3, 3.3.4, 3.3.7, 3.3.8 | Not yet evaluated | Automated tests check that problems are listed at the top and linked to their fields, that each field's message begins with Error: and says how to fix it, with an example such as name@example.com, that Check your answers comes before sending, with Change for each answer, and that answers kept in the browser come back. Not yet checked: details asked again within a booking (3.3.7), and the emailed code for one answer per person (3.3.8). |
| 4.1 Compatible4.1.2, 4.1.3 | Not yet evaluated | Automated tests check the names and roles of text, email, phone, website, date, number, yes or no, choice and tick box controls, and that sending and the spam check's result are announced politely. Not yet checked: rating, scale, grid, ranking and the other newer question kinds. |
Tell us about anything that gets in your way: support@kapiworks.com.