Visitar URL original
USWDS - Bug: Time picker instructions need more specificity to pass WCAG · Issue #6061 · uswds/uswds · GitHub
Skip to content

USWDS - Bug: Time picker instructions need more specificity to pass WCAG #6061

Closed
1 of 1 issue completed

Description

@amycole501

Describe the bug

The existing visible instructions for time picker aren't sufficient to prevent errors; we need to add clarity to the format and options to prevent users from typing in potentially invalid times.
See https://www.w3.org/TR/WCAG20/#minimize-error-cues for clarification on 3.3.2

Steps to reproduce the bug

  1. Go to https://designsystem.digital.gov/components/time-picker/
  2. View hh:mm
  3. Try typing in 12:15
  4. Try typing in 19:30

Findings: hh:mm may not provide enough instructions for a user to select a valid time.

Expected Behavior

Suggest adding more clear instructions. For example:

Start typing or select an AM or PM time in half-hour increments.

Screenshots

No response

System setup

No response

Additional context

FYI there's a related issue here for adding a 24 hour option #4947

Code of Conduct

Activity

  1. added
    Affects: Accessibility 🟡Affects access for disabled users or assistive tech. Record the barrier; not a severity score.
    A11y AuditAccessibility audit work or its findings. Preserve the test scope and evidence in the issue.
    A11Y Audit FindingsA finding from an accessibility audit. Keep links to the test, result, and affected user experience.
    on Sep 12, 2024
  2. added this to the uswds 3.10.0 milestone on Sep 12, 2024
  3. added
    A11Y Audit: FailsAn accessibility audit recorded a failure. Link the failing test and retest evidence before closing.
    on Sep 12, 2024
  4. moved this from Scheduled to Ready to Schedule in USWDS Core Project Dataon Sep 16, 2024
  5. changed the title [-]USWDS-Site - Bug: Time picker instructions need more specificity to pass WCAG[/-] [+]USWDS - Bug: Time picker instructions need more specificity to pass WCAG[/+] on Sep 18, 2024
  6. mejiaj commented on Sep 18, 2024

    @mejiaj
    Contributor

    Removed Site from the issue title to avoid confusion.

  7. added
    Added during SprintHistorical record of work added during a sprint. Not required for current triage.
    on Sep 20, 2024
  8. 5 remaining items

  9. moved this from In progress to Review in USWDS Core Project Dataon Sep 26, 2024
  10. moved this from Review to In progress in USWDS Core Project Dataon Oct 22, 2024
  11. amyleadem commented on Oct 23, 2024

    @amyleadem
    Contributor

    Update

    In a team discussion, we agreed to move forward with text that generally follows this structure: "Select a time from the dropdown. Type to filter options"

  12. moved this from In progress to Review in USWDS Core Project Dataon Oct 23, 2024
  13. moved this from Review to Fed Final Review in USWDS Core Project Dataon Oct 24, 2024
  14. moved this from Fed Final Review to Done in USWDS Core Project Dataon Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

A11Y Audit FindingsA finding from an accessibility audit. Keep links to the test, result, and affected user experience.A11Y Audit: FailsAn accessibility audit recorded a failure. Link the failing test and retest evidence before closing.A11y AuditAccessibility audit work or its findings. Preserve the test scope and evidence in the issue.Added during SprintHistorical record of work added during a sprint. Not required for current triage.Affects: Accessibility 🟡Affects access for disabled users or assistive tech. Record the barrier; not a severity score.

Type

No type

Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions