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

> So it's dead, for all practical purposes.

Errr... yes and no.

Some of us have continued to discuss how to make accesskey useful in
today's browsers, and Chaals (McCathie Nevile) has gone as far as writing
up a draft proposal (http://chaals.github.io/accesskey/index.src.html) that
is looking for support and 'sponsorship'. For this to move forward, we'll
need to get browser vendor support.

At the heart of the proposal is the ability for users to create their own
custom bindings, that also includes a string value, which could be mapped
to speech input. I also vaguely recall Chaals talking about possibly
mapping accesskey/shortcuts to custom gestures as well (huge benefit to
mobile), but I'll let him weigh in there.

I'm not 100% sure how to map this draft proposal and new WCAG Success
Criteria into a cohesive whole (I've not spent any time thinking on it),
but I think we should continue to watch this, and continue the discussion.
However, I also note (with some sadness, but also relief) that accesskeys
have not been that widely adopted, due to other issues around the use of
the @accesskey attribute (most notably the lack of discoverability).

See also: https://www.w3.org/WAI/PF/HTML/wiki/Accesskey

JF


On Thu, Jul 28, 2016 at 1: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>
>
>
>


-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion