DocsHook Gutenberg table mobile-width experiment — sanitized evidence
Test date: 2026-11-01

1. WordPress integration test (local-only)
WordPress 7.1.4; GeneratePress 3.6.1; LiteSpeed Cache 7.9.2.
Local loopback site 127.0.0.1:18080; Chromium 156.0.0.0.
Same five-column, two-row Gutenberg core/table content in three variants.
Anonymous request showed LiteSpeed cache miss, then hit. No production data, DNS, Cloudflare, or production plugin settings were involved.

At 375 CSS px viewport, each table wrapper was 300 px wide:
- Fixed cells: table 300 px; no local horizontal overflow; first body row 351 px high; five headers 60 px each.
- Fixed cells off: table 560 px; local horizontal overflow; first body row 147 px high; header widths 73/66/119/88/214 px.
- Scoped CSS override: table 1334 px; local horizontal overflow; first body row 45 px high; header widths 144/169/445/207/368 px.
The page document scroll width was 360 px, so the tables did not create whole-page horizontal overflow at this viewport.
At 768 px viewport, all three table widths equalled their 693 px wrappers. At 1280 px viewport, all three equalled their 740 px wrappers. Neither wider viewport had local table overflow.
The rendered tables retained th scope=col, td, and figcaption markup.
Two temporary local test posts were deleted after testing; both anonymous post URLs then returned 404. The VM was stopped.

2. Separate Chromium keyboard fixture (not a WordPress integration test)
At 375 CSS px viewport and 343 px table wrapper, a preceding link was focused and Tab was pressed. The first Tab moved to the overflowing fixed-off table figure; the second moved to the overflowing scoped-CSS table figure. ArrowRight moved each focused region from scrollLeft 0 to 40 px after a short wait. ArrowLeft returned the scoped region to 0 px.

Evidence boundary: These results do not establish physical-phone touch behavior, screen-reader output, or keyboard behavior in other browsers or themes. No accessibility conformance claim is made. The local full database snapshot contains test credentials and is intentionally not public.