department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
281 stars 202 forks source link

[CAIA A11y Research]: Sitewide Public Websites, Discharge Upgrade Wizard #94815

Open thejordanwood opened 2 days ago

thejordanwood commented 2 days ago

[!NOTE] High-Level Overview: Sitewide Public Websites Discharge Upgrade Wizard

  • Research Timeframe: Pilot: Oct. 16 Participants: Oct 22-Nov 1
  • Pilot 1: Mobile with Screen Reader: Ticket - 94866
  • Assistive Tech Users: 3 AT Users (13 in full research; 3 AT segment)
  • Artifacts Available: Research Plan and Convo Guide
  • Testing Environment & Schedule: Staging Test Environment and Source of Truth for Scheduling (Link)
  • Assistive Tech Being Used: Screen Readers or Screen Magnification
  • CAIA Internal Doc: CAIA Raw Session Notes: Google Doc
  • Task Lists: See task lists for next steps/definition of done

CAIA Assignee(s)

Toggle to view information about the CAIA Team. - **Pilot (Mobile):** 10/16/2024 #94866 - **Research Session Support:** - @sara-amanda `October 18 – 25, 2024` - @mutiaadhocteam `OOO October 18 – 25, 2024` - @SarahKay8 - @coforma-jamie

About the Team

Toggle to view more intake research ticket information ### Do you have an accessibility champion? Yes, we have a champion ### If you have an accessibility champion, what's their name? Laura Flannery ### 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? - [x] Yes, we have reviewed the CAIA capacity calendar and can confirm specialists are available to support in our research timeframe

About the Research

The team is looking to enhance the edit flow to account for questions with branching logic.

Toggle to view the team's research goals. ### Research Goals > 1. Veterans can understand how to edit an answer that introduces branching logic and navigate back to the review page. > 2. Veterans can understand why they may be asked additional questions when editing an answer to a particular question. > 3. After editing a question, updates to the review page are clear and easy for Veterans to understand. > 4. Veterans can navigate through the entire flow using the subtask pattern with ease. > 5. Veterans that use assistive technology, like screen readers or screen magnifier technology, can navigate through user flows with ease. > We will conduct remote moderated usability testing to observe research participants using the Discharge Upgrade Wizard in a live coded environment (staging or production) with the updated sub task pattern. This will allow us to use the current branching logic and our experimental edit flow pattern.

Research Sessions

[!TIP]

  • Providing CAIA A11ys with the time slots in advance for AT users, will allow a11ys to avoid conflicts on the CAIA A11y Capacity Calendar, and reach out to other a11ys, should CAIA not be available.
  • Providing CAIA A11ys with the technology and devices the users will be testing with, will allow CAIA to prepare in advance for the sessions.

Timeframe

Toggle to view research timing information. - **Pilot sessions:** Oct 15-21 (requesting one session - mobile) - Scheduled: 10/16 #94866 - **Participant sessions:** Oct 22-Nov 1 ### Length of sessions - **Session length:** - `TBD` - **AT Session Timing Examples**: - `90` minutes (screen reader or alternative navigation tool) - `60` minutes (screen magnification tool) - **Buffer time between sessions:** `30` minutes - **Maximum sessions per day:** `2`

Testing Schedule

CAIA A11Ys will be looking for device and AT information. We realize that some of this information will not be available until the day of the session.

Toggle to view time-related items #### Enter Testing Information - **Dates**: Oct. 22, 2024 to Nov. 1, 2024 - **Times**: `TBD` - **Planning to Recruit `#` Veterans for**: - minimum of `#` sessions with screen reader users - minimum of `#` sessions with alternative navigation users - minimum of `#` session with a screen magnification user #### Examples - **Date Range Example**: _Typically around `2` Weeks_ - **Timing Example**: _`9-10:30am`, `11-12:30pm`, `1-2:30pm`, `3-4:30pm` EST_ - **Recruitment Example**: _Planning to Recruit `12` Veterans for: a minimum of `3` sessions with screen reader users; minimum of `2` sessions with alternative navigation users; and a minimum of `1` session with a screen magnification user._ #### Source of Truth Testing Schedule (🔗 `To be Provided` as source of truth; **_also see table in this ticket_** Please use the following table to enter the following information for each participant: Date and Time, Assistive tech (AT), Device and Operating System, Browser, and Skill level: P# | Date and Time (ET) | AT | Device and OS | Browser | Skill | CAIA A11ys Available ------------------|------------------|--------------|--------------|--------------|--------------|-------------- Pilot | 10/16/24, 2-3 p.m. EST | VoiceOver, JAWS, etc `TBD` | **Mobile**; Windows, MacOS, iOS, Android, etc. `TBD` | Safari, Chrome, etc. `TBD` | **Pilot** | @mutiaadhocteam @SarahKay8 @coforma-jamie P# |10/#/24, #:##-#:## #m | VoiceOver, JAWS, etc `TBD` | Mobile or Desktop; Windows, MacOS, iOS, Android, etc. `TBD` | Safari, Chrome, etc. `TBD` | Novice, Intermediate, Advanced `TBD` | `TBD- Based on a11y availability` P# | 11/#/24, #:##-#:## #m | VoiceOver, JAWS, etc `TBD` | Mobile or Desktop; Windows, MacOS, iOS, Android, etc. `TBD` | Safari, Chrome, etc. `TBD` | Novice, Intermediate, Advanced `TBD` | `TBD- Based on a11y availability` - **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.

CAIA A11ys will review the coverage needed, and self-assign, based on a11y availability.

Supporting artifacts (if any)

Next Steps: Definition of Done

