Eintech Accessibility Conformance Report

Name of Product: Rogo Classic Test Engine

Report Date: 13/06/25

Product Description: The Rogo Classic Test Engine is an online, browser-based e-assessment platform used by candidates to sit assessments.

Contact information: Eintech Product Team

Notes :

“Voluntary Product Accessibility Template” and “VPAT” are registered

service marks of the Information Technology Industry Council (ITI)

Evaluation Methods Used: Evaluations have been conducted by the Eintech Product Team with assistance from Quality Assurance Engineers, using Windows 11 on Chrome 142.0.7444.176. Assistive technology used included NVDA, Windows Narrator and Windows Voice Access. Initial evaluation was completed by The Shaw Trust, under the guidance of testers who have a range of access requirements.

Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

Standard/Guideline

Included In Report

Web content Accessibility Guidelines 2.2

Level A (Yes)

Level AA (Yes)

Level AAA (No)

Terms

The terms used in the Conformance Level column of this report are as follows:

Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.

Partially Supports: Some functionality of the product does not meet the criterion.

Does Not Support: The majority of product functionality does not meet the criterion.

Not Applicable: The criterion is not relevant to the product.

WCAG 2.x Report

Table 1: Success Criteria, Level A

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non- text Content	Partially supports	Only the Rogo header does not have a text alternative.
1.2.1 Audio-only and Video-only (Prerecorded)	Fully supports	Rogo provides an area to write alternative text for audio and video content.
1.2.2 Captions (Prerecorded)	Not applicable	Captions are the responsibility of clients.
1.2.3 Audio Description or Media Alternative (Prerecorded)	Not applicable	Providing audio description is at the discretion of clients.
1.3.1 Info and Relationships	Fully supports	Classic test engine provides information in a meaningful order.
1.3.2 Meaningful Sequence	Fully supports	Correct reading sequence can be programmatically determined in the Classic test engine.
1.3.3 Sensory Characteristics	Fully supports	Instructions for the classic test engine do not solely rely on sensory characteristics such as size or colour.
1.4.1 Use of Color	Fully supports	Colour is not the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
1.4.2 Audio Control	Fully supports	Users have the ability to pause, stop and adjust the volume of automatically playing audio that lasts longer than 3 seconds.
2.1.1 Keyboard	Fully supports	Classic test engine is operable via keyboard.
2.1.2 No Keyboard Trap	Fully supports	Classic test engine components can be navigated by keyboard.
2.1.4 Character Key Shortcuts	Not applicable	Character key shortcuts are not available in the test engine.
2.2.1 Timing Adjustable	Fully supports	Adjustable times in tests are settings permitted, but Rogo offers pausing capability to candidates and admins, and admins are able to add time onto exams.
2.2.2 Pause, Stop, Hide	Fully supports	Blinking and scrolling information are not part of Rogo. Auto-updates are present where essential and therefore cannot be paused. These updates do not flash.
2.3.1 Three Flashes or Below Threshold	Fully supports	Rogo does not contain pages that flash.
2.4.1 Bypass Blocks	Fully supports	It is possible to skip navigation in the Rogo Classic test engine.
2.4.2 Page Titled	Fully supports	Classic test engine web pages are titled in ways that provide accurate descriptions.
2.4.3 Focus Order	Fully supports	Focusable components receive focus in an order that preserves meaning and operability. For example, response options can be navigated sequentially in the Classic test engine.
2.4.4 Link Purpose (In Context)	Fully supports	Links in Rogo have text to provide context.
2.5.1 Pointer Gestures	Fully supports	Single-pointer operation suffices throughout the test engine, including Drag and Drop questions.
2.5.2 Pointer Cancellation	Fully supports	Drag-and-drop actions can be undone in the test engine. Where possible in tests, candidates can undo selected responses.
2.5.3 Label in Name	Partially supports	The majority of functionality in the test engine can be accessed using speech input where label names match the names of buttons and text. Remaining functionality (spreadsheet working, notepad, reading ruler) will be addressed in future.
2.5.4 Motion Actuation	Not applicable	No content is dependent on the ability to move a device (e.g. a monitor).
3.1.1 Language of Page	Partially supports	English language content can be programmatically determined and is usable by screen readers. Other languages are not supported.
3.2.1 On Focus	Fully supports	Context does not change when focus is given to a component in the test engine. E.g. focus given to the “Finish” button does not automatically click Finish and submit the test.
3.2.2 On Input	Fully supports	All changes of context are explicit, e.g. a Finish button at the end of tests, a Next button to go to the next section. No automatic changes (e.g. moving through the exam) occur in the test engine, and candidates are warned where certain sections have time limits.
3.2.6 Consistent Help	Fully supports	Human help within the test engine is limited to live invigilators. The chat box to contact an invigilator remains in the same order relative to other content.
3.3.1 Error Identification	Fully supports	Input errors (where candidates do not meet admin-set validation guidelines) are automatically detected and communicated in the test engine.
3.3.2 Labels or Instructions	Fully supports	Labels are provided where input is required (e.g. radio buttons, text boxes).
3.3.7 Redundant Entry	Not applicable	No requirement to re-enter information across the Test Engine.
4.1.2 Name, Role, Value	Partially supports	Name, role and value can be programmatically determined and is compatible with assistive technology. Some functionality is not available using speech-input software.

