Onboarding UI is accessible to users with disabilities

Inaccessible signup and onboarding flows violate WCAG 2.2 SC 1.3.1 (Info and Relationships), 2.1.1 (Keyboard), 2.4.3 (Focus Order), 2.4.11 (Focus Not Obscured), and Section 508 §502.3 — and expose the company to ADA Title III litigation risk in the US. Form fields without labels are unusable with a screen reader; missing role="alert" means error messages are invisible to assistive technology. These aren't cosmetic gaps: they legally and functionally exclude users with disabilities from your product at the first interaction.

In src/app/(auth)/signup/page.tsx, associate every input with a visible label and link errors via aria-describedby:

<div>
  <Label htmlFor="email">Email</Label>
  <Input
    id="email"
    type="email"
    aria-describedby={emailError ? "email-error" : undefined}
  />
  {emailError && (
    <p id="email-error" role="alert" className="text-destructive text-sm">
      {emailError}
    </p>
  )}
</div>

Audit every outline: none in your global CSS — either remove it or add a visible :focus-visible replacement. For modal dialogs, use a focus trap library (focus-trap-react) so keyboard users can't tab outside the dialog.