Skip to content

[self-care:accessibility-checker] Keep one primary heading on the documentation landing page - #20172

Merged
mnkiefer merged 2 commits into
mainfrom
self-care/accessibility-single-landing-heading-4502ea8312839a8d
Nov 4, 2026
Merged

mnkiefer merged 2 commits into
mainfrom
self-care/accessibility-single-landing-heading-4502ea8312839a8d

Conversation

@mnkiefer

@mnkiefer mnkiefer commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

The documentation landing page exposed two h1 elements 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

  • Advisory — WCAG 2.2 1.3.1 structure: 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.
  • The hidden-on-page presentation title now uses styled text instead of a document heading. The visible page title remains the sole 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 h1 elements. After: it contains one h1, axe reports zero WCAG A/AA violations, the skip link moves focus to h1#_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 --check
  • npm run docs:build
  • Repeated landing-page axe and manual structure, skip-link, focus, reflow, reduced-motion, and slideshow checks in light and dark schemes
  • Changed-file secret scan

Workflow evidence: accessibility checker run.

cao: githubnext/gh-cao, correlation: 41730452701-3273

Generated by ♿ SelfCare / Accessibility · pi · gpt56 · ~95 AIC · ⌖ ~31 AIC · ⊞ 15.2K · ◷

@mnkiefer
mnkiefer marked this pull request as ready for review November 4, 2026 05:19
@mnkiefer
mnkiefer requested a review from pelikhan as a code owner November 4, 2026 05:19
@mnkiefer
mnkiefer merged commit 440542e into main Nov 4, 2026
16 checks passed
@mnkiefer
mnkiefer deleted the self-care/accessibility-single-landing-heading-4502ea8312839a8d branch November 4, 2026 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant