New Skip Navigation component #37629
Draft
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 suggests to add a new "Skip navigation" component to our list of components.
Motivation & Context
First of all, I know that it is not a real component since it doesn't require any extra JS nor CSS, and uses only utilities. However I'm wondering if, still, it shouldn't appear as a component in Bootstrap (it could be enhanced with another example with a navbar and a default design for example).
Another option would be to have a dedicated example page but it would remain hidden in some part of the docs.
I don't have a strong opinion on it but it could maybe help propagating accessibility good practices.
I'd love to have your feedback/opinion on this idea 🙏
Type of changes
Checklist
npm run lint)Live previews