Re: Add Character Key Shortcuts to Editor's Draft

Thanks for the vote Jason. In your comment you mention:

> If the user interface control that has focus (including its role) can 
> be "programmatically determined", then speech recognition systems can 
> implement a policy of not forwarding dictated text (e.g., as simulated 
> keystrokes) to the browser whenever the currently focused control is 
> not editable text. This working group should investigate (via 
> horizontal review from the ARIA Working Group or discussion with 
> speech technology developers, especially those who have implemented 
> ARIA already) whether platform accessibility APIs can be used, or 
> adapted, to fill this need.

While I think this may lead to a long wait, especially where the UA 
would have to add an extra loop of 'listening/distinguishing' between 
verbal commands that should be handled by the AT vs that which should be 
ignored. I wonder if the use of a modifier key would help. I don't know 
if we would have traction with speech AT vendors but in terms of the 
request for a process/horizontal or at least linking in the APA group 
for review I think this is reasonable - I'll bring it up at our 
co-ordination call.

Thanks

Josh

White, Jason J wrote:
>
> -1 for the reasons indicated in the survey and at the meeting.
>
> *From:* Andrew Kirkpatrick [mailto:akirkpat@adobe.com]
> *Sent:* Tuesday, June 6, 2017 11:07 PM
> *To:* WCAG <w3c-wai-gl@w3.org>
> *Subject:* CFC: Add Character Key Shortcuts to Editor's Draft
> *Importance:* High
>
> Call For Consensus — ends Thursday June 8 at 11:00pm Boston time.
>
> The Working Group has reviewed and approved a new Success Criterion 
> for inclusion in the Editor’s Draft: Character Key Shortcuts, at level 
> AA, with the goal of obtaining additional input external to the 
> working group.
>
> Survey results: 
> https://www.w3.org/2002/09/wbs/35422/character-key-issue69/results
>
> Call minutes: https://www.w3.org/2017/06/06-ag-minutes.html (after 
> resolution on approval process for understanding documents)
>
> The new SC can be reviewed here, in the context of the full draft:
>
> https://rawgit.com/w3c/wcag21/single-key-shortcuts_ISSUE-69/guidelines/#character-key-shortcuts
>
> 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, Standards and Accessibility
>
> Adobe
>
> akirkpat@adobe.com <mailto:akirkpat@adobe.com>
>
> http://twitter.com/awkawk
>
>
> ------------------------------------------------------------------------
>
> This e-mail and any files transmitted with it may contain privileged 
> or confidential information. It is solely for use by the individual 
> for whom it is intended, even if addressed incorrectly. If you 
> received this e-mail in error, please notify the sender; do not 
> disclose, copy, distribute, or take any action in reliance on the 
> contents of this information; and delete it from your system. Any 
> other use of this e-mail is prohibited.
>
>
> Thank you for your compliance.
>
> ------------------------------------------------------------------------

-- 
Joshue O Connor
Director | InterAccess.ie