Skip to content

Fix website SEO metadata and accessibility - #89

Merged
AdamXweb merged 1 commit into
websitefrom
fix/website-seo-accessibility
Oct 30, 2026
Merged

AdamXweb merged 1 commit into
websitefrom
fix/website-seo-accessibility

Conversation

@adamXbot

@adamXbot adamXbot commented Oct 30, 2026 •

Copy link
Copy Markdown
Collaborator

Documentation metadata could arrive outside the document head, retro controls could cover the content in short viewports, and several controls lost focus or exposed incomplete semantics. This makes metadata available to all crawlers before HTML streams and fixes the reported accessibility regressions.

Based directly on website after #86 and #87 were squash-merged. Restacked to preserve both merged changes and this PR’s SEO/accessibility changes. Website CI also covers PRs stacked on fix/website-* branches.

  • Improve generated descriptions and 404 metadata; verify titles, canonicals, descriptions and social tags in raw and hydrated document heads.
  • Let retro chrome scroll away on short/narrow screens, correct text contrast, and keep focus visible after minimising/restoring. Wrap narrow journey tabs and the expanded film description; include its closing platform scene.
  • Keep one keyboard comparison slider with accessible images and a stable zoom toggle; correct game progress/hint semantics, sidebar labels, breadcrumbs and empty contents lists.
  • Restore search-field focus after retry, retain navigation during search failures, and announce client-side route titles.
  • Publish the captured catalogue with English language, a main landmark and sufficient contrast. An idempotent publishing helper preserves these fixes after recapture and rejects unexpected generator structure. The captured reference page is noindex,follow; /docs/catalogue remains indexable.

The documented Escape-to-exit shortcut, journey canonical URLs and nonce-based HTML cache policy remain intentional. Screenshot evidence is unchanged.

Validation passed:

  • 34 Node tests on the declared minimum Node 22.18.0 after restacking, including Detect new generated assets during website docs refresh #87’s refresh regressions; production build on that version.
  • 21 Chromium browser tests, including 320×256 reflow/focus, light/dark catalogue contrast, three retro palettes, pointer/keyboard comparison, search recovery and metadata navigation.
  • Production Worker checks: 52 pages and 52 assets, crawler user-agent variants, 404 metadata, redirects, security headers and storage disclosures.
  • Typecheck, lint, 15 installer tests, Bash syntax, ShellCheck, dependency audit and Cloudflare deploy dry run.

Validation used the local built Worker and Chromium. No live production, real screen-reader, native zoom, Firefox or Safari audit was performed.

@adamXbot
adamXbot force-pushed the fix/website-review-followups branch from 7a3ceab to a9e08ca Compare October 30, 2026 05:25
@adamXbot
adamXbot force-pushed the fix/website-seo-accessibility branch from be3e37d to db87ddf Compare October 30, 2026 05:27
Base automatically changed from fix/website-review-followups to website October 30, 2026 05:30
@adamXbot
adamXbot force-pushed the fix/website-seo-accessibility branch from db87ddf to 456daca Compare October 30, 2026 05:38
@AdamXweb
AdamXweb merged commit 0906326 into website Oct 30, 2026
3 checks passed
@AdamXweb
AdamXweb deleted the fix/website-seo-accessibility branch October 30, 2026 05:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants