RE: System Assistive Technology...

In addition, the Section 508 refresh indicates the following:
502.2.2 No Disruption of Accessibility Features. Applications shall not disrupt platform features that are defined in the platform documentation as accessibility features.

But what I think is missing from the refresh and the EN301-549 which the original Section 508 included was “products that are identified as accessibility features,”  That is non-platform assistive technologies such as screen readers when using documented methods should also not be disrupted.

We need to ensure that AT that is not included with the platforms is not disrupted as well.  This is a slight difference but IMO an important one.

Jonathan

--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>
Phone 703.637.8957
Follow us: Facebook<http://www.facebook.com/#!/ssbbartgroup> | Twitter<http://twitter.com/#!/SSBBARTGroup> | LinkedIn<http://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog> | Newsletter<http://eepurl.com/O5DP>

From: David MacDonald [mailto:david100@sympatico.ca]
Sent: Wednesday, October 28, 2015 11:25 AM
To: ALAN SMITH
Cc: Michael Pluke; Alistair Garrison; public-mobile-a11y-tf@w3.org
Subject: Re: System Assistive Technology...

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



CanAdapt Solutions Inc.

Tel:  613.235.4902

LinkedIn<http://www.linkedin.com/in/davidmacdonald100>

www.Can-Adapt.com<http://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<mailto: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<mailto:Mike.Pluke@castle-consult.com>
Sent: ‎Friday‎, ‎23‎ ‎October‎, ‎2015 ‎11‎:‎20‎ ‎AM
To: ALAN SMITH<mailto:alands289@gmail.com>, Alistair Garrison<mailto:alistair.j.garrison@gmail.com>, public-mobile-a11y-tf@w3.org<mailto: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> [mailto:alands289@gmail.com<mailto:alands289@gmail.com>]
Sent: 23 October 2015 15:18
To: Alistair Garrison <alistair.j.garrison@gmail.com<mailto:alistair.j.garrison@gmail.com>>; public-mobile-a11y-tf@w3.org<mailto: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<mailto:alistair.j.garrison@gmail.com>
Sent: ‎Friday‎, ‎23‎ ‎October‎, ‎2015 ‎10‎:‎08‎ ‎AM
To: public-mobile-a11y-tf@w3.org<mailto: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:40:30 UTC