Skip to content

🔍 Multi-Device Docs Testing Report - 2026-03-22 #22226

@github-actions

Description

@github-actions

Test Summary

  • Triggered by: @pelikhan
  • Workflow run: §23394015047
  • Pages tested: 9 (static analysis across all devices)
  • Test date: 2026-03-22

Note: Playwright visual browser testing was blocked by network isolation in the sandbox environment (the Playwright container could not reach the docs server at 172.30.0.20:4321). Testing was completed via HTML/CSS static analysis and curl-based HTTP checks.

Results Overview

  • 🟢 Passed: 9 pages (HTTP 200), accessibility checks, SEO, responsive CSS
  • 🟡 Warnings: 1 broken link affecting 8+ pages
  • 🔴 Critical: 0

Broken Link Found

/gh-aw/introduction/architecture returns HTTP 404.

The page exists at /gh-aw/introduction/architecture/ (with trailing slash, HTTP 200), but all internal links reference the path without a trailing slash. This affects the following pages:

Page Link Text
/gh-aw/ (nav link)
/gh-aw/introduction/overview/ (nav link)
/gh-aw/introduction/how-they-work/ "safety layer"
/gh-aw/setup/quick-start/ (nav link)
/gh-aw/setup/creating-workflows/ (nav link)
/gh-aw/reference/faq/ "Security Architecture"
/gh-aw/reference/engines/ "Security Guide"
/gh-aw/reference/github-tools/ (nav link)

Fix: Add a trailing slash redirect or configure Astro to handle paths without trailing slash, or ensure all internal links use the / suffix.

View Detailed Test Results

HTTP Status Checks (All Devices)

All pages returned HTTP 200:

Page Status
/gh-aw/ ✅ 200
/gh-aw/introduction/overview/ ✅ 200
/gh-aw/introduction/how-they-work/ ✅ 200
/gh-aw/setup/quick-start/ ✅ 200
/gh-aw/reference/faq/ ✅ 200
/gh-aw/blog/ ✅ 200
/gh-aw/reference/engines/ ✅ 200
/gh-aw/reference/github-tools/ ✅ 200
/gh-aw/setup/creating-workflows/ ✅ 200
/gh-aw/introduction/architecture ❌ 404
/gh-aw/introduction/architecture/ ✅ 200

Accessibility Analysis

Checked across: Homepage, Overview, Quick Start, FAQ

Check Result
<main> landmark ✅ Present on all pages
<nav> landmark ✅ Present on all pages
lang attribute en
Viewport meta tag width=device-width, initial-scale=1
Images with alt text ✅ No missing alt attributes
Heading hierarchy ✅ No level jumps detected
Dark mode support data-theme="dark"
Print stylesheet ✅ Present
Hamburger/menu button ✅ Present for mobile
Search component ✅ Present
Theme toggle ✅ Present
Table of contents ✅ Present

Responsive Design

Check Result
Media queries in stylesheets ✅ 51 queries
Mobile breakpoint ✅ 768px
CSS breakpoints min-width: 769px and max-width: 768px
Touch-friendly hover handling @media (hover: hover)

SEO & Meta Tags

Check Result
og:title ✅ All pages
og:description ✅ All pages
og:image ✅ All pages (1200×630 PNG)
Canonical URLs ✅ All pages
Sitemap /gh-aw/sitemap-index.xml
RSS feed /gh-aw/blog/rss.xml
Testing Methodology Note

Playwright visual testing was attempted but blocked by network isolation: the Playwright MCP container runs with --network host, and the sandbox firewall prevented connections from the host network to the agent container's bridge IP (172.30.0.20:4321). All testing was performed using:

  • curl HTTP status and content checks
  • Python html.parser for DOM/accessibility analysis
  • CSS pattern analysis for responsive design
  • Internal link crawling for broken link detection

Recommendations

  1. Fix the broken link to /gh-aw/introduction/architecture — either update all internal links to include a trailing slash, or configure Astro's trailingSlash setting to "always" so paths redirect correctly.
  2. Consider adding a redirect rule: /gh-aw/introduction/architecture/gh-aw/introduction/architecture/

References:

Generated by Multi-Device Docs Tester ·

  • expires on Mar 24, 2026, 2:57 AM UTC

Metadata

Metadata

Assignees

No one assigned

    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