feat(core): ARIA live regions for dynamic state changes (stackwright-qb9)#477
Merged
Merged
Conversation
Contributor
✅ Visual Regression Test ResultsStatus: ✅ All visual tests passed! All screenshots match the baseline. No visual regressions detected! 🎉 |
Contributor
⚡ Performance Benchmark Results✅ Build Time Benchmarks: PASSED❌ Bundle Size Benchmarks: FAILED❌ Runtime Vitals Benchmarks: FAILED📝 Note: Detailed results are available in the job logs. 🎯 Performance Budgets:
Updated: 2026-05-31T14:39:12.671Z |
Contributor
✅ Visual Regression Test ResultsStatus: ✅ All visual tests passed! All screenshots match the baseline. No visual regressions detected! 🎉 |
Contributor
♿ Accessibility Test ResultsOverall Status: ✅ 0/0 tests passed 🦮 WCAG 2.1 AA ComplianceNo WCAG test results available ⌨️ Keyboard NavigationNo keyboard navigation test results available 📊 Detailed ReportDownload the full HTML accessibility report from the workflow artifacts for:
🔍 Testing ChecklistOur accessibility tests verify:
Powered by @axe-core/playwright and Playwright |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds WCAG 4.1.3-compliant
aria-liveregions to 4 components that previously had zero screen reader announcements for dynamic state changes.Changes
AriaLiveRegionutility component — visually-hidden, configurable politeness, reusable across the frameworkrole="status" aria-live="polite" aria-atomic="true"— the visible container IS the live region (no hidden duplicate text, which is the correct ARIA pattern for visible state messages)useMemo-derived live message announces result count changes ("5 results found for...") viaAriaLiveRegionrole="alert"for immediate screen reader interruptWhy
WCAG 4.1.3 (Status Messages) requires that status messages be programmatically determinable without receiving focus. None of these 4 components met this requirement. Grep confirms zero
aria-live/role=alert/role=statususage in core before this PR.Design note on Form
For Form's success message, the visible container itself carries
aria-liverather than using a hiddenAriaLiveRegioninside it. This avoids duplicate text in the DOM (which confuses bothgetByTextqueries and screen reader verbosity) and follows the WAI-ARIA authoring practice of making the visible status element the live region directly.Testing
AriaLiveRegionunit tests (polite/assertive, visual hiding, rerenders)ContentItemErrorBoundaryrole="alert"assertionrole="status"assertionCloses bead stackwright-qb9