🔍 Multi-Device Docs Testing Report - 2026-06-18

[github-actions]

Test Summary

• Triggered by: @pelikhan
• Workflow run: §27742704772
• Devices tested: 7 viewports (3 mobile, 2 tablet, 2 desktop)
• Pages tested: home + 4 content pages (5 total)
• Test date: 2026-06-18

Results Overview

• 🟢 Passed: responsive layout, tables, code blocks, core a11y across all 35 device×page combinations
• 🟡 Warnings: 1 (heading-level skips on the Cost Management page)
• 🔴 Critical: 0

Critical Issues

None. No horizontal overflow, no broken layout, and no blocking accessibility defects were found on any device.

Accessibility Findings

🟡 Heading-level hierarchy skips on reference/cost-management/ (WCAG 2.1 SC 1.3.1 — Info and Relationships). The page jumps from <h2> straight to <h4>, skipping <h3>. This is content-level (viewport-independent — reproduced on mobile, tablet, and desktop) and affects screen-reader navigation by heading outline.

Two locations:

1. H2: Trigger Frequency and Cost Risk → H4: High Risk (skips H3)
2. H2: Common Scenario Estimates → H4: Weekly digest (schedule, 1 repo) (skips H3)

All other tested pages had a clean heading outline (exactly one h1, no skips).

Recommendations

• On docs/.../reference/cost-management.md(x), change the #### sub-headings under Trigger Frequency and Cost Risk (High / Medium–High / Medium / Low Risk) and under Common Scenario Estimates (the four scenario estimates) to ###, or introduce an intermediate ### heading so levels increase by one. This restores a continuous outline for assistive tech.

View Detailed Test Results by Device

All values below: body horizontal overflow = none on every device; tables and <pre> code blocks are constrained to the viewport with internal scroll (no body overflow); every image has an alt attribute; each page has exactly one <h1>; all <button>/<a> elements have an accessible name.

Mobile Devices

Device	Viewport	H-overflow	Mobile menu	Nav/Search
iPhone 12	390×844	none	opens ✓	present ✓
Pixel 5	393×851	none	opens ✓	present ✓
Galaxy S21	360×800	none	opens ✓	present ✓

Tablet Devices

Device	Viewport	H-overflow	Nav/Search
iPad	768×1024	none	present ✓
iPad Pro 12.9	1024×1366	none	present ✓

Desktop Devices

Device	Viewport	H-overflow	Nav/Search
Desktop FHD	1920×1080	none	present ✓
Desktop 4K	2560×1440	none	present ✓

Content pages (responsiveness, narrowest mobile 360px → desktop)

Page	Tables	Code blocks	Tables/pre wider than viewport	Heading skips
reference/engines/	9	21	0	0
guides/open-telemetry/	2	10	0	0
introduction/architecture/	2	18	0	0
reference/cost-management/	0	25	0	2

Wide tables (e.g. on reference/engines/) use the Starlight responsive-table pattern: rows can be wider than the viewport but are wrapped in an overflow-x:auto container, so the page body never overflows. This is by design and renders correctly.

Environment note — home-page console error (not a docs defect)

The home page emits a repeating console error: Failed to load PDF slides — InvalidPDFException from src/components/WorkflowHero.astro. This is not a documentation bug. docs/slides/github-agentic-workflows.pdf is a 132-byte Git LFS pointer file in this CI checkout (LFS content was not fetched), so the hero's PDF slide viewer cannot parse it. The repo's build:slides script already guards for exactly this ("Did checkout skip Git LFS?"). In an environment with LFS content pulled, the slides load normally. No action needed in the docs source; flagged only for transparency.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• mtalk.google.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "mtalk.google.com"

See Network Configuration for more information.

Generated by 📝 Multi-Device Docs Tester · ◷

• expires on Jun 19, 2026, 11:13 PM UTC-08:00