Permit UA to ignore user-triggered changes inside live regions #1820
Conversation
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
cookiecrook
approved these changes
Oct 4, 2022
Co-authored-by: James Craig <[email protected]>
scottaohara
approved these changes
Oct 4, 2022
spectranaut
approved these changes
Oct 6, 2022
jnurthen
pushed a commit
that referenced
this pull request
Oct 6, 2022
…1820) Co-authored-by: James Craig <[email protected]>
jnurthen
pushed a commit
that referenced
this pull request
Oct 10, 2023
…1820) Co-authored-by: James Craig <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #72 by permitting user agents to ignore user-triggered changes inside live regions.
I created a quick Codepen to test the behavior described in #72 and was able to reproduce it in macOS 12.6 + VoiceOver + Safari 16.0. In that environment, values entered into a text input inside a live region announce themselves twice. In Chrome 106, it’s more severe: the value repeats itself a second time, then the input’s label is read again, then the value repeats a third time.
I didn’t find one obvious location in 1.3 to add a normative statement for this, but my first instinct was to put it in 6.6.2 Live Region Attributes, where the general concept of live regions is first described.
Alternatively, I wondered if it might belong in 6.7’s
aria-livedescription or even in thearia-relevantdescription?Preview | Diff