Repository navigation
Closed
Labels
Affects: Accessibility 🟡Affects access for disabled users or assistive tech. Record the barrier; not a severity score.Affects access for disabled users or assistive tech. Record the barrier; not a severity score.Affects: UsabilityRelates to the usability of our code or componentsRelates to the usability of our code or componentsContext: JavaScriptIssue is in JavaScriptIssue is in JavaScriptContext: SassIssue is in SassIssue is in SassPackage: Character countWork affecting Character count. Apply only when this area helps route or find the issue.Work affecting Character count. Apply only when this area helps route or find the issue.Role: DevDev expertise is relevant. Project Active Role tracks ownership; this label is not an assignment.Dev expertise is relevant. Project Active Role tracks ownership; this label is not an assignment.Severity: 1 🟡Major functionality, no workaroundMajor functionality, no workaroundUsability TestingUser research or findings from usability testing. Link the evidence and user impact.User research or findings from usability testing. Link the evidence and user impact.
Description
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
Labels
Affects: Accessibility 🟡Affects access for disabled users or assistive tech. Record the barrier; not a severity score.Affects access for disabled users or assistive tech. Record the barrier; not a severity score.Affects: UsabilityRelates to the usability of our code or componentsRelates to the usability of our code or componentsContext: JavaScriptIssue is in JavaScriptIssue is in JavaScriptContext: SassIssue is in SassIssue is in SassPackage: Character countWork affecting Character count. Apply only when this area helps route or find the issue.Work affecting Character count. Apply only when this area helps route or find the issue.Role: DevDev expertise is relevant. Project Active Role tracks ownership; this label is not an assignment.Dev expertise is relevant. Project Active Role tracks ownership; this label is not an assignment.Severity: 1 🟡Major functionality, no workaroundMajor functionality, no workaroundUsability TestingUser research or findings from usability testing. Link the evidence and user impact.User research or findings from usability testing. Link the evidence and user impact.
Type
Projects
- StatusShow more project fieldsDone
Activity
[-]Implement a visual cue, such as a red outline for the character box, when users go over the limit.[/-][+]Overflow warning isn't obvious to screen magnifier users[/+][-]Overflow warning isn't obvious to screen magnifier users[/-][+]Overflow warning isn't obvious to screen reader or screen magnifier users[/+][-]Overflow warning isn't obvious to screen reader or screen magnifier users[/-][+]USWDS - Character count: Overflow warning isn't obvious to screen reader or screen magnifier users[/+]chandracarney commentedon Aug 21, 2026
Closing after all work has been completed 🎉