W3C home > Mailing lists > Public > public-html-a11y@w3.org > August 2010

[Bug 10455] Mint a describedby attribute for the img element

From: <bugzilla@jessica.w3.org>
Date: Mon, 30 Aug 2010 16:07:39 +0000
To: public-html-a11y@w3.org
Message-Id: <E1Oq6tX-0001bV-DI@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10455





--- Comment #26 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>  2010-08-30 16:07:38 ---
(In reply to comment #24)
> what is there about "long description" that implies this item is going
> to be an exact text equivalent of the image, and not a longer caption?

What implies to Opera users that the context menu item called "Long
Description" points to an equivalent?

If you're just saying we should come up with a better term to use as UI text,
feel free to try.

As to what tells the user agent that it's a long description, that's the
purpose of an RDFa annotation.

> For all of the talk about the importance of "semantics" in HTML5, and having
> semantic equivalents for this and that, why on earth would we then remove an
> attribute that does have a specific "semantic" meaning? 

This bug is not about the removal of an attribute, but the addition of one.

> Expected means "likely to happen". I expect the UAs to implement the renderings
> in the section.

[snip]

> People are going to see EXPECT, and their expectations are going to be set. I
> would expect that most UAs would understand this, and act accordingly. UAs
> should have enough sense to know that when customer expectations are set, they
> better meet them.

If you say so, but people's "expectations" do not change what is required for
conformance.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 30 August 2010 16:07:40 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:13 UTC