Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
aria-label, aria-labelledby and aria-describedby: very unforeseeable behaviour #5398
Reported by jmuheim on 2015-10-05 14:35
I have created a small codepen to demonstrate the issue (browse it using browse and focus mode):
For example, in NVDA, on the a element, the aria-label and aria-labelledby seem to work in both browse and focus mode. But aria-describedby is only announced in focus mode, not in browse mode.
For the input element, none of the attributes seem to work in browse mode, but all work in focus mode.
For "bare" text elements like p or div, none of the attributes seem to work.
In JAWS, it's quite similar behaviour, but at least for the p element, when there is an aria-describedby, it announces that a description can be read by pressing "JAWS + alt + r".
I don't really see a clear pattern for this, so I wonder what are the general rules in NVDA on how to use these attributes? Or better: why don't they simply work for every element, as the spec proposes?
Comment 1 by jteh on 2015-10-05 23:51
With NVDA 2018.2.1 | Windows 7 | Chrome 73.xx I am attempting to use
I was delighted as I assumed an
I can only get NVDA to read when I use
So I went to a W3 example and put this code in an empty HTML5 page.
It reads Lady MacBeth but never reads the content of
Searching 'using aria to describe an img' seems to suggest using
Am I missing something?
I am loathed to use
This looks like an explanation, if it is, props to powermapper for stating this (I've not read this anywhere else yet):
Is this the answer and all is well, I just need to have in the
I cannot find an NVDA ""Say Description" keyboard shortcut", if I use
So looks like I am still stuck and use of