Visitar URL original
USWDS - File input: Improve file status readout for screen readers · Issue #5304 · uswds/uswds · GitHub
Skip to content

USWDS - File input: Improve file status readout for screen readers #5304

Open
Task
Open
USWDS - File input: Improve file status readout for screen readers#5304
Task
Labels
Affects: Accessibility 🟡Affects access for disabled users or assistive tech. Record the barrier; not a severity score.Context: VoiceOver (VO)Issue is in the VoiceOver screen readerPackage: File InputWork affecting File Input. Apply only when this area helps route or find the issue.Role: A11YA11Y expertise is relevant. Project Active Role tracks ownership; this label is not an assignment.Role: DevDev expertise is relevant. Project Active Role tracks ownership; this label is not an assignment.Type: ResearchResearch or audit work with a specific question and outcome; use native Task for the issue type.Type: SpikeA bounded investigation to answer a specific question; use native Task for the issue type.

Description

@amyleadem
amyleadem
opened on May 24, 2023

Summary

Originally posted by @mejiaj in #5213 (comment)

This function adds text describing:

  • How many files
  • Which files have been uploaded

So far I've only gotten it to read after initial upload. If I move to another area and comeback it doesn't get read on VoiceOver Chromium 113.

Possible Future enhancements:

  1. Add a unique ID to this message and tie it to the component via aria-labelledby [MDN on aria-labelledby]
  2. Move the preview heading text so it always gets read.
  3. Dynamically update the aria-label

Move the preview heading text example

file-input-label.mp4

Activity

  1. thisisdano
    added this to USWDS Core Project Dataon May 24, 2023
  2. amyleadem
    self-assigned this
    on May 24, 2023
  3. amyleadem
    added
    Added during SprintHistorical record of work added during a sprint. Not required for current triage.
    Needs: ConfirmationReported behavior needs validation. Remove after recording reproduction or investigation results.
    Package: File InputWork affecting File Input. Apply only when this area helps route or find the issue.
    Affects: Accessibility 🟡Affects access for disabled users or assistive tech. Record the barrier; not a severity score.
    on May 24, 2023
  4. amyleadem
    moved this to Scheduled in USWDS Core Project Dataon May 24, 2023
  5. amyleadem
    moved this from Scheduled to In progress in USWDS Core Project Dataon May 24, 2023
  6. amyleadem
    removed
    Needs: ConfirmationReported behavior needs validation. Remove after recording reproduction or investigation results.
    on May 24, 2023

  7. amyleadem commented on May 24, 2023

    @amyleadem
    amyleadem
    on May 24, 2023
    ContributorAuthor

    @mejiaj I am looking into this, but I'm not sure I understand the suggested change. Would the input end up with both an aria-label and an aria-labelledby?

  8. amyleadem
    moved this from In progress to On deck in USWDS Core Project Dataon May 30, 2023
  9. amyleadem
    moved this from On deck to Scheduled in USWDS Core Project Dataon Jun 5, 2023
  10. amyleadem
    removed
    Added during SprintHistorical record of work added during a sprint. Not required for current triage.
    on Jul 10, 2023
  11. amyleadem
    moved this from Scheduled to Ready to Schedule in USWDS Core Project Dataon Sep 11, 2023
  12. annepetersen
    assigned
    chandracarney
    on May 1, 2026
  13. chandracarney
    added
    Status: TriageLegacy intake label used by templates. Project Status is authoritative; avoid manual duplication.
    Type: SpikeA bounded investigation to answer a specific question; use native Task for the issue type.
    Role: A11YA11Y expertise is relevant. Project Active Role tracks ownership; this label is not an assignment.
    Role: DevDev expertise is relevant. Project Active Role tracks ownership; this label is not an assignment.
    on Sep 10, 2026

  14. chandracarney commented on Sep 10, 2026

    @chandracarney
    chandracarney
    on Sep 10, 2026
    Contributor

    In June, we discussed that this needs further testing and triage.

    Initial thought we had: Can try an aria-live?

  15. chandracarney
    unassigned
    chandracarney
    and
    amyleadem
    on Sep 10, 2026
  16. ryparker
    added the
    Task
    issue type on Sep 16, 2026
  17. ryparker
    added
    Type: ResearchResearch or audit work with a specific question and outcome; use native Task for the issue type.
    Context: VoiceOver (VO)Issue is in the VoiceOver screen reader
    and removed
    Status: TriageLegacy intake label used by templates. Project Status is authoritative; avoid manual duplication.
    on Sep 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Affects: Accessibility 🟡Affects access for disabled users or assistive tech. Record the barrier; not a severity score.Context: VoiceOver (VO)Issue is in the VoiceOver screen readerPackage: File InputWork affecting File Input. Apply only when this area helps route or find the issue.Role: A11YA11Y expertise is relevant. Project Active Role tracks ownership; this label is not an assignment.Role: DevDev expertise is relevant. Project Active Role tracks ownership; this label is not an assignment.Type: ResearchResearch or audit work with a specific question and outcome; use native Task for the issue type.Type: SpikeA bounded investigation to answer a specific question; use native Task for the issue type.

    Type

    Task

    Projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions