Re: Native keyboard support based on roles

The only thing I would caution people to think about is that we will want
web apps to respond to more than just the keyboard. This should be done in
a device independent way and the user agent should for the platform should
really perform the device bindings if possible. What if someone wanted a
standard gesture or voice command?



Rich Schwerdtfeger



From:	Léonie Watson <lwatson@paciellogroup.com>
To:	"WAI Protocols & Formats" <public-pfwg@w3.org>
Date:	12/15/2014 06:27 AM
Subject:	Native keyboard support based on roles



Hello,

When a custom control is created, would it be possible for a browser to
provide the expected keyboard support based on the presence of an explicit
role? For example a custom control with role="button" would automatically
be given the same interaction support as a native <button>.

If this were possible it could be beneficial to authors (who would not then
need to provide additional scripted behaviour), and beneficial to
accessibility because it would encourage authors to apply the correct
semantics to the control.

Léonie.


--
Senior Accessibility Engineer, TPG
@LeonieWatson @PacielloGroup

Received on Tuesday, 16 December 2014 02:31:33 UTC