W3C home > Mailing lists > Public > public-html@w3.org > June 2007

Re: fear of "invisible metadata"

From: Ben Boyle <benjamins.boyle@gmail.com>
Date: Sat, 23 Jun 2007 11:41:18 +1000
Message-ID: <5f37426b0706221841y419f5fdbg225ac4bcca8ff068@mail.gmail.com>
To: "Robert Burns" <rob@robburns.com>
Cc: "HTML WG" <public-html@w3.org>

Great summary Rob :)

I agree with all that, and I'm still after something extra!
Specifically, I would like to see a way that captions/descriptions can
be associated with media and can be associated with both the embedded
AND fallback content (not one or the other).

http://www.disability.qld.gov.au/community_involv/shared_visions/workshop/sessionone/assistive-technology.html#image-michele
This image has @alt, and a caption. The caption is for "everyone" and
provides more content around the image.

Let's assume we're living in the HTML5 world, using <figure> for this content:
<figure id="image-michele" class="cut-in">
<img alt="Michele Barry speaking at the conference"
src="../../images/accessible.jpg"/>
<legend>Translators and big screens assisted the translation of
presentations. Here Michele Barry from LifeTec speaks during the
community panel</legend>
</figure>

Looks fantastic on the surface right? Here comes my issue with the HTML5 spec:
The entire figure element (including the caption, if any) must be
treated as being a single paragraph with that inline-level content as
its content. [1]

This is instructing a screen reader to:
1. read the text from img@alt (great, I completely agree with this)
2. suppress and ignore everything else in the <figure>, including <legend>

I don't want the <legend> ignored. And I don't understand why anyone
would *ever* want the <legend> ignored. Anyone know the reasons for
suppressing legend when fallback content kicks in?

[1] http://dev.w3.org/cvsweb/~checkout~/html5/spec/Overview.html?rev=1.78#figure
Received on Saturday, 23 June 2007 01:41:22 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:45 UTC