add accessibility section for CSS Custom Highlight API#43469
Open
mohammed-ali-osman wants to merge 1 commit intomdn:mainfrom
Open
add accessibility section for CSS Custom Highlight API#43469mohammed-ali-osman wants to merge 1 commit intomdn:mainfrom
mohammed-ali-osman wants to merge 1 commit intomdn:mainfrom
Conversation
Documents the intended behavior of the API's `type` attribute for assistive technologies, and notes current limitations and inconsistent support across browsers.
Contributor
|
Preview URLs (1 page) Flaws (1) Found an unexpected or unresolvable flaw? Please report it here. URL:
|
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.
Description
This PR adds an Accessibility section to the CSS Custom Highlight API page.
Summarizes the intended behavior from the specification: the type attribute can be used by user agents to expose semantic meaning (such as spelling or grammar errors) to assistive technologies.
Notes that current support is limited and inconsistent across browsers and platform accessibility APIs.
Provides guidance for developers: custom highlights should not be relied on alone to convey important information; semantic HTML elements like
<mark>or additional accessible cues should be used when highlighting conveys meaning.This update ensures that developers are aware of accessibility limitations and helps prevent assumptions about screen reader support.
Fixes #43408