Open manav-sharma69 opened 1 month ago
Thanks for the issue.
So I tested out the following HTML using different combinations of screen readers and browsers, and this is the result:
<!-- A -->
<figure>
<img src="https://mdn.github.io/dom-examples/view-transitions/images/jungle-coast.jpg">
<figcaption>Jungle coast</figcaption>
</figure>
<!-- B -->
<img src="https://mdn.github.io/dom-examples/view-transitions/images/jungle-coast.jpg">
<!-- C -->
<img src="https://mdn.github.io/dom-examples/view-transitions/images/jungle-coast.jpg" alt="cool image of Jungle">
alt
for image C. So reading order is: "jungle-coast.jpg image, Jungle coast, jungle-coast.jpg image, cool image of Jungle image." Only when having VoiceOver read the entire page is the figure announced, at which point it's announced as "jungle coast, figure," before it announces the image URL as before.figcaption
as "has details, jungle coast" and image C as "cool image of Jungle graphic." This is the same when the reading the entire page.figcaption
as "figure caption jungle coast" and image C as "graphic cool image of Jungle." This is the same when reading the entire page.Based on the results it looks like VoiceOver and Safari does not really work with figure
. Because of this we may call this an accessibility supported issue and it would still be a violation. I'll confirm with the team and let you know if that's not the case.
Product
axe Extension
Product Version
4.80.1
Latest Version
Issue Description
Expectation
The extension should not throw warning because
<figcaption>
element was present to provide caption for the image.Actual
The extension threw a
critical
level issue titled "Images must have alternate text".How to Reproduce
The site tested was MDN's demo of Basic View Transitions.
Screenshot:![alt attribute error](https://github.com/dequelabs/axe-core/assets/157268750/4a07bdba-6aa9-4907-ba91-bf80e1af3762)
Additional context
W3's Guidance for conformance checkers says: