Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Position and set size not narrated for gridcell in treegrid #15818

Open
adamsamec opened this issue Nov 23, 2023 · 5 comments
Open

Position and set size not narrated for gridcell in treegrid #15818

adamsamec opened this issue Nov 23, 2023 · 5 comments
Assignees
Labels
ARIA p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.

Comments

@adamsamec
Copy link

adamsamec commented Nov 23, 2023

Steps to reproduce:

  1. Turn on NVDA.
  2. Visit this W3C tree grid cell navigation example #1.
  3. Using the Tab key, navigate to the inbox example tree grid element located under the "Example" heading.
  4. Using the Down or Up arrow key, navigate by rows in the tree grid, and observe the narration while navigating from one row to another.
  5. Visit this W3C tree grid row navigation example #2.
  6. Using the Tab key, navigate to the inbox example tree grid element located under the "Example" heading.
  7. Using the Down or Up arrow key, navigate by rows in the tree grid, and observe the narration while navigating from one row to another.

Actual behavior:

In the example #1, when nnavigating in the tree grid with the Down or Up arrow key, NVDA narrates the row and colun coordinates, but not the position of the row and the set size relative to the current tree level. Compare this with the example #2, where NVDA narrates the position and set size correctly, e.g. "2 of 3". The narration is missing regardless of whether the aria-posinset and aria-setsize are present on the row or not.

Expected behavior:

The position and set size should be narrated even when role="gridcell" element is focused, inheriting the data from the parent role="row" element, in the same manner how JAWS does.

System configuration

NVDA installed/portable/running from source:

Installed.

NVDA version:

NVDA 2023.3.0.29780.

Windows version:

Windows 11, version 21H2 (OS Build 22621.2715)

Name and version of other software in use when reproducing the issue:

  • Google Chrome, version 119.0.6045.160.
  • Mozilla Firefox, version 120.0.

Other questions

Does the issue still occur after restarting your computer?

Yes.

Have you tried any other versions of NVDA? If so, please report their behaviors.

No.

If NVDA add-ons are disabled, is your problem still occurring?

Yes.

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

Yes.

@Adriani90
Copy link
Collaborator

Is this also reproducible in Firefox?

@adamsamec
Copy link
Author

Yes, it is reproducable in Mozilla Firefox. I have updated the issue.

@seanbudd
Copy link
Member

Related - #14411

@seanbudd seanbudd added ARIA p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation. labels Nov 27, 2023
@gerald-hartig gerald-hartig added good first issue github features these at https://github.com/nvaccess/nvda/contribute and removed good first issue github features these at https://github.com/nvaccess/nvda/contribute labels Jan 31, 2024
@Adriani90
Copy link
Collaborator

cc: @jcsteh since it affects Firefox as well.

@SaschaCowley
Copy link
Member

@adamsamec could you provide a concrete example of the type of speech and/or braille output you'd expect when navigating a treegrid by cell?

Can anyone provide any examples of this authoring pattern in the wild?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARIA p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants