[CAIA A11y Research - PILOT] Disability Benefits: Contention Classification Team - New Conditions Page: Form: 21-526EZ (July 2024)

[sara-amanda]

Important

• TICKET STATUS: Recommended Spoke to Team in Kickoff` on 2/21/2024
• AUDIT: COMPLETED Audit of Prototype Prior to Research 76766 ✅
• PILOT DATE: COMPLETED 7/22/2024 - prior to the start of research "early" July 2024
• **PREP WORK (INTERNAL-CAIA) - Prep document for Sara and Jamie
• TYPES OF ASSISTIVE TECH: JAWS + WINDOWS (PILOT) ; Testing will use VoiceOver (majority); TalkBack and Screen Magnification (ZoomText).

CAIA A11y Support

This is a child ticket of the research ticket 76707 - created to track work, completed from this pilot session.

Tip

DEFINITION OF DONE: Refer to the task list in this ticket, for actionable items.

Two Variations to Test

"We can test variations of both options or consolidate to one if there's a strong opinion."

Variations

1. "Removing additional information"
2. "Adding additional information to component".

CAIA Assignee(s)

Toggle to view CAIA info

• Jamie (Pilot)
• Sara (Co-Pilot)

Team Info

Toggle to view team info

• Team name: Contention Classification
• OCTO product owner: Jen Bertsch
• Product name: 526EZ
• Product manager: Yurena Garcia
• Slack channel: benefits-contention-classification
• Dedicated content writer on your team (if you have one): N/A
• Dedicated a11y specialist on your team (if you have one): N/A

Description

Toggle to view the description

A CAIA a11y will participate as a user in a pilot of the Contention Classification New Conditions Page Form: 21-526EZ research study.

• Researcher: The VFS team researcher will test their prototype and conversation guide by conducting the pilot session with a CAIA A11Y.
• User: The CAIA A11Y team member will act as a real user in the pilot session.
• Assistive Tech: The CAIA A11Y team member will follow the prompts given by the VFS Researcher, while using and demonstrating how the behavior of a screen reader would behave.

Pilot Session

• Date: TBD - (Research starts "early" July 2024)
• Prototype in CodePen RCVD 3/22/2024
• Staging [Link for Pilot](URL: https://www.va.gov/disability/file-disability-claim-form-21-526ez/new-disabilities-revised/add) RCVD 7/19/2024
• Research conversation guide - RCVD 7/10/2024
• Research plan

Assistive Tech Options

Tip

DEVICE SUPPORT DURING RESEARCH SESSIONS

• Available AT: Screen readers on a desktop device is currently the primary source of AT that CAIA A11ys are able to support, in addition to screen magnification for user research sessions.
• Additional Specifications: If there is a particular test user, browser or operating system you would like us to use, please let us know in advance via this ticket's comments, tagging the assignee - or reach out to @coforma-terry in the CAIA Slack Channel: #sitewide-content-accessibility-ia

Definition of Done

A11y Tasks

Beta Give feedback

1. Schedule CAIA a11y (prior to the start of research in "early" July): (update assignees in ticket)
2. Determine date and time for pilot (prior to the start of research in "early" July): July 22
3. Update CAIA A11y Capacity Calendar: Add invite for pilot, when scheduled and flag who is covering it in the title
4. Review research conversation guide and provide feedback in comments.
5. Research plan rcvd 3/22/2024; see latest version on Google Docs
6. [a11y audit] Disability Benefits: Contention Classification Team - New Conditions Page: Form: 21-526EZ - Prior to User Research (CodePen Version) #76766
   5 of 5
   sitewide CAIA sitewide accessibility +2
   

   
7. Review prototype Prototype in CodePen rcvd 3/22/2024 audited 3/26/2024
8. Review live build (Second audit by Jamie)
9. Request AT device and tech to be used in sessions - Ref. Google Sheet - Scheduling Source of Truth
10. Receive AT device and tech from Team in research ticket to be used in sessions to prep for pilot = JAWS + Windows
11. Run pilot with VFS Researcher (prior to the start of research in "early" July 2024) - 7/22/2024
12. During Pilot Note that there are two variations**: "removing additional information" and "Adding additional information to component". "We can test variations of both options or consolidate to one if there's a strong opinion."
13. Note Taking: Pilot Prep and Notes - Jamie and Sara

[sara-amanda]

Timeline Shift

• April 2024 changed to May 2024

  • See comments in the main research ticket for additional info.

• This ticket title, high-level overview, body and tasks have been updated to reflect the change.

@coforma-terry @coforma-jamie

[sara-amanda]

Removed

• Team is aware of multiple studies:
  • ⚠️ Multiple Studies
  • 👍 Team confirmed awareness of multiple studies 3/22/2024

[sara-amanda]

Timeline Shift

• May 2024 changed to June/July 2024
• See comments in the main research ticket for additional info.
• This ticket title, high-level overview, body and tasks have been updated to reflect the change.

@coforma-terry @coforma-jamie

[coforma-jamie]

Timeline Shift

Jamie heard from the team 6/17/2024: "Timing on research with AT users is TBD, but the earliest this could begin (starting with the pilot) is early July."

Previously May, June/July adjusting to early July 2024

• This ticket title will be updated to reflect the change.
• GHP fields in this ticket will be updated to reflect the change.
• High-level overview in this ticket will be updated to reflect the change.
• This ticket's body and tasks will be updated to reflect the change.
• Research tracker will be updated to reflect the change.
• Primary ticket title and any reference to dates to be updated as well [CAIA A11y Research]: Disability Benefits: Contention Classification Team - New Conditions Page: Form: 21-526EZ (EOM July-Aug 2024) #76707
• CAIA Capacity Calendar Updates

cc: @NaomiPMC @sara-amanda @coforma-jamie

[sudeeptibh]

update - we will kick off recruiting next week with the goal of a 2-week recruitment period and to do the usability research week of July 22.

[sara-amanda]

CAIA Support

Note

• Thank you for the update! @sudeeptibh
• @sudeeptibh If you can reply in the main ticket I cross-posted this comment there, since it covers more than the pilot.
  

Pilot

• This ticket is for a pilot session.
  • Are you still wanting to try for a pilot session with AT, prior to your research starting on 7/22, since we did the two audits for you? (See below section on Previous Audits Completed)
  • I am only mentioning this because the week of the 15th we do have limited capacity and two other research sessions going at that time.

Previous Audits Completed

• Previously, @coforma-jamie completed an audit of the prototype in CodePen ticket 76766.
• Additionally, @coforma-jamie completed an audit of the prototype in Staging ticket 83767
• Confirming: Is this the URL that will be used in the testing sessions?
  • URL: https://staging.va.gov/disability/file-disability-claim-form-21-526ez/new-disabilities-revised/add
    User: Any user who can file a disability claim can get to this page for adding new disabilities. Allan Butler, Karl Howard, or Johnnie L. Weaver have worked fine for us.

Number of Sessions

• Confirming: How many sessions are you looking to have covered?
  • It looks like you will be needing support for two sessions, based on the research plan?
  • I have updated our research outlook tracking with the two sessions for now.
  • Just let us know when you have the dates/times and AT information available from Perigean.

At least 2 but no more than 3 Veterans who use assistive technology (AT) such as screen readers (AT/reader) or magnifiers (AT/magnifier)

Capacity Update

We are currently experiencing limited capacity; however, your testing the week of 7/22, does not appear to have any conflict at this time for any current scheduled testing or PTO.

cc: @coforma-jamie @EvanAtCoforma @SarahKay8 @NaomiPMC @artsymartha68

[coforma-jamie]

Spoke with team - I'll be piloting using Windows + JAWS.

URL: https://www.va.gov/disability/file-disability-claim-form-21-526ez/new-disabilities-revised/add

[sara-amanda]

Pilot Session Takeaways

Google Doc: Navigate to the Pilot Takeaways Section

• Logging in and getting to the URL may be a challenge.
• Inform the user that they may need to wait, while the page loads re: “We are checking to see if you have an intent to file, and that could take a couple of minutes.” That should read aloud to a screen reader user, so they know it is loading and why.
  • ^Not their page, but they can share that with the team responsible.
• We recommend allowing the user to explore the page first.
• Error Messages: Tricky, when you get the error message and you try to remove it and the error message comes up when you try to add another condition. Content: In general the content will confuse users “Enter a condition” “enter your condition” it doesn’t come off as an error message as you are just hearing it.
• Verbose: Tendonitis (tendinitis) in xxx (addressing spelling errors)
• Bypassing with Free Text: As you type you get the pop-up menu and it will announce that there are three items in the pop-up menu. Now, if I am typing something and I know what it is and maybe it is just easier for me to type it and not go into the popup menu at all I can type the whole word, hit tab and it takes me to the save button and you can bypass the pop-up menu when typing in free text. Wondering if some users, this one wasn’t in the list, why not just save it? Free text isn’t being validated? Automation if they choose from the list.
• Alert - one question on a page, it is easy for someone to get down there, on something like this no one is going to get to the alert. Exception? Move the alert under add a condition or above back and continue, you won’t come across it otherwise.

[sara-amanda]

Thanks for including, CAIA A11Ys in your research pilot! We appreciate this opportunity to work with your team, to help make your product as accessible as possible. 😄

• Shared feedback
• Completed session
• Closing out ticket

cc: @NaomiPMC @coforma-jamie