MEMBERS-DIRECTORY-001J — Preserve profile-recovery keyboard focus - #638
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This was referenced Aug 13, 2026
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.
Closes #637
Officer impact: In the preserved future My Account interface, keyboard and screen-reader users are moved to the available Reload settings action after a profile-photo or finder-setting failure, including each failed reload. The connected interface remains unavailable on production.
Officer documentation:
SYSTEM_DESIGN.md,IMPLEMENTATION_PLAN.md,SECURITY.md, and the optional member-directory text alternative plus no-terminal evidence-review procedure indocs/officers/EVENTS_SHOP_MEMBERS.md.Deployment evidence: None. This is source-only interface accessibility hardening.
memberDirectoryAvailability.tsremains byte-for-bytefalse; runmprc.com remains the inert #623 artifact; Firebase, providers, accounts, sign-in, production data, and connected-live behavior are unchanged.Outcome
Evidence
3d49752eef6dc72fb74408b055aea7bd0d691bb9e74a1777b0ae5284b127f2b3331815db94aac2cd2ccf563acd9021876f2c678a33ff797cdf460e238a84508b089ee14f72ecbbe10fa93f717104154adc2ea20dcbf110cbf6855d0egit diff --check: passed.No CSS, Account wiring, admin finder, client service, backend, Rules, index, package, workflow, release-control, provider, account, data, deployment, or live change is included. #507 retains connection/release authority, and active #616 paths/hunk are preserved.