QuizzesKeyboard Access and Focus Management — Concept Check
intermediate
html-css

Keyboard Access and Focus Management — Concept Check

Questions on Keyboard Access and Focus Management. Everything doable with a mouse must be doable with a keyboard. Test it by unplugging the mouse — most sites fail within a minute.

8 minutes 8 questions Pass at 70%
Time Limit
8 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

8 questions on Keyboard Access and Focus Management — Concept Check. Work through them here, then start the quiz to answer them and see your score.

  1. 1.You unplug your mouse to test a website's keyboard accessibility. You notice that after opening a modal dialog, pressing Tab cycles through elements outside the dialog. What is the issue?

    • AThe dialog's focus indicator is invisible
    • BThe dialog is not using tabindex correctly
    • CFocus is not trapped inside the dialog
    • DThe dialog lacks a role attribute
  2. 2.A developer removes outlines from focused elements because they consider them 'ugly'. What is a potential consequence of this action?

    • AMouse users will face navigation issues
    • BThe website will load faster
    • CKeyboard users may not see which element is focused
    • DScreen readers will stop working
  3. 3.You notice that pressing Tab navigates through elements in an unexpected order. What could be causing this?

    • AElements missing role attributes
    • BLack of focus-visible styling
    • CIncorrect use of tabindex="-1"
    • DCSS visual reordering without DOM reordering
  4. 4.A developer uses tabindex="3" to control tab order. What is the problem with this approach?

    • AIt disrupts the natural tab order
    • BIt improves keyboard navigation
    • CIt makes elements unfocusable
    • DIt enhances accessibility
  5. 5.After deleting a row in a table, focus unexpectedly shifts to the top of the page. What should be done to address this?

    • AAdd a focus-visible class to the table
    • BUse tabindex="-1" on the table
    • CEnsure the table has a role attribute
    • DMove focus to the next logical element
  6. 6.A custom button is implemented using a div with onclick but lacks certain attributes. Which attribute is essential for keyboard accessibility?

    • Atabindex="-1"
    • Baria-hidden="true"
    • Ctabindex="0"
    • Drole="presentation"
  7. 7.When a new section of content appears on a page, what should happen to ensure accessibility for screen reader users?

    • AEnsure the content is visible
    • BAnnounce the content using aria-live
    • CMove focus to the new content
    • DAdd tabindex="3" to the content
  8. 8.What is the purpose of the :focus-visible pseudo-class in CSS?

    • ATo enhance mouse click interactions
    • BTo apply styles to all focused elements
    • CTo apply styles only when an element is focused via keyboard
    • DTo hide focus outlines from all users