Accessibility Statement

Last updated: October 8, 2026

Integrevise is committed to ensuring that its platform is accessible to the widest possible audience, including individuals who use assistive technology or who have specific access needs. This statement applies to the Integrevise web platform. It describes the standards we work to, the features we have built into the product, how the platform has been assessed, and how to contact us if you encounter a barrier.

Scope

This statement covers the production Integrevise web platform, including the learner, educator, analytics, and administration interfaces. The optional customer support chat widget is supplied by a third party, and external websites linked from the platform are operated independently. Both are outside the scope of this statement.

Conformance Status

The platform is designed and developed to conform to the Web Content Accessibility Guidelines (WCAG) version 2.1, Levels A and AA. The platform meets all but two of the WCAG 2.1 Level A and AA success criteria. It is therefore partially conformant with WCAG 2.1 Level AA. Partially conformant means that some parts of the content do not fully conform to the standard.

Both exceptions relate to optional session recordings, which are off by default and are enabled for an individual assessment only where the teacher chooses to do so:

  • Captions (Prerecorded), success criterion 1.2.2: recorded sessions do not yet include a synchronised caption track. A full text transcript of each session is displayed alongside the player.
  • Audio Description (Prerecorded), success criterion 1.2.5: audio description of the recorded video is not currently provided. A timestamped event log describes the visual information in the recording as text.

Compatibility

The platform is designed and tested to work with current versions of the following:

  • Browsers: Google Chrome, Microsoft Edge, Mozilla Firefox, and Apple Safari, on both desktop and mobile devices.
  • Screen readers: NVDA and JAWS on Windows, VoiceOver on macOS and iOS, and TalkBack on Android.
  • Operating systems: Windows 10 and Windows 11, macOS, iOS, and Android.

Technical Specifications

The platform is delivered using HTML, CSS, JavaScript, and WAI-ARIA, the international standard for accessible rich internet applications. Its interactive components are based on widely used open source primitives that follow recognised accessibility patterns, including focus management, keyboard interaction, and screen reader semantics for menus, dialogs, popovers, tabs, and similar controls.

Measures to Support Accessibility

Text and Readability

  • Body text is presented at a comfortable default size and may be enlarged or reduced using standard browser or device settings.
  • Text sizes are defined in relative units, allowing the interface to scale proportionally when the system font size or browser zoom is adjusted, without disruption to layout.
  • Line height and letter spacing are configured to support sustained reading, including longer passages such as transcripts and feedback. Content remains usable when users apply their own text spacing settings.
  • Headings follow a consistent visual hierarchy across the product, supporting navigation by structure for both sighted users and screen reader users.

Zoom and Responsive Layout

  • The platform does not restrict pinch to zoom or browser zoom. Content and functionality remain available at zoom levels up to and including 200%.
  • Layouts adapt to a range of viewport sizes, from large desktop monitors to mobile devices. Content reflows at narrow viewport widths without loss of information or functionality.
  • Content and functionality remain available in both portrait and landscape orientations.

Colour and Contrast

  • The colour palette is governed by a centralised design system, ensuring that text and interactive elements meet WCAG Level AA contrast requirements against their backgrounds across all screens.
  • Focus indicators, form field boundaries, control states, and essential graphical elements meet WCAG non text contrast requirements.
  • Where status information is conveyed visually, for example in result summaries or charts, colour is paired with text labels and icons so that meaning is never communicated through colour alone.
  • Form fields, focus indicators, and error states use distinct visual treatments to remain identifiable within their surrounding context.

Assistive Technology Support

The interface is built using accessible component primitives that are designed to operate correctly with screen readers and keyboard input. For users of screen readers, the platform provides:

  • Accessible names for icon only buttons, allowing the screen reader to announce the function of the control.
  • Alternative text for meaningful images, including logos, sign in provider icons, and reference photographs. Decorative images are hidden from assistive technology.
  • Audible confirmations following key actions, such as the submission of feedback.
  • Status and validation messages that are announced to assistive technology without moving keyboard focus.
  • Form fields that announce their label, required state, and validation status, with error messages associated with the field they describe.

