[CAIA A11y Research]: Authenticated Experience, Authenticated Menu (January 2024)

[andaleliz]

Project Overview

Note

High-Level Overview: Authenticated Experience

• Timeframe: Jan 29-Feb 1, 2024
• Pilot: 11:30 a.m. ET on Jan. 26, 2024 #74259
• Assistive Tech Users: 3 or 4 Users based on Research Plan
• Assistive Technology: Screen Readers JAWS VO Fusion
• Task Lists: See task lists for next steps/definition of done for the Auth. Exp. Team and CAIA A11ys

Assignee(s)

• @coforma-jamie Research Session Support
• @eli-oat Pilot Support

A11y Availability

Toggle to reveal a11y availability information

Thank you for reaching out to CAIA! We are looking forward to supporting your study. We wanted to let your team know that there are multiple studies taking place during the same timeframe as your study.

We will do our very best to work with you and @artsymartha68, to support your research sessions, based on a11y availability. Should you have any questions, issues, or concerns please do not hesitate to contact @coforma-terry (CAIA A11Ys) and/or @artsymartha68 (OCTO) as soon as possible.

We have blocked out your time slots on our CAIA A11y Capacity Calendar and see that you are flexible, based on your notes in the Research Plan, thank you!

Team Info

• Team name: Authenticated Experience
• OCTO-DE product owner: Samara Strauss
• Product manager: Travis Chaill
• Designer: Liz Lantz
• FE engineer: Adam Whitlock
• Product/team Slack channel: #accountexp-authexp

Toggle to reveal additional team information

Do you have an accessibility champion?

No, we don't have a champion (yet)

If you have an accessibility champion, what's their name?

Liz Lantz

Is anyone on your team interested in becoming an accessibility champion?

No response

Calendar checking

• Based on this calendar, confirm we have specialists who can support your study in your desired timeframe
• Confirm you are filing this support ticket at least 1 week in advance of said timeframe, so we have enough heads up to provide support

Have you reviewed the CAIA capacity calendar?

• Yes, we have reviewed the CAIA capacity calendar and can confirm specialists are available to support in our research timeframe

When is the timeframe for your testing?

Jan 29-Feb 1

Research sessions

Toggle to reveal additional research session information

• Planned dates of research:
  • Start: Jan 29, 2024
  • End: Feb 1, 2024 Goal: Complete by Jan. 31, 2024, if possible
  • Reschedules: Feb. 1, 2024
  • Pilot:1/26 at 11:30 a.m. ET invite sent on 1/24/2024 @eli-oat @andaleliz

Length of sessions

• Session length: 30 minutes for non-screen reader participants, 45 minutes for screen reader participants
• Buffer time between sessions: 45 minutes
• Maximum Sessions per day: 4

Testing Schedule

Toggle to reveal additional testing schedule and device information

Availability

Date	Time Slots (Eastern)	Screenreader Session Holds
Jan 29	WINDOWS:10am-5:30pm, and 7:30pm-9pm	Screenreaders between 10am-12pm or 1-2:15pm
Jan 30	WINDOWS: 7-7:45am, 10am-5pm	Screenreaders between 10am-12pm or 1-2:15pm
Jan 31	WINDOWS: 10am-5:30pm	Screenreaders between 10am-12pm or 1-2:15pm
Feb 1	WINDOWS: 8:30am-4:00pm	Screenreaders between 8:30am-12pm or 1-2:15pm

LL Notes: These are ideal times when a specialist is available. OK to schedule outside of these times if absolutely needed.

Device & AT Combinations

CAIA A11Ys will be looking for information along the lines of the following. We realize that some of this information will not be available until the day of the session.

Participant Number	CAIA A11Y	Date of Research (Eastern)	Assistive Tech	Skill Level	Operating System	Browser	Device Type
_P#4	@coforma-jamie	1/29/2024 from 2:45 to 3:45 p.m.	Jaws	Advanced	Windows PC	Unsure which browser they will use	Laptop or Desktop
_P#8	@coforma-jamie	1/30/2024 from 2:45 to 3:45 p.m.	VoiceOver	Advanced	Apple	VoiceOver	Mobile
_P#12	no CAIA a11y attending @andaleliz	1/31/2024 from 2:45 to 3:45 p.m.	Fusion	Intermediate	Unsure	Unsure	Mobile

