Accessibility

We aim for WCAG 2.2 Level AA for the learner journey and the faculty application. We have not yet commissioned an independent audit and do not claim conformance; this statement is a self-assessment and will be replaced by an audited one when that work is complete. No VPAT or accessibility conformance report has been produced yet; one will be prepared with the audit.

• A typed alternative to recording is offered wherever the instructor's policy allows it, with no penalty; the consent text says so before anything is captured.
• Captions and text for the interviewer: when a spoken voice is unavailable or unsupported for a language, questions are shown as text with captions rather than falling back to a system voice.
• Keyboard operation of the learner recorder and the faculty workbench, with visible focus and no keyboard traps on modal surfaces.
• Live regions announce recording state and errors to screen readers.
• Reduced motion is respected: nothing essential moves, and animation is disabled for users who ask for it.
• Type and contrast: a 13px floor inside the application, navy on warm white for body text, and no information conveyed by colour alone (the active navigation item is marked by a rail as well as a colour).
• A technical problem is never an academic finding. A failed upload or a lost connection is recorded as a technical issue and the learner may resume.

• The evidence workbench for faculty is a dense, multi-panel screen; at narrow widths some panels stack in a long page and the keyboard order may not match the visual order in every state.
• Recordings made in a browser without media permissions show a plain error; the recovery path is the typed alternative, which is offered but could be made more prominent.
• Automatic transcripts contain errors. Faculty read the transcript alongside the recording, and learners are not assessed on transcript accuracy, but a learner cannot yet correct the transcript themselves.
• PDF and Word submissions are converted to text for questioning; the converted text is not shown back to the learner for checking.

An institution can, per activity, allow typed responses, extend time limits, disable video and keep audio, or run the explanation as a faculty-led conversation. Requests go through the institution's disability services office, which configures the activity with the instructor. Nothing about an accommodation is visible to the faculty reviewer as a signal about the learner; the reviewer sees the explanation.

If you cannot access any part of Verifi, tell your institution's accessibility office or write to [email protected] with Accessibility in the subject line. We reply within ten working days and fix what we can in the next release; where we cannot, we say so and offer the alternative path.

Institutions that are public bodies remain responsible for their own accessibility statements under the applicable regulations. This page is supplied so they can complete them accurately, and we will answer specific questions about a criterion on request.