# Accessibility Before Assessment

Canonical URL: https://skillsociety.com.au/blog/dei/accessibility-before-assessment
Markdown URL: https://skillsociety.com.au/blog/dei/accessibility-before-assessment/markdown
Published: 2026-08-08
Author: Alberto Cubeddu
Excerpt: Hiring assessments only become valid when candidates can access the process, request support, and show the job skill being measured.

Assessment design often starts with the wrong question: "How do we test this skill?" Inclusive hiring starts one step earlier: "Can qualified candidates access the process well enough to show the skill?"

That order matters. A hiring assessment can be structured, predictive, and expensive while still being unfair if candidates cannot use the application system, understand instructions, request accommodation, complete the task with assistive technology, or avoid irrelevant barriers. When access fails, the company is not measuring job capability. It is measuring friction.

Accessibility is not a late-stage accommodation note. It belongs before assessment design, before vendor selection, before automation, and before candidates are invited.

## Access Is Part Of Validity

A valid assessment measures what it claims to measure. If a customer support exercise is intended to measure judgment, it should not accidentally measure whether a candidate has a quiet home office, a particular browser, perfect broadband, quick typing speed, confidence on video, or the ability to use an inaccessible form.

The ADA makes this principle concrete. EEOC guidance on employment testing explains that employers should administer tests so results reflect the skills or aptitude being measured rather than an impairment, unless that impairment-related factor is itself job-related and consistent with business necessity. ADA.gov guidance on testing accommodations gives practical examples such as screen readers, large print, Braille, extended time, accessible locations, and other changes that allow a test to measure the intended skill.

That logic applies to modern hiring workflows even when the assessment is not called a test. Application forms, chatbot screens, video interview platforms, timed work samples, coding environments, scheduling tools, and AI screening tools can all become assessment gates.

## Where Accessibility Breaks In Hiring

Accessibility failures rarely sit in one obvious place. They accumulate.

| Hiring step           | Accessibility risk                                                | What it may accidentally measure                          |
| --------------------- | ----------------------------------------------------------------- | --------------------------------------------------------- |
| Job ad                | Vague physical requirements, unexplained travel, unclear schedule | Candidate risk tolerance, not role fit.                   |
| Application form      | Poor labels, keyboard traps, timeouts, inaccessible uploads       | Ability to fight the form, not capability.                |
| Screening chatbot     | No clear alternative path, unsupported assistive tech             | Tool compatibility, not job evidence.                     |
| Timed test            | Unnecessary speed pressure                                        | Test-taking speed, not real work quality.                 |
| Video response        | Captions missing, no alternate format                             | Comfort on camera, bandwidth, disability disclosure risk. |
| Work sample           | Long unpaid task, unclear rubric                                  | Free time and insider knowledge.                          |
| Scheduling            | Only narrow business-hour slots                                   | Schedule privilege.                                       |
| Accommodation process | Hidden contact, unclear response time                             | Persistence and willingness to disclose.                  |

The danger is that these failures can look like candidate quality problems. Candidates disappear, submit incomplete materials, score poorly, or decline to continue. Without accessibility metrics, the team may never know why.

## The Evidence Principle

Every assessment should be governed by a simple rule: remove anything that does not improve role-relevant evidence.

If the role requires fast live response, a timed scenario may be appropriate. If the role requires thoughtful analysis, an artificial speed test may be a poor proxy. If the role requires video facilitation, a video exercise may be job-related. If the role does not require video performance, forcing a video response may add risk without adding much evidence.

Before launch, ask:

- What skill is this step measuring?
- Why is this format necessary?
- What assumptions does the format make about device, language, disability, time, location, bandwidth, or privacy?
- What accommodations or alternatives preserve comparability?
- What evidence would convince us the candidate can do the job if this format is inaccessible?
- How will reviewers compare alternate evidence fairly?

The answer cannot be "the vendor default." Defaults are design decisions made outside your hiring context.

## Use WCAG As A Baseline, Not A Finish Line

For digital hiring experiences, WCAG is the most practical baseline. WCAG 2.2 organizes accessibility around content being perceivable, operable, understandable, and robust. Those words translate directly into recruiting operations.

