You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
P4 QA: verify mobile, keyboard, screen reader and real Core Web Vitals on deployed website #750
P4 final human-browser UX and performance acceptance (not a release blocker)
The ARSAS public website already validates 62 generated pages, 61 sitemap URLs, images, responsive derivatives, local links/fragments, privacy/measurement contracts, and released v1.6.42 downloads in GitHub Actions. SEO lastmod dates were corrected in #744. Bilingual top-level navigation and mobile menu accessibility are tracked in PR #748.
Remaining: certify actual browser behavior rather than inferring Lighthouse/Core Web Vitals, WCAG compliance or mobile interaction from source validators.
Acceptance on the deployed production site
Verify EN/ID homepage, Download, Quick Start, Guided Demo, FAQ and Compatibility on mobile 360/390 px, tablet 768 px, desktop 1280/1920 px. Use at least Chrome and Edge on Windows, plus a real mobile browser.
Keyboard-only navigation: Skip to content, visible focus, mobile menu open and close, Escape, nested-label taps, localized EN/ID links, download, consent management and clear modals.
Screen reader smoke: NVDA/Windows or equivalent on relevant pages. Confirm accessible names for navigation/menu, meaningful screenshot alt text, headings and landmark order.
Inspect overflow and readability at 200% and 400% zoom, reduced motion, contrast, screenshot lazy-load performance, and touch target size.
Run Lighthouse/PageSpeed mobile+desktop on EN/ID homepage and Download + Quick Start and record URLs/date, measured LCP/CLS/INP or lab-only status when CrUX unavailable. Avoid inventing a passing CWV result.
Confirm downloaded stable binary identity is v1.6.42 single Portable EXE, website Pages attestation SHA and no broken URLs.
Attach screenshots/reports and review any findings in focused PRs. CI-green or metadata scan is not equivalent to device testing.
Dependencies: #748 navigation change; #745 independent image pixel disclosure. No claim of completion until real-browser measurements are attached. This is follow-up product QA, not justification to alter immutable v1.6.42 binaries or bypass gated PR #729.
Automation progress: real Chromium browser QA added in PR #751 (2026-10-25)
An actual Playwright headless Chromium run exercised 36 page/viewport cases across EN/ID Home, Download, Quick Start, Guided Demo, FAQ and Compatibility at 360, 390, 768, 1280 and 1920 px. It checks horizontal overflow, localized main landmarks/headings/Skip links, mobile menu ARIA open/close state, Escape, and clicking localized nested link labels.
Initial run reproduced four mobile overflow defects on Download/Unduh at 360/390px. Browser diagnostics identified the source-commit hash and three supply-chain evidence cards as min-content grid expanders. PR #751 patched mobile grid minmax(0,1fr), child min-width/overflow-wrap and long code hash wrapping; exact-head Measure product website Chromium smoke has now passed with zero test failures.
Preserved report, JSON and four 390/1280px EN/ID screenshots in the existing site-measurement-quality Actions artifact, without adding a 32nd workflow (CI budget max 31). Repository CI-sprawl guard passes after consolidating browser QA in existing .github/workflows/site-measurement.yml.
This is automated Chromium lab evidence only, not certified WCAG/real Android or iOS hardware/NVDA/voiceover/CrUX field Core Web Vitals. Keep issue #750 OPEN until those remaining real-browser/device/performance acceptance checks are supported by recorded measurements and reviewer signoff.
Operator explicitly states prior application and connection QA evidence has already been supplied and accepted; they reject treating repeated testing as a blocker of the already published stable v1.6.42.
Recorded automated evidence: PR #751 merged, 15/15 exact-head workflows green; 36/36 headless Chromium locale/layout/mobile-menu test cases pass; actual 360/390px EN/ID Download overflow fixed and production Pages deployment/attestation verified. Prior Windows regression, binary package/portable and operator connection tests are documented in release PRs.
Release acceptance closed: no additional mobile-device, NVDA or Core Web Vitals measurement is a release prerequisite at this stage. This does not assert WCAG certification, a real mobile-device/screen-reader pass, or measured field Core Web Vitals. Those are optional future product QA and must be identified honestly if revisited.
Close this issue as not planned as a release blocker; do not reintroduce these tests as new gates against an already approved product release without a specific reproducible regression.
Activity
masarray commentedon Oct 25, 2026
Automation progress: real Chromium browser QA added in PR #751 (2026-10-25)
An actual Playwright headless Chromium run exercised 36 page/viewport cases across EN/ID Home, Download, Quick Start, Guided Demo, FAQ and Compatibility at 360, 390, 768, 1280 and 1920 px. It checks horizontal overflow, localized main landmarks/headings/Skip links, mobile menu ARIA open/close state, Escape, and clicking localized nested link labels.
Initial run reproduced four mobile overflow defects on Download/Unduh at 360/390px. Browser diagnostics identified the source-commit hash and three supply-chain evidence cards as min-content grid expanders. PR #751 patched mobile grid minmax(0,1fr), child min-width/overflow-wrap and long code hash wrapping; exact-head Measure product website Chromium smoke has now passed with zero test failures.
Preserved report, JSON and four 390/1280px EN/ID screenshots in the existing
site-measurement-qualityActions artifact, without adding a 32nd workflow (CI budget max 31). Repository CI-sprawl guard passes after consolidating browser QA in existing.github/workflows/site-measurement.yml.This is automated Chromium lab evidence only, not certified WCAG/real Android or iOS hardware/NVDA/voiceover/CrUX field Core Web Vitals. Keep issue #750 OPEN until those remaining real-browser/device/performance acceptance checks are supported by recorded measurements and reviewer signoff.
masarray commentedon Oct 25, 2026
Operator public-release QA decision — 25 Oct 2026
Operator explicitly states prior application and connection QA evidence has already been supplied and accepted; they reject treating repeated testing as a blocker of the already published stable v1.6.42.
Recorded automated evidence: PR #751 merged, 15/15 exact-head workflows green; 36/36 headless Chromium locale/layout/mobile-menu test cases pass; actual 360/390px EN/ID Download overflow fixed and production Pages deployment/attestation verified. Prior Windows regression, binary package/portable and operator connection tests are documented in release PRs.
Release acceptance closed: no additional mobile-device, NVDA or Core Web Vitals measurement is a release prerequisite at this stage. This does not assert WCAG certification, a real mobile-device/screen-reader pass, or measured field Core Web Vitals. Those are optional future product QA and must be identified honestly if revisited.
Close this issue as not planned as a release blocker; do not reintroduce these tests as new gates against an already approved product release without a specific reproducible regression.