PROGRAMMING SKILLS

Web accessibility test for hiring

See how developers review everyday web interfaces for accessibility issues and choose practical fixes.

10 minutes
15 questions
Intermediate
Multiple choice
Questions in English
Phone and desktop

Use this test free See the question formats

The short answer

The web accessibility for developers test is an intermediate, timed assessment for frontend and web developers, accessibility engineers, UI engineers, web designers who write code, and QA engineers testing web interfaces. Candidates review short HTML, CSS, and JavaScript snippets, audit findings, and user scenarios, then choose a fix or judgment about accessible interfaces.

What it measures

Writing and reviewing HTML, CSS and JavaScript so that web interfaces work with keyboards, screen readers, zoom and other assistive technology.

Accessible HTML

Candidates consider semantic markup and how HTML supports interfaces used with keyboards and assistive technology.

Accessible CSS

Candidates consider styling in interfaces used with zoom and other assistive technology, including contrast questions with measured ratios in a table.

Dynamic content and ARIA

Candidates consider interactive widgets, live updates, and the use of JavaScript and ARIA in web interfaces.

Accessibility principles and testing

Candidates apply WCAG 2.2 and accessibility testing to everyday web development scenarios.

Question formats

Multiple choice

The candidate: Reads a short situation, table or statement and picks the right answer, or every right answer.

You see: Whether the candidate knows the material well enough to apply it, not just recognize it.

15 questions in 10 minutes, served one at a time.

Roles this test fits

Frontend and web developers, accessibility engineers, UI engineers, web designers who write code, and QA engineers who test web interfaces for accessibility.

What this test can show

Practical code review
Short HTML, CSS, and JavaScript snippets show how applicants choose fixes for accessibility issues, beyond what a resume says about web development.
Judgment in everyday interfaces
User scenarios and audit findings reveal how applicants reason about sign-up forms, shop listings, and dashboards.
Coverage of assistive use
The test measures whether developers account for keyboards, screen readers, zoom, and other assistive technology when reviewing interfaces.
Consistent question context
Plainly written code and measured contrast ratios avoid color-by-eye judgments, browser quirks, screen reader brands, idioms, and local knowledge.

What you get for each candidate

Example report (fictional data)Web Accessibility for Developers

76%Percentile 57. Benchmark: HireValid candidates, n = 652

Accessible HTML90%

Accessible CSS79%

Dynamic content and ARIA64%

Accessibility principles and testing69%

Integrity ScoreHigh confidence

Stayed on the test tab throughout
No pasted answers
Answered at a steady pace

Scores, profiles and integrity signals are evidence for you to review alongside an interview, never an automatic decision.

Use this test free

Test integrity signals

Each candidate receives a different question set and order from large pools, with shuffled answer options. The browser shows one question at a time, and answer keys stay on HireValid’s servers. Timing runs on the server; reloading restores the same question with only the time left. Candidates cannot go back to earlier questions. Text cannot be copied or selected, and a blocked copy attempt is recorded in the timeline. Personal invitation links expire, and a finished test cannot be taken again. HireValid records signals such as time away from the test tab, pastes into answers, and unusually fast answers, then summarizes them in an Integrity Score and evidence timeline for employer review. With candidate consent, employers can add webcam photos at random moments. The system does not decide on its own. See how we build our tests.

How we prevent AI cheating · Integrity signals

Use the score as evidence

Review the score alongside a work sample and a structured interview; do not use it alone to decide. A work sample can ask an applicant to review a web interface and explain a proposed fix. Compare that reasoning with the test's code snippets and audit findings. You can also consider related skills covered by the HTML5, CSS, and React tests.

Structured interview questions

How would you review a sign-up form for keyboard access?
Listen for a clear review process, specific interface details, and how the applicant would explain and verify a proposed fix.
Tell me about a time you changed a web interface after finding an accessibility issue.
Listen for the issue, the change to the HTML, CSS, or JavaScript, and how the applicant evaluated the result.
How would you investigate a live update that is not clear to a screen reader user?
Listen for consideration of dynamic content, the role of ARIA, and a way to test the updated interface.

Understand scoring and benchmarks

Fairness and accommodations

Questions use short, plainly written code and everyday web pages such as sign-up forms, shop listings and dashboards, with no idioms, money symbols or local knowledge. They never depend on the quirks of one browser or one screen reader brand. Nothing in a question is conveyed by color alone, and contrast questions give the measured ratios in a table, so no candidate needs to judge color by eye.

You can give any candidate extra time as an accommodation. Results are evidence for a person to review, never an automatic decision.

Provisional: reliability is reported once 200 candidates have completed it.

Read our fairness approach

Test details

A timed test of how well a developer builds web pages and apps that people with disabilities can use. Candidates read short HTML, CSS and JavaScript snippets, audit findings and user scenarios, and choose the fix or judgment an experienced accessibility-minded developer would make. It covers semantic markup, styling, interactive widgets and live updates, and applying WCAG 2.2 in day-to-day work.

Questions are in English.
No aids are needed.
Each question is answered once, in order, with no going back.
4 practice questions, 4 minutes, before the timed test.

WCAG, WAI-ARIA are trademarks of their owners. HireValid is not affiliated with or endorsed by them.

Frequently asked questions

How does the Web Accessibility for Developers test handle fairness?+

Questions use short, plainly written code and familiar pages such as sign-up forms, shop listings, and dashboards. They do not depend on a browser or screen reader brand, convey information through color alone, or require judging color by eye; contrast ratios appear in a table.

Can candidates use aids or return to questions in the Web Accessibility for Developers test?+

No aids are allowed, and candidates cannot go back to an earlier question. The test does not require a desktop computer. Candidates can try the separate practice set of 4 questions in 4 minutes to see how the questions work.

Which applicants should take the Web Accessibility for Developers test?+

It is an intermediate test for applicants to frontend and web developer, accessibility engineer, UI engineer, web designer who writes code, and QA engineer roles that test web interfaces for accessibility.

What do candidates do in the Web Accessibility for Developers test?+

In 10 minutes, candidates answer 15 multiple-choice questions based on short HTML, CSS, and JavaScript snippets, audit findings, and user scenarios. They choose a practical fix or judgment about web accessibility.