VA Forms System Core will be a React library hosted in NPM that will allow engineers and designers to easily interact with Forms inside of vets-website.
Align labeling and other design elements on the burial demo form with the final versions of the UXPin prototypes that Kristen is developing via work on ticket #172 and will be updating via work on ticket #583.
This includes:
Remove the heading that appears on all pages directly below "Page X of X: XYZ". They are unneeded, given that the "Page X of X..." tells the user the page topic. The exception is for the Military Service History page, which should have a Service History sub-header. The user could enter multiple service periods, and the sub-header helps to clarify that.
Change the current Save and Continue title case button label to Save and continue (sentence case). (Kristen's note: in the staging site I see this button as "Back to Review page". I think we intended to change it to "Save and continue".) (Karen's note: This is correct, we do want to change this button label).
Do a sweep of the demo form to ensure that all page headings use sentence case.
On the Review page (some of this is duplicated in #589):
Change title/header to "Review Application". (There should only be 1 title/header; currently there are 3.)
Add anchor links and link them to the appropriate section below. (This appears to be complete.)
There are two "Deceased Veteran Information" sections, referencing the military history and previous military names. We decided to give these sections unique headings, which match the headings in the steps of the form. See the correct section names (per several team discussions) in the UXPin prototype.
At one point the "Plot or interment allowance" section was appearing after the "Claimant contact information" section. The "Plot or interment allowance" section should appear directly after the "Burial allowance" section (if the user has selected this benefit), as it does in the UXPin prototype.
The privacy policy checkbox should only have the checkbox and its associated description text; please remove the line of text above it.
"Blue box" messages (e.g., Your "x" has been updated text on the Review Page): Match to the styling used for Background alert or Background alert with icon, as applicable.
Also note that when one field in a section is updated or added, use the text "[Field name] has been updated [or added]." If more than one field in a section has been updated, change the text to "[Section name] has been updated [or added]." (Ensure this behavior is logged in the appropriate place.)
Fix some things that we have noticed are broken on step step 6, Benefits Selection:
When you check the "Transportation allowance" checkbox, a field to enter the amount should appear, but does not.
It seems that the first click over a checkbox puts the checkbox in focus and the second click selects the checkbox. I would expect the first click to select it, not just put it in focus.
Finally, the selected checkboxes do not save when you click Back and then return to this page (or Continue to the next page and then go Back to this page). However, the value is saved on the Review page.
Additional notes:
We will not implement the logic for the edit previous name and add plot or interment scenarios at this time. This will take more time than we will have available. This will be addressed on Ticket #589.
We will not add the purple "hints" (see page 9.0 for an example) that guide the user in the UXPin prototype into the demo.
If you notice any bugs or inconsistencies in the UXPin prototype, please tag Kristen.
Acceptance Criteria
[ ] Labeling and other design elements on the burial demo form are aligned with the final versions of the UXPin prototypes that Kristen is developing via work on ticket #172 and will be updating via work on ticket #583.
Task Description
Additional notes:
Acceptance Criteria