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

Re: unifying alternate content across embedded content element types

From: Andrew Sidwell <takkaria@gmail.com>
Date: Mon, 16 Jul 2007 03:24:32 +0100
Message-ID: <469AD6E0.4040800@gmail.com>
To: Robert Burns <rob@robburns.com>
CC: Smylers <Smylers@stripey.com>, public-html@w3.org

Robert Burns wrote:
> The issue I'm raising is not about that situation. Its about the
> situation when <object> contains long rich text. How then will a UA
> provide an @alt like rendering of that lengthy alternate text?

I think that gets to the root of the issue, and now we have a problem
statement: "It is unspecified how to find or create shortened fallback
text for the <object> element."

The first thing to find out if UA vendors want to do this.  If they
don't, then it's fairly pointless discussing how to.

Of those that do want to provide alt-like rendering, some may already
have an algorithm set up to produce such text.  That may be suitable for
inclusion into the specification, or it may be a point for UAs to
compete on, and thus not be suitable for standardisation yet.

Then some background info might be useful, e.g. how many pages with <img
alt="" longdesc=""> actually contain meaningful info in both attributes.
 This would be useful because it tells us how useful a new attribute or
element is likely to be other places where two equivalents are allowed.

BTW, how does one actually talk to the accessibility UA vendors?  It
would be nice to have somewhere where the HTML-WG could go to ask people
who know what they're talking about on such matters.

Andrew Sidwell
Received on Monday, 16 July 2007 02:24:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:02 GMT