This section is normative.
This module defines the Role attribute collection and the access element.
|access||Common, key, targetid, targetrole||EMPTY|
The access element assigns an accessibility mapping to elements within a document. Actuating the shortcut results in the element gaining focus.
The invocation of access keys depends on the implementation. For instance, on some systems one may have to press the "alt" key in addition to the access key. On other systems, one generally has to press the "cmd" key in addition to the access key.
The rendering of access keys depends on the user agent. We recommend that authors include the access key in label text or wherever the access key is to apply. User agents should render the value of an access key in such a way as to emphasize its role and to distinguish it from other characters (e.g., by underlining it).
If a targetid and a targetrole are both specified for an element, the targetid attribute value must take precedence.
Access element that focuses into a field
<access key="s" title="Social Security Number" targetrole="ss:number" />
Accessing a table of contents
<access key="c" title="Table of Contents" targetrole="toc" />
Access that moves to the main content
<access key="m" title="Main content" targetrole="main" />
Access element that goes to a specific element
<access key="u" title="Username" targetid="username" />
<nl role="wai:sitemap"> <li href="downloads">Downloads</li> <li href="docs">Documentation</li> <li href="news">News</li> </nl>
Additional roles may be defined through the use of this attribute. Roles shall be defined as qnames referencing RDF definitions for them. The RDF definition can be used define what the object is, how you would interact with it, how it relates to other elements, and what other objects it is like or sub classes. This defines the basis for taxonomies defined amongst common sets of document elements. For example, dynamic web content often recreates GUI widgets using combinations of web page elements, style sheets, and script thus applying different meaning to the elements. This has benefits for the intraction between web content, user agents, and assistive technologies by providing for a discoverable interaction model. For example, this model can be used to allow a screen reader to provide a speech interface based on real semantics. The user agent could use the information to create device navigation mappings.
Authors may use the following relationship names, listed here with their conventional interpretations. User agents, search engines, etc. may interpret these relationships in a variety of ways. For example, user agents may provide access to linked documents through a navigation bar.
Users may extend this collection of relationships. However, extensions must be defined in their own namespace, and the relationship names must be referenced in documents as qualified names (e.g., dc:creator for the Dublin Core "creator" relationship).
The following attributes will be standard. They are designed to define pertinent parts of a document for the purpose of accessibility. User agents may incorporate device equivalents, such as key mappings in the case of a desktop user agent, to navigate to these sections of a document.