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

[Bug 10481] Default role of <IMG> should be "img"

From: <bugzilla@jessica.w3.org>
Date: Wed, 08 Sep 2010 10:15:42 +0000
To: public-html-a11y@w3.org
Message-Id: <E1OtHgs-0006N6-Nb@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10481


steve faulkner <faulkner.steve@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |




--- Comment #5 from steve faulkner <faulkner.steve@gmail.com>  2010-09-08 10:15:42 ---
(In reply to comment #4)
> I doublechecked the data for a Flickr page and the photo page I tested has 35
> <img> tags.
> All images 2500 pixels in size and larger were thumbnails or other content
> stuff (maps and the real photos).. perhaps the role should be applied based on
> photo size? That seemed flawed, as well.
> Opt-in for the role=img is certainly a bummer, but I think it's fair to say the
> role=img semantics wouldn't be accurate for most <img> elements.

We all know that table/td/tr are widely abused and so why not prohibit user
agents from providing the mappings for these elements to accessibility APIs?

Assistive technology (screen readers) generally offer a range of preferences to
users on how they want the UI presented to them aurally. By not providing the
role information via an accessibility API users are being denied the choice.

image role information provides necessary context to the text alternative for
vision impaired users (not just blind).

-- 
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 Wednesday, 8 September 2010 10:15:44 UTC

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