Skip to content

🔍 Multi-Device Docs Testing Report - 2026-03-20 #21896

@github-actions

Description

@github-actions

Test Summary

  • Triggered by: @pelikhan
  • Workflow run: §23326629638
  • Pages tested: 13 documentation pages
  • Test date: 2026-03-20
  • Note: Visual Playwright browser tests were skipped due to container network isolation (bridge IP unreachable from Playwright's host-network context). Static HTML/CSS analysis was performed instead.

Results Overview

  • 🟢 Passed: 6 pages (no issues)
  • 🟡 Warnings: 9 findings across 7 pages
  • 🔴 Critical: 0

Responsive Design Assessment

The documentation site (Starlight/Astro) demonstrates solid responsive design fundamentals:

  • Viewport meta tag: ✅ width=device-width, initial-scale=1 present on all pages
  • Breakpoints: 30em, 50em, 50rem, 640px, 72em, 768px, 769px, 900px
  • Approach: Predominantly mobile-first (30 min-width queries vs 17 max-width)
  • Layout: Extensive Flexbox (199 uses) and Grid (42 uses)
  • Mobile navigation: ✅ Hamburger menu with aria-label="Toggle navigation menu"
  • Dark mode: ✅ prefers-color-scheme media feature supported
  • Motion preferences: ✅ prefers-reduced-motion supported
  • Focus styles: ✅ focus-visible supported
  • Internal links: ✅ All 122 internal navigation links return HTTP 200
View All Warnings
Page Warning Severity
/gh-aw/ Duplicate page title: GitHub Agentic Workflows | GitHub Agentic Workflows — both sides of the | separator are identical 🟡
/gh-aw/introduction/architecture Logo image missing alt attribute — site logo (img) has no alt="". Link text "GitHub Agentic Workflows" provides fallback, but alt="" should be explicit for decorative images 🟡
/gh-aw/introduction/architecture 9 <th> elements missing scope attribute — content tables lack scope="col" or scope="row" on header cells 🟡
/gh-aw/reference/engines/ 4 <th> elements missing scope attribute 🟡
/gh-aw/reference/github-tools/ 3 <th> elements missing scope attribute 🟡
/gh-aw/blog/ 4 <th> elements missing scope attribute 🟡
/gh-aw/examples/multi-repo/ 4 <th> elements missing scope attribute 🟡
/gh-aw/reference/fuzzy-schedule-specification/ Duplicate H1 headings — page renders two <h1> elements with the same text; one in the Starlight hero area (id="_top") and one in the document body 🟡
/gh-aw/reference/fuzzy-schedule-specification/ 16 <th> elements missing scope attribute 🟡
View Detailed Test Results by Page

✅ Passing Pages (6)

  • /gh-aw/introduction/overview/
  • /gh-aw/introduction/how-they-work/
  • /gh-aw/setup/quick-start/
  • /gh-aw/setup/creating-workflows/
  • /gh-aw/reference/faq/
  • /gh-aw/reference/glossary/

⚠️ Pages with Warnings (7)

All pages return HTTP 200 and are fully functional.

Homepage /gh-aw/

  • Title duplicated: GitHub Agentic Workflows | GitHub Agentic Workflows
  • All other checks pass (viewport ✅, H1 ✅, skip-link ✅, semantic HTML ✅)

Architecture /gh-aw/introduction/architecture

  • SVG logo (img) lacks alt attribute (decorative — link text compensates)
  • 9 table <th> cells missing scope (affects screen reader table navigation)
  • Mermaid diagrams render as SVG ✅
  • All other checks pass

Engines /gh-aw/reference/engines/

  • 4 table <th> cells missing scope

GitHub Tools /gh-aw/reference/github-tools/

  • 3 table <th> cells missing scope

Blog /gh-aw/blog/

  • 4 table <th> cells missing scope
  • 42 blog posts render correctly ✅

Multi-Repo Example /gh-aw/examples/multi-repo/

  • 4 table <th> cells missing scope

Fuzzy Schedule Specification /gh-aw/reference/fuzzy-schedule-specification/

  • Duplicate <h1> (Starlight rendering artifact — hero title + document heading)
  • 16 table <th> cells missing scope
  • ABNF code blocks fall back to txt highlighting (build warning in server log)
Build Warnings (from server log)

Two warnings observed at server startup:

  1. abnf language not supported in docs/src/content/docs/reference/fuzzy-schedule-specification.md — blocks fall back to txt highlighting. Fix: remove the abnf language identifier or add it to the expressive-code langs config.

  2. starlight-blog ThemeSelect conflictstarlight-blog warns that a ThemeSelect component override already exists in Starlight config. This may cause the theme toggle to not appear in the blog sidebar. Fix: follow the starlight-blog migration guide to update the navigation plugin option or merge the overrides.

Accessibility Findings

The site has generally strong accessibility:

  • Skip-to-content link present on all pages ✅
  • All interactive buttons have aria-label attributes ✅
  • Named nav landmarks (aria-label="Primary navigation") ✅
  • Proper (main), (nav), (header), (footer) landmarks ✅
  • Single H1 per page (except fuzzy-schedule spec) ✅
  • All images have alt text (except the site logo SVG) ✅

Main gap: <th> elements across 6 pages lack scope="col"/scope="row". This affects screen reader users navigating tables.

Recommendations

  1. Fix duplicate homepage title — Change Starlight's title config or the site name so the page title format is unique (e.g., "GitHub Agentic Workflows" without the separator repeat).

  2. Add alt="" to site logo (img) — The logo is decorative (the link text already identifies the destination), so alt="" is the correct fix.

  3. Add scope to table headers — In the affected markdown files, use HTML table syntax or a remark plugin to add scope="col" to column headers. Affects 6 pages.

  4. Investigate duplicate H1 on fuzzy-schedule page — The Starlight hero section creates one <h1 id="_top"> and the page content creates another. Check if the page front matter is correctly configured (hero: vs standard doc layout).

  5. Fix ABNF language highlight — Either remove the abnf language specifier in fuzzy-schedule-specification.md or add a custom language grammar to the expressive-code langs config.

  6. Resolve ThemeSelect conflict in starlight-blog — Follow the plugin's documentation to merge or delegate the ThemeSelect override correctly.

References:

Generated by Multi-Device Docs Tester ·

  • expires on Mar 22, 2026, 2:48 AM UTC

Metadata

Metadata

Labels

cookieIssue Monster Loves Cookies!documentationImprovements or additions to documentationtesting

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions