LAUNCH QA · NAVIGATION + MOBILE

Nothing should feel like a dead end—or fall off the screen.

This QA center turns navigation and responsive testing into a repeatable founder workflow. Automated browser-local checks help spot overflow and duplicate IDs; manual smoke checks cover the parts that still need human eyes.

TEST NOW — THIS BUILDOpen the critical journeys, resize through the listed widths, and record only what you actually checked. You do not need to retest every page every release when nothing relevant changed.

PRODUCTION LATERReal production auth/roles, connected data/payments, final device coverage, performance and production-domain behavior belong to later QA layers. This page should not fake those results.

CURRENT PAGE CHECK

Run responsive sanity checks here

Checks visible horizontal overflow, duplicate IDs, viewport size, touch/pointer context, and flags small interactive targets for review.

Not run in this viewport yetRun the check at desktop, tablet, and mobile widths.

VIEWPORT TESTING

Resize without losing the checklist

Use the same page at common widths and record the result. ClaraWide remembers each checked viewport in this browser.

Browser windows cannot be resized by ClaraWide itself; these are target widths for manual QA.

NAVIGATION SMOKE MAP

Critical journeys that must have no mystery pages

Open each route, complete the stated journey, then record Pass or Needs Work.

RESPONSIVE CHECKLIST

What to inspect at mobile/tablet widths

These are manual because clipping, hierarchy, readability, and “does this feel sane?” still need a person.

RECENT CHECKS

Browser-local QA history

STATIC ROUTE AUDIT

Build-time link scan

0 missing internal filesThe v0.12.6 package was scanned for relative HTML/CSS/JS/image destinations before packaging.

Hash-only buttons, JavaScript actions, dynamic query routes, and production-only destinations still require manual smoke testing.

NEXT QA LAYER

Browser, device & production smoke evidence

Navigation/mobile checks catch layout and route problems. The next layer records real browser/device and production-domain results.

Open Browser & Device QA →

Launch boundaryPassing this page does not mark Navigation or Mobile launch QA Complete. Final sign-off requires the real production domain, production authentication/roles, real connected data/payment flows, supported desktop/mobile browsers, zoom/orientation tests, and a documented list of unresolved exceptions.