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/element versus module

From HTML accessibility task force Wiki
< Access
Revision as of 02:23, 20 May 2010 by Grosmai (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

The Access Element versus The XHTML Access Module

  • status of this page: this page is currently under construction; please bookmark and return often

Abstract

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.

Why Use The XHTML Access Module As the Basis for accesskey Replacement

Although this document is a first editor's draft, it is based on the Last Call Working Draft of the XHTML Access Module, produced by the XHTML 2 Working Group. The XHTML Access Module has been used as the basis of this document, as the XHTML Access Module reflects a consensus among the members of the XHTML2 Working Group, in conjunction with extensive input from the User Agent Accessibility Guidelines Working Group and others in the accessibility and standards community.

Drafts