[Frontend] Add accessible names to icon-only and toggle controls

[ogazboiz]

Join the discussion on Telegram

Why this matters

Several interactive controls across the app are icon-only or custom toggle elements with no accessible name, so screen-reader and keyboard users cannot tell what they do. Concrete examples already in the codebase:

• The browser-notifications toggle in frontend/src/app/settings/page.tsx is a bare <button> containing only a styled <span> — no text, aria-label, or aria-pressed, so it announces as an unlabeled button with no state.
• The copy-address / copy-contract buttons in the same file are icon-only (<Copy />) with no aria-label.
• Only ~15 of ~40 component files under frontend/src/components use any aria-*/role attributes at all.

For a finance app this is both an inclusivity and a quality issue.

Acceptance criteria

• Add aria-label (and aria-pressed for toggles) to the icon-only / custom-toggle controls in frontend/src/app/settings/page.tsx.
• Audit the primary interactive surfaces (stream cards, dashboard actions, wallet buttons, notification dropdown) and add accessible names where icon-only controls exist.
• Ensure custom toggles are reachable and operable by keyboard.
• Where feasible, add a lint rule or note for future contributors (e.g. eslint-plugin-jsx-a11y) — optional but encouraged.

Files to touch

• frontend/src/app/settings/page.tsx
• frontend/src/components/NotificationDropdown.tsx
• frontend/src/components/streams/IncomingStreamCard.tsx
• other icon-only controls surfaced during the audit

Out of scope

• A full WCAG audit / color-contrast overhaul.

[Nuel-ship-it]

@Nuel-ship-it has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hello Maintainer, I'm excited about this issue and would like to solve it

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Nuel-ship-it to this issue.

[Muhammadcodes112]

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

I would like to work on this if assigned Thanks

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

[0xMegie]

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

Can I work on this issue sir..?

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

[dee-john]

@dee-john has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi, I'd like to work on this issue! because I am very conversant with solving problems like this!

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

[drips-wave]

Congratulations, @0xMegie! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @0xMegie: 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 🌊

[drips-wave]

This issue has been completed by @0xMegie as part of the Stellar Wave Program's 5th Wave 🥳

😎 @0xMegie: 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.