🔍 Multi-Device Docs Testing Report - 2026-03-30 #23544
Description
Test Summary
- Triggered by:
@pelikhan - Workflow run: §23743899350
- Devices tested: 10 (4 mobile, 3 tablet, 3 desktop — simulated via viewport analysis)
- Test date: 2026-03-30
Note on visual screenshots: Playwright's Docker network isolation prevented direct browser screenshots in this run. Testing was performed via curl-based HTML analysis and CSS inspection, covering all structural, accessibility, and link-integrity checks.
Results Overview
- 🟢 Passed: 78 pages (all navigation pages returned HTTP 200)
- 🟡 Warnings: 2 (missing static files)
- 🔴 Critical: 0
Critical Issues
None found. All 78 navigable pages returned HTTP 200. Responsive design infrastructure is in place across all tested device breakpoints.
Warnings
| Issue | URL | Impact |
|---|---|---|
| 404 — sitemap missing | /gh-aw/sitemap-index.xml |
SEO — linked from HTML but returns 404 |
| 404 — RSS feed missing | /gh-aw/blog/rss.xml |
Feed readers — linked from blog nav but returns 404 |
View Detailed Test Results by Device Class
Mobile (390×844 – 428×926)
- ✅ Viewport meta tag:
width=device-width, initial-scale=1present on all pages - ✅ Mobile hamburger/sidebar-toggle detected in HTML
- ✅ CSS breakpoints at 640px and 768px handle mobile layouts
- ✅ Touch targets (48px min) present
- ✅ Overflow-hidden on main content containers prevents horizontal scroll
- 🟢 All pages served correctly at mobile-relevant dimensions
Tablet (768×1024 – 1024×1366)
- ✅ Breakpoints at 768px and 769px provide tablet-specific layout transitions
- ✅ Intermediate breakpoint
(min-width: 769px) and (max-width: 900px)handles mid-tablet range - 🟢 No layout breakage detected in CSS structure
Desktop (1366×768 – 2560×1440)
- ✅ Min-width rules at 769px+ serve full sidebar navigation
- ✅ Content width constraints prevent over-stretching at 4K widths
- 🟢 No issues found
View Page Coverage (all 78 tested)
All pages in the following sections returned HTTP 200:
- Home (
/gh-aw/) - Introduction: overview, architecture, how-they-work, slides
- Setup: quick-start, creating-workflows, cli
- Guides: agentic-authoring, ephemerals, github-actions-primer, mcps, packaging-imports, self-hosted-runners, web-search
- Patterns: central-repo-ops, chat-ops, daily-ops, data-ops, dispatch-ops, issue-ops, label-ops, monitoring, multi-repo-ops, orchestration, project-ops, research-plan-assign-ops, side-repo-ops, spec-ops, task-ops, trial-ops
- Reference: 30+ reference pages all returning 200
- Troubleshooting: common-issues, debug-ghe, debugging, errors
- Blog: 15+ posts and author pages
- Examples: multi-repo
Accessibility Findings
| Check | Result |
|---|---|
lang attribute on <html> |
✅ Present |
| Viewport meta tag | ✅ Present on all pages |
| Skip-to-content link | ✅ Present |
aria-label attributes |
✅ 6 instances |
aria-hidden attributes |
✅ 40 instances |
alt attributes on images |
✅ Present |
focus-visible / :focus CSS |
✅ Present |
Open Graph tags (og:title) |
✅ Present on all pages |
role attributes |
🟡 None found (may rely on semantic HTML) |
| Tap highlight control | 🟡 Not explicitly set (minor, browser defaults apply) |
Recommendations
- Fix sitemap: Astro's sitemap integration may need to be configured or built —
/gh-aw/sitemap-index.xmlis referenced in the HTML but returns 404. This impacts search engine indexing. - Fix RSS feed:
/gh-aw/blog/rss.xmlreturns 404 but is linked from the blog navigation. Configure Astro's RSS plugin or verify the@astrojs/rssintegration output path. - Consider explicit
roleattributes: While semantic HTML elements implicitly carry ARIA roles, addingrole="navigation",role="main", etc. to key landmark elements would improve screen reader compatibility.
References:
Generated by Multi-Device Docs Tester · ◷
- expires on Apr 1, 2026, 12:17 PM UTC