RE: Question about aria-roledescription in the 1.1 spec

Okay, I'll make note of that.

One problem I'm facing now though is that we have compliance checker algorithms for some automated tools, and currently these can match roles with required versus supporting attribute combinations with a relatively high percentage of accuracy.

The use of aria-roledescription however is impossible to validate, because it can literally include anything, making it impossible to detect until after it hits production.




Bryan Garaventa
Accessibility Fellow
SSB BART Group, Inc.
bryan.garaventa@ssbbartgroup.com
415.624.2709 (o)
www.SSBBartGroup.com

-----Original Message-----
From: Rich Schwerdtfeger [mailto:richschwer@gmail.com] 
Sent: Friday, September 30, 2016 4:38 AM
To: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
Cc: ARIA Working Group <public-aria@w3.org>
Subject: Re: Question about aria-roledescription in the 1.1 spec

Bryan,

1. The underlying role and label are still preserved with roledescripton. It should seldom be used unless absolutely necessary, such as what a reacher is referring to in a class (pie slice) on a role of option in a listbox. 

2. Roles are already localized by ATs

This property must be used sparingly.

Rich



Sent from my iPad

> On Sep 29, 2016, at 5:03 PM, Bryan Garaventa <bryan.garaventa@ssbbartgroup.com> wrote:
> 
> Hi,
> I've been reading through the spec because I have to write up internal guidelines for these things, and in reading aria-roledescription something jumped out at me.
> 
> Historically we've always said to developers don't put the role of an element in a label, like so:
> 
> <button aria-label="Attachment button"></button>
> 
> So, I'm not clear on how this is meant to be different, here is an excerpt from the 1.1 spec for aria-roledescription:
> 
> The following examples show the use of aria-roledescription to indicate that a button in a web-based email client is associated with an "attachment."
> 
> Example 27
> <div role="button" tabindex="0" aria-roledescription="attachment 
> button">family_reunion.jpg</div> Example 28 <button 
> aria-roledescription="attachment button">family_reunion.jpg</button>
> 
> http://www.w3.org/TR/wai-aria-1.1/#h-aria-roledescription
> 
> So is the guidance always for the use of this attribute to reflect the underlying role? What happens if developers don't?
> 
> 
> 
> Bryan Garaventa
> Accessibility Fellow
> SSB BART Group, Inc.
> bryan.garaventa@ssbbartgroup.com
> 415.624.2709 (o)
> www.SSBBartGroup.com
> 
> 
>

Received on Friday, 30 September 2016 16:45:22 UTC