[Frontend] Send Remittance recipient-address error is rendered in a detached div, not associated with the input

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

frontend/src/app/components/remittance/RemittanceForm.tsx l.159-176: the recipient Input only receives a className border (l.167) and is NOT passed the error prop, so the Input never sets aria-invalid or points aria-describedby at the message; the validation text sits in a sibling div (l.171-176) with no id and no role=alert/aria-live. Assistive tech is never told the field is invalid and the error is not announced when it appears. The amount field on the same form correctly uses error={errors.amount} (l.211), confirming the intended pattern was bypassed for the recipient field.

Acceptance criteria

• Pass the recipient error via the Input error prop (or add aria-invalid, aria-describedby, and role=alert) so the message is programmatically tied to the field and announced

Files to touch

• frontend/src/app/components/remittance/RemittanceForm.tsx

[adeboladee]

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

Hello maintainer, Please I would like to work on this issue

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

[Olajcodes]

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

Hi maintainer! I would love to help you with this issue. Given my theoretical knowledge and background, I am quite sure that I am well-equipped to tackle it. Please kindly assign it to me.

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

[lishmanTech]

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

Hello maintainer

Can I work on this

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

[grantfox-oss]

🦊 GrantFox — @lishmanTech has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #1111)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

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

🧑‍💻 @lishmanTech: 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!

@lishmanTech's PR #1121 was approved and merged by @ogazboiz.

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

👏 Great work, @lishmanTech! Keep contributing to LabsCrypt.

[drips-wave]

This issue has been completed by @lishmanTech as part of the Stellar Wave Program's 6th Wave 🥳

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