Accessibility Feedback - Staging Review - Virtual Agent Chatbot

[1Copenut]

This will be the epic to capture accessibility tickets (one per issue) for the Virtual Agent Chatbot staging review: #24884

[1Copenut]

@ianpsant & @shiragoodman The accessibility staging review is now complete. All issues entered.

[ianpsant]

@1Copenut For the two Must Haves, we've identified them as issues we need to address with Microsoft. The remaining additional 508 issues, we still intend to review, but after our Study release or perhaps during. We still want to look at these because we want to understand for PVA what's within our purview versus what we need Microsoft's intervention. Feel free to leave open and we'll leave similar comments depending on what we find out.

[ianpsant]

@1Copenut We've looked at the remaining defect level 2, 3, and 4s and categorized it according to 1) Custom - Within our control and we are able to change, 2) Requires Microsoft change, or 3) Requires Microsoft change, unlikely but worth asking. This is summarized in our ticket https://github.com/department-of-veterans-affairs/va-virtual-agent/issues/221. I will also comment on your tickets.

If PVA development progresses beyond the study we can continue to track these and address them then. Not sure for all the Microsoft related issues if you wanted to file tickets with them in order to improve their product. Either way, let me know if it's safe to close this ticket.

[shiragoodman]

hi @ianpsant. @1Copenut is out of the office this week. Thanks for the follow up on Microsoft. You can close this ticket, but please do not close the child tickets linked above until the issues are resolved. Thanks!

[ianpsant]

For reference, filed these corresponding tickets with Microsoft:

• [KEYBOARD]: Links in the chat log must be keyboard focusable microsoft/BotFramework-WebChat#3933
• [COGNITION]: Links must be announced to screen readers as links. Currently being announced as "messages" or just text microsoft/BotFramework-WebChat#3934
• [KEYBOARD]: Navigation through the chat log must be easy and intuitive microsoft/BotFramework-WebChat#3935
• [SCREENREADER]: New messages must be announced consistently across assistive technology software microsoft/BotFramework-WebChat#3936
• [SCREENREADER]: Content should not be repeated when users are navigating through the chat messages microsoft/BotFramework-WebChat#3937
• [COGNITION]: The chat messages should not have screen reader only information between the end of chat message and text input microsoft/BotFramework-WebChat#3938
• [SEMANTIC HTML]: Consider simplifying the HTML for each list item for better clarity and ease of testing microsoft/BotFramework-WebChat#3939