Open ayush-chak opened 7 months ago
Hello! I checking - hoping - to see if we can get Accessibility support for the screen reader users we have participating in the study. To date we have 3 screen readers scheduled (below) with a 4th yet to be scheduled.
Friday, April 19, 2024 at 11am EST - 12 Friday, April 26, 2024 at 12:30pm EST - 1:30 Wednesday, May 1 at 11am EST - 12
@coforma-terry
Hi @carafrissell1, I let our accessibility specialists know about this but a good next step would be to fill out the a11y research support request ticket: here.
Thank you @strelichl! Done
hi @carafrissell1, does the prototype already exist for testing? or are you asking for CAIA help drafting it?
Hey @carafrissell1 @ayush-chak , Wanted to check in on this travel pay work — looks like you all did some research that wrapped in early May. What are your next steps? I think this may involve a way to check status of travel pay claims, and we want to look at how those statuses align with statuses on other types of VA claims and forms. Thanks!
Hey @laurwill The experience is making it's way into dev and can be seen here after logging in with any test user (let me know if you need one).
A couple of items that could use your expertise...
The help content was vetted as part of the governance review but would love if you have any tweaks.
If you need to manage a claim, log into the BTSSS portal or call 855-574-7292 from 7 a.m. to 7 p.m. Monday through Friday. Have your claim number ready to share when you call.
Additionally, I'd appreciate your take on the upcoming feature of adding filters to the page.
The current filter design can be seen in this Mural.
User testing showed that users really only wanted to know about claims that they wanted to take action on (Denied, On hold, In manual review
). I'd like to allow those as filters but "Others" seems like it might be odd even with the help text.
Hey Micah! Looks like you're farther along in the designs that I realized, and I don't think anyone from CAIA has been involved with this new page yet (unless I missed that!). I have a bunch of questions about the statuses and how this page relates to BTSSS — let's find time for a sync to get me up to speed. I'll look for a time tomorrow or next week.
Documenting our Slack discussion here as well. The status page on dev is an MVP integration with the BTSSS API. We are in the beginning stages of discovery and research around status language. @carafrissell1 will start the connection with @laurwill over status language. I'll also lead the connection over filtering.
Tuesday 6/11 Content / IA Syncin meeting: @Laura Willwerth , @Sara Sterkenburg @Ayush Chakravarty and Cara Frissell
Notes/collab in Canvas
@sterkenburgsara feedback on 6/11 below. Also see in Slack here.
@Kevin Duensing things I'm seeing in staging that maybe you could look into? Missing pagination. Most teams load 10 items per page, and I'd suggest passing a parameter to load pages in the URL? There are duplicate "Feedback" buttons Need to add the back to top component H1 (page title) in staging is spanning all 12 grids, but we typically wrap content at 8/12 grids (75%) of the screen. Reason is scannability - it reduces cognitive load when we minimize characters per line. Update the page title tag to read "Check travel claim status | Veterans Affairs" Sort label that says "showing 1-150 of 150" needs to come after the sort button and before the list. Right now it is above the sort button / selection dropdown.
Research that informed the placement of this page: Status Visibility IA Study and Reimbursement Status Look and Feel Study
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
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?
Creating a prototype to conduct a look-and-feel study to validate finding from a tree study. If validated it will likely move on to engineering implementation.
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?
Tell us briefly about what you're working on now (such as initial discovery, wireframing, or usability research planning) and add any known dates for upcoming milestones or deadlines.
Honestly, all of things. We are still discovering what users want, as well as testing with what is available from the begining stages of the new BTSSS API. We are mostly in the later phase of discovery but still in the early phase of wireframing and research.
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:
[79471](https://github.com/department-of-veterans-affairs/va.gov-team/issues/79471)
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.
Mural board with userflow and mockups
CodePen prototype
Next steps
@Terry Nichols
. We’ll reply within 24 hours to acknowledge receipt. We'll then review the artifacts in more detail and work with you to determine timing for collaboration. Depending on the work, we may schedule a kickoff meeting to better understand how we'll partner together.Tasks