Re: New SC: Avoid disrupting working accessibility features

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

Received on Friday, 15 July 2016 16:08:09 UTC