W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2012

Any thoughts on this?

From: Travis Leithead <travis.leithead@microsoft.com>
Date: Fri, 16 Mar 2012 21:05:17 +0000
To: Doug Schepers <schepers@w3.org>
CC: "www-dom@w3.org" <www-dom@w3.org>
Message-ID: <9768D477C67135458BF978A45BCF9B3838280AE7@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
Bug 10896<https://www.w3.org/Bugs/Public/show_bug.cgi?id=10896>. Accessibility requirements, assigned to you.



Should I assign this to myself? Are you planning on taking action on this one?



Here's my recent comment on the bug:



Travis Leithead [MSFT] 2012-03-15 23:23:39 UTC

--DOM3 Events--Last Call Bugs Review--



I'm concerned with adding these Accessiblity APIs (how I understand

requirements EV1-4) alongside the other APIs described in this document [DOM3

Events], primarily becuase the conformance criteria for the existing APIs in

this spec relate to browsers and script engine interop in particular, and the

accessibility APIs for event inspection and dispatch would belong to a whole

different conformance criteria.



In short, I wouldn't expect to see the accessibility APIs (if defined herein)

available to a browser's scripting engine, nor would I expect them to be

testable using the same techniques employed for the APIs already described in

this spec.



If accessibility APIs were added to this spec, how would they be tested and

verified?



To me these requirements seem so distinct as to merit a document all their own.



Would love to hear feedback. Have there been new developments since this bug

was filed? (This bug was filed just under a year and a half ago.)
Received on Friday, 16 March 2012 21:05:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:09 GMT