Browser QA — MinuteFlow sample

Date: 2026-08-27

Environment

• Production build: npm run build
• Logic tests: npm test
• Browser: installed Google Chrome, headless
• Viewports: 1280 × 1400 and 390 × 844

Results

• Input: sample source document is visible and replaceable.
• Strategy/copy: sample is grounded in decisions, next owner, and deadline; unsupported performance claims are excluded.
• Art direction: bold editorial cards with orange, blue, yellow, and green; not a generic blue SaaS template.
• PC: no visible clipping at 1280px.
• SP: initial check found horizontal clipping in the question heading and two-column cards. Mobile CSS now constrains the scene to the viewport, enables forced Japanese wrapping, and changes the choices to one column. A fresh device-emulated full-flow visual check remains required before publication.
• Accessibility: semantic buttons and iframe title are present; reduced-motion CSS is present. Automated contrast and keyboard traversal are not yet measured.
• Performance: production build succeeds; the PDF reader chunk exceeds 500 kB and is dynamically loaded, so document parsing remains the main payload risk.
• Conversion: the sample CTA is document download and copy describes what follows. No live form destination is connected.

Artifacts

• output/browser-check/pc-1280.png
• output/browser-check/sp-390.png
• output/browser-check/sp-390-fixed.png (headless viewport check; device-emulated full-flow check still pending)