Repository navigation
[self-care:accessibility-checker] Keep one primary heading on the documentation landing page - #20172
Merged
mnkiefer merged 2 commits intoNov 4, 2026
Conversation
…ng-4502ea8312839a8d
mnkiefer
deleted the
self-care/accessibility-single-landing-heading-4502ea8312839a8d
branch
November 4, 2026 07:40
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.
The documentation landing page exposed two
h1elements in the rendered accessibility structure. This change keeps the page title as the single primary heading while preserving the presentation title slide's visual treatment.Action: Documentation maintainers should review the rendered landing page and merge when the heading structure and unchanged slideshow appearance meet expectations.
Critical finding
https://githubnext.github.io/gh-cao/rendered both “Central Agentic Ops” and “Monitor and govern GitHub Agentic Workflows at scale.” as level-one headings in light and dark schemes.h1; the slideshow still presents “Central Agentic Ops” at the original 80px computed size.Browser evidence and audit coverage
Audited with the prepared Astro preview, Playwright, and bundled axe-core in light and dark schemes:
https://githubnext.github.io/gh-cao/https://githubnext.github.io/gh-cao/setup-quickstarts/https://githubnext.github.io/gh-cao/dashboard-language-specification/https://githubnext.github.io/gh-cao/architecture-at-a-glance/Before: the landing page accessibility structure contained two
h1elements. After: it contains oneh1, axe reports zero WCAG A/AA violations, the skip link moves focus toh1#_top, focus outlines remain visible in both schemes, the 320 CSS-pixel viewport has no document overflow, and reduced-motion mode has no running animations. Keyboard sequences, landmarks, heading levels, names, alternatives, focus styling, reflow, and reduced-motion behavior were sampled across all four pages; no additional reproducible barrier was selected for this focused fix.Validation
git diff --checknpm run docs:buildWorkflow evidence: accessibility checker run.