AT Testing

[msbtterswrth]

Background

We want to test our pattern with AT users to make sure we're in compliance with accessibility guidelines.

We want to specifically test if our alerts are being read by screen readers at the right time (or at all) and that tabbing through the page they get focused in the proper order.

Consult with platform defect severity rubric.

ACs

• We have tested our prefill pattern for
  • tab navigability
  • screen readers using Voiceover on Mac and NVDA on PC
  • we have run our pattern through aXe

[msbtterswrth]

Should we engage with CAIA to help us test the pattern?

[bellepx0]

Tested on MAC. Findings & questions in this doc

[bellepx0]

Assigning @adamwhitlock1 to test on PC

[adamwhitlock1]

I updated the AT doc with Windows notes and some potential next steps:

https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/authenticated-patterns/engineering/%23113-AT%20Testing.md

@bellepx0 I don't think I missed anything, but feel free to add to the list at the end if needed.

@msbtterswrth we will need to create tickets for some of these items for next sprint, and should discuss during refinement / planning further.

[msbtterswrth]

Sounds good to me!

[beckyphung]

@adamwhitlock1 @msbtterswrth I'm curious how we plan to address the next steps/open questions. Can we make sure to consult with CAIA? Is that noted somewhere already?

[msbtterswrth]

We have created a number of tasks for future sprints based on this work:

• A11y Address tabindex and focus issues #161
• A11y Improve screen reader content and alert behavior #162
• A11y Improve navigation and structural elements #163
• A11y Form system fixes for prefill and save in progress #164

We just had a meeting with CAIA that may resolve some of these things natively as part of our next pattern as well.