RE: The two speech SCs

Ø  I would like to suggest we withdraw it so as to concentrate our attention on those that have a better chance.

David, that’s fine with me – but I’d like to defer to Kim who sponsored the SC to get her opinion on how we might change it to make it fit better.


Ø  basically a functional requirement which is not in line with normal SCs

As I understand it all of the WCAG 2 SC are functional requirements.  WCAG SC are not technical requirements.  I think what you are trying to say is that it’s an outcome based goal.

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/>
Download our CSUN Presentations Here!<http://info.ssbbartgroup.com/CSUN-2017_Gateway-Sig-Slide-Decks-2017.html>

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.

From: David MacDonald [mailto:david100@sympatico.ca]
Sent: Thursday, April 06, 2017 6:57 AM
To: public-mobile-a11y-tf@w3.org
Subject: The two speech SCs

We have two Speech SCs. I think the single key shortcut one is in a good position to be accepted. I've amended it to address concerns from comments without compromising its requirements.

> Single-character shortcuts are not used to activate a control, unless a mechanism is available to turn them off or remap them to shortcuts with two or more characters, except on components that are closed on page load and single key shortcuts are not enabled until the component is opened.
https://github.com/w3c/wcag21/issues/69


There will probably be some more word smithing as we approach next drafts but I think it has a good chance.

The non interference of speech basically says, everything has to work with speech. It is difficult to test, and is basically a functional requirement which is not in line with normal SCs. Comments on it have not been positive. I would like to suggest we withdraw it so as to concentrate our attention on those that have a better chance.


Cheers,
David MacDonald



CanAdapt Solutions Inc.

Tel:  613.235.4902

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

twitter.com/davidmacd<http://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>