[Audit] Wallet connection modal has no focus trap or focus restoration

[K1NGD4VID]

Filed from the second-wave repository audit (issue 55/100). See the audit summary for full category context.

• Location: frontend/src/components/wallet/WalletModal.tsx:26-196
• Problem: This modal hand-rolls its own Escape handling (61-73) and body-scroll lock (76-81) instead of using useModalDialog (used by every other modal: TopUpModal, CancelConfirmModal, StreamDetailsModal, StreamCreationWizard, Navbar's MobileMenu). As a result it has no focus trap and no focus restoration to the previously-focused element on close — the very first modal a new user interacts with is the one without proper keyboard accessibility.
• Evidence: No useModalDialog import/usage in the file, unlike every sibling modal.
• Suggested implementation: Migrate WalletModal to useModalDialog, removing its bespoke Escape/scroll-lock logic.
• Acceptance criteria: Tab key cannot move focus outside the modal while open; closing it returns focus to the button that opened it, verified by a keyboard-navigation test.
• Difficulty: S
• Expected impact: Fixes the most consequential accessibility gap in the app, given it's the entry point to using the product at all.

[zainabwahab-eth]

@zainabwahab-eth has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Please assign to me. Thank you

ℹ️ Repo Maintainers: To accept this application, review their application or assign @zainabwahab-eth to this issue.

[Senatormike001]

@Senatormike001 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

‎I’ll take ownership of this issue and work toward a clean, reliable solution that meets all acceptance criteria. I’ll also ensure the implementation is properly tested before raising the pull request.
‎

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Senatormike001 to this issue.

[abimbolaalabi]

@abimbolaalabi has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Please assign issues to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @abimbolaalabi to this issue.

[drips-wave]

Congratulations, @zainabwahab-eth! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @zainabwahab-eth: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@zainabwahab-eth's PR #1349 was approved and merged by @K1NGD4VID.

🏆 @zainabwahab-eth: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (516 total points). Track your full progress on GrantFox.

👏 Great work, @zainabwahab-eth! Keep contributing to LabsCrypt.

[drips-wave]

This issue has been completed by @zainabwahab-eth as part of the Stellar Wave Program's 8th Wave 🥳

😎 @zainabwahab-eth: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.