Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USWDS - Banner: Some screen reader setups may not announce the full banner #5926

Open
jaclinec opened this issue May 13, 2024 · 2 comments
Open
Assignees
Labels
Affects: Accessibility 🟡 Relates to the accessibility of our components Context: JAWS Issue is in the JAWS screen reader Needs: Confirmation We need to confirm that this is an issue Package: Banner Role: Dev Development/engineering skills needed Severity: 4 Minor functionality, workaround available Status: Can't Reproduce We can't reproduce this issue Usability Testing Relates to usability testing fidings

Comments

@jaclinec
Copy link

Summary

It's possible for some screen readers to only announce "Here's how you know" instead of the entire banner copy, and this lack of context could be confusing to blind users. It's recommended that we consider solutions to make the banner announcement more useful for screen reader users in forms mode, such as making more of the text part of the interactive button since forms mode only takes users to interactive elements.

Observations

Upon interacting with the banner component, the JAWS screen read a blind participant was using only announced "Here's how you know" instead of the entire banner copy. We believe they were in "forms mode." It did not hinder the participant or confuse them at all, but it's reasonable to assume this could confuse others.

we were unable to replicate this issue internally, however.

Affected user groups

  • JAWS users

Research method

Usability testing with 8 participants with disabilities:

  • 5 visually impaired (3 blind, 2 low vision/legally blind (1 with nystagmus))
  • 1 motor impairment
  • 1 ADHD
  • 1 anxiety and depression

Screen reader software participants used: JAWS, NVDA, and VoiceOver

[Link to public findings report forthcoming...here is the internal Zebra findings report] 🔒

Next steps

Consider solutions that would guarantee the entire banner is announced by screen readers in a multitude of tech setups and in JAWS forms mode.

@jaclinec jaclinec added Affects: Accessibility 🟡 Relates to the accessibility of our components Needs: Discussion We need to discuss an approach to this issue Status: Triage We're triaging this issue and grooming if necessary Role: Dev Development/engineering skills needed Usability Testing Relates to usability testing fidings Package: Banner Severity: 4 Minor functionality, workaround available labels May 13, 2024
@mejiaj mejiaj added Status: Can't Reproduce We can't reproduce this issue and removed Needs: Discussion We need to discuss an approach to this issue labels May 23, 2024
@mejiaj
Copy link
Contributor

mejiaj commented May 23, 2024

@amycole501 or @alex-hull could you please try to reproduce and add a comment to this issue?

@mejiaj mejiaj added Needs: Confirmation We need to confirm that this is an issue and removed Status: Triage We're triaging this issue and grooming if necessary labels May 23, 2024
@jaclinec jaclinec added the Context: JAWS Issue is in the JAWS screen reader label May 24, 2024
@amycole501
Copy link

Both @alex-hull and I have tested this and only Alex could somewhat reproduce it but not consistently. We think this issue may be intermittent and dependent on the person's AT settings and how they navigate using their screen reader. At this time we think no coding improvements are necessary however we may want to add guidance or a "heads up" warning on the page noting that some AT users may encounter confusion when landing in the banner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Affects: Accessibility 🟡 Relates to the accessibility of our components Context: JAWS Issue is in the JAWS screen reader Needs: Confirmation We need to confirm that this is an issue Package: Banner Role: Dev Development/engineering skills needed Severity: 4 Minor functionality, workaround available Status: Can't Reproduce We can't reproduce this issue Usability Testing Relates to usability testing fidings
Projects
Status: Scheduled
Development

No branches or pull requests

4 participants