Open ChristineRoseSteiffer opened 2 months ago
@ChristineRoseSteiffer in office hours we discussed Laura doing a review of the language before testing--is your Figma file ready for her to take a look? If not let us know when it is!
Hi @strelichl ! I'm so sorry I missed your comment last week. The designs are ready for review from the CAIA team. They can review them here and please focus on:
Please let me know if there are any questions about this. I'm happy to jump on another office hours call tomorrow or another meeting later this week to go over any questions if we need to. Thank you so much for your help!
@laurwill ready when you have a chance!
@laurwill could you please provide any further comments by the end of tomorrow, Thursday Aug 22nd? We have testing starting next week so if at all possible we'd like to get those changes in before then. If you don't think that will work, please just let me know. Thank you for your help!
Audit Status: INITAL REVIEW
[!NOTE] @ChristineRoseSteiffer, I took a look at this from an accessibility POV and things are looking good! Just wanted to bring up something for whenever this gets developed.
It's important to manage focus between form screens so that screen reader users don't get lost. Often teams will put focus on the H3, so a screen reader user hears something like Continue, button.
[selects the continue button, goes to the next screen] The next question, heading level 3.
The SR user is kept in the question flow - they don't hear the stepper, page title, etc.
So if you want those users to hear your alerts, like this one:
Teams should know that they'll need to manage focus so that focus goes to the ALERT, not the H3.
Same with this one:
Let me know if that makes sense or if you have any questions :)
This updated has been noted below, and added to the a11y Task List in the body of this ticket.
10/9/2024 Ticket Opened
Our next pattern is about Updating Prefilled Information, so we were planning on trying to recruit AT users for that study. We will test our recommendations for Prefill as well as some variations related to updating that info. ...
cc: @coforma-jamie @NaomiPMC @strelichl
Updated Comment: 10/10/2024
[!NOTE] [Internal] CAIA Note
The new content inquiries stemming from today's accessibility meeting (10/16/2024), can be found in this ticket: #95070.
- [x] The ticket has been added to the
content task list
in this intake ticket.- [x] The
sitewide content
label has been applied.- [x] @strelichl I added you to the ticket and placed it in status:
Ready
for your review.
cc: @NaomiPMC
Hi CAIA team! Our newly formed AE Design Patterns team is working to improve the patterns in our VADS library with to goal of contributing a few of them for inclusion in the USWDS pattern library. Our first pattern is 'Prefill' which is to help Veterans know when their forms include prefilled data, where it comes from and how they can edit it to save time, reduce errors and complete forms more efficiently when applying for benefits and services.
We believe that this pattern will consist of a variety of components and content including, but not limited to:
*Note that the actual edit process for prefilled data will be covered by our next pattern.
We are putting together a research study that tests some of the variations to this component and how it is used throughout VA.gov (here are the design files for the prototype). Since the next pattern we will work on is so closely related, we are also testing some variations of the 'edit' workflow in this round as well. We would love your assistance as we finalize our designs and get them ready for testing. Some of the questions we have for your team include:
I'm sure you will also have lots of smart and interesting questions for us so I will leave it at that for now and we look forward to working together with y'all on this! Let me know what other information you need from us. Thanks for your help.