- From: David MacDonald <david100@sympatico.ca>
- Date: Wed, 28 Oct 2015 11:24:59 -0400
- To: ALAN SMITH <alands289@gmail.com>
- Cc: Michael Pluke <Mike.Pluke@castle-consult.com>, Alistair Garrison <alistair.j.garrison@gmail.com>, "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
- Message-ID: <CAAdDpDYU5VqW3K_H55mGybYiR5afO_UOC1-wbY7JifXk7BztjA@mail.gmail.com>
I think this gives us a good area of exploration for our 2.5.1 (works with AT turned on) except it's in reverse... on iOS when AT is turned on it intercepts the regular gestures... so we'll have to navigate that... Cheers, David MacDonald *Can**Adapt* *Solutions Inc.* Tel: 613.235.4902 LinkedIn <http://www.linkedin.com/in/davidmacdonald100> www.Can-Adapt.com * Adapting the web to all users* * Including those with disabilities* If you are not the intended recipient, please review our privacy policy <http://www.davidmacd.com/disclaimer.html> On Fri, Oct 23, 2015 at 12:44 PM, <alands289@gmail.com> wrote: > Mike, > I like this wording as well. > > We should visit this topic at one of our meetings. > I’ll let Kathy make that call, though. > > Regards, > > Alan > > Sent from Windows Mail > > *From:* Michael Pluke <Mike.Pluke@castle-consult.com> > *Sent:* Friday, 23 October, 2015 11:20 AM > *To:* ALAN SMITH <alands289@gmail.com>, Alistair Garrison > <alistair.j.garrison@gmail.com>, public-mobile-a11y-tf@w3.org > > Hi > > > > A similar but slightly simpler wording is also provided in the EN 301 549 > standard (the European equivalent of the Section 508 refresh): > > > 11.4.2 No disruption of accessibility features > > Where software provides a user interface it shall not disrupt those > documented accessibility features that are defined in platform > documentation except when requested to do so by the user during the > operation of the software. > > > > Best regards > > > > Mike > > > > *From:* alands289@gmail.com [mailto:alands289@gmail.com] > *Sent:* 23 October 2015 15:18 > *To:* Alistair Garrison <alistair.j.garrison@gmail.com>; > public-mobile-a11y-tf@w3.org > *Subject:* Re: System Assistive Technology... > > > > Allistair, > > > > I like the wording. > > > > This would fit into our Mobile Techniques item M007. > > > > Any thoughts on me writing a similar paragraph into this technique? > > > > Sent from Windows Mail > > > > *From:* Alistair Garrison <alistair.j.garrison@gmail.com> > *Sent:* Friday, 23 October, 2015 10:08 AM > *To:* public-mobile-a11y-tf@w3.org > > > > Hi, > > > > We were talking about the disruption of "system assistive technology" > relating to swipe gestures. > > > > The following clause from VPAT contains some very similar concepts, albeit > about a slight different area… I just thought some of the wording could be > useful. > > > > All the best > > > > Alistair > > > > Alistair Garrison > > > > --- Copied from http://www.state.gov/m/irm/impact/126343.htm --- > > > Section 1194.21 Software Applications and Operating Systems - Detail > Voluntary Product Accessibility Template > > > > (b) Applications shall not disrupt or disable activated features of other > products that are identified as accessibility features, where those > features are developed and documented according to industry standards. > Applications also shall not disrupt or disable activated features of any > operating system that are identified as accessibility features where > the application programming interface for those accessibility features has > been documented by the manufacturer of the operating system and is > available to the product developer. >
Received on Wednesday, 28 October 2015 15:25:30 UTC