⌨ Manual accessibility testing for Notifications

[gobyrne]

⌨ Accessibility Issue

Work with @esizer to perform manual accessibility testing on the notification feature.

Paths for testing

1. View notification on nav and activate link
2. Mark all as read
3. View notifications on nav and click to "view all notifications"
4. On notification page, view read vs unread?
5. Account settings page, toggle on/off for families
6. Read an email - send one to team? best effort

✅ Acceptance Criteria

A set of assumptions which, when tested, verify that the issue was addressed.

• Windows Chrome + JAWS (@esizer)
• Windows Edge + Narrator (@esizer)
• Windows Firefox + NVDA (@yonikid15)
• macOS Safari + VoiceOver (@mnigh)
• Android Chrome + Talkback (@esizer)
• iOS Safari + VoiceOver (@esizer)
• Basic keyboard (@vd1992)

[petertgiles]

Plan to look at this on Friday

[esizer]

Completed my tests, it went very well except for the instructions. I had a lot of difficulty with them and believe they may cause confusion for non-sighted users.

Created a ticket #10630

[vd1992]

Gave the testing a go, asked Eric some questions now and there. Thanks for answering

Issues
#10637
#10638
#10640

[mnigh]

I have completed the testing on macOS Safari + VoiceOver and created issues:

• ⌨ Notifications Mark all as read action is not announced #10636
• 🔤 Notifications panel instructions are unnecessary #10641
• 🐛 Update notifications pane text and null state message #10639

[yonikid15]

Testing done, looked pretty good overall.

Issues:
#10646
Found same issue #10638
Found same issue #10637. When tabbing again the focus should start on the next notification, not the panel. Same with entering "mark all as read".

[esizer]

Looks like everyone has completed their test at this point. Are we good to close this now?