QuizzesTesting Accessibility — Concept Check
intermediate
html-css

Testing Accessibility — Concept Check

Questions on Testing Accessibility. Automated tools catch roughly a third of issues. The rest need a keyboard, a screen reader and about ten minutes — which is still far cheaper than the alternative.

7 minutes 7 questions Pass at 70%
Time Limit
7 minutes - timer starts when you begin
Change Answers Freely
Revisit and change any answer before submitting
Full Review After Submit
Correct answers and explanations shown for every question
Auto-submit on timeout
Quiz submits automatically when time runs out

Questions in this quiz

7 questions on Testing Accessibility — Concept Check. Work through them here, then start the quiz to answer them and see your score.

  1. 1.A developer runs Lighthouse and gets a score of 100. What should they do next to ensure accessibility?

    • AConsider the work done, as 100 is perfect.
    • BAssume all accessibility issues are resolved.
    • CRun a manual checklist to catch issues Lighthouse misses.
    • DRely on automated tools only for complete coverage.
  2. 2.During a manual accessibility test, a developer finds that pressing 'Escape' does not close a modal. What is the issue?

    • AThe modal is not trapping focus correctly.
    • BThe modal is not keyboard accessible.
    • CThe modal is missing a close button.
    • DThe modal should close with 'Escape' for accessibility.
  3. 3.Which tool provides the most thorough automated accessibility testing with the best explanations?

    • ALighthouse
    • Beslint-plugin-jsx-a11y
    • Caxe DevTools extension
    • DWAVE
  4. 4.A developer notices that increasing the font size to 24px causes text overflow. What should they do?

    • AAssume it's a browser issue and not fix it.
    • BRely on CSS to automatically adjust the layout.
    • CIgnore it, as users rarely change default font sizes.
    • DRedesign the layout to accommodate larger font sizes.
  5. 5.A developer uses `eslint-plugin-jsx-a11y` and finds no errors. What should they conclude?

    • ANo further testing is needed.
    • BOnly basic issues like missing alt are covered.
    • CAll accessibility issues are resolved.
    • DThe code is fully accessible.
  6. 6.Why is manual accessibility testing considered cheaper in the long run?

    • AIt requires no specialized tools.
    • BIt identifies issues early, avoiding costly retrofits.
    • CIt requires less developer time.
    • DIt can be skipped if automated tests pass.
  7. 7.What is the practical target level for WCAG compliance that most legal requirements reference?

    • ALevel AAA
    • BLevel A
    • CLevel B
    • DLevel AA