Accessibility in Candidate Assessment

Accessibility in candidate assessment is a failure-analysis control, not a checkbox on a test vendor's page. A privacy reviewer should record what the assessment measures, which access route was offered, what evidence was used and who could pause the decision. This is general educational information, not legal advice or a conformance claim.

Set the assessment boundary

Name the role, brief version, stage and modality: CV review, written test, work sample, interview, video response or another method. Record the assessment owner, accessibility contact, time limit, equipment assumptions, scoring rule, essential functions and every system receiving a response. Keep an access request separate from the evidence used to assess job-related capability.

The OPM Assessment Decision Guide, issued 6 June 2007, starts with job analysis and connects tasks, competencies and assessment content. It warns that administration conditions, time limits and scoring can introduce error. Ask whether a result reflects the competency or an avoidable barrier; consult qualified advisers for applicable rules.

Test modality and accessible design

WCAG 2.2 became a W3C Recommendation on 12 December 2024. For a web assessment, test keyboard operation, visible focus, labels, text alternatives, contrast, zoom and reflow, captions, error recovery, timing controls and a non-drag path. Test with assistive technology and people, not only an automated scan. WCAG addresses web content and does not prove that an assessment is fair.

For a timed task, ask whether speed is an essential, documented part of the work or merely a test convention. Offer an equivalent format or adjustment that preserves the job-related construct: for example, keyboard input instead of drag-and-drop, a screen-reader-compatible document, captions, a quieter room, a break or additional time where appropriate. Do not force a candidate to use an inaccessible channel while an alternative is being considered.

Run an adjustment request safely

Tell candidates, in plain language, what the assessment measures, its format, timing, technology and how to request access support. Use inclusive language such as disabled person or person with a disability according to the person's preference. Avoid assumptions, euphemisms and labels such as suffers from; never treat eye contact, accent, handwriting or a communication style as a capability proxy without job-related evidence.

The EEOC resource guide issued 3 February 2015 describes recruiting and reasonable-accommodation questions, while the EEOC's pre-employment guidance explains limits on disability-related questions before an offer. The latter page displays no issue date; both are US guidance, not universal law. Ask what access the candidate needs, not for a diagnosis. Name one accommodation owner, confirm options, record a decision and provide a question route. If the request is unresolved by the assessment date, pause rather than making the candidate absorb the risk.

Keep documentation to the minimum needed. A privacy or accommodation owner should see sensitive details only when necessary; assessors should receive the access instruction, not a diagnosis. Do not put medical documents in general email, chat or scoring notes. Use restricted access, authentication, audit logs, encrypted transfer and a retention and deletion review. The ICO's AI recruitment considerations dated 6 November 2024 call for a DPIA where appropriate, a lawful basis, clear responsibilities, minimisation, transparency and fairness monitoring. Consent may be relevant to one action, but is not blanket permission to collect or reuse health information; document the privacy decision with qualified advice. Source status was checked on 5 September 2026; re-open each authority before publication because the dates identify cited editions, not current law.

Separate essential from incidental criteria

For each criterion, write the essential job task, evidence, modality dependency, available adjustment and human decision owner. Remove incidental hurdles. A data-entry role may require accuracy and keyboard use, but not a mouse-only drag gesture. Customer support may require clear information exchange, but not an uncaptioned video response. Do not silently reward stamina, speed, facial expression or familiarity with one device when those are not essential.

Apply the same job-related standard after an adjustment and document why any difference is material. Review completion, access-request and progression signals only where collection is approved and interpretable; never infer disability from a name, profile, writing style or result. Non-discrimination requires human evidence review, not an AI label that says accessible or fair.

Use evidence gates and human ownership

Use these gates:

EVIDENCE: construct, access route, adjustment, provenance and owner are documented.
UNKNOWN: accessibility testing, criterion relevance or candidate need is not yet known.
HOLD: a material request, equivalent format or scoring question remains open.
STOP: the route is inaccessible, sensitive data was exposed, an unapproved proxy is used,
      security is compromised or nobody accountable can pause the assessment.

An EVIDENCE gate is not a hiring recommendation. The assessment owner maintains the design; the accommodation owner handles access; the privacy owner controls sensitive data; and the decision owner reviews the evidence and records the final human decision. No tool should automatically reject a candidate because a test could not be completed through an inaccessible route.

Fictional example and revision record

In this fictional example, a finance analyst work sample requires spreadsheet accuracy but includes a mouse-only drag exercise. A candidate asks for keyboard access and additional time. The reviewer marks HOLD, confirms drag speed is incidental, gives a keyboard-compatible sample and keeps request details away from the assessor. The revised score records accuracy, not the removed gesture. The owner later reviews completion and progression for a barrier, without inferring disability. This is not a benchmark.

Record each change so the earlier decision remains auditable:

Revision: 2026-09-05
Change: removed drag-only step; added keyboard-compatible path and access contact
Reason: candidate access review and WCAG 2.2 check
Owner: assessment lead; privacy reviewer retained the restricted request record
Gate: HOLD -> EVIDENCE after assistive-technology and human testing
Follow-up: review incidents, requests and retention at the next role cycle

Talent Summoner is our product for public-source candidate sourcing and CV ranking. Candidate sourcing starts from a role brief, while candidate ranking compares an existing CV set for human review. It does not run a candidate assessment, process accommodation requests, validate WCAG conformance, manage medical information or make automatic rejections. People own the accessible design, privacy decision and hiring outcome.

Publish the assessment format and access contact before inviting candidates; route evidence to candidate sourcing or candidate ranking only when owners and privacy controls are in place.