Re: CFC - Changes to "Character Key Shortcuts"

Understood. First letter navigation was hashed out on the issue thread.

I don’t know if any example of first letter navigation that’s a single character key shortcut. You always have to do a non single key shortcut first to get to the dropdown with, for example, a Tab. So the command sequence for choosing Massachusetts, for example, would be “Tab”,  “m”. That’s not a single character shortcut and so does not cause any problem and is useful for speech users. They would have no need to be able to turn it off. If, however, a developer got the idea that it might be OK to use a single character key shortcut for focusing menu and allowed a user to navigate to a dropdown with, for instance, the single letter shortcut “s”, that would be a problem and would fall under the original wording. In my experience it really is that simple.

If anyone can find a real example of a single character key shortcut that drops down a menu please send it to me to test and I can post another example video — I can’t see how it would be similar to any other true single character key shortcut, but would be glad to show.

I think we should not add a phrase that isn't informed by a real example.

Cheers,
Kim

Kim Patch
scriven.com/kimpatch
PatchonTech.com




> On Nov 10, 2017, at 8:24 PM, David MacDonald <david100@sympatico.ca> wrote:
> 
> Hi Kim
> 
> I think what that last phrase is trying to address, is first letter navigation. Focus goes to a drop down to choose your state. When the drop down opens the user can hit the first letter to skip over lots of states.
> 
> But the first letter navigation is only active when the combo has focus, the rest of the time it is inactive. This is native behaviour of the HTML UI  https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_select 
> 
> It could be a lot of effort to force devs to over ride that behaviour.
> 
> Cheers,
> David MacDonald
>  
> CanAdapt Solutions Inc.
> Tel:  613.235.4902
> LinkedIn 
> twitter.com/davidmacd
> GitHub
> 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
> 
>> On Fri, Nov 10, 2017 at 1:26 AM, Kim Patch <kim@redstartsystems.com> wrote:
>> Good with the first two changes. The “unless... focus” change would be very bad for users. The background section of the understanding document addresses this. So do the videos. See the “Hey Kim” use case. This is a show stopper for speech users.
>> 
>> Cheers,
>> Kim
>> 
>> Kim Patch
>> scriven.com/kimpatch
>> PatchonTech.com
>> 
>> 
>> 
>> 
>>> On Nov 10, 2017, at 11:22 AM, Andrew Kirkpatrick <akirkpat@adobe.com> wrote:
>>> 
>>> Call For Consensus — ends Tuesday November 14th at 1:00am Boston time.
>>> 
>>>                                                                                                                     
>>> 
>>> The Working Group has discussed a change to the Character Key Shortcuts SC at TPAC.
>>> 
>>>  
>>> 
>>> The specific changes are detailed in this pull request: https://github.com/w3c/wcag21/pull/573
>>> 
>>>  
>>> 
>>> Call minutes: https://www.w3.org/2017/11/07-ag-minutes.html#item03
>>> 
>>>  
>>> 
>>> If you have concerns about this proposed consensus position that have not been discussed already and feel that those concerns result in you “not being able to live with” this decision, please let the group know before the CfC deadline.
>>> 
>>>  
>>> 
>>> Thanks,
>>> 
>>> AWK
>>> 
>>>  
>>> 
>>> Andrew Kirkpatrick
>>> 
>>> Group Product Manager, Accessibility
>>> 
>>> Adobe 
>>> 
>>>  
>>> 
>>> akirkpat@adobe.com
>>> 
>>> http://twitter.com/awkawk
>>> 
>>>  
>>> 
>>>  
>>> 
>