Files
jobtrackingapp/docs/ui-modernisation/visual-correction/LANDING_BASELINE_REVIEW.md
T

2.3 KiB

Public homepage baseline

Reviewed the existing anonymous landing page on built runtime e8e7d83958587e8b5a4b93d03d3e736896df5a48. No final launch design was selected or implemented. This is the public root disposition for A3 and input to the separate LAUNCH-SITE-01 workstream.

12 controlled navigation journeys passed at 320, 768 and 1440 px, EN/NB and light/dark. Language switched locally, the features anchor worked from the keyboard, and sign-in and free registration opened their existing routes without submission. All three SVGs loaded in all 12 captures. No page overflow, page exception or unexpected request occurred. The audit intercepted and rejected 24 authenticated-preference requests triggered by anonymous language switching. No preference was persisted server-side.

Findings

  • All 12 captures reported two axe best-practice rules for missing main/content landmarks. This audit does not pass accessibility acceptance. Native screen-reader and device checks remain open.
  • The raw static response contains the generic English title and description, but no rendered hero heading, canonical link or locale alternates. Runtime UI copy requires client rendering. Treat crawlable locale HTML and metadata as launch work.
  • The current preview images show the earlier product styling and a technology-stack line occupies hero space. Replace these with approved, representative screenshots and user-facing content during the launch work. The existing dashboard SVG contains a non-fixture email address. The audit substitutes a synthetic address for its screenshots and leaves the application source unchanged.
  • Anonymous language switching tries the authenticated preference writer. The existing public-auth screens have a local-only choice. Record this as a focused candidate for the landing implementation.

Navigation and audit data · Desktop capture · Tablet capture · Phone capture

The earlier design-neutral launch contract at af8c48ce still controls the launch design and claims. Provider access, billing, production SEO results and launch approval remain separate.