search

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 201 forks source link

[a11y Support] Office Hours Support Log (October 2023 to Feb 2024) #68324

Closed sara-amanda closed 5 months ago

sara-amanda commented 11 months ago

a11y Office Hours Support History

Date Updated Hours Tracked Teams Supported Sessions Held
3/5/2024 4 7 7

About this Ticket

Support Summary Notes by Date

2/20/2024

1/23/2024

Toggle to view a11y-related support given on 1/23/2024 - **CAIA Presence**: `Jamie` `Eli` `Laura` - **Group Needing Support's Slack Channel:** benefits-contention-classification - **Resources Provided:** After [discussing with CAIA](https://coforma.slack.com/archives/C05LB36ATAQ/p1706044287137799), shared resources and discussed with the team [in their Slack channel](https://dsva.slack.com/archives/C04AZ8T7XN1/p1706142153316829), and met with them to address additional concerns the following week. The team is trying to improve the UX of an autocomplete combo box, which comes with accessibility challenges. - **Total time in Office Hours:** 0.5

1/9/2024

Toggle to view a11y-related support given on 1/9/2024 - **CAIA Presence**: `Sara`Lily`Laura` - **Group Needing Support's Slack Channel:** benefits-non-disability - **Resources Provided:** See ticket: #73590 - **Total time in Office Hours:** 0.5

12/12/2023

Toggle to view an overview of a11y-related support given on 12/12/2023 - **CAIA Presence**: `Lily` `Jamie` `Sara` `Laura` - **Group Needing Support:** `Benefits Decision Review` - **Group Needing Support's Slack Channel:** #### Notes **Met with**: `Eileen Chi` - HTML page, with an option for a PDF - AT testing wanting to be done - Design is done, coded prototype next sprint - Need help with an expert who can help with the research plan (almost done with this) - Recruitment for folks who use screen readers with different levels of expertise - Perigean Timing: 1 week to recruit + 5 days if we have 5 sessions; recruit 8-10 - Plus, holiday - CAIA can observe from that point of view - CAIA can provide some tech support - They will be testing on Staging. - **Eileen** is meeting with Charlotte tomorrow. - **DK** is split between teams (reviewed the confirmation page and the persistent HTML page) - **IA URL question coming FYI** - heads up to Kristin needed. - Ticket to be submitted for research @coforma-terry FYI - Screen reader resources provided on call - [Screen Reader Checklist](https://depo-platform-documentation.scrollhelp.site/research-design/screen-reader-checklist) - [Research with AT Users](https://depo-platform-documentation.scrollhelp.site/research-design/research-with-assistive-technology-users) - **PDFS** - PDF download options w/in the Medical Records Tool (Bobby) - aware of those - **Issue**: Dependency of lighthouse to make the PDF - so far they have not been accessible, layering data on top of that. - :warning: Meant for central mail, not for Veterans to receive. - Would be a larger lift to build the PDFs. - So trying the HTML version approach first. - SK and Evan would you like to be on this call too? [ss - reached out via Slack](https://oddball.slack.com/archives/C05LB36ATAQ/p1702416625289609) - [This is connected to the a11y chat the other day with DK FYI in DSVA Slack. ](https://dsva.slack.com/archives/C0335Q88X0S/p1702070187818259) #### Follow-Up - @coforma-jamie and @sara-amanda to meet. - [Eileen to submit Research Ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=coforma-terry&labels=508%2FAccessibility%2C+sitewide+CAIA%2C+sitewide+accessibility%2C+CAIA-a11y-research&projects=&template=caia-a11y-research.yaml&title=%5BCAIA+A11y+Research%5D%3A+Team+name%2C+product+name) and meet with Charlotte, finishing research plan and find out timing from Perigean. - CAIA plan to support end of year/start of the year - **Total time in Office Hours:** 0.5

11/7/2023

Toggle to view an overview of a11y-related support given on 11/7/2023 - **CAIA Presence**: `Lily` `Eli` - **Group Needing Support's Slack Channel:** [va-virtual-agent-public ](https://dsva.slack.com/archives/C01KTS3F493) > Anita and Nichelous from VA Virtual Agent popped in for a second but decided to come back next week instead, [per Lily](https://oddball.slack.com/archives/C04JVQGEK8F/p1699391411437289?thread_ts=1699382903.790929&cid=C04JVQGEK8F). #### Follow-Up - Eli had reached out to them in Slack, prior to the meeting. - He is following up with them re: Chatbot. - **Total time in Office Hours:** 0

10/31/2023

