Accessibility Usability Test Plan
Include people with disabilities in testing respectfully.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Plan usability testing that includes people with disabilities. Product and key tasks: [PRODUCT_TASKS]. Assistive technologies to consider: [ASSISTIVE_TECH]. Constraints: [CONSTRAINTS]. Outline recruitment through appropriate organisations, fair compensation, accessible communication and consent, session logistics (assistive technology setup, breaks, sharing materials in advance), test tasks, observation guide, and safety. Provide questions that avoid assumptions, and an analysis plan that separates issues by barrier type. Remind me this complements, not replaces, accessibility standards review and expert audits, to be confirmed [VERIFY]. Include a checklist for the moderator on language and conduct. Add a short list of principles for working respectfully with participants, such as asking about preferences before the session and not assuming what someone needs, and a table of common barrier types with the evidence to capture. Include a plan to report findings in a way that links to the relevant guidelines and to fix priorities. Also add a short section on reporting back to participants about what changed, as a matter of respect, and on keeping their information confidential.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.
See an example result (fictional data)
Product: appointment booking. Tasks: find a time, book, cancel. Participants: 5 recruited through a disability organisation, paid fairly. Assistive technologies: screen reader, magnification, switch access, voice control. Logistics: send materials in advance; allow breaks; remote setup check the day before. Questions that avoid assumptions: "What do you usually do first on a page like this?" Observation guide: where did they get lost? What did the screen reader announce? Analysis: group issues by barrier type, link to relevant guidelines [VERIFY]. This complements, not replaces, an expert audit. Report back to participants on what changes.
Illustrative only, made-up data. Your results will differ and must be reviewed.