Project review step: Fix all project review headers#246
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR addresses accessibility issues in the "Review" tab of the Create AKS Project workflow by fixing the semantic heading hierarchy. The changes ensure that heading elements follow a sequentially-descending order (h1 → h2 → h3) while maintaining the desired visual styling, resolving multiple Lighthouse accessibility flags.
Changes:
- Added
component="h3"to four Typography components in ReviewStep to establish proper semantic heading hierarchy - Maintains visual styling (
variant="h6") while ensuring correct HTML semantics for screen readers
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
skoeva
approved these changes
Feb 18, 2026
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 fixes a collection of a11y issues identified by Lighthouse where headings were not in sequential order for the New Project workflow "Review" tab.
The title components are visually styled as an h6 header without following the current headers present on the screen. This caused Lighthouse to flag improper heading hierarchy which can negatively impact screen reader navigation.
Related Issues
Related to #219
Changes Made
"Heading elements are not in a sequentially-descending order"
"Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies."
How to test:
Images