Page Structure

  • Pages are constructed using semantic landmark regions, including main content and navigation, enabling screen reader and keyboard users to move through the page by structure.
  • Each page has a descriptive title that identifies the current view or task.
  • Tabular data is presented using semantic table markup so that screen readers can describe rows, columns, and headings.
  • The page declares its language so that browsers and assistive technologies render content with appropriate pronunciation and behaviour.

Keyboard Navigation

  • All interactive elements are reachable and operable via the keyboard, including navigation, forms, dialogs, assessment controls, review interfaces, and administration workflows.
  • A visible focus indicator is rendered around the element that currently holds keyboard focus, and focus moves through each page in a logical order.
  • When a dialog or modal is opened, keyboard focus is moved into the dialog and constrained to it until it is dismissed, after which focus is returned to the originating element.
  • The conversational viva provides keyboard shortcuts for frequent actions, including toggling the camera, toggling the microphone, toggling transcription, and leaving the session. Shortcuts do not interfere with ordinary text entry, and a built in dialog lists the complete set of shortcuts and may be consulted at any time.

Conversational Viva

  • Live transcription and captions are available throughout conversational viva sessions and may be turned on or off from the session interface.
  • A typed response mode is available for users who prefer to type rather than speak.
  • Camera and microphone controls are clearly labelled, and audio never starts automatically.
  • The viva does not require device motion, multi point gestures, or path based gestures.

Recorded Sessions

  • Session recording is off by default and is enabled for an individual assessment only where the teacher chooses to do so.
  • Recorded sessions are presented to educators with a full text transcript displayed alongside the player, and a timestamped event log describing the visual information captured during the session, including identity check outcomes, face presence, gaze direction, head pose, and browser focus.

Assessment Time and Attempts

  • Viva sessions do not impose a time limit. The session timer shows elapsed time only and does not end the session.
  • Ordinary navigation and review tasks do not impose time limits.
  • Individual learners can be granted additional attempts.
  • Consequential assessment actions use explicit review and confirmation steps, and educators retain control over the review and release of assessment outcomes.

Forms and Input

  • Form fields are paired with visible labels.
  • Required fields are clearly indicated.
  • Inline validation provides clear, plain language error messages adjacent to the field requiring attention, including guidance on how to correct the error.
  • Common personal information fields use appropriate input attributes, allowing browsers and assistive technologies to help users complete them.
  • Text input is supported throughout the platform, including a typed message mode within the conversational viva for users who prefer to type rather than speak.

Errors, Loading, and Notifications

  • A descriptive page is presented in response to a request for a URL that does not exist, including alternative text for the accompanying illustration.
  • Background loading is communicated through skeleton placeholders, indicating that content is being retrieved.
  • An application level error boundary prevents an unhandled error from disrupting the entire interface.
  • The in app notification control announces the count of unread notifications to assistive technology.
  • The platform contains no content that flashes more than three times in any one second period.

Assessment Approach

The most recent accessibility assessment was a self assessment of the production web platform, completed in July 2026 against the WCAG 2.1 Level A and AA success criteria. The assessment combined automated testing using Lighthouse and axe DevTools (axe-core) with manual testing, including keyboard only navigation and testing with screen readers.

The review covered keyboard operation; semantic structure and WAI-ARIA; accessible names, roles, and states; focus management; validation and error handling; colour contrast; text resize and spacing; reflow; and responsive layouts. It also covered the conversational viva, including typed response mode, live captions, keyboard controls, camera and microphone controls, recorded session playback, and per learner attempt settings.

The findings are documented in an Accessibility Conformance Report based on VPAT® Version 2.5 (WCAG edition). A copy is available on request from info@integrevise.com.

Reporting an Accessibility Issue

If you encounter content or functionality on the platform that you are unable to access, or if you require information in an alternative format, please contact us at info@integrevise.com or contact your institution's student support team. Reports from users are an essential input to the continued improvement of the platform.

Who We Are

Company: Integrevise Ltd
Company number: 16264734, registered in England & Wales
Registered office: Alacrity House, Kingsway, Newport, Wales, NP20 1HG, United Kingdom
Accessibility enquiries: info@integrevise.com