Skip to content

[bug] Tab order incorrect on forms #591

Closed

Description

@ritaifeoluwa

Problem

Tab order doesn't follow visual order on some forms.

Impact

  • Confusing keyboard navigation
  • Accessibility violation
  • Poor form UX

Fix

Fix tab order to match visual order.

Location

src/components/ forms

Activity

  1. added
    bugSomething isn't working
    accessibilityWCAG / keyboard / screen reader compliance
    on Oct 16, 2026
  2. Ranjeet2063 commented on Oct 16, 2026

    @Ranjeet2063

    Hello maintainers,

    I reviewed the requirements for "[bug] Tab order incorrect on forms" and would like to work on this implementation.

    Technical Implementation Outline:

    1. Audit component lifecycle, state synchronization, and reactive props.
    2. Implement clean responsive layout with TypeScript typings and proper accessibility.
    3. Add automated component unit tests covering loading, empty, and error states.
    4. Verify clean production build without console warnings or lint errors.

    Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!

  3. benfoster-dev commented on Oct 16, 2026

    @benfoster-dev
    Contributor

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

    Hi, kindly assign, i would love to fix

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

  4. Aonlike commented on Oct 16, 2026

    @Aonlike

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

    I would like to work on this issue. I am a FullStack Developer. I have experience in frontend technologies such as HTML, CSS, JavaScript, React, Next.js, Tailwind CSS, and backend technologies including Node.js, Express.js, Python, Django, PHP, Laravel, and databases like MongoDB and MySQL

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

  5. onitsha-droid commented on Oct 16, 2026

    @onitsha-droid

    @onitsha-droid has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    I'd like to take this issue. It covers an important part of the project, and I want to contribute something that fits the existing architecture and development standards and holds up over time.

    I've worked across backend and frontend development, APIs, databases, testing, DevOps, and blockchain-based applications. I'm comfortable reading an unfamiliar codebase, tracking an issue down to its root cause, and writing clean fixes with tests that guard against regressions.

    My plan is to start by reading the existing implementation and project conventions, then build the solution in small, focused steps. I'll test the changes, document them where needed, and keep the code simple so nothing existing breaks. I'll also respond quickly to review feedback so the PR is easy to merge.

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

  6. drips-wave commented on Oct 16, 2026

    @drips-wave

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

    🧑‍💻 @benfoster-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 🌊

  7. grantfox-oss commented on Oct 16, 2026

    @grantfox-oss

    🦊 GrantFox — @benfoster-dev has been assigned to this issue!

    Next steps:

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

    Good luck! Track your progress on GrantFox.

  8. added a commit that references this issue on Oct 16, 2026
  9. grantfox-oss commented on Oct 16, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @benfoster-dev's PR #642 was approved and merged by @ritaifeoluwa.

    🏆 @benfoster-dev: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,628 total points). Track your full progress on GrantFox.

    👏 Great work, @benfoster-dev! Keep contributing to SmartDropLabs.

  10. drips-wave commented on Oct 16, 2026

    @drips-wave

    This issue has been completed by @benfoster-dev as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @benfoster-dev: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programaccessibilityWCAG / keyboard / screen reader compliancebugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions