Ensure skip to main content logic is working #12439
Merged
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.
Summary
Adds
id=main
on the div immediately surrounding the<slot/>
in AppBarPage where the index page goes.Note that this does not resolve some lingering semantic page structure issues where there are some ambiguous
<main>
elements in various plugins/pages, as the existing logic was not actually based on the HTML element but rather the id. My browser extension suggests that the addition ofid=main
on this div does not add additionalmain
elements to the page that would be confusing (i.e. potentially multiple in a section, if a nested page already has an HTML<main>
)Reviewer guidance
Does skip to main work in all plugins?
Testing checklist
PR process
Reviewer checklist
yarn
andpip
)