MilestoneActions' Fund/Deposit buttons have no distinguishing accessible name across multiple milestones/pools, so screen-reader users can't tell which button is which out of context

[chonilius]

src/app/milestones/MilestoneActions.tsx#MilestoneFundButton and #PoolDepositButton
both render a plain, generically-labeled button per instance:

<Button size="sm" variant="outline" onClick={handleFund} disabled={pending || connecting}>
  {pending || connecting ? "Confirming in wallet..." : "Fund milestone"}
</Button>
...
<Button size="sm" variant="outline" onClick={handleDeposit} disabled={pending || connecting}>
  {pending || connecting ? "Confirming..." : "Deposit"}
</Button>

Neither has an aria-label incorporating which milestone or pool it applies to.
src/app/milestones/page.tsx renders one of each per milestone/pool — with several
milestones and pools on the page (per the mock data, at least two of each), a screen
reader user navigating by control (a common assistive-technology pattern — e.g. NVDA's
"list all buttons" or VoiceOver's rotor) hears "Fund milestone, button" and "Deposit,
button" repeated identically for every card, with no way to distinguish which milestone
or pool a given instance belongs to without first navigating through the surrounding,
unassociated heading text.

Suggested fix: pass the milestone name / pool repo into each button's accessible name,
e.g. aria-label={Fund ${milestoneName}} / aria-label={Deposit to ${poolRepo} pool},
so each control is independently identifiable out of context.

[codefather2026]

Hi maintainer, i will like to solve this issue

[brightpixel-dev]

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

hello can i work on this issue please

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

[Otfrugger]

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

Hello can i work on this?

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

[drips-wave]

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

🧑‍💻 @brightpixel-dev: 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 @brightpixel-dev as part of the Stellar Wave Program's 8th Wave 🥳

😎 @brightpixel-dev: 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.