Re: Proposed new Customizationof shortcut SCs to reduce risk of accidental voice activation

The last modification was 8 days ago
https://www.w3.org/Bugs/Public/show_activity.cgi?id=13576


Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*
Tel:  613.235.4902

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

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>

On Thu, Jul 28, 2016 at 2:51 PM, Jeanne Spellman <
jspellman@spellmanconsulting.com> wrote:

> Kim just pointed out that the dates on this were 2011 and 2013.  :(
>
> So it's dead, for all practical purposes.  I should have read it more
> carefully.
>
> On 7/28/2016 9:39 AM, Jeanne Spellman wrote:
>
> 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>
>
>
>