### CAIA A11Y Tasks
- [x] **INTAKE TICKET:** @sara-amanda to process intake ticket 10/11/2024
- [x] Receive prototype from Team
- [x] **Links**: Research Guide and Convo Guide Support
- [x] **PILOT CALENDAR HOLDS** - on the A11y [**CAIA Capacity Calendar**](https://calendar.google.com/calendar/u/0/embed?src=c_f982350fc73a8162a1088ab14d00dd37335b2b559a60d6b67eb8021416f81c2a@group.calendar.google.com&ctz=America/Chicago) `HOLDS ON CALENDAR FOR DATE RANGE`
- [x] **PILOT SESSION MOBILE: SCHEDULE** Pilot session with team. `Conduct around 10/16-21/2024` 
- [x] **PILOT SESSION MOBILE: CREATE TICKET** See `related tickets task list` in this ticket.
- [x] **CALENDAR HOLDS** Update A11y [CAIA Capacity Calendar](https://calendar.google.com/calendar/u/0/embed?src=c_f982350fc73a8162a1088ab14d00dd37335b2b559a60d6b67eb8021416f81c2a@group.calendar.google.com&ctz=America/Chicago) with holds for user research sessions with AT, when dates become available. `HOLDS ON CALENDAR FOR DATE RANGE`
- [ ] Receive Source of Truth for Scheduling 🔗 (Examples: Google Sheet, Slack Canvas, etc.)
- [ ] **Requested device breakdown:** Desktop, Mobile and Tablet
- [ ] **Divvy user research session support with CAIA A11ys** - based on availability and technology available to support.
- [ ] **Updated Holds:** waiting on official invites (table to be updated in this ticket)
- [ ] **REMOVE CALENDAR HOLDS** Remove holds on A11y [**CAIA Capacity Calendar**](https://calendar.google.com/calendar/u/0/embed?src=c_f982350fc73a8162a1088ab14d00dd37335b2b559a60d6b67eb8021416f81c2a@group.calendar.google.com&ctz=America/Chicago) and replace with invitations from project team (or Perigean) Updated holds x/xx/2024
- [x] **Review research folder and assets**
- [x] **OFFICIAL RAW RESEARCH NOTES** Create [CAIA notes document](https://docs.google.com/document/d/1hAXf9SwxNiNdjU76bGe8xr8cNuqETj3rQ0F7ETxLT-w/edit?usp=sharing)
- [ ] **Participate in research** **Date Span:** `10/22/2024` and `11/1/2024`
- [ ] **SYNC:** Connect with CAIA A11ys on research findings (meeting)
- [ ] **Create/update the CAIA A11y Research Deliverable** This is dependent on the number of study participants CAIA supports. If minimal, A11Ys may share feedback only in the feedback Mural or this ticket.
- [ ] **Share the completed deliverable** with the project team via Slack: `Primary Team Slack` and `Ticket`
- [x] **TEMPLATE SESSION NOTES**: Create [CAIA notes document](https://docs.google.com/document/d/1hAXf9SwxNiNdjU76bGe8xr8cNuqETj3rQ0F7ETxLT-w/edit?usp=sharing) for a11ys to use during the sessions
### VFS TEAM Tasks
- [x] Tag @Naomi Eke in Slack [#sitewide-content-accessibility-ia](https://dsva.slack.com/archives/C01K37HRUAH) Link to VA [OCTO Slack Thread 10/10/2024](https://dsva.slack.com/archives/C8E985R32/p1728593064618919)
- [ ] Your team's researchers and observers read through platform guidance on [research with assistive technology users](https://depo-platform-documentation.scrollhelp.site/research-design/research-with-assistive-technology-users) and have also read and learned [how to be respectful of participants with disabilities](https://depo-platform-documentation.scrollhelp.site/research-design/disability-etiquette)
- [ ] Your team's researchers have read through the resources for researchers on the VA Platform's [Accessibility on Va.gov page.](https://depo-platform-documentation.scrollhelp.site/developer-docs/accessibility-on-va-gov#AccessibilityonVA.gov-ResourcesforResearchers)
- [ ] [Inclusive Recruitment Strategies](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsa/accessibility/research/recruitment.md)
- [x] Consider [creating your prototype in CodePen](https://depo-platform-documentation.scrollhelp.site/research-design/accessible-prototyping-with-codepen) for the most accurate results - `Using Staging`
- [x] `Recommending Pilot` Review our [assistive technology pilot guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/CAIA/accessibility/assistive-tech-pilot-guide.md) and request a pilot, if desired - `REQUESTED MOBILE`
- [x] Request pilot sessions with CAIA a11ys  `
- [x] Schedule pilot session with CAIA a11ys (Mobile) **[Available](https://dsva.slack.com/archives/C8E985R32/p1728662548407519?thread_ts=1728593064.618919&cid=C8E985R32)**: 10/16, 17 or 18 (1-3 p.m. CT)
- [x] ~Schedule pilot session with CAIA a11ys (Desktop)~ `REQ. MOBILE ONLY`
- [x] **PROTOTYPE:** Provide prototype to CAIA A11ys via this ticket in the supporting artifacts section.
- [ ] **SPECIFIC DATES NEEDED** See `Table` in the ticket above. Please provide date range and slots for AT sessions being planned. `Estimated Start: Oct. 22/Nov. 1`
- [ ] **ASSISTIVE TECH. INFO NEEDED:** Please provide the AT the users will be utilizing during the research sessions in the `Table` in the ticket above.
- [ ] **INVITES:** Forward invites from Perigean to CAIA A11ys (@sara-amanda)
- [ ] **Device Detail:** Desktop, Mobile and Tablet - Device breakdown needed for session prep
### Related Tickets
- [ ] #80777
- [ ] https://github.com/department-of-veterans-affairs/va.gov-team/issues/94866
coforma-jamie commented 1 day ago

Conversation Guide Review

@thejordanwood, I reviewed your conversation guide!

It looks great, just wanted to note a couple of things for you to consider:

Session Duration

2 hour sessions: While it’s recommended to give extra time for assistive tech users, there’s a good chance that you won’t need the full 2 hours to complete all the tasks. Couple of recommendations:

Heads Up

“Share sound”

A heads up that if the participant is using a phone or tablet, there won’t be a share sound button, and very likely you won’t hear their screen reader speaking. You will see a prominent focus indicator surrounding whatever item on the page is being read aloud. You can also ask those folks in particular to speak what actions they’re taking, since you won’t be able to hear them.

Screen Magnification Over Zoom

A heads up that often, screen mag doesn’t visually come through over Zoom, depending on the means of the magnification (browser text size increases will show, full-screen zooming in and out often won’t). So don’t panic if you don’t see the magnification, just double-check with the participant and let them know that you don’t see it on your end.

sara-amanda commented 1 day ago

CAIA a11y Research Support

@thejordanwood Thank you for submitting a research ticket with CAIA! Our a11ys are looking forward to working with you on your latest research project.

Next Steps

The following are the initial, next steps in our process:

We are happy to answer any questions you may have, along the way. Thank you for reaching out to us and we are happy to help!

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