Start with the task a learner must complete
List the steps: find the task, understand the instructions, use the supplied material, provide a response and check submission. Review the complete journey rather than just the appearance of the first screen.
Discuss known access needs with the appropriate school staff and the learner where suitable. A general label on a product cannot establish that a particular task works for everyone.
Check the interaction
- Can the task be completed using the required keyboard or assistive technology?
- Are instructions, labels and error messages understandable?
- Is important information available without relying only on colour?
- Do audio and video resources have suitable alternatives?
- Can required adjustments be made without changing the learning being assessed?
Try the actual setup
Test the devices, browser, account role and response format intended for use. Include the point at which a student reviews or submits an answer.
Record what was tried, what happened and any adjustment needed. An automated scan can help identify issues, but it cannot settle every accessibility question.
Know the limits of a preview
The GoHiMark public tools are a way to explore examples. They do not certify that a future school assessment service or every question format meets accessibility requirements.
Use the W3C guidance as a reference and arrange the testing and support appropriate to the school’s context.
Further reading
These sources offer further context. Links do not imply endorsement of GoHiMark.
Explore the question examples or estimate a task with the marking workload planner.