This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24311 - figcaption does not currently replace alt
Summary: figcaption does not currently replace alt
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 editorial
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, a11y_text-alt
Depends on:
Blocks:
 
Reported: 2014-01-16 16:29 UTC by dmacdona
Modified: 2015-06-19 14:13 UTC (History)
5 users (show)

See Also:


Attachments

Description dmacdona 2014-01-16 16:29:16 UTC
Accessibility support can be improved but there
several fundamental problems that will make it difficult for screen reader
users to understand and deal with a figure element with the figcaption
instead of an alt text on the image.

I don't think we can assume that screen readers will begin to announce that
there's a graphic inside the figcaption. Assumptions about longdesc got us
into a lot of problems 15 years ago. I think reporting the figure with a
role of group could be a problem that will be hard to resolve for screen
reader users. Although semantically it is a group, it will take a while for
SR users to understand that it *may* be an image inside a group but maybe
not, the figure element won't tell them that.

I think this belongs in the larger discussion about alt text, and whether we
should allow options to it. Because currently figcaption is probably more
confusing than aria-labelledby, aria label etc.

I would like to see good unity with html5 and WCAG. My thinking is that we
should go one way or the other... allow the gambit of substitutes for alt,
or none... I don't think this one exception of figcaption makes sense.

Perhaps this is a Face to face CSUN topic?

Testing here
http://davidmacd.com/test/figure.html
Comment 1 dmacdona 2014-01-16 16:40:06 UTC
I assign this to 5.1
Comment 2 Charles McCathieNevile 2015-06-19 14:13:13 UTC
This is a bug that applies to some software, not to the spec, which already has interoperable implementation and which makes sense.

Note that WCAG might want to recommend not *using* this until it is better supported…