- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Mon, 16 Jun 2014 11:30:17 -0400
- To: Richard Schwerdtfeger <schwer@us.ibm.com>, Alexander Surkov <surkov.alexander@gmail.com>, clown@alum.mit.edu
- CC: Protocols and Formats Working Group <w3c-wai-pf@w3.org>, PF <public-pfwg@w3.org>
On 2014-06-13 1:58 PM, Richard Schwerdtfeger wrote: > Yes, it would solve the problem if we were to expose the item in the > tree. In fact, we have a requirement that presentational items be > exposed if they have tabindex applied (are focusable). By exposing a > doClick function this would map to an API function that allows the AT > to click the item. For IA2 this would be an accessible action - > similar to if we had a doClick() on a focusable functions. In addition to the focus constraint, the Core-AAM (formerly UAIG) states that there must be an accessible in the a11y tree if the element fires an accessibility event [1] (second bullet). I assume the proposed doClick() causes a DOM click event, and that *always* causes an a11y event. Is that right? [1] http://www.w3.org/TR/2014/WD-core-aam-1.1-20140612/#include_elements -- ;;;;joseph. 'A: After all, it isn't rocket science.' 'K: Right. It's merely computer science.' - J. D. Klaun -
Received on Monday, 16 June 2014 15:30:46 UTC