Repository navigation
[CI/a11y] Add automated heading-hierarchy check to site_lint.yml - #8740
Open
Jubayeromi wants to merge 1 commit into
Open
Jubayeromi wants to merge 1 commit into
Jubayeromi wants to merge 1 commit into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
This branch was successfully deployed
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.
[CI/a11y] Add automated heading-hierarchy check to site_lint.yml
##8610
Add a heading-order check to the site lint workflow to catch new heading-level skips in Markdown content, such as jumping from
to
. The check compares results with the PR’s base commit, so existing skips don’t block CI while new ones do. This uses a static content check rather than axe-core.
Validation: Confirmed the check passes for the current baseline and fails when a skipped heading level is introduced.