Re: Proposal for <canvas src> to allow images with structured fallback by Tab Atkins Jr.

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>
	<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 
leif halvard silli

Received on Friday, 11 March 2011 14:18:48 UTC