microsoft / microsoft/fluentui

[Bug]: [DataGrid] JAWS doesn't follow column navigation in VPC mode

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

Nobody has claimed this yet.

Area: Accessibility Component: DataGrid Fluent UI react-components (v9) Resolution: Soft Close
Dominant language
TypeScript
Stars
20.3k
Forks
2.9k
Avg merge
2d 9h
Merged PRs (30d)
46

Description

Library

React Components / v9 (@fluentui/react-components)

System Info
System:
    OS: Windows 10 10.0.22631
    CPU: (12) x64 Intel(R) Xeon(R) E-2176M  CPU @ 2.70GHz
    Memory: 13.12 GB / 31.74 GB
  Browsers:
    Edge: Chromium (119.0.2151.97)
    Internet Explorer: 11.0.22621.1
Are you reporting Accessibility issue?

None

Reproduction

https://codesandbox.io/p/sandbox/sweet-dubinsky-hmlcqd

Bug Description

Run JAWS.
Switch to VPC mode.
Navigate to the grid in VPC mode
use ctrl+alt+up/down arrow keys to navigate in the column

Actual Behavior

JAWS navigates in the same column

Expected Behavior

JAWS doesn't keep the same column, but jumps to different one.
NVDA works OK.

Tested with Chrome.

Logs

No response

Requested priority

Normal

Products/sites affected

No response

Are you willing to submit a PR to fix?

no

Validations
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • The provided reproduction is a minimal reproducible example of the bug.

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 React Components v9 DataGrid implementation and the linked CodeSandbox reproduction, then reproduce the behavior with JAWS in VPC mode using Ctrl+Alt+Up/Down. Done means column navigation moves to a different column in JAWS on Chrome while preserving the existing working NVDA behavior.

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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.