WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Use of label without input

for

From: Jonathan Cohn
Date: Nov 16, 2019 5:22PM

Steve,
Is this still the case in JAWS 2019/2020? It was my understanding that JAWS generally uses the iAccessible2 protocol for both Chrome and Firefox. If this is true, I would not expect your described behavior to still occur.


> On Nov 16, 2019, at 4:42 PM, Steve Green < <EMAIL REMOVED> > wrote:
>
> Actually, it does cause an issue, which is caused by one of JAWS' heuristics. If a page contains a <label> element that is not programmatically associated with a labelable element, and the page also contains an unlabelled element that is labelable, JAWS uses the contents of the <label> element to label the other element.
>
> I have seen this many times, and at first I had no idea what was going on because the two elements were hundreds of lines apart in the DOM and there was no apparent relationship between them. However, it was easy to create a minimal test page to verify the theory.
>
> To the best of my knowledge, this issue does not occur with any other screen reader.
>
> Steve Green
> Managing Director
> Test Partners Ltd
>
>
>