Skip to main content
Quality & testing

How I check this site.

I test the interactions, accessibility, and layouts, then keep a record of what passed and what still needs a human review.

Recorded checks passed

Last recorded review:

Checks you can inspect

Unit tests

Passed

10

tests passed

Permission boundaries, cancellation, theme choices, and project navigation.

Browser interactions

Passed

12

checks passed

Keyboard paths, saved preferences, the combobox, and the agent-review flow.

Automated accessibility

Passed

0

violations in 29 scans

Recorded page and component states, including light, dark, and high contrast.

Responsive layouts

Passed

580

checks across 116 pages

Phone, tablet, and desktop widths, with additional menu and recovery-state checks.

Results come from a local production build. Checkmarks describe the recorded checks; they are not a live monitor.

What the checks cover

Clear keyboard focus, readable themes, saved display settings, and layouts that keep text and controls within the viewport. The prototype also checks that permission decisions, failures, and human review remain separate steps.

Layout checks use 320px, 390px, 768px, 1024px, 1440px widths, plus 57 interactive layout states. Wide tables and code examples scroll inside their own regions.

Try the ReactZero combobox, the agent-review prototype, or selected work.

Performance measurements

Lab results

Three Lighthouse runs per page, using simulated mobile throttling. These measurements describe the test setup; real-user Core Web Vitals have not been collected.

Home

90 / 100

Performance score · median of 3 runs

LCP 3.53 s · CLS 0.000 · blocking time 70 ms

Selected work

87 / 100

Performance score · median of 3 runs

LCP 4.08 s · CLS 0.000 · blocking time 24 ms

The next human checks

Manual screen-reader review and developer usability sessions are still to come. Automated scans cover the recorded pages and states; they do not establish WCAG conformance.

Read the accessibility information or report something that gets in your way.

See testing methods and recorded results

Methods and scope

Chrome with emulated CSS viewports against a local production server. Menu checks include enlarged text and reading spacing. This record does not claim physical-device or screen-reader testing.

Logic and browser checks can be rerun with npm test, npm run test:browser, and npm run test:responsive against a running production build.

Browser checks

  • PassedStable first screen without a canvas or model download
  • PassedDisplay dialog keyboard access, containment, close and focus return
  • PassedExplicit theme persists and System follows OS changes
  • PassedReading and reduced-motion preferences persist and can be reset
  • PassedExperimental theme deep links and return to system preference
  • PassedA slower experimental theme cannot overwrite a newer choice
  • PassedSelected work, archive and direct project links
  • PassedPublished combobox keyboard selection and empty state
  • PassedPermission denial preserves work and cannot silently continue
  • PassedApproval, expiry and human review are separate steps
  • PassedFailure recovery requests fresh permission; cancellation preserves context
  • Passed320 CSS-pixel layouts and mobile navigation

Recorded data