WEB-002D: publish bounded keyboard-navigation and SPA-focus chain - #660
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #659
Officer impact: Publishes one bounded accessibility-only website artifact after every gate passes. Keyboard users receive reviewed visible focus, deterministic and truthfully announced phone-menu closure, and a one-time focus move into destination main content after client-side path navigation. No officer duty, sign-in workflow, member-directory behavior, backend, or production data changes.
Officer documentation:
SYSTEM_DESIGN.md,IMPLEMENTATION_PLAN.md,SECURITY.md,OPERATIONS_RUNBOOK.md,OFFICER_START_HERE.md,docs/officers/README.md,docs/officers/PUBLISH_AND_CHECK.md, anddocs/officers/UPDATE_PUBLIC_CONTENT.mdcontain the pending-only release boundary and a complete no-terminal procedure. Final live truth remains a separate post-publication change.Deployment evidence: Exact-head CI run
31781730576passed all five jobs. Netlify Deploy Preview6a7ec998bf8fde00086d2bfeis ready at exact control head137d8a8721339a6ca1079283cc34c1bd7cc2706c, review 660, branchcodex/issue-659-netlify-release, contextdeploy-preview, andpublished_at:null; provider metadata reports no Netlify Functions and no edge functions. Header and redirect checks passed; Pages-changed was neutral as expected. The exact marker binds frozen source7496fe0881fb52908c4ff2f40f488df09c94c908, treeccac4c189c195db8ab594e0eefe256ea9fa04996, sole parent prior live sourcec2d87d1f69f15e128a0bc9b1b9f915b7c8417aec, previous sourcec2d87d1f..., rollback deploy6a7e072f8f346b0008510d29, 62 files, and digeste4c26e6f0fbcd086663d86238675f0be228fb649a00628c1c97d1166612f49c7. Marker/root are HTTPS 200 with HSTS and noindex; the marker is alsono-storeandnosniff. Signed-out safe GET/HEAD checks for/,/shop,/events/calendar,/login,/account,/admin/member-directory, and SPA fallback returned 200/noindex without form, sign-in, or data actions. At 1280×900, a client-side Shop route change placed focus onmain#main-content, retained scroll 0/0, and caused no horizontal overflow. At 390×844, the phone menu exposedaria-expanded=trueandaria-controls=primary-navigation; activating Events closed it toaria-expanded=false/hide__nav, moved focus tomain#main-content, retained scroll 0/0, and caused no horizontal overflow. The scoped cue geometry and two-tone styling are proven by mutation-sensitive tests and byte-exact served CSS/source maps; pointer-origin browser activation correctly did not claim a keyboard:focus-visiblemodality. PR #660 merged as exact two-parent commit46e23647d8e0bf9fa3a574ea5c5f993be10a419d, tree3ef47ed0f664e1e9a2c703332ca9071cfda27ad2; exact-main CI run31783141914passed all five jobs. Netlify production deploy6a7ece87c5ca4d0007c1a3fcis ready and published from that merge with the exact marker and artifact; all 62 live files match digeste4c26e6f..., and signed-out desktop/phone checks passed again. Repause PR #661 merged as exact two-parent commit3138a00c1c48e1d5d1dcda0b44722b09a2194ff7; exact-main CI run31783808994passed all five jobs, while Netlify attempt6a7ed0ddb00a46000818878dremained unpublished and the published deploy/marker stayed unchanged. Final live-truth documentation remains pending and must be recorded separately. Firebase, Rules, Functions, indexes, providers, accounts/sign-in, production data, payments, DNS, and connected directory behavior are excluded and unchanged.Exact control
137d8a8721339a6ca1079283cc34c1bd7cc2706c3ef47ed0f664e1e9a2c703332ca9071cfda27ad295880748e15c03b0ee58da6e1ed11ac6c952652911bef16e7b2a46b4ba0d4d3e844bfca0654f6e438a42d73b59012122e6254290WEB-002D-KEYBOARD-FOCUS-2026-08-14codex/netlify-source-659-rollbackpinned toc2d87d1f...94c949abed3759c15cdaa98afc6896343e8a6edd, sole parent exact control head, exact three-file diff SHA-256757f3c16a444d3c371c350a6a109aff24f3f166c9bbb56c2c45e8eb9bd05ad2cLocal verification
e4c26e6f...Publication gate
Merge only with a GitHub merge commit after exact-head CI, exact pinned preview marker/assets, signed-out 1280×900 and 390×844 focus/menu checks, no-directory-request proof, exact rollback ref, and the prepared repause all independently pass. Stop on any main advance or source/tree/path/count/digest/marker/behavior mismatch. Never squash, rebase, promote a preview, invoke a build hook or
netlify deploy --prod, or dispatch the Firebase/GitHub Pages workflow.