Table 2: Success Criteria, Level AA

Criteria	Conformance Level	Remarks and Explanations
1.2.4 Captions (Live)	Not applicable	Rogo test engine does not contain live audio.
1.2.5 Audio Description (Prerecorded)	Not applicable	Rogo test engine does not feature prerecorded video content. Any media uploaded is at the responsibility of end-users.
1.3.4 Orientation	Fully supports	Classic test engine is not restricted to a single display operation.
1.3.5 Identify Input Purpose	Partially supports	Not all functionality is supported by speech input software.
1.4.3 Contrast (Minimum)	Fully supports	Classic test engine meets a contrast minimum of 4:5:1, but images uploaded by clients are not covered.
1.4.4 Resize Text	Fully supports	Text can be resized up to 200% without loss of context. Rogo test engine re-adjusts the entire view to meet the resize parameters.
1.4.5 Images of Text	Fully supports	Images of text are only found in logos in the header and footer of Rogo.
1.4.10 Reflow	Fully supports	Content can be enlarged without increasing line length.
1.4.11 Non-text Contrast	Fully supports	User interface components (buttons, tools) have a contrast ratio of at least 3:1.
1.4.12 Text Spacing	Fully supports	Candidates are able to adjust text spacing with no loss of content or functionality in the test engine.
1.4.13 Content on Hover or Focus	Fully supports	Any additional content triggered when hovering over buttons is easily dismissible, hoverable and persistent.
2.4.5 Multiple Ways	Not applicable	Not applicable in an examination context, but navigator tools are available in screen options to permit candidates to locate sections in a test in multiple ways.
2.4.6 Headings and Labels	Partially supports	Majority of content in the test engine has headings and labels.
2.4.7 Focus Visible	Fully supports	All elements have suitable indicators (e.g. dashed lines) when in keyboard focus.
2.4.11 Focus Not Obscured (Minimum)	Fully supports	No components are hidden when interface components receive keyboard focus.
2.5.7 Dragging Movements	Fully supports	Dragging movements can be conduced using a single pointer.
2.5.8 Target Size (Minimum)	Fully supports	Buttons and inputs in the test engine are at east 24 by 24 CSS pixels.
3.1.2 Language of Parts	Partially supports	Assistive technology can identify English language content within the pages of the test engine. Other languages are not supported.
3.2.3 Consistent Navigation	Fully supports	Navigation through the test engine is predictable.
3.2.4 Consistent Identification	Fully supports	Components that have the same functionality (e.g. Finish buttons, on-screen tools such as the calculator) have a consistent style
3.3.3 Error Suggestion	Fully supports	Reasons that candidates receive validation errors are given to the candidate.
3.3.4 Error Prevention (Legal, Financial, Data)	Not applicable	Legal commitments and financial transactions are not part of the test engine.
3.3.8 Accessible Authentication (Minimum)	Fully supports	Autologin links can be provided to candidates, negating the need to remember a password.
4.1.3 Status Messages	Fully supports	Assistive technology informs users of changes in content

Disclaimer (Eintech)

Eintech has taken all reasonable steps to ensure the information in this report is accurate and reliable as of the report's date. However, we do not warrant that the Assessment Runner is entirely free of accessibility issues. The information contained in this document may be updated or modified without prior notice. This document does not create any contractual obligations, either explicitly or implicitly, and should not be considered part of any agreement between the parties.

Eintech Accessibility Conformance Report

WCAG Edition (Based on VPAT® Version 2.5)