W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2012

Re: Requesting Clarification re CR Exit Stacks Criteria

From: Maciej Stachowiak <mjs@apple.com>
Date: Thu, 20 Sep 2012 16:15:19 -0700
Cc: 'Janina Sajka' <janina@rednote.net>, 'HTML Accessibility Task Force' <public-html-a11y@w3.org>
Message-id: <880FEF54-51B1-4D6D-982E-16CEBAEF73C6@apple.com>
To: John Foliot <john@foliot.ca>

On Sep 20, 2012, at 3:48 PM, John Foliot <john@foliot.ca> wrote:

> Maciej Stachowiak wrote:
>> 
>> In my opinion, two different,
>> independent browsers talking to two different, independent assistive
>> technologies would count as independent even if they used the same
>> accessibility API as a connecting layer, so long as that API is just a
>> general-purpose interface and does not itself materially relate to
>> implementing the feature.
> 
> Hi Maciej,
> 
> So to press a point, in your opinion JAWs + IE _and_ Firefox + WindowEyes
> supporting an attribute would count, where-as JAWS + IE and JAWS + Firefox
> would not.
> 
> Further, even if neither Firefox nor IE, standing alone, did anything more
> than expose the attribute to the AAPI, as long as 2 independent screen
> readers delivered the proscribed functionality, it would be deemed
> successful.
> 
> Have I summarized that correctly?


That's my understanding of the CR exit criteria, assuming the implementation conformance requirements for a feature are in fact fulfilled by such combos. No promises that others would see it the same way, though I feel my interpretation is pretty sensible.

Regards,
Maciej
 
Received on Thursday, 20 September 2012 23:15:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 20 September 2012 23:15:44 GMT