• Consideration: You can also consider asking participants more specific AT and device combinations.
• For instance: TalkBack on Samsung Galaxy 8, or VoiceOver on iPad with magnification.

Pilot Session

Date	Time (Eastern)	Pilot Session	CAIA A11Y(s) Available
Jan 26	11:30 a.m.	Pilot Session with CAIA Ticket: #74259	@eli-oat Evan Observing

Session Note Taking in Mural

LL 1/24/2024 Slightly new approach in Mural for note taking. Here’s the section setup for the pilot, loosely organized by the tasks in the conversation guide.

A couple of notes:

• When you’re typing in a sticky in Mural, if you press tab it’ll automagically create a new sticky right next to the one you were just in, using the same color. I think this makes it faster to keep up with the speed of convo if necessary, so I didn’t set up a ton of blank stickies this time.
• If there are general observations or something that comes up that isn’t totally related to the task, it’s helpful to me if you leave the sticky in that section rather than try to separate it and organize it elsewhere.

Supporting artifacts

Toggle to reveal supporting artifacts

• [Product outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/header-
  • QUESTION: Product Outline: Link cut off Should the link be this?
  • ANSWER: This is the link to the federal standardized header/footer product outline. I'm not sure where it was cut off but I'm happy to update it :)
• Prototype or mockups: not ready yet, will be added to research plan and convo guide when ready. We are forking the prototype for the standardized header and footer, which your team has already reviewed.
  • Prototype in Research Plan as of 1/22/2024Confirmed
• Research plan
• Research conversation guide
• Epics/issue that may be helpful

Note: this is supporting the standardized header/footer work. Here is their epic if that's helpful.

Next steps

Authenticated Experience Team - Next Steps

Preview Give feedback

1. Post a link to this ticket in the accessibility-help Slack channel and tag Terry Nichols.
2. Your team's researchers and observers read through platform guidance on research with assistive technology users
3. LINK TO PROTOTYPE: Prototypes will be tested in the following environment:CODEPEN with CAIA A11y(s). Is this the prototype @andaleliz ? CONFIRMATION REQUESTED
4. QQ RE: Product Outline: See question in supporting artifacts, regarding the product outline link.
5. PILOT: Schedule a pilot with CAIA A11ys, if time allows. Possibly 1/25 or 1/26/2024 - scheduled for 1/26 at 11:30 a.m. ET with Eli
6. INVITE CAIA A11YS: CAIA Specialists will need to be assigned to your research, be sure to add the respective a11y specialist(s) to your session invites (include the Zoom or Teams link). Be sure to invite the CAIA A11y Capacity Calendar - if possible. Generic Holds Placed Currently
7. AT PARTICIPANT COUNT AND DETAILS: See table in the body of this ticket (above in the Device & AT Combinations section). Provide specialists your participant details like skill level, operating system, assistive tech used, browser Prior to Sessions - If Possible Partial Info Prior to Sessions Helps

CAIA A11Y - Next Steps

Preview Give feedback

