TJR Bootcamp Practice Test

Understanding what ARIA provides to assistive technologies is key. ARIA exposes meaningful information about UI elements through roles, states, and properties. This lets screen readers and other assistive tech understand what an element represents (for example, a button, slider, or dialog), how it behaves, and its current condition (such as enabled, disabled, expanded, or checked). By adding these attributes—like specifying a button role on a non-native element, or using aria-expanded, aria-pressed, aria-label, and aria-live—you can communicate both the purpose of an element and how it should be announced or updated as the user interacts with it. This is especially important for custom widgets or dynamic content that aren’t standard HTML controls. ARIA’s role is to provide this structured, machine-readable information so assistive technologies can convey accurate and helpful feedback to users. It doesn’t speed up builds, replace HTML, or improve image resolution, which is why the option describing roles, states, and properties to improve accessibility is the best fit.