This Wiki page is edited by participants of the HTML Accessibility Task Force. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Task Force participants, WAI, or W3C. It may also have some very useful information.
Access
From HTML accessibility task force Wiki
Access Key Replacement
Contents
Access (Key) Local Wiki Pages
- Accesskey Requirements from PFWG
- Access Element versus the Access Module
- "The Access Element defines an element that, when used in conjunction with XML and HTML derived markup languages, enables a more robust accessibility model than is presently possible. The Access Element also provides a means of designating a navigational flow for document formats, such as SVG, which lack an inherent navigational document order."
- Robert J. Burns' Keyboard Focus Attributes Module (page in progress)
- Defines a cascading keybinding mechanism, compatible with the XHTML Access Module and HTML. This proposal takes the powerful idea of cascade from stylesheets and applies those ideas to a cascading input device event binding mechanism where the user is ultimately in control, but where authors can provide powerful and discoverable key bindings to interact with their authored content. It also provide an alternate attribute to the "
key" attribute which is fairly limited in its use of characters rather than Qnames. The use of Qnames also makes Internationalization (i18n) easier to achieve.
- Defines a cascading keybinding mechanism, compatible with the XHTML Access Module and HTML. This proposal takes the powerful idea of cascade from stylesheets and applies those ideas to a cascading input device event binding mechanism where the user is ultimately in control, but where authors can provide powerful and discoverable key bindings to interact with their authored content. It also provide an alternate attribute to the "
Access/Accesskey References
XHTML Access Module
Accesskey
- accesskey in HTML 4.01
- WCAG 1.0, Checkpoint 9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. [Priority 3]
- For example, in HTML, specify shortcuts via the "accesskey" attribute.
- WCAG 2.0, Guideline 2.1: Keyboard Accessible: Make all functionality available from a keyboard
- accesskey in HTML5 (NOTE: accesskey was originally deprecated in the initial draft of HTML5 submitted to the W3C by the WHAT WG)
Discussions in Related Fora
User Agent Accessibility Guidelines Working Group
- Access Module Review on the UAWG Wiki
- Keyboard access discussion at 2008-10-02 UAWG Telecon
- input configuration in UAAG 2.0 Public Working Draft
Discussions and Position Papers Delivered to non-WAI W3C Fora
- Intent Based Events in Ubiquitous Web Applications charter
- WAI/Device Independence briefing at Backplane Workshop (2006)
The Developer's and Author's Perspective
- Robert J. Burns' Command and Event Module proposal, which incorporates material from the HTML5 document as well as the XHTML Access Module, including a cascade for keybindings and a truly tokenized replacement for the
keyattribute - User Defined Accesskeys (Juicy Studios)
- Greasemonkey Script to Manage Accesskeys (Juicy Studios)
Dissenting Opinions