ARIA attributes help assistive technologies understand information that is not always obvious from a custom interface. The aria-relevant attribute controls which live-region changes should be announced.
What it communicates
Controls which live-region changes should be announced. This information becomes part of the accessibility representation of the page, so it may help people using screen readers or other assistive tools.
An ARIA attribute does not usually change what you see on screen. It also does not automatically add keyboard handling, validation, or scripted state changes.
Example with accessible markup
<div aria-live="polite" aria-relevant="additions text">
<p>New activity will appear here.</p>
</div>Reading the example
Notice the aria-relevant setting and the element or role it describes: status. If the value refers to another element, that other element needs a matching id.
Choose only changes that matter; announcements depend on assistive technology.
When is it appropriate?
Use aria-relevant when this information is genuinely needed and the chosen role supports it. Before adding ARIA, check whether a native HTML element already expresses the same meaning. Native buttons, forms, tables, and progress controls usually need less custom code.
If a script changes the state of the interface, update the ARIA state at the same time. The screen reader’s description and the visible behavior should always agree.
Quick accessibility test
Try the example using only your keyboard. Inspect the accessibility tree and check whether the role, name, and state are what you expect. For an interactive control, confirm that the actual behavior matches its announced state.
Common Beginner Mistakes
- Choose only changes that matter; announcements depend on assistive technology.
- Adding ARIA to an element that already has the right native semantics, without a clear reason.
- Changing the visual state of an interface without updating its ARIA state.
Key Takeaways
aria-relevantcontrols which live-region changes should be announced.- Choose only changes that matter; announcements depend on assistive technology.
- Correct native HTML comes first; ARIA fills gaps rather than replacing working behavior.