Toggle to view an overview of a11y-related support given on 10/31/2023 - **CAIA Presence**: `Sara`and `Lily` - **Group Needing Support's Slack Channel:** [va-virtual-agent-public ](https://dsva.slack.com/archives/C01KTS3F493) - **Resources Exchanged:** - #67376 - [Links to the Chatbot Playbook in Column A of the Deliverable](https://docs.google.com/spreadsheets/d/1KY_apLWtdDMxbA42sfuDqC81umA3yF1Yt5NwXZqbEYE/edit#gid=98119274) - **Chatbot Team** [Chatbot Team Ticket #1201](https://github.com/department-of-veterans-affairs/va-virtual-agent/issues/1201). - **Asking CAIA:** Would the [Microsoft recommendation](https://github.com/microsoft/BotFramework-WebChat/blob/main/docs/ACCESSIBILITY.md#ux-navigating-activities-in-the-chat-history) of the [Grid Layout Widget](https://www.w3.org/WAI/ARIA/apg/patterns/grid/) be applicable here (see W3 standards). - #67309 - **Screen Recordings:** Anita added a comment with the [recordings](https://github.com/department-of-veterans-affairs/va.gov-team/issues/67309#issuecomment-1788042975) they showed on 10/31/2023 [#67309](https://github.com/department-of-veterans-affairs/va.gov-team/issues/67309). #### Topics Discussed: - Progress on the Accessibility Defects - Challenges Chatbot Team is Facing - Clarifications and questions answered
Toggle to view an expanded view of a11y-related notes from 10/31/2023 #### Keyboard Navigation - **Scroll with a mouse and scroll up and down smoothly with arrow keys.** - Similar functionality in our chatbot. - Keyboard navigation instead of the smooth scroll it jumps from message to message. - **Not their expectations** - _Governance Team_ - **Use a semantic tool to look at Dev tools to mitigate those issues.** - **Raina**: Recommendations that were given from the findings, made those changes to see if we could achieve the desired behavior. Using some of the pattern for a grid widget, that is why we are able to use up and down arrow keys in the chat history. > **Question** _Since Microsoft has done research on best practices, on applications similar to our chatbot. Is that a guideline that we could be following?_ - Chatbot Team [Chatbot Team Ticket #1201](https://github.com/department-of-veterans-affairs/va-virtual-agent/issues/1201) - Would the [Microsoft recommendation](https://github.com/microsoft/BotFramework-WebChat/blob/main/docs/ACCESSIBILITY.md#ux-navigating-activities-in-the-chat-history) of the [Grid Layout Widget](https://www.w3.org/WAI/ARIA/apg/patterns/grid/) be applicable here (see W3 standards). #### Reading/Skipping Messages ##### VoiceOver // Windows NVDA // JAWS - [CAIA Card Ticket #67309 related issue](https://github.com/department-of-veterans-affairs/va.gov-team/issues/67309): Instead of reading every message out, the screen reader for VO will not read them one at a time, as they are appearing. - Microsoft would be submitting a ticket to VoiceOver. - They can look into it. - Microsoft is not able to replicate it. - Inconsistencies within VoiceOver using the same flow. #### Adaptive Cards // Larger Blocks - **How they are being read out … have implemented some changes:** - Decided to add a delay based on the number of characters in the message itself. - Depending on how long the message is, added a slight delay, increase the delay in between messages, when a bubble appears, to give the user more time to understand the message delivered by the SR. Give them more time to react to the message as well, if certain actions need to be delivered. - This helps to get around messages appearing too fast. - The next change, for the adaptive card, they have added a summary to that card, so that it actually displays key characteristics, summary to let the SR know that a card is being displayed on the screen, use keyboard to get elements within the card. - It improves the experience. - **Video from Anita shown.** - Display message → Delay → adaptive card → delayed - Separate outputs with delay in between - It takes longer for the message to be there. - Summary of the adaptive card reading is off a bit, previously it would have been skipped. - Speech synthesis markup language being read. - That same tag is being used by the SR. - Jaws reads that correctly, VO does not, and reads it as intended.) - There is some inconsistency across screen readers, the speak tag of the adaptive card, and how it works across SR. - **Microsoft’s Expectations vs VA Expectations how to navigate:** - Summary of the card, but you would need for keyboard navigation to dive into the card to be able to get to each of the fields. - Speak tag to the card as a whole, card and short description, like a caption on an image as a summary. The intent of the speak tag is not to expose every text content in the card itself. Expectation is that if the user wants more details and what labels and values that they can use the keyboard to navigate in the chat history to get into the card to get the detail. - _**Functionality as expressed by Microsoft. ^**_ - **Additional information** - originally this functionality was for a voice experience with no screen at all. Screen you got a card if no card summary text above and ability to ask follow-up questions. This functionality still exists. The experience can stand without that card being read out on a screen reader because the reader has the ability to ask other questions. - No Microsoft Documentation - Mark Tucker. - **_Read off one at a time so that navigation only goes to the previous one, in the event there are multiple prescriptions._** #### Questions - **Is it possible to create a VoiceOver Transcript?** - **Overarching Categories (team is thinking this through further - how to approach):** - Face-Value Feedback - Limitations of Microsoft - VA Standards - **Next Time: Chatbot Team Will ... ** - Go over the cards and come back with the essence that is remaining … Microsoft or CAIA support. - Level 1 Feedback Impact so far? - Defect at face value - Microsoft’s feedback on behavior and how it relates to the VA standard. - **Current Approach by Chatbot Team** - Overarching themes SR and Keyboard Navigation Issues - Are there any other overarching umbrellas for feedback to see if anything is missing. - **Should we consider the W3 Patterns, based on feedback from Microsoft?** - **Who owns the VA Accessibility Standards?** (DST/USWDS)

