- From: Jonathan Avila <jon.avila@ssbbartgroup.com>
- Date: Thu, 14 Apr 2016 16:33:27 +0000
- To: David MacDonald <david100@sympatico.ca>, Gregg Vanderheiden <gregg@raisingthefloor.org>
- CC: Chris McMeeking <chris.mcmeeking@deque.com>, "Patrick H. Lauke" <redux@splintered.co.uk>, "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
- Message-ID: <BY2PR03MB2721AD16A048A1D76629EF99B970@BY2PR03MB272.namprd03.prod.outlook.com>
Great job – I like it! That’s what I was trying to express last call but could not so eloquently say. Jonathan Jonathan Avila Chief Accessibility Officer SSB BART Group jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com> 703.637.8957 (Office) Visit us online: Website<http://www.ssbbartgroup.com/> | Twitter<https://twitter.com/SSBBARTGroup> | Facebook<https://www.facebook.com/ssbbartgroup> | Linkedin<https://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog/> Check out our Digital Accessibility Webinars!<http://www.ssbbartgroup.com/webinars/> From: David MacDonald [mailto:david100@sympatico.ca] Sent: Thursday, April 14, 2016 12:26 PM To: Gregg Vanderheiden Cc: Chris McMeeking; Patrick H. Lauke; public-mobile-a11y-tf@w3.org Subject: Re: Tweak 2.5.3 We've taken all the comments and revised the language of the Success Criteria 2.5.3 ===== 2.5.3 Up-Event Activation: Single touch and/or pointer activation triggers on the up-event, or has at least one of the following characteristics (Level A): - provides confirmation, - is reversible, - a mechanism is available to trigger on the up-event. Note: This is when platform assistive technology that remaps touch gestures is not turned on. Also have revised the understanding document and provided some alternative language for the SC. https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_revision_of_2.5.3 On Thu, Apr 7, 2016 at 12:12 PM, David MacDonald <david100@sympatico.ca<mailto:david100@sympatico.ca>> wrote: We've revised the proposed 2.5.3 Touch Up Activation. https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_revision_of_2.5.3#Proposed_2.5.3 On the call we felt it was ready to bring to the larger WCAG group for further consideration on April 26 On Fri, Apr 1, 2016 at 1:48 PM, David MacDonald <david100@sympatico.ca<mailto:david100@sympatico.ca>> wrote: +1 On Fri, Apr 1, 2016 at 11:59 AM, Gregg Vanderheiden <gregg@raisingthefloor.org<mailto:gregg@raisingthefloor.org>> wrote: The WCAG used the following formulation (if this is helpful to you ) The SC needs to be met by the web page with the assumption that the user is using commonly available AT and access features commonly available in browsers. The "programmatically determined” phrase is key to the AT support. Anything where the SC addressed a problem through AT - the term programmatically determined was use to cover both AT and access features in browsers. gregg On Apr 1, 2016, at 10:40 AM, Chris McMeeking <chris.mcmeeking@deque.com<mailto:chris.mcmeeking@deque.com>> wrote: You're correct, it is very relevant. However, not when considering whether a success criteria is a criteria or not. But, whether or not such a criteria is enforced on a given platform in a given situation, etc. If you want to go out there and test every criteria against all combinations of browsers (Chrome, Firefox, Safari, Internet Explorer (6, 7, 8, 9)) against all possible ATs (Jaws, NVDA, VoiceOver, ChromeVox, TalkBack, VoiceOver (iOS)) you are never going to have 100% compliance. Are you suggesting we scrap all of WCag because nobody can possible conform? On Fri, Apr 1, 2016 at 11:28 AM, Patrick H. Lauke <redux@splintered.co.uk<mailto:redux@splintered.co.uk>> wrote: On 01/04/2016 16:03, Chris McMeeking wrote: The user agent vs AT vs webpage/app as the "responsible party" for a conformance to a criteria I find irrelevant as it pertains to the formation of a criteria. Saying that the user agent "should be responsible" is all fine. That doesn't mean that it's not part of the criteria. But as the criteria are part of the Web Content guidelines, meaning that they're the responsibility of the web content developer to ensure, it IS relevant - if these are things that are simply out of the developer's control, or issues relating to global settings (which I don't believe can be successfully mandated for each and every site/app, or they'll simply be ignored), developers will not be able to satisfy the SC. Then what? P -- Patrick H. Lauke www.splintered.co.uk<http://www.splintered.co.uk/> | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com<http://redux.deviantart.com/> twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Thursday, 14 April 2016 16:33:59 UTC