microsoft / microsoft/fluentui

[Accessibility Bug] Screen Reader Announcing Additional Information

Open
#30,665 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Fluent UI react (v8) Resolution: Soft Close
Dominant language
TypeScript
Stars
20.3k
Forks
2.9k
Avg merge
2d 9h
Merged PRs (30d)
46

Description

Environment Information
  • Package version(s): Details List - Fluent UI 8.57.0
  • Browser and OS versions: Windows 11, Edge Dev Version 121.0.2277.4 (Official Build) dev (64 - bit)
Describe the issue:

On the Details List Column Header Screen reader is announcing additional information (<Header_name> section) along with the actual information. The information is redundant and irrelevant and should not be announced.

Actual behavior:

For example header name is ‘Status’ and the screen reader announces as ‘Status column header row 1 Status column1, Status section’.

Expected behavior:

For example header name is ‘Status’ and the screen reader should announce it as ‘Status column header row 1 Status column1’.

If applicable, please provide a codepen repro:
Priorities and help requested (not applicable if asking question):

Are you willing to submit a PR to fix? No

Requested priority: High

Products/sites affected: All the environments including Production environment.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Fluent UI Details List column-header implementation and reproduce the announcement in Edge on Windows 11 with a screen reader. Check how the header name and additional section information are exposed. Done means the example announces “Status column header row 1 Status column1” without the redundant “Status section” text.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
accessibility, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.