The Element.ariaNotify() method queues a string of text to be announced by a screen reader (MDN). Unlike ARIA live regions, you can announce at any time — not only after a DOM change.
Pass the required arguments shown below. Check return values and browser support before you rely on the result.
Detect first. Branch on whether the method exists.
Prefer the new API. No hidden live-node dance when supported.
Fall back to live regions. Update textContent on an aria-live element.
Keep one path for users. Same message string in both branches.
Compatibility
Browser Support
Element.ariaNotify() is Baseline 2026 Newly available on MDN (across latest browsers since September 2026). It is not Deprecated, Experimental, or Non-standard. Feature-detect and keep an aria-live fallback for older browsers and blocked Permissions Policy cases.
✓ Baseline Newly available
Element.ariaNotify()
Programmatic screen reader announcements without a DOM mutation. Newly Baseline — still pair with live-region fallbacks.
2026Newly available
Google ChromeLatest (Baseline 2026)
Supported
Mozilla FirefoxLatest (Baseline 2026)
Supported
Apple SafariLatest (Baseline 2026)
Supported
Microsoft EdgeLatest (Baseline 2026)
Supported
OperaChromium latest
Supported
Internet ExplorerNot supported — use aria-live
Unavailable
ariaNotify()Newly Baseline
Bottom line: Use when available; always ship an aria-live fallback for older clients.
Frequently Asked Questions
It queues a string of text for a screen reader to announce (MDN). You can call it at any time — announcements do not require a DOM content change like classic ARIA live regions.
No. MDN marks Element.ariaNotify() as Baseline 2026 Newly available (since September 2026). It is not Deprecated, Experimental, or Non-standard. Older browsers still need a live-region fallback.
undefined. There is no promise or status object. Feature-detect the method, then call it; blocked Permissions Policy usage fails silently.
For urgent interruptions, similar to aria-live="assertive". Prefer priority: normal (default, like polite) for most status updates so you do not interrupt the user constantly.
MDN notes that some screen readers may only speak the most recent ariaNotify() call. Combining messages into one string is more reliable than firing several calls in a row.
Fall back to an ARIA live region (update textContent on an aria-live element) or another accessible pattern. Always feature-detect typeof el.ariaNotify === "function".