Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation from Jeanne Spellman on 2016-07-28 (public-mobile-a11y-tf@w3.org from July 2016)

From: Jeanne Spellman <jspellman@spellmanconsulting.com>
Date: Thu, 28 Jul 2016 09:39:44 -0400
To: public-mobile-a11y-tf@w3.org
Message-ID: <131de4a2-9697-9454-8be8-fa8d10a30449@spellmanconsulting.com>

On 7/24/2016 4:30 PM, David MacDonald wrote:
> thought we might be interested in this... not sure if it affects the 
> issue or not... a proposal to let accesskeys accept strings.
>
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=13576
>

Nice job from GregL.  Even though is was marked as "Later", there was 
support from Hixie, which is a positive step.
<quote>

The plan is to do this in v2, once we've proved that the stuff in the spec already actually works. The idea is we'll define key labels to use in the attribute, as in accesskey="up". For sequences we might do something like "accesskey="x-s". To enable this future expansion, the spec currently limits values to one character.

I'm marking this LATER for now but will reopen this once browsers have more widely adopted what we have in the spec so far.

</quote>

Received on Thursday, 28 July 2016 13:40:21 UTC