Update 4.1.3 Status Messages interpretation to cover ariaNotify#5079
Update 4.1.3 Status Messages interpretation to cover ariaNotify#5079patrickhlauke wants to merge 12 commits intomainfrom
ariaNotify#5079Conversation
Based on ARIA25, but uses ariaNotify instead of live region
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
adampage
left a comment
There was a problem hiding this comment.
Exciting to see WCAG’s first reference to ariaNotify. 💪🏻
Are we in the habit of warning readers when a feature is still cutting edge? If so, I inserted a draft note suggestion after the technique’s description.
A couple of years ago, I removed numerous "workaround needed for IE10", "not supported in in Firefox 9", and similar comments from Techniques documents. If we want to add comments like "this is cutting edge" then we're also adding more work for ourselves in the future having to go in and remove the comments. |
Co-authored-by: Adam Page <adam@adampage.net>
Would that need browser sniffing to decide whether to notify via live regions or with |
Feature sniffing, luckily, not browser sniffing. |
|
I was actually pondering if I should add a tiny feature detect on the working example itself, to show a warning about the user's current browser not supporting |
|
Added feature detect to working example 41a16d5 |
Co-authored-by: Bruce Bailey <bruce@bailey4.us>
Co-authored-by: Adam Page <adam@adampage.net>
Co-authored-by: Kenneth G. Franqueiro <kfranqueiro@users.noreply.github.com>
Co-authored-by: Kenneth G. Franqueiro <kfranqueiro@users.noreply.github.com>



While ideally we'd want to actually change the normative wording of the SC (see #4952), if that fails for now, this PR adds a note to 4.1.3 Status Messages understanding that handwaves "when we say roles and properties, we also meant accessibility API access". It also adds a new technique and working example demonstrating the use of
ariaNotify./cc @adampage @scottaohara @fstrr
Previews: