# Include the people whose access needs your tests miss

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Include the people whose access needs your tests miss

ID: MHC-D-RESEARCH-1097 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/include-the-people-whose-access-needs-your-tests-miss

An accessibility score is not a person completing the task.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- An interface passes automated checks but some people still cannot use it.

### Avoid when

- Do not ask people to simulate a disability as a replacement for involving users. Participation must be accessible and voluntary.

### Explanation

Include participants with relevant disabilities and assistive technologies in realistic task evaluation. Ask about their usual setup and access needs before the session. Combine their findings with standards-based checks instead of making either stand for the other.

### Steps

1. Recruit across the relevant needs rather than treating one participant as representative of everyone.
2. Support the participant’s familiar tools and agreed accommodations.
3. Record barriers, successful workarounds and untested combinations explicitly.

### Example

A keyboard check passes, but a screen-reader user cannot tell whether a recording has finished processing.

### Check

Can the team connect each finding to a task, setup and observed barrier, while stating what was not tested?

### Limits

- Do not ask people to simulate a disability as a replacement for involving users. Participation must be accessible and voluntary.

### Evidence and sources

- supports: W3C recommends involving users with disabilities alongside standards-based accessibility evaluation. — RS-789B0E22EE7CFA3B. Neither a small user sample nor an automated scan certifies complete accessibility. (Combining user involvement with conformance evaluation.)
- RS-789B0E22EE7CFA3B: Involving Users in Evaluating Web Accessibility — https://www.w3.org/WAI/test-evaluate/involving-users/

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/give-the-user-a-goal-and-keep-your-instructions-out-of-the-result
Related (useful_with): https://vedokrok.com/knowledge/announce-the-result-without-stealing-the-user-s-place
