Fix sequence of content in Subhead #1950
Merged
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
When a heading, description, and action are rendered in the Subhead component, the content now follows logical order on screen readers.
🦋 Changeset detectedLatest commit: e1f9d57 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
1 task
Merged
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.
What are you trying to accomplish?
When a heading, description, and action are rendered in the Subhead component, the content now follows logical order on screen readers.
Before
Accessibility tree
After
Accessibility tree
What approach did you choose and why?
I decided to reorder the elements on the DOM and use the flexbox order property so elements are still rendered in the same way.
The main advantage of this approach is that it is 100% nonbreaking. If the DOM elements are not reordered, things will keep rendering correctly (the accessibility issue will still be there though).
Are additional changes needed?