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 - Memorable date: Input formatting requirements are unclear to users of screen readers. #5902

Open
jaclinec opened this issue Apr 29, 2024 · 0 comments
Assignees
Labels
Affects: Accessibility 🟡 Relates to the accessibility of our components Package: Memorable date Role: Dev Development/engineering skills needed Usability Testing Relates to usability testing fidings
Milestone

Comments

@jaclinec
Copy link

jaclinec commented Apr 29, 2024

Summary

The memorable date hint messaging announced to screen readers is overly described and unclear:

  1. It announces the same hint for each field ("For example, January 19 2000" is announced when the user lands on the month field, the day field, and the year field).
  2. It doesn’t describe the digits/format needed for inputs, so users are left guessing what to type.

Observations

2 participants (using JAWS and NVDA) experienced friction with understanding the formatting required for the memorable date inputs because the hint announced was not explicit on what is expected for each input and digit requirements. See video clips for memorable date version 1. 🔒

The hint message announced in another version of memorable date that we tested performed much better since the hints were specific to the formatting expectations for each input. See video clips for memorable date version 2 🔒

Affected user groups

  • Screen reader 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

Change the hint message announced to screen readers to be relevant to each input and clear on digit requirements.

@jaclinec jaclinec added Affects: Accessibility 🟡 Relates to the accessibility of our components Status: Triage We're triaging this issue and grooming if necessary Role: Dev Development/engineering skills needed Severity: 1 🟡 Major functionality, no workaround Package: Memorable date Usability Testing Relates to usability testing fidings labels Apr 29, 2024
@brunerae brunerae added Needs: Discussion We need to discuss an approach to this issue and removed Severity: 1 🟡 Major functionality, no workaround Status: Triage We're triaging this issue and grooming if necessary labels May 2, 2024
@amyleadem amyleadem added this to the 2024.06 June milestone May 20, 2024
@mejiaj mejiaj removed the Needs: Discussion We need to discuss an approach to this issue label May 21, 2024
@brunerae brunerae modified the milestones: 2024.06 June, uswds 3.10.0 May 30, 2024
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 Package: Memorable date Role: Dev Development/engineering skills needed Usability Testing Relates to usability testing fidings
Projects
Status: Ready to Schedule
Development

No branches or pull requests

4 participants