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

Re: Default role of <IMG> should be "img"

From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Date: Mon, 13 Sep 2010 12:25:04 +0100
Cc: public-html-a11y@w3.org
Message-Id: <5C1BB07E-A286-4D4A-92E4-11349030D683@googlemail.com>
To: Steven Faulkner <faulkner.steve@gmail.com>
On 13 Sep 2010, at 11:04, Steven Faulkner wrote:
> "Better questions for getting screen reader user views on UI images might be:..."
>  
> yes many better questions could be asked, but I am fairly certain the screen reader users who responded (included a screen reader developer, yahoo accessibility evangelist, a developer working on drupal accessibility),  understood the intent of the question.

Sorry, but from my perspective they are extremely different questions, regardless of whom you asked.

> "<button><img alt="Edit" src="pencil.png"></button>"
> "because the button text would be represented as just button text in the accessibility tree rather than as an image with a text alternative?"
>  
> NO I would argue for the current behaviour:
> The accessible tree (can be viewed using firefox DOM inspector) looks like this:
>  
> - pushbutton > name > bottle
> -- graphic > name > bottle
> When an AT such as JAWS encounters the button announces the button role and its accessble name value (from the image alt text) it does not announce the image. BUT the image is not removed by the browser from the accessible tree.

Because of the way you snipped my message, it's somewhat difficult to determine what you're replying to.

Are you saying that given the input:

   <button class="edit">Edit</button>

   button.edit { content: url(pencil.png); }

The accessible tree (in ARIA terms) should be:

- button - name: Edit
-- image - name: Edit

rather than:

- button - name: Edit

(I realise ARIA doesn't specify what to do about replaced content yet, I'm just asking what you think it should specify.)

> When an AT such as JAWS encounters the button announces the button role and its
> accessble name value (from the image alt text) it does not announce the image.
> BUT the image is not removed by the browser from the accessible tree.

So  given the markup:

   <button><img src="pencil.png" alt="Edit"></button>

So does any AT under any configuration announce the image in this scenario? Do any users find that useful, and if so, what for?

--
Benjamin Hawkes-Lewis
Received on Monday, 13 September 2010 11:25:46 UTC

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