New Confirmation Page: Successful submit flow (with claim id, less than 30 seconds) - part 2

[christinec-fftc]

Issue Description

Part 2 of scenario where submit_all_claimreturns 200 success and submission_status also returns 200 with a claim id.

mocks: https://www.figma.com/design/qyTtKDOTHZPGU59PAfqVhq/(526ez)-New-Confirmation-Page-and-Email-Touchpoints?node-id=8405-81028

1. Move print button outside of blue card, add new content, styling to match designs

2. Modify remaining p (paragraph) content. This includes all the rest of the copy after the blue card. There's 4 sections here. (small sample screenshot here, refer to figma for full content)

Front end tasks

• Ensure the page is styled according to design spec.
• Ensure the back end data from API is displayed in local and review instance
• Ensure unit tests are available.
• Ensure your code changes are covered by E2E tests
• Run axe checks using the Chrome or Firefox browser plugin
• Test for color contrast and color blindness issues
• Zoom layouts to 400% at 1280px width
• Test with 1 or 2 screen readers
• Navigate using the keyboard only

Acceptance Criteria

• [ ] Verify styling and content for claim info and printing
• [ ] Verify content on the rest of the page matches figma, all links are functional
• [ ] Verify claim id is still displayed on blue card (any further edits to the blue card are in a subsequent story)
• [ ] Designer comments on this issue to approve page styling
• [ ] Unit tests pass
• [ ] E2E tests cover current code and regression
• [ ] End-to-end tests show 0 violations.
• [ ] The data returned matches API response (for given user or scenario)
• [ ] All axe checks pass
• [ ] All color contrast checks pass
• [ ] All zoom testing passes
• [ ] All keyboard checks pass
• [ ] All screenreader checks pass

Appendix

Ensure your code changes are covered by E2E tests (expand)

- Add E2E tests if none exist for this addition/change. - Update existing E2E tests if this code will change functionality. - Include axe checks, including hidden content

Run axe checks using the Chrome or Firefox browser plugin (expand)

- Ensure no heading levels are skipped. - Ensure all buttons and labeled inputs use semantic HTML elements. - Ensure all buttons, labeled elements and images are identified using HTML semantic markers or ARIA roles. - Ensure form fields have clearly defined boundaries or outlines. - Ensure form fields do not use placeholder text. - Ensure form fields have highly visible and specific error states.

Test for color contrast and color blindness issues (expand)

- All text has appropriate contrast.

Zoom layouts to 400% at 1280px width (expand)

- Ensure readability and usability are supported when zoomed up to 400% at 1280px browser width - Ensure no content gets focused offscreen or is hidden from view.

Test with 1 or 2 screen readers (expand)

- Ensure the page includes a skip navigation link. - Ensure all links are properly descriptive. - Ensure screen reader users can hear the text equivalent for each image conveying information. - Ensure screen reader users can hear the text equivalent for each image button. - Ensure screen reader users can hear labels and instructions for inputs. - Ensure purely decorative images are not announced by the screenreader.

Navigate using the keyboard only (expand)

- Ensure all links (navigation, text and/or image), form controls and page functions can be reached with the tab key in a logical order. - Ensure all links (navigation, text and/or image), form controls and page functions can be triggered with the spacebar, enter key, or arrow keys. - Ensure all interactive elements can be reached with the tab key in a logical order - Ensure all interactive elements can be triggered with the spacebar, enter key, or arrow keys. - Ensure focus is always visible and appears in logical order. - Ensure each interactive element has visible focus state which appears in logical order.

---

How to configure this issue

• [ ] Attached to a Milestone (when will this be completed?)
• [ ] Attached to an Epic (what body of work is this a part of?)
• [ ] Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
• [ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
• [ ] Labeled with Type (bug, request, discovery, documentation, etc.)

[mayacarrolluxa6]

@christinec-fftc The Confirmation page design has been updated to align with the VFF template. You can find the latest designs on the page in the Figma file underlined in red.

A few notes from the our meeting with @pacerwow and @StevenStraily:

• @pacerwow has confirmed that building the new confirmation page can be pulled out of Sprint 10 and into Sprint 9.
• We have confirmed with the VFF team that the date in the "Form submission started on date" should be the date the user clicked submit on the form connected to the confirmation page.
• Claim ID will not be on the confirmation page on a successful backup path.
• The blue box's title "Disability Compensation Claim (Form 21-526EZ)" will be adjusted to align with the plain language guidance that CAIA published today, please coordinate directly wtih @StevenStraily on this copy update.

Mockup of Confirmation Page Design - Happy Path below 👇