- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Fri, 11 Mar 2011 15:17:06 +0100
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: Richard Schwerdtfeger <schwer@us.ibm.com>, Steve Faulkner <faulkner.steve@gmail.com>, Laura Carlson <laura.lee.carlson@gmail.com>, HTML WG LIST <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>, public-html-request@w3.org
Tab Atkins Jr., Thu, 10 Mar 2011 15:01:38 -0800:
[...]
>> <img src="eiffeltower.jpg">
>>
>> This is a picture of the Eiffel tower. The tower is composed of ...
>> The tower is open from ...
>>
>> <h1>Entrance Fees</h1>
>> The tower entrance fees are as follows:
>>
>> <table>
>> <th> ....
>>
>> </table>
>> </img>
[...]
> Having all that information exposed solely as an image
> means that sighted users can't copypaste or find-in-page on it, etc..
That's what it means, but only because graphical UAs don't search or
copy the fallback.
> In general, actual content should still be in the normal page,
> accessible to all users. Rich fallback (like what @longdesc and
> <canvas src> are designed to expose) should only be necessary in rare
> circumstances, when the author has a particularly information-dense
> graphic for some reason, like a webcomic or a chart.
There is, in fact, the same issue with simple things like
<td><img src=star-image alt="New item" ></td><td>iPad</td>
and
<p> I <img src=heart alt=Love > you. </p>
I use find-in-page a lot, and not only on information dense pages, and
I often stumble upon unfindable information.
But all these details about how to best use fallback, how to make info
find-in-page-able etc, is beside the point: Your suggestion simply is
to have <caption src></caption> as an alternative to using <object
data=img></object>.
--
leif halvard silli
Received on Friday, 11 March 2011 14:18:48 UTC