Element.ariaRelevant is an instance property that reflects the aria-relevant attribute. Learn which live-region changes get announced (additions, removals, text, all), how it pairs with aria-live, and how to get or set the property from JavaScript—with five examples and try-it labs.
01
Kind
Instance property
02
Type
String
03
Values
additions · removals · text · all
04
Reflects
aria-relevant
05
Status
Non-standard
06
Pair with
aria-live
Fundamentals
Introduction
A live region tells assistive technologies that content may update. Not every update is equally useful—sometimes you care about new nodes, sometimes only text changes, sometimes removals too.
aria-relevant filters which kinds of changes should be announced. ariaRelevant is the JavaScript reflection of that attribute.
JavaScript
const el = document.getElementById("clock");
console.log(el.ariaRelevant); // "all"
el.ariaRelevant = "text";
💡
Beginner tip
Start with ariaLive (polite / assertive). Use ariaRelevant when you need finer control over which DOM changes inside that region are announced. Keep announcements short and test with a screen reader.
Concept
Understanding the Property
MDN: the ariaRelevant property of the Element interface reflects the value of the aria-relevant attribute, which indicates what notifications the user agent will trigger when the accessibility tree within a live region is modified. It describes which changes in an aria-live region are relevant and should be announced.
Reflected attribute — mirrors aria-relevant.
Get / set — readable and writable string (space-separated tokens).
Live-region filter — works with aria-live regions.
Non-standard IDL — MDN marks the property Non-standard (Baseline widely available).
Foundation
📝 Syntax
JavaScript
ariaRelevant
Value
A string containing one or more of the following values, space separated:
Value
Meaning (MDN)
"additions"
Additions of element nodes within the live region are relevant.
"removals"
Deletion of nodes from the live region is relevant.
"text"
Changes to the textual content of existing nodes are relevant.
"all"
Equivalent to "additions removals text".
⚠️
Combine tokens
You can write space-separated values such as el.ariaRelevant = "additions text". Use "all" when every change type should be relevant.
Pattern
📋 MDN Example Shape
MDN starts with a timer live region marked aria-relevant="all", then narrows it to "text":
Element.ariaRelevant is marked Non-standard on MDN and also listed as Baseline Widely available (since October 2023). Logos use the shared browser-image-sprite.png sprite from this project. Feature-detect and test with assistive technology.
✓ Non-standard · Baseline
Element.ariaRelevant
Space-separated string — reflects aria-relevant for live region change types.
BaselineWidely · Non-std
Google ChromeSupported (ARIA reflection)
Yes
Microsoft EdgeSupported (ARIA reflection)
Yes
Mozilla FirefoxSupported (ARIA reflection)
Yes
Apple SafariSupported (ARIA reflection)
Yes
OperaFollow Chromium support
Yes
Internet ExplorerNo ariaRelevant IDL — use setAttribute
No
ariaRelevantBaseline
Bottom line: Use ariaRelevant carefully: MDN marks the IDL Non-standard. Pair with aria-live, keep announcements useful, and verify behavior with a screen reader.
Wrap Up
Conclusion
ariaRelevant reflects aria-relevant so live regions can declare which change types matter—additions, removals, text, or all. Remember MDN marks the IDL property Non-standard: learn it, feature-detect when needed, and always validate announcements with assistive technology.
Feature-detect the IDL property when relying on it
Test announcements with a screen reader
❌ Don’t
Ignore MDN’s Non-standard warning in production planning
Announce every removal if it creates noise
Expect ariaRelevant alone to create a live region
Spam assertive updates for minor text ticks
Skip real AT testing after changing tokens
Summary
Key Takeaways
Knowledge Unlocked
Five things to remember about ariaRelevant
Non-standard reflected filter for live-region change types.
5
Core concepts
📄01
Get / set
on Element
Kind
📝02
Token list
additions text all…
Values
🔍03
Needs live
aria-live region
Pair
✅04
Non-standard
MDN IDL note
Status
🎯05
Test AT
screen reader
Rule
❓ Frequently Asked Questions
It reflects the aria-relevant attribute as a string, indicating which changes inside an aria-live region should trigger assistive technology notifications (additions, removals, text, or all).
MDN marks Element.ariaRelevant as Non-standard. It is also listed as Baseline Widely available (since October 2023). It is not labeled Deprecated or Experimental on that MDN page.
A space-separated string of one or more tokens: "additions", "removals", "text", or "all" (equivalent to "additions removals text").
ariaLive turns on a live region and sets urgency (polite / assertive / off). ariaRelevant filters which kinds of DOM changes inside that region are announced.
Use carefully. MDN marks the Element.ariaRelevant IDL property Non-standard and does not recommend non-standard features in production. Prefer well-supported live-region patterns and test with real screen readers.
MDN reads aria-relevant="all" from a timer live region via ariaRelevant, then assigns "text" so only text changes are considered relevant.
Did you know?
"all" is just a shortcut for "additions removals text". If removals create noisy announcements, prefer a narrower list such as "additions text" instead of "all".