Perceivable means candidates can receive the information. Job ads, instructions, error messages, videos, documents, and assessment prompts need accessible text alternatives, readable contrast, captions where relevant, and clear structure.

Operable means candidates can complete the workflow. Keyboard-only navigation, visible focus states, no keyboard traps, enough time, and predictable controls matter in application forms and assessments.

Understandable means candidates know what is being asked. Plain-language instructions, consistent labels, clear error messages, and no hidden rules reduce confusion and avoid punishing candidates who do not already know the company's hiring norms.

Robust means the experience works with assistive technologies. A form that only works visually is not robust.

WCAG compliance alone does not answer every hiring fairness question, but it gives teams a shared standard for digital access. The DOJ's 2024 rule for state and local government web and mobile accessibility points to WCAG 2.1 AA for covered public entities, and many private-sector teams use WCAG AA as a procurement and quality benchmark even when their legal obligations differ by context.

## The Application Form Is An Assessment

Many companies think assessment begins after application. For disabled candidates, the application form may be the first and hardest test.

The ADA National Network summarizes research where 16 blind screen-reader users attempted 32 online applications across 16 companies. Only 9 of 32 application attempts could be completed independently without assistance. That finding is older, but it remains instructive: a company can lose qualified people before recruiters ever see them.

Application accessibility needs practical checks:

- Can the form be completed with keyboard only?
- Are labels programmatically associated with inputs?
- Are required fields clearly identified?
- Are error messages specific and announced accessibly?
- Are uploads optional when the same evidence can be provided another way?
- Does the session timeout preserve work?
- Can candidates review before submitting?
- Is the accommodation contact visible before the candidate reaches a blocked step?
- Does the form work on mobile, desktop, screen readers, and common browsers?

If the application is broken, later assessment quality does not compensate.

## Timed Tasks Need A Business Case

Timed assessments are common because they are convenient, comparable, and easy to score. They are also risky when speed is not essential to the job.

A timed test can measure:

- Role-relevant speed under realistic conditions.
- Familiarity with the test format.
- Typing speed.
- Anxiety response.
- Disability-related processing differences.
- Internet reliability.
- Access to uninterrupted time.
- Whether instructions were clear on first reading.

Only the first item may be relevant. If the role does not require the same speed condition, use a more realistic measure. Give candidates a reasonable window, explain expected effort, and allow accommodation requests before the timer begins.

## Accommodation Must Be A Workflow

Accommodation is often described as a candidate-facing sentence: "Contact us if you need accommodation." That is not enough. The candidate needs to know the request will be handled promptly and privately. The recruiter needs to know who owns the decision. The hiring manager needs to understand how alternate evidence will be compared. The system needs to store sensitive information appropriately.

A mature accommodation workflow defines:

| Workflow element | Good operating question                                                 |
| ---------------- | ----------------------------------------------------------------------- |
| Visibility       | Can candidates find the request path before every high-friction step?   |
| Ownership        | Who receives, triages, and approves the request?                        |
| SLA              | How quickly will the team respond?                                      |
| Privacy          | What information is separated from hiring evaluation notes?             |
| Alternatives     | Which formats are already approved for common scenarios?                |
| Comparability    | How will reviewers score alternate evidence against the same criterion? |
| Escalation       | What happens when a vendor tool cannot support the accommodation?       |
| Recordkeeping    | What must be retained, and who can access it?                           |

The best workflow is prepared before the first candidate asks. Improvising accommodation under deadline pressure creates inconsistent treatment.

## AI Screening Adds New Access Questions

AI-assisted screening can improve access when it gives candidates scheduling flexibility, consistent prompts, plain-language instructions, and faster follow-up. It can create barriers when it depends on inaccessible interfaces, rigid formats, unclear scoring, or single-channel interaction.

The U.S. Department of Labor's AI and Inclusive Hiring Framework is a useful prompt for employers because it treats disability inclusion as a lifecycle issue: identify risks, procure carefully, test systems, communicate with candidates, provide accommodations, and keep humans accountable.

