Re: ISSUE-636 ACTION-1398 Provide spec. text for aria-roledescription

Hi again. :)

On 04/03/2014 04:15 PM, James Craig wrote:
> On Apr 3, 2014, at 12:10 PM, Joanmarie Diggs <jdiggs@igalia.com> wrote:

> Thank you for clarifying and I agree. Perhaps we can limit usage (or recommend against usage) of @role and @aria-roledescription on elements where there is no one-to-one mapping to an ARIA role. <video> is currently one of these cases.

I think this would be an excellent limitation (or recommendation). Thanks!!

> The tokenized role approach is already available in ARIA 1.0. In other words, you can do role="button link" and the computed role will be button. If and when the video roles is standardized, authors will be able to use role="video group" the way you've described.

I understand that it will work, but here's what I'm asking you to
consider: <div role="video group" aria-roledescription="video"> as
something allowable *today*.

Now I realize that we do NOT want to allow or encourage web devs to be
able to put anything they feel like as the first role. But if it is
restricted somehow, perhaps to:

* Things we are pretty certain will be roles, and
* Things which are already part of the host language

Then we could handle some of these cases for ATK now, and do so without
breaking anything for the other platforms. And if web developers did
that in their apps now, it would continue to work when it is a valid
ARIA role.

If allowing the above *now* is not acceptable because video is not a
valid role yet, the only other idea I have is to provide some way to
specify as an attribute what the equivalent element tag would be.

>> Again, my sincerest apologies for any offense I may have caused.
> 
> No offense taken. Mutual apologies for the misunderstanding. Welcome to the W3C mailing lists, where many things are misconstrued, but we usually end up with the right solution. ;-)
> 

Thank you James. :)

--joanie

Received on Thursday, 3 April 2014 20:58:18 UTC