Re: suggestions for new roles and properties in ARIA next

If role="presentation" is provided then alt="" should not be required. They
are the same thing. If alt="" is set then nothing is rendered of value when
images are turned off.

It is so much cleaner to have alt="" = role="presentation"

Rich Schwerdtfeger
CTO Accessibility Software Group



From:	Steve Faulkner <faulkner.steve@gmail.com>
To:	James Craig <jcraig@apple.com>
Cc:	W3C WAI-XTECH <wai-xtech@w3.org>, Richard
            Schwerdtfeger/Austin/IBM@IBMUS
Date:	04/20/2011 05:56 AM
Subject:	Re: suggestions for new roles and properties in ARIA next



Hi james,

>> Seconded, but this example would probably need aria-label, because
overriding the img role means the alt attribute is now meaningless. Agreed?

My thinking is that for graphical user agents its still an image, and
it will still need alt for that purpose. also they generally map alt
to the accessible name property in APIs, so why require an additional
aria-label that does the same thing?

>Kind of seems like you're stretching description to support the semantics
of @summary and maybe @longdesc. What makes you certain this necessary?

my thinking is that there are use cases where a developer would want
to provide info to AT users which is redundant for non AT users, but
is more a description than a name. having to place this information
somewhere else and then refernece via describedby can be a pain.

I don't think this is a replacement or alternative for longdesc as it
does not provide a structured content laternative and it cannot point
to an external resource.


>Associated how? aria-describedby? aria-labelledby? If so, why is the role
necessary? This reminds me of the label role that was previously removed
from ARIA.

I would think the relationship can be implemented in the browser
if a table has a child caption = accessible name
if a figure has a child caption = accessible name

the usefulness of the role would be in being able to identify the
caption as a caption, especially for images in figure


BTW these suggestions were only that, not particularly thought out.

regards
Stevef

On 20 April 2011 03:19, James Craig <jcraig@apple.com> wrote:
> I second your nomination of the text and disclosure roles, but have a few
comments and questions inline.
>
>
> On Apr 19, 2011, at 1:29 PM, Steve Faulkner <faulkner.steve@gmail.com>
wrote:
>
>> a few suggestions for ARIA next
>>
>> role="text"
>> when a non text object has a role of text , its to be treated as text.
>> example use:
>>
>> My <img src="heart.png" alt="heart" role="text"> breaks.
>
> Seconded, but this example would probably need aria-label, because
overriding the img role means the alt attribute is now meaningless. Agreed?
>
>
>> provides a way convey an objects text alternative without exposing its
role.
>>
>>
>> role="disclosure"
>> a disclosure widget (http://en.wikipedia.org/wiki/Disclosure_widget)
>>
>> HTML5 has a disclosure widget (details/summary) and they are common in
web apps.
>
> Seconded.
>
>> aria-description="text"
>>
>> like aria-label except it maps to the acc description in accessibility
APIs
>>
>> provides a means of including an extended text description internal to
>> an element , could be used in place of table summary attribute. for
>> images when an accessible name is not provided but a description is.
>
> Kind of seems like you're stretching description to support the semantics
of @summary and maybe @longdesc. What makes you certain this necessary?
>
>
>> role="caption"
>> identifies text inside an element as a caption for an associated
>> object such as a table or image
>
> Associated how? aria-describedby? aria-labelledby? If so, why is the role
necessary? This reminds me of the label role that was previously removed
from ARIA.
>
>> provides a role for HTML elements such as table <caption> and figure
>> <figcaption>
>>
>>
>>
>>
>> --
>> with regards
>>
>> Steve Faulkner
>> Technical Director - TPG
>>
>> www.paciellogroup.com | www.HTML5accessibility.com |
>> www.twitter.com/stevefaulkner
>> HTML5: Techniques for providing useful text alternatives -
>> dev.w3.org/html5/alt-techniques/
>> Web Accessibility Toolbar -
www.paciellogroup.com/resources/wat-ie-about.html
>>
>



--
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar -
www.paciellogroup.com/resources/wat-ie-about.html