> [[provide|Provided]] [[annotate|annotated]] evidence for usability testing[^1]. Testing to inform evaluation is worth only 5 marks, but it forms the foundation of your final evaluation. Usability testing is one of the two key components of this stage, and without strong evidence here, it may be difficult to access all marks in the final evaluation. Annotated screenshots or videos can efficiently demonstrate testing of usability. Testing usability features often involves input from end-users—likely your stakeholders. Feedback from your stakeholders is "vital" at this stage in your evaluation[^2]. > [!check] Moderators' report > "Usability testing is often best evidenced by an end-user survey, interview or similar"[^3]. Stakeholder testing can be done with "use-case or scenario testing"[^2] . Use-case/scenario testing could look like a series of tasks given to the stakeholder, followed by some way of recording what they think about their experience. If you choose to interview or survey your stakeholder, there is no need to include the full text of it in the body of your write-up. Including the full text in an appendix with a summary of its impact in your write-up is likely sufficient. It is important that the impact is discussed rather than just stating facts[^2]. ## Notes [^1]: OCR, “Computer Science H446 A Level Specification,” OCR, March 2024, 25, https://www.ocr.org.uk/Images/170844-specification-accredited-a-level-gce-computer-science-h446.pdf. [^2]: Cambridge OCR, A Level Computer Science: A Guide to Creating Concise NEA Documentation, 2026, video, 39:05, https://train.ocr.org.uk/mod/scorm/view.php?id=1893. [^3]: OCR, “A Level Computer Science Moderators’ Report H446/03/04 Summer 2024 Series,” OCR, 2024, 6, https://www.ocr.org.uk/Images/726389-moderators-report.pdf.