Test Summary
- Triggered by:
@pelikhan
- Workflow run: §23708510481
- Pages tested: 12 (all discoverable pages)
- Device simulation: Static HTML/CSS analysis (Playwright unavailable due to network isolation)
- Test date: 2026-03-29
Note: Playwright browser tools were unavailable due to Docker network isolation between the agent container and Playwright container. Tests were performed via curl-based HTML/CSS static analysis, which covers layout structure, accessibility attributes, meta tags, link integrity, and responsive CSS — but not JavaScript-rendered interactions or visual screenshots.
Results Overview
- 🟢 Passed: 14 checks
- 🟡 Warnings: 2 items
- 🔴 Critical: 0 items
Critical Issues
None. All pages are accessible, structurally sound, and responsive.
View All Warnings
⚠️ Warning 1: Skip Link Target (#_top instead of #main-content)
The skip link (<a href="#_top" class="skip-link">) exists and is accessible via keyboard (visually hidden until focused per WCAG 2.4.1 CSS comment), but it points to #_top which scrolls to the top of the page rather than bypassing the navigation to reach the main content. For optimal keyboard/screen-reader experience, the skip link should target the main content area (e.g., #main-content on <main id="main-content">).
- Impact: Minor — skip link exists but doesn't optimally skip navigation
- Affected pages: All pages (global component)
⚠️ Warning 2: Sitemap Returns 404 in Dev Mode
/gh-aw/sitemap-index.xml returns HTTP 404 when served via astro dev. This is expected Astro behavior (sitemap is generated at build time via @astrojs/sitemap), but the HTML <head> references it as <link rel="sitemap" href="/gh-aw/sitemap-index.xml"/>. The sitemap will be available in production builds.
- Impact: None in production — dev-mode only limitation
- Affected pages: All pages reference the sitemap link
View Detailed Test Results by Device
Static analysis was performed — visual device screenshots were unavailable due to Playwright network isolation.
Responsive CSS Coverage
The site implements responsive design with the following breakpoints:
max-width: 640px — small mobilemax-width: 768px — mobile/tablet boundarymin-width: 769px — tablet and upmin-width: 769px and max-width: 900px — narrow tabletmin-width: 50em / 72em / 90rem — desktop variants
Mobile
| Feature |
Status |
| Viewport meta tag |
✅ width=device-width, initial-scale=1 |
| Mobile hamburger menu |
✅ <button aria-label="Toggle navigation menu"> |
| Mobile search cancel button |
✅ .md:sl-hidden (hidden on desktop) |
| Touch-friendly breakpoints |
✅ 640px, 768px |
prefers-reduced-motion |
✅ 4 CSS rules |
Tablet
| Feature |
Status |
| Tablet-specific breakpoints |
✅ 769px–900px |
| Navigation layout |
✅ Responsive grid |
Desktop
| Feature |
Status |
| Max-width containers |
✅ 720px, 768px, 900px |
| Full navigation sidebar |
✅ |
| Theme toggle |
✅ starlight-theme-select |
All Pages — Structural Checks
| Page |
HTTP |
Viewport |
Lang |
H1 |
Nav |
Main |
Images w/o Alt |
/gh-aw/ |
✅ 200 |
✅ |
✅ en |
✅ |
✅ |
✅ |
0 |
/gh-aw/introduction/overview/ |
✅ 200 |
✅ |
✅ en |
✅ |
✅ |
✅ |
0 |
/gh-aw/introduction/architecture/ |
✅ 200 |
✅ |
✅ en |
✅ |
✅ |
✅ |
0* |
/gh-aw/introduction/how-they-work/ |
✅ 200 |
✅ |
✅ en |
✅ |
✅ |
✅ |
0 |
/gh-aw/setup/quick-start/ |
✅ 200 |
✅ |
✅ en |
✅ |
✅ |
✅ |
0 |
/gh-aw/setup/creating-workflows/ |
✅ 200 |
✅ |
✅ en |
✅ |
✅ |
✅ |
0 |
/gh-aw/reference/engines/ |
✅ 200 |
✅ |
✅ en |
✅ |
✅ |
✅ |
0 |
/gh-aw/reference/faq/ |
✅ 200 |
✅ |
✅ en |
✅ |
✅ |
✅ |
0 |
/gh-aw/reference/github-tools/ |
✅ 200 |
✅ |
✅ en |
✅ |
✅ |
✅ |
0 |
/gh-aw/examples/multi-repo/ |
✅ 200 |
✅ |
✅ en |
✅ |
✅ |
✅ |
0 |
/gh-aw/blog/ |
✅ 200 |
✅ |
✅ en |
✅ |
✅ |
✅ |
0 |
/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/ |
✅ 200 |
✅ |
✅ en |
✅ |
✅ |
✅ |
0 |
*Architecture page had a false-positive image-without-alt detection — the <img src=x onerror=...> is XSS example code inside a copy-button data-code attribute (documentation content), not a real <img> element.
Accessibility Findings
| Check |
Result |
| Viewport meta |
✅ All pages |
lang attribute |
✅ en on all pages |
| Skip link |
⚠️ Present but targets #_top instead of main content |
| ARIA labels |
✅ Search (×3), navigation (×2), toggle (×1) |
| Focus styles |
✅ 13 CSS focus rules |
| Image alt text |
✅ All real images have alt text |
| Table headers |
✅ All tables use <thead> + <th> |
prefers-reduced-motion |
✅ 4 CSS rules |
prefers-color-scheme |
✅ Supported |
| Dark/light theme toggle |
✅ Present |
| OG meta tags |
✅ title, description, image (1200×630) |
Recommendations
-
Skip link target (low priority): Update <a href="#_top" class="skip-link"> to <a href="#main-content" class="skip-link"> and add id="main-content" to the <main> element. This improves keyboard navigation for screen reader users (WCAG 2.4.1 compliance).
-
Sitemap in dev mode (informational): No action needed — this is expected Astro behavior. The sitemap is generated at build time and will be available in production.
References:
Generated by Multi-Device Docs Tester · ◷
Test Summary
@pelikhanResults Overview
Critical Issues
None. All pages are accessible, structurally sound, and responsive.
View All Warnings
#_topinstead of#main-content)The skip link (
<a href="#_top" class="skip-link">) exists and is accessible via keyboard (visually hidden until focused per WCAG 2.4.1 CSS comment), but it points to#_topwhich scrolls to the top of the page rather than bypassing the navigation to reach the main content. For optimal keyboard/screen-reader experience, the skip link should target the main content area (e.g.,#main-contenton<main id="main-content">)./gh-aw/sitemap-index.xmlreturns HTTP 404 when served viaastro dev. This is expected Astro behavior (sitemap is generated at build time via@astrojs/sitemap), but the HTML<head>references it as<link rel="sitemap" href="/gh-aw/sitemap-index.xml"/>. The sitemap will be available in production builds.View Detailed Test Results by Device
Responsive CSS Coverage
The site implements responsive design with the following breakpoints:
max-width: 640px— small mobilemax-width: 768px— mobile/tablet boundarymin-width: 769px— tablet and upmin-width: 769px and max-width: 900px— narrow tabletmin-width: 50em / 72em / 90rem— desktop variantsMobile
width=device-width, initial-scale=1<button aria-label="Toggle navigation menu">.md:sl-hidden(hidden on desktop)prefers-reduced-motionTablet
Desktop
starlight-theme-selectAll Pages — Structural Checks
/gh-aw//gh-aw/introduction/overview//gh-aw/introduction/architecture//gh-aw/introduction/how-they-work//gh-aw/setup/quick-start//gh-aw/setup/creating-workflows//gh-aw/reference/engines//gh-aw/reference/faq//gh-aw/reference/github-tools//gh-aw/examples/multi-repo//gh-aw/blog//gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/*Architecture page had a false-positive image-without-alt detection — the
<img src=x onerror=...>is XSS example code inside a copy-buttondata-codeattribute (documentation content), not a real<img>element.Accessibility Findings
langattributeenon all pages#_topinstead of main content<thead>+<th>prefers-reduced-motionprefers-color-schemeRecommendations
Skip link target (low priority): Update
<a href="#_top" class="skip-link">to<a href="#main-content" class="skip-link">and addid="main-content"to the<main>element. This improves keyboard navigation for screen reader users (WCAG 2.4.1 compliance).Sitemap in dev mode (informational): No action needed — this is expected Astro behavior. The sitemap is generated at build time and will be available in production.
References: