send accessibility announcement events as confirmation for some state changes - #1380
Merged
QuantumBadger merged 6 commits intoSep 13, 2026
Merged
Conversation
QuantumBadger
force-pushed
the
a11y-announcements
branch
from
September 13, 2026 13:24
e2e6dd1 to
b615414
Compare
QuantumBadger
added a commit
that referenced
this pull request
Sep 13, 2026
Owner
|
Thanks for this! I've tested it and it works, so happy to merge in. I've also added individual comments to the announcement strings, in the hope that the 30-char limit will be shown in the Weblate UI. Thanks again! |
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
2 participants
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.
This PR adds accessibility announcement events for:
The
announceForAccessibilitymethod was deprecated in Baklava, but the suggested replacements on that page don't really work for us and other projects are dealing with this as well. There's no timeline for removal, so I think this is fine to use for the foreseeable future.Closes #986.