1. REVIEW PROTOTYPE: Prototype is now available to be tested in the following environment:CODEPEN
2. REVIEW ARTIFACTS: CAIA Specialists review your conversation guide and research plan.
3. CALENDAR HOLDS - RESEARCH WINDOW Put initial calendar holds on CAIA A11y Capacity Calendar GENERIC HOLDS CURRENTLY OFFICIAL INVITES CURRENTLY
4. PILOT SCHEDULING Participate in a pilot session with the Auth. Exp. team for 1/24/2024 (date in Research Plan) if time allows. If taking place, please create a pilot ticket (a11y can ref. prev. historical pilot tickets - DONE [CAIA A11y Research - PILOT]: Authenticated Experience, Authenticated Menu - PILOT SESSION (January 2024) #74259). 1/25 or 1/26 inquiry sent to a11ys on 1/23 - TBD based on availability. SCHEDULED 1/26 at 11:30 a.m. ET with Eli
5. [CAIA A11y Research - PILOT]: Authenticated Experience, Authenticated Menu - PILOT SESSION (January 2024) #74259
   9 of 9
   CAIA-a11y-research sitewide CAIA sitewide accessibility +3
   

   
6. PILOT Notes [c/o Evan via GitHub](https://github.com/department-of-veterans-affairs/va.gov-team/blob/0c6c5ce66b56528813218b24f806a5d294d4916f/teams/CAIA/accessibility/Deliverables/Authenticated Experience/2024 01 26 Authenticated Experience - Authenticated Menu - Pilot Research Session.md) shared via comments 1/26/2024 in this ticket and via the Pilot Ticket (noted in this task list).
7. CALENDAR HOLDS - OFFICIAL INVITES Put official calendar holds on CAIA A11y Capacity Calendar PENDING INVITES FROM TEAM/PERIGEAN
8. PARTICIPATION: Participate in User Research Sessions: 'START1/29/2024 END 2/1/2024 - 1 of 3 sessions
9. A11Y FEEDBACK: CAIA Specialists to use the following: research notes prepared for the session
10. NOTE TAKING: New Mural from Liz, see note taking section of this ticket. (Also linked in pilot ticket)
11. POST-RESEARCH: CAIA Post research, specialists will add accessibility findings to a comment

[andaleliz]

Hi @sara-amanda just want to follow up with you on this since our study starts next week. Do you have any questions? Shall I just have you added to the SR sessions as they're scheduled? Thanks!

[sara-amanda]

Hi @sara-amanda just want to follow up with you on this since our study starts next week. Do you have any questions? Shall I just have you added to the SR sessions as they're scheduled? Thanks!

Hi, @andaleliz ! Yes, that works! I can see who might be available for your session, and also add that specific session to our CAIA A11y Capacity Calendar. Thank you! I went ahead and updated the ticket, and added a task list "next steps" for your team and for CAIA A11ys. 😄

[sara-amanda]

Research Ticket Updates

• Moving ticket to: In Progress
• Title: Adding Testing Timeframe to Title
• Pilot Session: TBD - if time allows
• Additional Ticket Updates: Updated ticket body to reflect schedule window and dates, information needed for a11ys prior to or during sessions, current status, pending invites, and additional next steps. Plus, generated task lists for the Auth.Exp. Team and CAIA A11Ys.
• Multiple studies note added.

cc: @coforma-terry

[andaleliz]

Thank you @sara-amanda! I love how organized your team is, this is so easy to work through ❤️

• I updated the ticket above with a link to the product outline, and confirmed that yes, that is the correct CodePen link to our prototype
• I'd love to schedule an a11y pilot with your team if possible. It looks like there is availability Thursday or Friday during the same windows I noted in our availability table. Can I just send an invite to you (or another specialist) during one of those open times?
• I based the screenreader session times based on the availability I saw on the CAIA calendar. If I didn't interpret it correctly, please let me know. I'd be glad to do an SR session any time during the available windows, but plan on doing them on my own if needed.

[sara-amanda]

Thank you @andaleliz for your flexibility! 😄 I am reaching out to the team to see if we can get a pilot set up for 1/25 or 1/26 and will keep you posted.

[andaleliz]

@sara-amanda 3 of the SR sessions have been scheduled. Who should I add to the invites? I saw your note about adding the CAIA capacity calendar but I'm not quite sure how to do that. Thanks!

[sara-amanda]

Thank you, @andaleliz !

I will add them, now to that calendar and see if we are available for you.

Speaking of availability, are you available to do the pilot in either of these windows?

• Friday between 11:30 and 1 eastern (first choice, preferred window)
• Thursday between 1:30 and 3:30 (second choice, if first choice window doesn't work)

[andaleliz]

@sara-amanda yep, I can do Friday! I'd love to start at 11:30 if possible.

[sara-amanda]

3 of the SR sessions have been scheduled - @andaleliz

I see one invite so far from Perigean c/o Matt.

• January 29⋅10:15 – 11:00am not a screen reader
• January 29 - 2:45-3:45 p.m.
• January 30 - 2:45-3:45 p.m.
• January 31 - 2:45-3:45 p.m.

I will take a look at our capacity during these times when the other two are added. Thanks!

[andaleliz]

@sara-amanda that first session isn't a screenreader session. I'll forward them all to you, via the email in your Slack profile. Coming at ya!

[sara-amanda]

@andaleliz Perfect! Thank you! I will remove that first one. Thanks, again!

[sara-amanda]

@andaleliz do you happen to know the type of AT (i.e. VoiceOver) your users will be needing support with in the studies?

[andaleliz]

@sara-amanda I don't have the roster yet, so not specifically. I may have it by tomorrow though.

I requested that 2 be on a mobile device, so I'd prefer to test on mobile with VoiceOver or TalkBalk for the pilot if possible. I'm really curious how the auth menu works on mobile for SR users.

Thanks for checking!

[sara-amanda]

Mobile Testing Limitations

... I'd prefer to test on mobile with VoiceOver or TalkBalk for the pilot if possible. I'm really curious how the auth menu works on mobile for SR users.

Hi, @andaleliz ! We would love to test that for you, but unfortunately, we are currently only equipped to test on desktop devices. However, @artsymartha68 is looking into this for us, with our contractor officers at VA, to see if CAIA A11Y folks can use their personal mobile devices for pilot testing.

@eli-oat will be reaching out shortly to you about the pilot session, tomorrow.

cc: @coforma-terry

[EvanAtCoforma]

Hello @andaleliz , here's the link to the pilot deliverable notes. Please let me know if you have any issues!

cc: @sara-amanda , @eli-oat

[coforma-jamie]

Findings

There's a lack of understanding about "My VA"

• P4 didn’t understand the difference between “profile” and “My VA”, suggested combining them. “My VA…is My VA and Profile the same thing?”
• P8 didn’t understand what My VA was without explanation, but found it valuable after hearing the meaning explained. “No, had I known that [it was a dashboard], I’d rank it higher. I’d put it first. Above profile.”
• Hypothesis: "Profile" had meaning to participants, but "My VA" didn't. It may be worth researching the name recognition of "My VA" - if users generally don't understand what that term means, perhaps it should be renamed, or advertised. Or perhaps in the future, "My VA" and "Profile" are combined into one thing.

The accessible name ([user], menu, popup) wasn't understood; users expected to be taken to a profile, not a menu

• P4: “Just saying ‘Derek’ doesn’t mean anything. ‘Derek’ what? Tell me before I land on this what I should expect." He suggested "Derek's VA account."
• P8: Expected to hear “Your information” or “Your profile” or similar. “I thought when it said ‘Calvin, popup,’ it would’ve had my information pop-up that I would’ve been able to review and edit.”
• Recommendation: Use a different accessible name, either by changing the visible text or adding an aria-label. You may want to work with the CAIA content team to come up with appropriate language.

Screen readers don't pronounce "MyHealtheVet" correctly

• Both participants' screen readers mispronounced MyHealtheVet. One participant understood - they were used to the pronunciation - and another didn't.
• Recommendation: Leave this alone. We try to avoid "hacking" how a screen reader pronounces things via aria-labels for many reasons. A great quote from this article:

"...there is little that can be done by the content creator (or web developer) to fix it which wont compromise the output on (say) a Braille device. So testing widely might reveal more pronunciation issues, but we still have no way to solve them."

User navigating by links missed part of the navigation

• P4 navigated by header, then by link. He didn't TAB to interactive elements. Therefore, he missed all menu BUTTONS, including the auth menu.
• I looked into this to see if it was a concern by discussing in the private accessibility channel. Liz continued the discussion in #sitewide-public-websites (see discussion)
• Recommendation: Leave this as is, for now. The navigation BUTTONS - which trigger submenu - are coded semantically and accessibly. Unless folks observe that a lot of AT users are navigating by link and missing the buttons, the buttons shouldn't be changed. That being said, VA's researchers may want to keep this in mind during AT user sessions, and note if the user is missing the buttons, and why. If more data comes to light that this is a problem, VA should consider alternatives.