Review dynamic page updates so screen reader users hear status changes without moving focus. Check ARIA live regions, areas that announce updates, choose suitable announcement urgency, and identify markup or interaction issues to verify with accessibility tools.
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Announce dynamic content with ARIA live regions. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Run score Not tested
See how to installReview how changing information on a page, such as form submission results and cart updates, reaches screen reader users. Check ARIA live regions, the areas that announce content changes. Use aria-live='polite' for routine updates and aria-live='assertive' for critical alerts. The review also checks whether role='alert' and role='status' are appropriate.
Use this skill when notifications, input errors, or loading states appear on screen but are not announced. It examines rendered HTML and the states shown during interaction. Where needed, it also checks keyboard operation, focus flow, and screen reader output. It identifies specific places to fix and explains how to verify the changes with browser accessibility features or assistive technology.
The announcing region must already exist in the DOM, the page structure, before its content changes. Reserve assertive for critical alerts.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Without live regions, screen reader users miss dynamic updates entirely—they won't know their form submitted, their cart updated, or an error occurred.
Verify that dynamic content changes (notifications, form errors, loading states) use aria-live regions appropriately.
Add aria-live attributes with correct politeness levels (polite, assertive) to containers with dynamic content.
Explain how ARIA live regions enable screen readers to announce content changes without requiring user focus.
Review the rendered markup and interactive states that affect Announce dynamic content with ARIA live regions. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/accessibility/aria-live-regions
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.