- From: Alexander Surkov <surkov.alexander@gmail.com>
- Date: Mon, 16 Jun 2014 10:21:18 -0400
- To: Richard Schwerdtfeger <schwer@us.ibm.com>
- Cc: Joseph Scheuhammer <clown@alum.mit.edu>, Protocols and Formats Working Group <w3c-wai-pf@w3.org>, PF <public-pfwg@w3.org>
- Message-ID: <CA+epNsc4-48F_KMuLwopFNQGPbfYOqDbTdif+_Upmxyd+eESFg@mail.gmail.com>
Hi, Rich. On Fri, Jun 13, 2014 at 1:58 PM, Richard Schwerdtfeger <schwer@us.ibm.com> wrote: > Hi Alex, > > I just saw this. Please make all posts to the public pfwg list (on cc > above). This list is member confidential. I seldom look at this list any > more. I happened to look out here and saw this post. We are supposed to > operate in the open with the new charter. :-) > If answer is supposed to be on public channel then would it be good to make ISSUE notification email sent to public list as well? Actually I just answer email to all not checking for specific addressee. > > 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. > > > .... so, if we have clickable children that are marked presentational this > should be considered an error condition and we should expose the > corresponding accessible to the AT. > ok, sounds good. How to bring this resolution into the spec? > > Please make sure you make these changes to SVG as well. > do you talk about implementation, right? or something that should addressed in the spec? > > Cheers, > > > Rich > > > Rich Schwerdtfeger > > [image: Inactive hide details for Alexander Surkov ---06/13/2014 08:15:19 > AM---Hi, Rich. Would it solve the problem if they were expose]Alexander > Surkov ---06/13/2014 08:15:19 AM---Hi, Rich. Would it solve the problem if > they were exposed in the tree? Thanks. > > From: Alexander Surkov <surkov.alexander@gmail.com> > To: Protocols and Formats Working Group <w3c-wai-pf@w3.org> > Date: 06/13/2014 08:15 AM > Subject: Re: PFWG-ISSUE-663: Presentational children of some widgets have > doclick actions if make presentational who handles the click [ARIA 1.1 > Implementation Guide] > ------------------------------ > > > > Hi, Rich. Would it solve the problem if they were exposed in the tree? > Thanks. > Alex. > > > On Mon, Jun 9, 2014 at 3:26 PM, Protocols and Formats Working Group Issue > Tracker <*sysbot+tracker@w3.org* <sysbot+tracker@w3.org>> wrote: > > PFWG-ISSUE-663: Presentational children of some widgets have doclick > actions if make presentational who handles the click [ARIA 1.1 > Implementation Guide] > > *https://www.w3.org/WAI/PF/Group/track/issues/663* > <https://www.w3.org/WAI/PF/Group/track/issues/663> > > Raised by: Richard Schwerdtfeger > On product: ARIA 1.1 Implementation Guide > > There are time where the author puts a doClick on a child of an > element with role="button". We should look at this for presentational > children. This was brought up by Freedom Scienfic > > > > >
Attachments
- image/gif attachment: graycol.gif
Received on Monday, 16 June 2014 14:21:45 UTC