W3C home > Mailing lists > Public > wai-xtech@w3.org > April 2012

Fwd: Re: Alternative to @aria-describedAT: <a role=img>

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Mon, 9 Apr 2012 15:46:56 +0200
To: wai-xtech <wai-xtech@w3.org>
Message-ID: <20120409154656150469.564ac361@xn--mlform-iua.no>
Forward to the list - due to address error.

----- Begin forwarded message -----
From: Alexander Surkov <surkov.alexander@gmail.com>
Date: Mon, 9 Apr 2012 11:51:48 +0900
Subject: Re: Alternative to @aria-describedAT: <a role=img>
To: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Cc: Leif Halvard Silli <xn--mlform-iua@målform.no>, "wai-xtech@w3.org" 
<faulkner.steve@gmail.com>
In-Reply-To: 
<CAEhSh3d7_PYJ4Q4T73V6=q=s4ZWw0vszD1e4V_vDC0vP32VgCw@mail.gmail.com>

Hi, Benjamin.

<a role=img href> is a real edge case and it doesn't sound a good ARIA
use case. See 
http://www.w3.org/WAI/PF/aria-implementation/#mapping_conflicts

"WAI-ARIA roles, states, and properties are intended to add semantic
information when native host language elements with these semantics
are not available, and are generally used on elements that have no
native semantics of their own."

Also look at:
"user agents MUST use the semantic of the WAI-ARIA role for
processing, not the native semantic, unless the role requires WAI-ARIA
states and properties whose attributes are explicitly forbidden on the
native element by the host language"

<a role="img" href> is not described case but the most interesting
part that ARIA doesn't require to ignore the native semantics blindly.
It sounds reasonable with me if ARIA would add or extend native
semantics rather than completely remove it. From the user/web author
point of view I don't see any benefits that AT users see an image but
sighted users see a normal link.

Thanks.
Alex.


On Sat, Apr 7, 2012 at 4:53 PM, Benjamin Hawkes-Lewis
<bhawkeslewis@googlemail.com> wrote:
> On Sat, Apr 7, 2012 at 6:50 AM, Alexander Surkov
> <surkov.alexander@gmail.com> wrote:
>> <a role=img href>
>> role is html:a accessbile is image, action is "jump" since it's a
>> still link after all.
> 
> Woah. Is it?
> 
> "When a WAI-ARIA role is provided, user agents MUST use the semantic
> of the WAI-ARIA role for processing, not the native semantic"
> 
> http://www.w3.org/WAI/PF/aria/host_languages#host_general_conflict

> 
> Steve, I reckon the mapping of actions from implicit semantics when an
> ARIA role is overriding those semantics would be a critical aspect to
> cover in your implementation guide.
> 
> Bug filed:
> 
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=16656

> 
> 
> 
> --
> Benjamin Hawkes-Lewis
Received on Monday, 9 April 2012 13:47:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 13:16:16 GMT