Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
cannot navigate to images with loading=lazy attribute #238
Chrome 76 introduced their current implementation for lazy loading content. for instance:
<img loading='lazy' src='https://placekitten.com/400/400' width='400' height='400' alt='a lazy loaded random cat photo'>
However, when testing a page of lazy loaded images with JAWS, JAWS will not navigate to images that have the
Should be able to navigate to any image in the document (all have been provided
Only images that lack
There are 73 total graphics in the test file.
While the graphics cannot be directly navigated to, their
testing with macOS VoiceOver and Chrome and NVDA 2019.1.1 and Chrome, the graphics remain discoverable by quick key navigation.
JAWS version and build number
JAWS 2019 august release
Operating System and version
Browser and version:
I have another output with JAWS 2019 and Chrome 76:
If I add at https://mathiasbynens.be/demo/img-loading-lazy alt attribute with content at the img element, the output is fine (these image are not inside links)
Further research has shown that it's definitely not the loading attribut. Instead, JAWS 2019 no longer outputs graphics within links if the graphic is the only link content.
The problem does not occur in IE and Firefox.
The problem does not occur with Chrome and old JAWS versions (tested with JAWS 18).
test2 is not output because the link has no other content
Thank you for the retest @JAWS-test
After rebooting my machine, I'm now getting the results that match what you're reporting.
JAWS + Chrome don't announce graphics within links, but testing with Firefox 68 graphics are announced within links when navigating by G.
There isn't the issue with lazy loading images as I had previously experienced with even graphics that weren't within links.
As such, I'll close this issue as clearly something was amiss yesterday that no longer holds true in retesting.
The same behaviour also occurs with buttons: graphics within these are not output by JAWS in Chrome, but are output in IE 11. However, Chrome may be closer to the specification here, since the contents of buttons implicitly have role=presentation (at least the ARIA buttons with role=button)