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.


From HTML accessibility task force Wiki
Jump to: navigation, search

Access Key Replacement

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.

Access/Accesskey References

XHTML Access Module


Discussions in Related Fora

User Agent Accessibility Guidelines Working Group

Discussions and Position Papers Delivered to non-WAI W3C Fora

The Developer's and Author's Perspective

Dissenting Opinions

Email Threads