Fix accessibility issue with ContextualHelp and screen readers #61
Conversation
This file contains 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
…s screen reader text. Prefers a separate label, falling back to using the primary non-screen-reader text when no screen reader specific text is present. This helps avoid an accessibility issue with ContextualHelp component not being correctly announced by a screen reader.
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.
Updated ContextualHelp component to make use of the Drawer component's screen reader text.
Prefers a separate label, falling back to using the primary non-screen-reader text when no screen reader specific text is present.
This helps avoid an accessibility issue with ContextualHelp component not being correctly announced by a screen reader.