Repository navigation
Fix revealjs screen reader fragment announcements - #15020
Open
jooyoungseo wants to merge 1 commit into
Open
jooyoungseo wants to merge 1 commit into
jooyoungseo wants to merge 1 commit into
Conversation
Collaborator
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
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
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.
Fixes #15019.
Description
Backport hakimel/reveal.js#3946 to the bundled reveal.js 5.1.0 without upgrading to 6.x.
Hidden incremental content is excluded from
.aria-statusuntil it is revealed, including nested fragments and pauses. The fragment itself can still be announced when activated, and the built-in initially visible and transient styles retain their behavior.URL handling no longer navigates back to the current slide or fragment after writing its own history entry. Named horizontal slide indices are normalized, explicit fragment links still work, and browser Back can return to the state before the first fragment when
fragment-in-urlis enabled.The readable source patch is retained in
package/src/common/patches/and reapplied by the HTML dependency updater before rebuilding both JavaScript bundles and source maps. Remove this backport when updating to an upstream release containing the fix.Validation
js/reveal.jsandjs/controllers/location.js.Checklist
I have (if applicable):
No format option or documentation change is required.