Claimant Type (Veteran vs. non-Veteran)

[oddball-lindsay]

Issue Description

The Claimant Type page will be available to:

1. Veteran and Non-Veteran users
2. Authenticated users and unauthenticated users
3. 21-22 and 21-22a forms

Content is not dynamic.

The claimant type will be used to guide the user flow, but does not route to any fields in the 21-22/21-22a forms.

URL: /claimant-type

Previous path: /introduction Next path: /representative-select

MVP Planning Mural

Designs

Prototype, Canvas, Annotations

Screenshots

---

Tasks

• [ ] Create the Claimant Type page based on the designs above
• [ ] Set up the proper logic for displaying the page in the Appoint flow
• [ ] Set up routing to the proper form fields

Acceptance Criteria

• [ ] A Claimant Type page has been implemented, with the specs outlined above.

[cosu419]

Assigning to @mtri for review

[mtri]

• The "Tell us who you are" heading is missing
• Noting this page will not display the process bar since the number of steps changes depending on if you are the Veteran vs. if you are not the Veteran

Other than that, looks good!

[cosu419]

Thanks @mtri - wondering if you were drawing from any existing form apps as far as this screen goes? I ask because the default pattern seems to be that once the user passes the "Introduction" page, they have entered the tabbed form flow. So those pre-amble type screens (eg determining eligibility to fill out the form) typically happen before the Intro page.

If we do want to implement this as is, I suspect there are some workaround options available - just wanted to check whether it's been implemented somewhere before I explore further.

[oddball-lindsay]

@oddball-lindsay and @mtri will let Colin know if they find examples where there are questions after the intro page, but not yet part of a chapter.

[cosu419]

This is ready for review @mtri - note that the size discrepancy between the buttons is a bug in the shared component. Will ask someone from the design system team about that.

[mtri]

Looks good!