feat: add visually invisble h1 to search result page #1125
Conversation
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
coseeian
added
the
Accessibility: Best Practice
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Resolves #1126.
Summary
<h1>"Search Results" heading to the search page for accessibilityDetails
The search page was missing a level-one heading, which is a WCAG best practice for proper document structure and assistive technology navigation. This change adds an
<h1>element with thesr-onlyclass to make it accessible to screen readers while keeping it visually hidden to maintain the current design.Changes
<h1 class="sr-only">Search Results</h1>tosrc/layouts/SearchLayout.astro