[Design] Review policy documentation from NJ team

[Samara-Strauss]

Background

In the 8.19.20 regroup with the NJ team, the NJ team handed off some policy documentation to Melissa that will affect the design of the basic information section and the rest of the app. This includes some of the following:

• People need to be able to submit the application on any page.
• We need to ask certain required information on the first page of the basic info section — Name, address, email, program the applicant is interested in.

Melissa needs to review this documentation and see if there are other relevant policy requirements that she needs to incorporate into the design.

Tasks

• Add that documentation to Github
• Link that documentation to this ticket
• Read/review the documentation
• Create a list of additional design requirements based on that documentation
• Add that list or requirements to this ticket

[melissajschaff]

After speaking with Jenn, we came to the conclusion/decision that what has been designed by USDS adheres to the policy documentation. We believe that the concern raised by the NJ team (more pages/clicks than current app) is acceptable and adheres to best practice for form design. While the questions that are asked in basic information are on multiple screens in the redesign, this is intentional and users prefer having information broken down, rather than on a single page. Additionally, the proposed design adheres to best practice for the mobile experience.

I am reviewing the documentation Brian, FNS, and existing application to ensure we are asking the right/required questions in these screens, in order to submit an application without filling out all the sections.

[melissajschaff]

Documentation

• OneApp SNAP compliance comparison (created by Brian)
• SNAP Online Applications Best Practices (aka FNS) (provided by NJ team)

[Samara-Strauss]

Review this in 9.2.20 design meeting

[leahbannon2]

Allyce has taken the lead on this and created additional issues to resolve remaining questions.