Task-based evaluation with personal assistive technology
Generated file currentAuthoring: Content completeWhat file status means
This status reports only whether the generated procedure matches the current controlled source hash. It is not independent content verification, regulatory approval, product evidence or a conformance decision.
Recorded standards review: No optional specialist review recorded. Next review: Not scheduled.
Observe disabled participants completing realistic tasks with their personal assistive technology under an approved, privacy-protective study protocol.
Available formats
Use this test in the format you need
The HTML procedure includes the working worksheet. JSON provides the structured source data. Editable Markdown files are delivered inside package downloads.
Observe disabled participants completing realistic tasks with their personal assistive technology under an approved, privacy-protective study protocol.
What this result means: This procedure determines whether Evaluate a task with disabled participants meets its stated expectations for the recorded targets and accessibility-user-research. Unexecuted targets, states and environments remain outside that result.
Why it matters
Identify accessibility and usability barriers that standards checks or laboratory configurations may miss. People most likely affected: the disabled participant groups represented by the study; findings must not be generalised to all disabled people. Important barriers, effort, workarounds and recovery problems may remain invisible if assessment uses only standards checks and synthetic environments. In the recorded accessibility-user-research environment, protect participant consent, support needs and privacy while observing the complete task; an inaccessible study method can harm participants and produce findings that misrepresent their experience.
When to use it
Use when disabled-user evaluation is ethically approved and useful for the study objective. Combine findings with standards evaluation; do not use the study alone to claim WCAG conformance.
Confirm before starting
Is there a specific research objective that requires disabled-user evidence?
Are participant characteristics relevant to the target audience and study question?
Are recruitment, informed consent, accessibility accommodations, privacy, safeguarding, retention and withdrawal procedures approved?
Mark it not applicable only when
Disabled-user evaluation is not part of the authorised engagement or no ethically approved study protocol exists. This does not mean user barriers are absent.
Exceptions
This is an informative usability-evaluation method, not a normative conformance rule. Protocol exclusions and ethical stop conditions are study design controls, not normative exceptions.
Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.
Participant context
Coded relevant characteristics, personal assistive technology/environment and accommodations.
Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.
Task observation
Task actions, completion, assistance, interruption/recovery, impact, workarounds and consented evidence reference.
Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.
Analysis record
Separation of standards findings, usability observations, platform limitations and unresolved questions.
Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.
Privacy and review record
Consent restrictions, reviewer findings, retention/deletion dates and authorised outputs.
Use a redacted extract or evidence reference. Do not include credentials, secrets or unnecessary personal data.
Worked example and outcome calibration
A11Y-USER-003-WORKED-001: representative worked example
Context: Illustrative research record for a Civic Benefits Portal address-change journey; no participant session occurred.
Inspected: The prepared task script, consent flow, observation categories, assistance threshold, synthesis and reporting boundary.
Observed output: A representative observation describes a participant becoming unsure after an address lookup clears the street field, requesting help at the declared threshold and explaining that the change was unexpected.
Evidence:
EVD-REF-017 synthetic observation sheet
EVD-REF-018 representative participant-statement field
EVD-REF-019 synthesis trace
Tester reasoning: The example shows how to separate behaviour, reported impact and facilitator inference. It cannot establish frequency or represent real-user evidence because no participant performed it.
Decision: blocked
Finding: FND-REF-005 — Address lookup replacement is not explained. A user may lose entered address detail and need assistance to recover.
Remediation: Announce before replacement what the lookup will change, preserve manually entered values where possible and provide an explicit undo or edit path.
Reviewer feedback: Reviewer replaced 'users will abandon' with the bounded statement 'the representative scenario may require assistance' and marked all participant-derived fields synthetic.
Final client wording: Prepared research hypothesis: replacing manually entered address text without explanation may cause loss of context and assistance. Validate this with consented participants before presenting it as observed user evidence.
Retest: RT-REF-006 cannot occur until an authorised participant study and a remediated product build exist; the pilot package is ready for scheduling.
Boundary: This is a representative, synthetic worked example for training and calibration. It is not evidence from a client product, participant or real assistive-technology execution.
Outcome calibration
Passed
Under the approved protocol, each participant completes the selected task with their normal assistive technology; observations and limitations are reported only for the represented sample.
The study-defined task outcome passes without becoming a WCAG claim.
Failed
Several participants cannot recover from a validation error within the declared assistance threshold, and the source observations support a material task barrier.
The study-defined task fails; a separate technical test is linked for any standards claim.
Not applicable
The engagement authorises standards testing only and includes no disabled-user study.
The method is not part of scope; this is not evidence that users face no barriers.
Cannot tell
A participant abandons a task but declines follow-up, leaving the cause and impact ambiguous.
Preserve the observation and uncertainty without inventing a cause.
Not tested
Participants were recruited, but an inaccessible consent document blocks lawful session execution.
The execution is blocked and task outcomes remain untested.
Sampling, complete processes and platform limitations
Recruit participants and select tasks from the research plan. Record who and what the sample represents, without treating it as universal coverage.
If this check is part of a user journey, test the selected journey from start to finish, including relevant errors and recovery. Record any path that was not tested.
A small study cannot be generalised to all disabled people and cannot establish WCAG conformance by itself.
Check relevant browser, tool or assistive-technology release notes before assigning unexpected behaviour to the product.
If responsibility is unclear, record the reproducible behaviour and use cannot tell until it is resolved.
Related procedures
No related procedure is recorded.
ACT rules and WCAG technique traceability
This is a project-authored manual procedure, not a W3C Approved ACT Rule. An ACT result can support only the part of this procedure covered by that rule. It does not replace the remaining manual or assistive-technology checks.
No supporting W3C Approved ACT Rule is selected for this procedure.
This specialist procedure is not assigned to one WCAG success criterion.
Review history and source register
2026.08.27-rc.9 — Reworked for plain language, case-focused steps, scoped evidence and transparent draft review status.
2026.08.27-rc.9 — Migrated to professional catalogue schema v3 with separated outcomes, structured authority, applicability, evidence, decision and review records.
2026.08.27-rc.9 — Specialist procedure mapped to its task family and current first-party platform guidance and checked for internal consistency; competent review and real execution remain separate.
2026.08.27-rc.9 — Replaced migrated boilerplate with a case-specific reference implementation and completed generated-file integrity review.
2026.08.27-rc.9 — Rewritten as an atomic professional-delivery flagship with component effort guidance and a complete representative worked example.
2026.08.27-rc.9 — Procedure guidance and presentation simplified without changing draft governance status.
Review decision: pending. Open issues: No participants have been recruited and no user-study execution, consent, data or review is claimed.; A qualified user researcher, privacy reviewer and disabled research adviser must review the protocol before execution.