QuizzesARIA — When to Use It, and When Not To — Concept Check
intermediate
html-css

ARIA — When to Use It, and When Not To — Concept Check

Questions on ARIA — When to Use It, and When Not To. ARIA changes what assistive technology reports without changing behaviour. That asymmetry is why incorrect ARIA is worse than none — it makes a promise the code does not keep.

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 ARIA — When to Use It, and When Not To — 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 role="button" but forgets to add keyboard operability. What is the consequence?

    • AThe role attribute is ignored, making it a regular div.
    • BThe div becomes focusable and operable with the Enter key.
    • CIt automatically gains button-like behavior, including keyboard support.
    • DScreen readers announce it as a button, but it won't function as one.
  2. 2.When should ARIA roles be used instead of native HTML elements?

    • ATo make elements more interactive without JavaScript.
    • BWhen you want to override default browser behavior.
    • CWhen HTML cannot express the required semantics, like live regions.
    • DTo enhance the appearance of elements with CSS.
  3. 3.A developer sets aria-hidden="true" on a focusable button. What issue does this create?

    • AThe button is focusable but not perceivable by screen readers.
    • BScreen readers will ignore the button, but it remains clickable.
    • CThe button becomes invisible and unfocusable.
    • DThe button will not respond to any user interaction.
  4. 4.Why is it risky to use ARIA attributes without proper implementation?

    • AThey can introduce errors if not synchronized with JavaScript.
    • BThey are only useful for styling purposes.
    • CARIA attributes are ignored by most browsers.
    • DThey automatically change element behavior, causing conflicts.
  5. 5.A developer uses aria-expanded="true" on a menu button but does not update it when the menu closes. What happens?

    • AThe menu automatically updates its state to closed.
    • BThe aria-expanded attribute is ignored by assistive technologies.
    • CThe screen reader reports the menu as open even when it's closed.
    • DThe menu cannot be reopened due to state mismatch.
  6. 6.What is the primary purpose of the ARIA Authoring Practices Guide?

    • ATo list all possible ARIA roles and their uses.
    • BTo explain how to replace native HTML elements with ARIA roles.
    • CTo provide guidelines for implementing complex widgets with required keyboard behavior.
    • DTo offer styling tips for ARIA attributes in CSS.
  7. 7.A developer uses aria-live="assertive" for all updates on a page. What issue might this cause?

    • AAll updates will be ignored by screen readers.
    • BUsers may find the page unusable due to constant interruptions.
    • CUsers will not be able to perceive any updates.
    • DThe page will load slower due to excessive ARIA processing.