Closed kristenmcconnell closed 3 years ago
@mdewey I updated this story based upon our conversation this afternoon. It might be written more from my perspective and the tasks that I need to complete, but it should now include all of the use cases that we talked about. Let me know if I missed anything. Feel free to add them in this story, then copy to create a ticket for yourself.
Thanks @kristenmcconnell! I only added what exactly the audit of alert boxes will produce. I will copy this ticket for myself!
Review https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/engineering/error-flows/README.md when completing this task.
The three use cases that @mdewey found during his audit that need UX are:
WIP Selections from https://design.va.gov/patterns/messaging-dictionary were made to fulfill the below questionnaire error message states:
When we can't generate the PDF on the Questionnaire list, because the services are down.
When we can't generate the PDF on the confirmation page, because the services are down.
When the service goes down, but a Veteran is already working on the questionnaire, so what to put on the questionnaire pages.
Wireframe drafts (available in Zeplin at https://zpl.io/VOOek8j or https://scene.zeplin.io/project/5f3d86a458ea2231e60a4780). Still under review by Peggy.
When we can't generate the PDF on the Questionnaire list, because the services are down.
When we can't generate the PDF on the confirmation page, because the services are down.
When the service goes down, but a Veteran is already working on the questionnaire, so what to put on the questionnaire pages.
Regarding the white background, there is precedent for it. See the following Slack thread: https://dsva.slack.com/archives/C0NGDDXME/p1611176108064500. It would be a change to the base alert component. Platform asked to incorporate an updated alert style within our next usability test. This is possible from my end, but would need to be discussed with the rest of the team. Also, the timing on the test will need to be discussed, because we aren't testing immediately.
Met with accessibility specialist, Josh Kim. He recommended..."As for placement, I’d recommend placing the error directly above the button rather than below. If the error is placed below the button it is referring to, should a screen reader user read out the contents of the error and key tab, they will be taken to the following card’s button which can cause confusion since they share the same string."
Therefore, the following changes have been made.
After clarifying some of the use cases with engineering and getting feedback from content, the final proposed error messages can be viewed within the "Error Message" section of Zeplin. https://scene.zeplin.io/project/5f3d86a458ea2231e60a4780 or https://zpl.io/VOOek8j
User Story
Related Documentation
Description
An audit of error states within the questionnaire and suggestions on any edits that need to be made to said error states.
Use cases to review/think about:
Tasks
Acceptance Criteria