- From: <bugzilla@jessica.w3.org>
- Date: Thu, 15 Mar 2012 23:23:41 +0000
- To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=10896
Travis Leithead [MSFT] <travil@microsoft.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P2 |P1
CC| |travil@microsoft.com
Severity|normal |major
--- Comment #4 from Travis Leithead [MSFT] <travil@microsoft.com> 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.)
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 15 March 2012 23:23:43 UTC