10/24/2023

Toggle to view a11y-related support given on 10/24/2023 - **CAIA Presence**: Lily, Sara and Laura - **Group Needing Support's Slack Channel:** iir-product-teams-public - **Page Referenced for a11y support:** - https://www.va.gov/school-administrators/ - **Resources Provided:** - **[Example of the component](https://design.va.gov/storybook/?path=/story/components-va-on-this-page--default)** - **[Design System Site](https://design.va.gov/components/on-this-page)** - **[Component in Storybook](https://design.va.gov/storybook/?path=/docs/components-va-on-this-page--default)** > **Accessibility considerations** > - Heading levels should increase only by one. The proper order of heading levels conveys the structure of the page for screen reader users and provides a natural hierarchy for your content. When heading elements are applied correctly, the page becomes much easier for both screen reader and sighted users to navigate. > - The focus should be on the destination. When a user clicks on an item on the On this page component, the focus should move to the heading that it links to. > - Allow enough spacing between components. Space should be 1.5 rem (36px) from the bottom of the descender to the top of the ascender. > - **On this page jump links should be contained in a` navigation landmark` so it can be easily discovered by screen reader users.**

Template below task lists.

### Office Hours Support Log 2023
- [ ] https://github.com/department-of-veterans-affairs/va.gov-team/issues/63458
- [x] [a11y Support] Office Hours 10/24/2023: SS: Support (1 Group; .5 hour)
- [x] [a11y Support] Office Hours 10/31/2023: SS: Support Given (1 Group; 1.5 hours)
- [x] [a11y Support] Office Hours 11/7/2023: No Support Given Directly - [see notes](https://github.com/department-of-veterans-affairs/va.gov-team/issues/68324#:~:text=Toggle%20to%20view%20an%20overview%20of%20a11y%2Drelated%20support%20given%20on%2011/7/2023) (1 Group; 0 hours)
- [x] [a11y Support] Office Hours 11/14/2023: No A11y Attendees for this session.
- [x] [a11y Support] Office Hours 11/21/2023: No A11y Attendees for this session.
- [x] [a11y Support] Office Hours 11/28/2023: No A11y Attendees for this session.
- [x] [a11y Support] Office Hours 12/5/2023: No A11y Attendees for this session
- [x] [a11y Support] Office Hours 12/12/2023: SS/JKF Support Given (1 Group; 0.5 hours) - see notes above
- [x] [a11y Support] Office Hours 12/19/2023:  No A11y Attendees for this session
- [x] [a11y Support] Office Hours 12/26/2023:  No A11y Attendees for this session
### Office Hours Support Log 2024
- [x] Add Slack Channel [Reminder Locations](https://github.com/department-of-veterans-affairs/va.gov-team/issues/68324#:~:text=Slackbot%20Reminders%20in%20Multiple%20Channels) to Ticket (in the event updates need to be made) 11/7/2023
- [x] [a11y Support] Office Hours 1/2/2024 - No A11y Attendees for this session.
- [x] [a11y Support] Office Hours 1/9/2024 - Support Given (see notes)
- [x] [a11y Support] Office Hours 1/16/2024 - No A11y Attendees for this session.
- [x] [a11y Support] Office Hours 1/23/2024 -Support Given (see notes)
- [x] [a11y Support] Office Hours 1/30/2024 - No A11y Attendees for this session.
- [x] [a11y Support] Office Hours 2/6/2024 - No A11y Attendees for this session.
- [x] [a11y Support] Office Hours 2/13/2024 - No A11y Attendees for this session.
- [x] [a11y Support] Office Hours 2/20/2024 - Support Given (see notes)
- [x] Add new office hours to 2024 list or keep this ticket? Tracking in Looker Studio Report.

Template for Future Updates

Date Goes Here

Toggle to view a11y-related support given on date - **CAIA Presence**: `Team Members` - **Group Needing Support's Slack Channel:** - **Resources Provided:**

Slackbot Reminders in Multiple Channels

Should office hours change, reminders are currently setup in the following three channels:

sara-amanda commented 10 months ago

@artsymartha68 - this is the ticket I am using to track Office Hours Support relating to accessibility within CAIA.

sara-amanda commented 9 months ago

@artsymartha68 see notes for 12/12/2023 - Evan is going to hop on this with Jamie and myself as well.

sara-amanda commented 7 months ago

Slack Workflow: CAIA Office Hours (NEW!)

How to Request CAIA Office Hours

sara-amanda commented 5 months ago

Tracking Office Hours