Add accessible labels to dashboard dialog input fields

[MamidiDhana]

Linked issue

Closes #251

What this PR does

• Adds accessible labels to the input fields in the Import from URL dialog.
• Adds an accessible label to the input field in the Scan Organization dialog.
• Associates labels with inputs using htmlFor and id.
• Preserves the existing UI and functionality while improving accessibility.

Type of change

• Bug fix
• New feature
• ML model / training pipeline
• Refactor (no behaviour change)
• Documentation
• Tests only

ML tier (if applicable)

• Tier 1 — Triage
• Tier 2 — Predictive
• Tier 3 — Autonomous
• Not ML-related

Stack affected

• Backend
• Frontend
• Both

---

Changes

Backend

• None

Frontend

• Added accessible labels for dialog input fields.
• Connected labels to inputs using htmlFor and id.

New dependencies

• None

Database / schema changes

• None

---

Testing

How did you test this?

• Ran the application locally.
• Opened both dialogs.
• Verified that each input has a meaningful accessible label.
• Confirmed keyboard navigation and existing functionality work correctly.

Checklist

• Tested locally end-to-end (relevant UI tested)
• New ML model falls back gracefully when model file is absent (Not applicable)
• No new console.error or unhandled Python exceptions introduced
• Added or updated tests where applicable
• requirements.txt / package.json updated if new dependencies added (Not applicable)
• New model files (.pkl, .pt, etc.) are gitignored, not committed

---

Anything reviewers should focus on

Please verify that the dialog input fields now expose meaningful accessible names to screen readers and remain visually unchanged.

Screenshots (if UI changed)

No visual UI changes.

[github-actions]

🎉 Thank you @MamidiDhana for submitting a Pull Request!

We're excited to review your contribution.

Before Review

✅ Ensure all CI checks pass
✅ Complete the PR template
✅ Link the related issue

⚡ Want faster reviews and contributor support?

Join our Discord community:

🔗 https://discord.gg/FcXuyw2Rs

Maintainers and mentors are active there and can help resolve blockers quickly.

Happy Contributing! 🚀

[github-actions]

✅ PR template check passed!

@arpit2006 this PR is ready for your review. 🚀

[arpit2006]

LGTM!
✅ Approved

Accessibility labels are correctly wired — this is exactly what was needed.

What was verified:

All three htmlFor ↔ id associations are correctly matched:

• Label htmlFor=""repo-url"" → Input id=""repo-url"" ✅
• Label htmlFor=""repo-ref"" → Input id=""repo-ref"" ✅
• Label htmlFor=""org-url"" → Input id=""org-url"" ✅

The existing @radix-ui/react-label component (label.tsx) was reused correctly — no new dependencies introduced. The space-y-2 → space-y-4 spacing change in the URL dialog is sensible layout hygiene.

Bonus fix noted 👍

The incidental correction of the 'View' button navigation from "/" → "/dashboard" for non-completed scan jobs is a welcome improvement — routing users back to the dashboard instead of the landing page is the right behaviour.

Minor observation (non-blocking)

The label 'Organization Name' paired with a placeholder of https://github.com/your-org is a slight semantic mismatch, but this pre-exists the PR and is out of scope here.

No regressions. No new dependencies. UI visually unchanged. Screen reader experience meaningfully improved. Merging."

@ionfwsrijan , Ready to Merge!

[arpit2006]

@MamidiDhana , Resolve Merge Conflicts PR is ready to merge