W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2012

Re: Action 712 (fast)

From: Jeanne Spellman <jeanne@w3.org>
Date: Thu, 12 Apr 2012 11:18:50 -0400
Message-ID: <4F86F25A.3080609@w3.org>
To: UAWG list <w3c-wai-ua@w3.org>
My rationale for the AA is that
* no browser is doing it currently (firebug extension is the only one I 
can think of)
* I don't see how it is a level 5 barrier - that it blocks people from 
information.  The information already isn't there, we are helping people 
to guess.  I would rate this as a level 3-4 barrier (according to our 
spreadsheet).

If we want UAWG to be accepted, we need to consider how many new level A 
SCs the browsers have to put into the feature development pipeline.  If 
we have too many, they ignore us, the way they did UAAG 1.0.

Please don't get me wrong, I think this is a great feature - 
particularly for photo web sites - but is this the feature we go to bat 
for and say, you MUST have this?  I'm open to that discussion, but that 
is why I said AA.

jeanne


On 4/12/2012 10:52 AM, Richards, Jan wrote:
> OK, so if it is A then it actually would go first.
>
> BTW: Another idea is to make use of "Accessibility Information", a defined term in ATAG 2.0 (http://www.w3.org/TR/2012/WD-IMPLEMENTING-ATAG20-20120410/#def-Accessibility-Information). Implementing ATAG 2.0 even includes an Appendix that clearly connects the term to the requirements of WCAG (http://www.w3.org/TR/2012/WD-IMPLEMENTING-ATAG20-20120410/#prompting-types).
>
> Cheers,
> Jan
>

-- 
_______________________________
Jeanne Spellman
W3C Web Accessibility Initiative
jeanne@w3.org
Received on Thursday, 12 April 2012 15:19:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 12 April 2012 15:19:49 GMT