Repository navigation
Conversation
Matched terms were styled spans, so the highlight was only visual. Render them as <mark> so screen readers can announce them, keeping the existing look by inheriting the text colour. In forced colours mode the highlights now use the system Mark colours instead of disappearing. Closes microbit-foundation#1249
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.
Closes #1249
Search highlights were styled spans, so the highlight was only visual. This renders matched terms as
<mark>so assistive technology can pick them up, and inherits the text colour so the look stays the same.markrole.Checked with typecheck, lint, unit tests, the documentation and accessibility e2e tests, and a build. I've checked the accessibility tree in Chromium but haven't yet tried it with a real screen reader, so a quick listen would be welcome.
AI-assisted.