For AI screening, review:

- Can candidates understand when AI is involved and what it does?
- Can candidates complete the step with assistive technology?
- Is there a non-AI or alternate route when needed?
- Does the tool require voice, video, speed, or emotion signals that are not job-related?
- Are candidates told how to request support?
- Are recruiters reviewing transcripts or evidence, not just a score?
- Are completion and pass rates monitored for accessibility issues?
- Can the vendor explain accessibility testing and incident handling?

AI should not become a locked door with a smarter label.

## Vendor Procurement Questions

Most hiring teams rely on vendors for applications, scheduling, screening, assessments, background checks, and interview tools. Procurement is therefore part of DEI.

Ask vendors:

- Which accessibility standards do you test against?
- Do you provide a current VPAT or accessibility conformance report?
- Which assistive technologies are included in testing?
- Can candidates request accommodation inside the workflow?
- Can recruiters provide alternate formats without losing records?
- Are keyboard-only workflows supported?
- Are captions, transcripts, and text alternatives available where needed?
- Can time limits be adjusted per candidate?
- Can candidates pause, save, and resume?
- How are accessibility defects prioritized and resolved?
- What data can customers export for completion, drop-off, and support analysis?

Do not accept "we are accessible" as a complete answer. Ask how they know.

## Build An Accessibility Gate Before Launch

Before any assessment goes live, run an accessibility gate.

1. Map the skill being measured.
2. Identify the candidate action required.
3. Test the workflow on desktop and mobile.
4. Test keyboard-only navigation.
5. Review labels, instructions, errors, and timeouts.
6. Confirm accommodation language is visible before the task.
7. Define alternate evidence paths.
8. Confirm reviewer scoring for alternate evidence.
9. Confirm sensitive accommodation notes are stored separately.
10.   Run a small pilot and capture candidate comments.

This gate should be short enough to use, but strong enough to stop a broken assessment from launching.

## Metrics That Reveal Access Problems

Accessibility should appear in hiring dashboards, not only policy documents.

Track:

- Application completion rate.
- Assessment invitation to start rate.
- Assessment start to completion rate.
- Drop-off by device type.
- Drop-off by browser or platform when available.
- Average time to complete.
- Support requests by stage.
- Accommodation request response time.
- Alternate assessment completion.
- Candidate comments about instructions or access.
- Rejection rates after alternate evidence paths.
- Vendor accessibility incidents.

If a stage has high drop-off, do not assume weak candidates. Review access, clarity, time burden, and support first.

## Common Failure Modes

Accessibility work fails when teams:

- Treat accommodation as a legal footer rather than an operational workflow.
- Buy assessment tools before defining what skill should be measured.
- Use timed tests because they are easy to score.
- Require video when video performance is not part of the job.
- Let vendor limitations decide candidate access.
- Store sensitive accommodation information in general interview notes.
- Monitor average candidate satisfaction but not drop-off or support requests.
- Assume no requests means no barriers.

That last point is important. Candidates may not request accommodation because they do not see the option, fear stigma, lack trust, or abandon the process before asking.

## How SkillSociety Helps

SkillSociety supports structured screening that can be aligned to role criteria and reviewed by recruiters. Teams can design questions around job evidence, preserve transcripts, document alternate evidence, and keep human review in the loop.

That helps accessibility become part of the assessment design. The goal is not to make selection less rigorous. It is to make the evidence more valid by removing barriers that should never have counted.

## Further Reading

- [ADA.gov: Testing Accommodations](https://www.ada.gov/resources/testing-accommodations/)
- [Job Accommodation Network: Employment Testing and the ADA](https://askjan.org/publications/consultants-corner/vol12iss02.cfm)
- [W3C: Web Content Accessibility Guidelines 2.2](https://www.w3.org/TR/WCAG22/)
- [ADA National Network: Accessibility of Job Application Websites for Blind Users](https://adata.org/research/investigating-accessibility-and-usability-job-application-web-sites-blind-users)
- [U.S. Department of Labor: AI and Inclusive Hiring Framework](https://www.dol.gov/newsroom/releases/odep/odep20240924)
