Re: New SC: Avoid disrupting working accessibility features

don't we already have that?

* Non-Interference:* If technologies
<https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#technologydef> are
used in a way that is not accessibility supported
<https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#accessibility-supporteddef>,
or if they are used in a non-conforming way, then they do not block the
ability of users to access the rest of the page. In addition, the Web page
<https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#webpagedef> as
a whole continues to meet the conformance requirements under each of the
following conditions:

   1.

   when any technology that is not relied upon
   <https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#reliedupondef>
is
   turned on in a user agent,
   2.

   when any technology that is not relied upon is turned off in a user
   agent, and
   3.

   when any technology that is not relied upon is not supported by a user
   agent

In addition, the following success criteria apply to all content on the
page, including content that is not otherwise relied upon to meet
conformance, because failure to meet them could interfere with any use of
the page:

   -

   *1.4.2 - Audio Control*,
   -

   *2.1.2 - No Keyboard Trap*,
   -

   *2.3.1 - Three Flashes or Below Threshold*, and
   -

   *2.2.2 - Pause, Stop, Hide*.


Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*
Tel:  613.235.4902

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

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

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, Jul 15, 2016 at 12:07 PM, Alastair Campbell <acampbell@nomensa.com>
wrote:

> Hi Sailesh,
>
> That’s an interesting idea, I get the goal, but I’m not sure about the
> practicalities.
>
> Just taking keyboard-use as one example, as a developer, would I have to
> know all the keyboard short cuts of all operating systems and all screen
> readers before applying keyboard commands to a web application?
>
> It sounds like something that would apply to a closed platform (e.g. iOS)
> rather than the web.
>
> I’m open to examples, but at first glance (on a Friday afternoon 5 minutes
> before leaving) I can’t see how it would be possible.
>
> Kind regards,
>
> -Alastair
>
> On 15/07/2016, 16:46, "Sailesh Panchang" <sailesh.panchang@deque.com>
> wrote:
>
>     An SC is needed along the lines of:
>     • 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.
>     [Ref: S508 1194.21 Para (b) Softtware Apps]
>
>     This is relevant because authors misapply techniques or  implement
>     them incorrectly / incompletely leading to confusion  and
>     inconsistencies.
>
>     Thanks,
>     Sailesh Panchang
>
>
>
>