Skip to content

USWDS - Character count: Overflow warning isn't obvious to screen reader or screen magnifier users #5574

@jaclinec

Description

@jaclinec

Summary

It is not obvious to users of screen readers and screen magnifiers when they have exceeded the character count limit due to limited visual and audible cues.

Observations

  • 1 screen magnifier user did not notice that she went over the limit. She expected it to outline in red if she went over or to stop her from typing. She did not notice the little white hint box saying she went over the cutoff.
  • 3 users talked about how they prefer and expect to be prevented from typing or for some other indicator to let them know they have exceeded the limit. "That's the best way to alert me because I will no longer hear characters being typed. So that kind of lets me know that I've hit the end."

Video clip - Need visual cue 🔒
Video clip - Users prefer 'hard cutoff' or obvious indicator they've gone over 🔒

Affected user groups

  • All users
  • Screen reader users
  • Screen magnification users

Research method

Usability testing with 5 visually impaired participants. See findings report for details.

Next steps

It is NOT advised to implement a hard cutoff/prevent users from typing when they exceed the limit, based on a light landscape analysis we conducted - see details in #5573

Instead, it is recommended to provide visual and audible feedback to users when they have reached or exceeded the character count limit:

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Ready to Schedule

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions