Audit and fix keyboard navigation and focus-visible rings across marketplace filters and grids

[1nonlypiece]

📌 Description

The marketplace surfaces — MarketplaceFilter/MarketplaceFilters.tsx,
MarketplaceGrid.tsx, MarketplaceResultsLayout.tsx, and MarketplaceCard.tsx
— use custom controls (sort, filter chips, view toggles) whose keyboard
operability and focus visibility are inconsistent. Keyboard users can lose track
of focus or be unable to reach controls.

This issue audits and fixes keyboard navigation and :focus-visible rings across
these components and adds tests to prevent regressions.

🎯 Requirements and Context

• Every interactive control reachable and operable by keyboard.
• Visible :focus-visible ring on cards, filters, chips, and toggles.
• Correct roles/ARIA on custom controls (e.g. toggle buttons, listboxes).
• Tests asserting tab order and keyboard activation.

🛠️ Suggested Execution

1. Fork the repo and create a branch

git checkout -b a11y/marketplace-keyboard-focus

2. Implement changes

• Fix focus/keyboard issues across the listed marketplace components.
• Add src/components/__tests__/MarketplaceKeyboardA11y.test.tsx covering tab
  order, keyboard activation, and focus visibility of key controls.
• Add docs/accessibility/MARKETPLACE_A11Y.md documenting the audit and fixes.
• Validate keyboard-only browsing of the marketplace.

3. Test and commit

• Run pnpm test.
• Cover edge cases: clearing all filters via keyboard, toggling view, focus after
  filtering, empty results focus.

Example commit message

a11y: keyboard navigation and focus rings across marketplace

✅ Guidelines

• Minimum 95% test coverage on changed components.
• Clear, reviewer-friendly documentation.
• Timeframe: 96 hours.

🏷️ Labels

type-security · type-enhancement · area-frontend · MAYBE REWARDED ·
GRANTFOX OSS · OFFICIAL CAMPAIGN

💬 Community & Support

• Join the CommitLabs contributor Discord to coordinate and get unblocked fast:
  https://discord.gg/WV7tdYkJk
• Introduce yourself before starting so we can avoid duplicate work and pair you
  with a reviewer. Maintainers triage actively and review fast.

[amehsamuel200225-sketch]

@amehsamuel200225-sketch has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi…. I’m a software engineer, let me fix this issue please!

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

[abdullahilateefat03-boop]

@abdullahilateefat03-boop has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello maintainers,
I’m interested in taking up this issue. I have experience in Full-stackweb development. After reviewing the issue requirements, I believe I can implement a proper solution and follow the project guidelines.
Kindly assign the issue to me.
Thanks.

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

[GBOYEE]

I'd like to work on this.

Approach:

• I'll add the audit logging with proper schema and query support
• Verify with existing tests + add new ones if needed

Estimated effort: ~1-2 hours. PR incoming shortly.

[GBOYEE]

I'd like to work on this.

Approach:

• I'll add the audit logging with proper schema and query support
• Verify with existing tests + add new ones if needed

Estimated effort: ~1-2 hours. PR incoming shortly.

[GBOYEE]

I'd like to work on this issue.

My Approach

• Analyze the root cause of: ##
• Implement a clean, tested fix
• Follow existing code patterns and conventions

Files Likely Modified

• TBD after analysis

Timeline

• Estimated completion: 15-30 minutes
• PR will be submitted with tests and documentation

Closes #654