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

Re: Proposal: accessibility revision for the img element...

From: Sander Tekelenburg <st@isoc.nl>
Date: Fri, 6 Jul 2007 21:08:27 +0200
Message-Id: <p0624060ac2b441f26b89@[192.168.0.102]>
To: public-html@w3.org

At 11:14 +0100 UTC, on 2007-07-06, Joshue O Connor wrote:

> Sander Tekelenburg wrote:
>> I think "fallback content" will be misunderstood by many authors.  [...]
>
> I agree, and also think that the term 'fallback' content is
> inappropriate for other reasons. IMO it is not a suitable term at all.
> As I think Gregory pointed out, 'fallback' for whom?

>From a UA implementor's point of view it is a fallback mechanism. So I
completely understand why the term is in the current spec the way it is. But
yes, for authors it shouldn't be called "fallback". So optimally the spec
would say "x is for authors to provide a textual alternative (or
"equivalent") for when the non-text can for whatever reason not be presented.
UAs are to fallback to the textual alternative when the non-text cannot be
presented". Something along those lines.

[...]

>> The same problem exists with the title attribute. It might be a good
> idea if
>> the spec would define a maximum length (in characters, if possible)
> for both
>> attributes, so that authors can be sure that conforming UAs will present
>> these attributes' content in its entirety.
>
> It may be best to 'suggest' a limit and indicate it they need more that
> can use /<insert suitable attribute/element/method>/.

See <http://lists.w3.org/Archives/Public/public-html/2007Jul/0387.html>


-- 
Sander Tekelenburg
The Web Repair Initiative: <http://webrepair.org/>
Received on Friday, 6 July 2007 19:13:11 UTC

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