department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
278 stars 194 forks source link

[CAIA intake]Form Upload #81623

Open tbaker1026 opened 2 months ago

tbaker1026 commented 2 months ago

Content, accessibility, information architecture (CAIA) new initiative collaboration request

Use this ticket to start collaboration on a new initiative with the sitewide content, accessibility, and information architecture (CAIA) team.

Note: If you’re already partnering with us on an initiative, you don't need to fill out this request form. If you don’t have access to your initiative’s CAIA epic, post a message in the #sitewide-content-accessibility-ia slack channel and tag @Terry Nichols and @Lily Strelich.

About your team

About your initiative

There is a current tool called QuickSubmit that we were going to point users to so they can upload a handwritten PDF but there are accessibility issues with it. This is a tool that allows a user to upload a PDF from the Find a Form about page. There will be three different treatments to the About Page.

Which of these descriptions best fits the work we’ll partner on?

Select all that apply.

What's the nature of your initiative and desired outcomes?

Review Source of truth for content changes

Tell us briefly about your work and the outcomes you’re aiming to achieve.

Collaboration timeframe

Note: We work on nearly every OCTO product and manage all unauthenticated content on VA.gov, so we will need to prioritize intake requests based on overall workload and VA and OCTO priorities.

Is this work tied to a Congressional mandate, change in law or policy, or upcoming event with a specific deadline?

Where are you at in your timeline?

Wireframes & research

Enter your description here

Collaboration cycle

Which phases of the collaboration cycle have you completed?

Select all that apply.

Collaboration cycle ticket

If you’re going through the collaboration cycle, provide your ticket number and link:

Supporting artifacts

Provide links to any supporting artifacts that can help us better understand your initiative and begin collaboration. Include artifacts like your product outline, user flows, mockups and prototypes, or any draft content.

Source of Truth Figma Files

Next steps

Tasks


### VFS team tasks
- [ ] **If you also need engineering support from the public websites team**, fill out their intake request form as well.<br> [Open a public websites intake request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=Public+Websites%2C+Sitewide+content&labels=vsa-public-websites%2C+vsa%2C+vsa-public-websites-intake%2C+sitewide-content%2C+needs-grooming&template=public-websites-intake.md&title=%3CType+of+Request%3E+from+%3CTeam%3E)
- [ ] **If you're requesting a page/URL redirect, a URL change, or a vanity URL**, submit an additional request for this work. <br> [Open a redirect, URL change, or vanity URL request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=jennymayoco%2C+kristinoletmuskat%2C+strelichl%2C+FranECross&labels=sitewide+CAIA%2C+Sitewide+IA%2C+Public+Websites%2C+VA.gov+frontend%2C+Redirect+request&projects=&template=redirect-request.md&title=Redirect+Request)
- [ ] **If you're creating an experimental design**, also contact the design system team. <br> [Read more about experimental designs](https://design.va.gov/about/contributing-to-the-design-system/experimental-components-and-patterns#what-is-an-experimental-component-or-pattern?) <br> [Suggest an addition or update to the design system team](https://design.va.gov/about/contributing-to-the-design-system/suggest-an-addition-or-update)
- [ ] **If you're requesting a11y support for usability research**, submit a research support request next. <br> [Open an a11y research support request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=coforma-terry%2Cangelafowler82&labels=508%2FAccessibility%2C+sitewide+CAIA%2C+sitewide+accessibility%2C+CAIA-a11y-research&template=caia-a11y-research.yaml&title=%5BCAIA+A11y+Research%5D%3A+Team+name%2C+product+name)
- [ ] **If you are requesting content support**, please share your content source of truth (preferably as a SharePoint document).
### CAIA operations
- [x] Initial Review - @coforma-terry and @strelichl
### CAIA a11y tasks
- [ ] Staging Artifact Support `TBD`
- [ ] Research with AT? Is Jeana supporting that and assisting in the design?
- [ ] https://github.com/department-of-veterans-affairs/va.gov-team/issues/85573
- [ ] https://github.com/department-of-veterans-affairs/va.gov-team/issues/85447
### CAIA content tasks
- [ ] https://github.com/department-of-veterans-affairs/va.gov-team/issues/85538
### CAIA IA tasks
- [ ] IA support for form upload feature
tbaker1026 commented 1 month ago

Potential problem: The 'find a form' tool is not the only entry point into these PDF forms. Many forms also have drupal-managed pages on va.gov that tell a user to 1) download a PDF from 'find a form' and 2) upload the PDF into the legacy QuickSubmit tool (see example screenshot below). But, we don't want to send any users to the legacy QuickSubmit tool because it's not accessible. So Matt identified 4 diff types of pages that will need content updates to route users to the correct tool (this new uploader thing within find-a-form).

Screenshot 2024-05-13 at 2 34 38 PM

A. Can point to a specific form or forms These we can handle the English version by pointing users to the About form page or pages (and we can work on getting Español versions) VA Survivors Pension (ESP version) About VA DIC for spouses, dependents, and parents (ESP version) Veterans headstones, markers, and medallions How to apply for a VA pension as a Veteran Burial in a private cemetery

B. Do not point to a specific form, or are unclear about which form or forms they might be pointed to These we cannot handle, at least not right now. We're not yet able to handle ANY VA form ala QuickSubmit. We can handle specific VBA Compensation and Pension forms that can be submitted via the Benefits Intake API. When Premal's IVC Forms team gets VHA forms working through Pega then we MAY be able to handle SOME VHA forms through that mechanism. We cannot (and probably should not attempt to) handle rando document that may or may not be a VA generated PDF. I would recommend that we STOP pointing users at QuickSubmit from these pages. The QuickSubmit UI does not meet our accessibility standards. If there are specific forms we can point to then we could shift traffic towards the new tool once it has shipped. Upload evidence to support your disability claim How to change your legal name on file with VA How to apply for the GI Bill and related benefits (ESP version)

C. Point to QuickSubmit but have, or will soon have, a superior online experience When a user can apply online I would not recommend pointing toward PDF upload (neither QuickSubmit nor this new tool) as it provides a sub-par experience. Presidential Memorial Certificates Get help from a VA accredited representative or VSO

D. Points to a specific form but requires additional documentation that is not part of the PDF form. We cannot handle these, at the moment. We'll do an audit to see how many forms have this requirement (we were aware of this category but I didn't realize this form was one of them) Get paid back for test fees

laurwill commented 1 month ago

Hi @tbaker1026 @jeana-adhoc @rachelshearerux , Thanks for talking about this work with me and @megzehn this week! Noting here some questions from that chat and a couple more I had while reviewing this intake.

How will the find-a-form uploader relate to & communicate with the claim status tool?

How will we confirm receipt or communicate status of these uploaded PDFs?

How will this project categorize PDF forms with optional or conditional supporting documents?

Happy to sync again if it's easier to discuss on a call!

rachelshearerux commented 1 month ago

@laurwill, @tbaker1026 and I met to talk through these questions.

I've compiled our Q&As in the GH folder for this project here.

laurwill commented 3 weeks ago

Hi @rachelshearerux , I left comments in the Figma file with a few questions and suggested content edits. I'm not sure if we did IA work on this yet, so I'll check in on that on Monday.

My biggest remaining question is about tracking the form post-submission. The designs currently list SSN, file number, and zip code as info we'll "include" with the form so that they can track it. Is this the info we pull from their profile to tie the form to the correct person? How can they track the form exactly — do they need to call a number to ask about the status?