-
-
Notifications
You must be signed in to change notification settings - Fork 659
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
regions labeled by aria-labelledby won't read with NVDA. #13307
Comments
How about NVDA 2021.3? |
Confirmed on my side. Last version of NVDA where the heading was read as it should is NVDA 2019.2, so while this is a regression it is not a recent one. |
This bug is still an issue. I just checked with the current NVDA version 2022.1:
Please look into this and fix it soon! :-) |
Created pen for this to show issue |
… outside using quicknav or focus in browse mode (#14303) Fixes #13307 Fixes #13996 Summary of the issue: Some time after NVDA 2019.2, labels of landmarks and regions were no longer automatically spoken when jumping inside from outside using quick nav or focus in browse mode. Although a label should not be spoken when moving into a landmark or region with the arrow keys if the label is from an associated node via aria-labelledby, when jumping in with quick nav / focus, it always should, as context is more important than rare duplication. Description of user facing changes A landmark or region's name is always automatically spoken when jumping inside from outside using quick navigation or focus in browse mode. Description of development approach landmark and region roles are treated the same as groupings and propertypages in getcontrolFieldSpeech. I.e. the name is always announced if it has one when entering from outside for a reason of quicknav or focus.
@michaelDCurran - has this gotten released yet? I don't see this commit in the latest version (unless I'm looking at the wrong thing) |
Even I couldn't see the fixed for the issue in the latest NVDA version . I have tested the same in both Chrome and Firefox . When I navigate to the regions which is labelled by aria-labelledby, NVDA screen reader is not identifying the label of the region. In the below example , NVDA identified the label of the region which is labelled using aria-label. But, same regions when I labelled using aria-labelledby , it is not identifying the label of the region. |
@michaelDCurran can we get an update on the fix for this? Doesn't look like the linked commit has shipped? Do we have an ETA? |
This fix went into NVDA mastr on Oct 27. Unfortunately this was too late for NVDA 2022.4. Therefore this will be in NVDA 2023.1. However, you could test this in NVDA alpha snapshots if you are curious. |
Would the two scenarios below be considered a regression or are these intended behaviors when the reporting of landmarks and regions is unchecked in the document formatting settings?
|
that's continues as a problem, regions with aria-labelledby don't announces its label, but it can be seen in region list with nvda+F7 |
@cizquierdof which version of NVDA are you using? |
I cannot reproduce the issue anymore with NVDA 2024.2 Beta, tested in Firefox 126, Edge 125 and Chrome canary 127. |
Steps to reproduce:
Actual behavior:
Upon entering, nvda does not read the labelledby but it does read the labelledby when I touch the node with object nav.
Expected behavior:
The heading is read
System configuration
NVDA installed/portable/running from source:
installed
NVDA version:
alpha-24583,61000de2
Windows version:
Windows 11 21H2 (x64) build 22000.434
Name and version of other software in use when reproducing the issue:
Chrome: Version 97.0.4692.99 (Official Build) (64-bit)
Issue also repros under firefox, so rendering engine independent.
The text was updated successfully, but these errors were encountered: