RE: suggestions for new roles and properties in ARIA next

James Craig wrote:
> 
> >> 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.
> 
> Can you give a specific example (using real text, not lorem ipsum) of
> where this might be needed? I'd just like to come up with a defensible
> case that cannot be done another way, or one that would gain
> significant benefit over the alternative if done this way.

Hi James,

Taking a stab at this request:

<img
src="http://macdailynews.files.wordpress.com/2011/02/110201_nielsen_01.png
" alt="Line Graph - Mobile Operating System Share, US Q4 '09 - Q4 '10"
aria-description="The graph shows the rapid growth of Android from 2% to
27% market share, a 11% decline for Blackberry OS to 27%, and a relatively
flat pattern for iOS at 28% over a 14 month period.">

(image source:
http://macdailynews.com/2011/02/01/nielsen_q410_u-s-_mobile_os_market_shar
e_apple_ios_28_rim_blackberry_27_goo/) 

I note that data supplied in the aria-description - notably the before and
after percentages - are not spelled out in the associated article, as
those numbers are 'obvious' to sighted users reading the article. 

Would this meet your use-case request?

JF

Received on Wednesday, 20 April 2011 19:39:36 UTC