QuizzesAccessible Structure — What a Screen Reader Hears — Concept Check
intermediate
html-css

Accessible Structure — What a Screen Reader Hears — Concept Check

Questions on Accessible Structure — What a Screen Reader Hears. A screen reader builds its own picture of your page from the accessibility tree. Understanding what that tree contains explains why semantic markup is not a formality.

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 Accessible Structure — What a Screen Reader Hears — Concept Check. Work through them here, then start the quiz to answer them and see your score.

  1. 1.A developer uses a <div> with an onclick event to create a button. What is the issue with this approach?

    • AThe div is not accessible to screen readers.
    • BThe div will automatically have a role assigned.
    • CThe div will not be clickable.
    • DThe div will announce as a button.
  2. 2.What happens if you use aria-hidden="true" on a button?

    • AThe button is only hidden from screen readers.
    • BThe button becomes a trap for screen reader users.
    • CThe button is hidden visually but still announced.
    • DThe button becomes completely inaccessible.
  3. 3.A page is constructed using only <div> elements. How will this affect screen reader users?

    • AScreen reader users will navigate using default roles.
    • BScreen reader users will hear all content correctly.
    • CScreen reader users will have no navigation aids.
    • DScreen reader users will have enhanced navigation.
  4. 4.Which attribute silently overrides visible text on a button?

    • Atitle
    • Bnative label
    • Caria-labelledby
    • Daria-label
  5. 5.Why is it important to use semantic HTML elements like <header> and <nav>?

    • AThey create landmarks for screen reader navigation.
    • BThey improve the visual design of a page.
    • CThey increase page load speed.
    • DThey automatically enhance CSS styling.
  6. 6.A developer uses display: none to hide a menu but leaves its links tabbable. What is the consequence?

    • ALinks are announced but not visible.
    • BUsers can tab into invisible links.
    • CLinks are removed from the accessibility tree.
    • DLinks become visible when tabbed.
  7. 7.What is the role of the tabindex="-1" attribute on a <main> element?

    • AIt hides the element from screen readers.
    • BIt prevents the element from receiving focus.
    • CIt makes the element focusable by default.
    • DIt allows focus to move to the element.