962b2e63d01877c7eaa1350a26d194cb
Scripting is disabled and therefore
annotations cannot be shown.
<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="http://www.w3.org/StyleSheets/TR/base.css" type="text/css"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/MarkUp/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org" />
<title>XHTML Access Module</title>
<style type="text/css">
.dtd-code { font-family: monospace; background-color: #dfdfdf; white-space: pre; border: #000000; border-style: solid; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px}
code {
color: green;
font-family: monospace;
font-weight: bold;
}
h4 { color: #005A9C; background: white }
code.greenmono {
color: green;
font-family: monospace;
font-weight: bold;
}
.example {
border: solid green;
border-width: 2px;
color: green;
font-weight: bold;
margin-right: 5%;
margin-left: 0;
}
.bad {
border: solid red;
border-width: 2px;
margin-left: 0;
margin-right: 5%;
color: rgb(192, 101, 101);
}
div.navbar { text-align: center; }
div.contents {
background-color: rgb(204,204,255);
padding: 0.5em;
border: none;
margin-right: 5%;
}
.tocline { list-style: none; }
td { text-align: left }
.ins { background-color: yellow }
.del { background-color: yellow; text-decoration: line-through }
ul.acks { list-style: none }
p.issueTitle {
font-size: 150% ;
}
div.issue {
background-color: #cfc ;
border: none ;
margin-right: 5% ;
}
/* assertion styles */
.must, .mustnot, .required, .shall, .shallnot, .should, .recommended, .may, .optional {
font-style: italic ;
background-color: #FF8040 ;
}
</style>
<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css" />
</head>
<body>
<div class="head"><a href="http://www.w3.org/"><img height="48" width="72" alt="W3C" src="http://www.w3.org/Icons/w3c_home" /></a>
<h1><a id="title" name="title"> XHTML Access Module</a></h1>
<h2><a id="subtitle" name="subtitle"> Module to enable generic document accessibility</a></h2>
<h2><a id="w3c-doctype" name="w3c-doctype"> W3C Editor's Draft 24 October 2007</a></h2>
<dl>
<dt>This version:</dt>
<dd><a href="http://www.w3.org/MarkUp/2007/ED-xhtml-access-20071024">http://www.w3.org/MarkUp/2007/ED-xhtml-access-20071024</a></dd>
<dt>Latest version:</dt>
<dd><a href="http://www.w3.org/TR/xhtml-access">http://www.w3.org/TR/xhtml-access</a></dd>
<dt>Previous Editor's Draft:</dt>
<dd><a id='previousDraft' href='http://www.w3.org/MarkUp/2007/ED-xhtml-access-20070905'>http://www.w3.org/MarkUp/2007/ED-xhtml-access-20070905</a></dd>
<dt>Diff from previous Editor's Draft:</dt>
<dd><a href="xhtml-access-diff.html">xhtml-access-diff.html</a></dd>
<dt>Editors:</dt>
<dd><a href="mailto:Mark.Birbeck@x-port.net">Mark Birbeck</a>, <a href="http://www.x-port.net">x-port.net Ltd.</a></dd>
<dd><a href="mailto:shane@aptest.com">Shane McCarron</a>, <a href="http://www.aptest.com">Applied Testing and Technology, <abbr title="Incorporated">Inc.</abbr></a></dd>
<dd><a href="http://www.cwi.nl/~steven/">Steven Pemberton</a>, <a href="http://www.cwi.nl"><abbr lang="nl" xml:lang="nl" title="Centrum voor Wiskunde en Informatica">CWI</abbr></a>/<a href=
"http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup></dd>
<dd><a href="mailto:raman@google.com">T. V. Raman</a>, Google, Inc.</dd>
<dd><a href="mailto:schwer@us.ibm.com">Richard Schwerdtfeger</a>, IBM Corporation</dd>
</dl>
<p>This document is also available in these non-normative formats: <a href="xhtml-access.ps">PostScript version</a>, <a href="xhtml-access.pdf">PDF version</a>, <a href="xhtml-access.zip">ZIP
archive</a>, and <a href="xhtml-access.tgz">Gzip'd TAR archive</a>.</p>
<p>The English version of this specification is the only normative version. Non-normative <a href="http://www.w3.org/Consortium/Translation/">translations</a> may also be available.</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2007 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">
W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title=
"European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href=
"http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href=
"http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p>
</div>
<hr />
<h2><a id="abstract" name="abstract"> Abstract</a></h2>
<p>The XHTML Access module defines an element that, when used in conjunction with other XHTML modules, enables a more robust accessibility model than that found in traditional HTML.</p>
<h2><a id="status" name="status"> Status of This Document</a></h2>
<p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of
this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
<p>This document is an internal editors draft for development purposes. However, its content is based upon mature materials from [<a class="nref" href="#ref_XHTML2">XHTML2</a>] and is therefore
considered relatively mature.</p>
<p>This document has been produced by the <a class="member" href="http://www.w3.org/MarkUp/Group/">W3C HTML Working Group</a> (<em><a href="http://cgi.w3.org/MemberAccess/AccessRequest">Members
only</a></em>) as part of the <a href="http://www.w3.org/MarkUp/Activity">HTML Activity</a>. The goals of the HTML Working Group are discussed in the <a href="http://www.w3.org/2002/05/html/charter">
HTML Working Group charter</a>.</p>
<p> This document was produced by a group operating under the <a href="http://www.w3.org/TR/2002/NOTE-patent-practice-20020124">24 January 2002 CPP</a> as amended by the <a href=
"http://www.w3.org/2004/02/05-pp-transition">W3C Patent Policy Transition Procedure</a>. W3C maintains a <a rel="disclosure" href="http://www.w3.org/MarkUp/2002/Disclosures">public list of any patent
disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the
individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href=
"http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p>
<p>Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is
inappropriate to cite this document as other than work in progress.</p>
<p>Please report errors in this specification to <a href="mailto:www-html-editor@w3.org">www-html-editor@w3.org</a> (<a href="http://lists.w3.org/Archives/Public/www-html-editor/">archive</a>). It is
inappropriate to send discussion email to this address. Public discussion may take place on <a href="mailto:www-html@w3.org">www-html@w3.org</a> (<a href=
"http://lists.w3.org/Archives/Public/www-html/">archive</a>).</p>
<h1><a id="contents" name="contents"> Table of Contents</a></h1>
<div class="toc">
<ul class='toc'>
<li class='tocline'>1. <a href="#s_intro" class="tocxref">Introduction</a></li>
<li class='tocline'>2. <a href="#s_conformance" class="tocxref">Conformance Requirements</a>
<ul class="toc">
<li class='tocline'>2.1. <a href="#docconf" class="tocxref">Document Conformance</a></li>
<li class='tocline'>2.2. <a href="#hostconf" class="tocxref">Host Language Conformance</a></li>
<li class='tocline'>2.3. <a href="#uaconf" class="tocxref">User Agent Conformance</a></li>
</ul>
</li>
<li class='tocline'>3. <a href="#s_terms" class="tocxref">Terms and Definitions</a>
<ul class="toc">
<li class='tocline'>3.1. <a href="#sec_3.1." class="tocxref">Compact URIs</a>
<ul class="toc">
<li class='tocline'>3.1.1. <a href="#sec_3.1.1." class="tocxref">CURIE Syntax Definition</a></li>
</ul>
</li>
</ul>
</li>
<li class='tocline'>4. <a href="#s_access" class="tocxref">XHTML Access Module</a>
<ul class="toc">
<li class='tocline'>4.1. <a href="#sec_4.1." class="tocxref">The <code>access</code> element</a>
<ul class="toc">
<li class='tocline'>4.1.1. <a href="#sec_4.1.1." class="tocxref"><code>activate</code> = ( yes | no* )</a></li>
<li class='tocline'>4.1.2. <a href="#sec_4.1.2." class="tocxref"><code>key</code> = <span class="datatype"><a href="http://www.w3.org/TR/xhtml-modularization/abstraction.html#dt_Character">
Character</a></span></a></li>
<li class='tocline'>4.1.3. <a href="#sec_4.1.3." class="tocxref"><code>targetid</code> = <span class="datatype"><a href="http://www.w3.org/TR/xhtml-modularization/abstraction.html#dt_IDREF">
IDREF</a></span></a></li>
<li class='tocline'>4.1.4. <a href="#sec_4.1.4." class="tocxref"><code>targetrole</code> = <code>basic-curie</code></a></li>
</ul>
</li>
</ul>
</li>
<li class='tocline'>A. <a href="#a_Schema_definition" class="tocxref">Schema Implementation</a>
<ul class="toc">
<li class='tocline'>A.1. <a href="#a_schema_access" class="tocxref">Access Element Module</a></li>
</ul>
</li>
<li class='tocline'>B. <a href="#a_DTD_definition" class="tocxref">DTD Implementation</a>
<ul class="toc">
<li class='tocline'>B.1. <a href="#a_module_qname" class="tocxref">Qualified Names Module</a></li>
<li class='tocline'>B.2. <a href="#a_DTD_module_xhtml_hyperAttributes" class="tocxref">XHTML Access Module</a></li>
</ul>
</li>
<li class='tocline'>C. <a href="#a_DTD_example" class="tocxref">DTD Markup Language Example</a>
<ul class="toc">
<li class='tocline'>C.1. <a href="#a_example_DTD_content_model" class="tocxref">XHTML+Access Content Model Module</a></li>
<li class='tocline'>C.2. <a href="#a_example_DTD_driver" class="tocxref">XHTML+Access Driver Module</a></li>
</ul>
</li>
<li class='tocline'>D. <a href="#s_refs" class="tocxref">References</a>
<ul class="toc">
<li class='tocline'>D.1. <a href="#s_norm-refs" class="tocxref">Normative References</a></li>
<li class='tocline'>D.2. <a href="#s_other-refs" class="tocxref">Other References</a></li>
</ul>
</li>
<li class='tocline'>E. <a href="#s_acks" class="tocxref">Acknowledgments</a></li>
</ul>
</div>
<!--OddPage-->
<h1><a id="s_intro" name="s_intro">1. Introduction</a></h1>
<p><em>This section is informative.</em></p>
<p>This document contains a single module designed to be used to help extend the scope of XHTML-family markup languages into new environments. It has been developed in conjunction with the W3C's Web
Accessibility Initiative and other interested parties. It is designed to provide a generic mechanism for defining the relationship between document components and well-known accessibility
taxonomies.</p>
<!--OddPage-->
<h1><a id="s_conformance" name="s_conformance">2. Conformance Requirements</a></h1>
<p>This section is <em>normative</em>.</p>
<p>The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [<a class="nref" href=
"#ref_RFC2119">RFC2119</a>].</p>
<p>Note that all examples in this document are informative, and are not meant to be interpreted as normative requirements.</p>
<h2><a id="docconf" name="docconf">2.1. Document Conformance</a></h2>
<p>XHTML Access is not a stand-alone document type. It is intended to be integrated into other host languages such as XHTML. A conforming XHTML Access document is a document that requires only the
facilities described as mandatory in this specification and the facilities described as mandatory in its host language. Such a document must meet all the following criteria:</p>
<ol>
<li>
<p><span class="must">The document MUST conform to the constraints expressed in <a href="Overview.html#a_Schema_definition">Appendix A - Schema Implementation</a> or <a href=
"Overview.html#a_DTD_definition">Appendix B - DTD Implementation</a>, combined with the constraints expressed in its host language implementation.</span></p>
</li>
<li>
<p><span class="must">If the host language is not in the XHTML namespace, and the host language does not incorporate these modules into its own namespace, then the document MUST contain an <code>
xmlns</code> declaration for the XHTML RDFa namespace [<a class="nref" href="#ref_XMLNAMES">XMLNAMES</a>]</span>. The namespace for XHTML Access Module is defined to be <code>
http://www.w3.org/1999/xhtml</code>. An example start tag of a root element might look like:</p>
<div class="example">
<p>Example</p>
<pre>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" >
</pre>
</div>
</li>
</ol>
<h2><a id="hostconf" name="hostconf">2.2. Host Language Conformance</a></h2>
<p><span class="must">When XHTML Access is included in a host language, all of the facilities required in this specification MUST be included in the host language.</span> <span class="must">In
addition, the elements and attributes defined in this specification MUST be included in the content model of the host language.</span> <span class="must">Finally, XHTML Access requires the
availability of the XHTML Role Attribute Module [<a class="nref" href="#ref_XHTMLROLE">XHTMLROLE</a>] and of the Core Attribute Collection as defined in XHTML Modularization.</span></p>
<h2><a id="uaconf" name="uaconf">2.3. User Agent Conformance</a></h2>
<p><span class="must">A conforming user agent MUST support all of the features required in this specification.</span></p>
<!--OddPage-->
<h1><a id="s_terms" name="s_terms">3. Terms and Definitions</a></h1>
<p>This section is <em>normative</em>.</p>
<h2><a id="sec_3.1." name="sec_3.1.">3.1. Compact URIs</a></h2>
<p>In order to allow for the scoped expression of <code>targetrole</code> values, this specification uses a superset of of <span class="datatype"><a href=
"http://www.w3.org/TR/xhtml-modularization/abstraction.html#dt_QName">QName</a></span>s that allows the contraction of all URIs (QNames have a syntactic restriction on the sorts of URI that can be
contracted).</p>
<p>These Compact URIs are called CURIEs here.</p>
<h3><a id="sec_3.1.1." name="sec_3.1.1.">3.1.1. CURIE Syntax Definition</a></h3>
<em>Note that this syntax definition will ultimately be defined in an external document [<a class="nref" href="#ref_CURIE">CURIE</a>].</em>
<p>A basic CURIE is comprised of two components, a <em>prefix</em> and a <em>reference</em>. The prefix is separated from the reference by a colon (<code>:</code>).</p>
<pre>
<span id="P_curie">curie := [ [ prefix ] ':' ] reference</span>
prefix := <a href="http://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-NCName">NCName</a>
reference := irelative-ref (as defined in [<a class="nref" href="#ref_IRI">IRI</a>])
</pre>
<p><span class="must">The prefix value MUST be defined using the 'xmlns:' syntax specified in [<a class="nref" href="#ref_XMLNAMES">XMLNAMES</a>].</span></p>
<p><span class="must">If the prefix is omitted from a CURIE, the default value of http://www.w3.org/1999/xhtml MUST be used.</span></p>
<p><span class="must">A CURIE is a representation of a full IRI. This IRI is obtained by concatenating the IRI associated with the <code>prefix</code> with the <code>reference</code>. The result MUST
be a syntactically valid IRI [<a class="nref" href="#ref_IRI">IRI</a>]</span>.</p>
<p>The CURIE prefix '_' is reserved. <span class="should">For this reason, prefix declarations using '_' SHOULD be avoided by authors.</span></p>
<p><span class="may">Host languages MAY define additional constraints on these syntax rules when CURIES are used in the context of those host languages.</span> <span class="mustnot">Host languages
MUST NOT relax the CURIE syntax constraints defined in this specification.</span></p>
<!--OddPage-->
<h1><a id="s_access" name="s_access">4. XHTML Access Module</a></h1>
<p>This section is <em>normative</em>.</p>
<p>This module defines the <a class="eref" href="#edef_access">access</a> element.</p>
<table class="moduledef" border="1" summary="Elements and Attributes in Text Module">
<thead>
<tr>
<th>Element</th>
<th>Attributes</th>
<th>Minimal Content Model</th>
</tr>
</thead>
<tbody>
<tr>
<td><a class="eref" href="#edef_access">access</a></td>
<td><a class="csref" href="mod-attribute-collections.html#col_Common">Common</a>, <a class="aref" href="#adef_activate">activate</a>, <a class="aref" href="#adef_key">key</a>, <a class="aref" href=
"#adef_targetid">targetid</a>, <a class="aref" href="#adef_targetrole">targetrole</a></td>
<td class="content">EMPTY</td>
</tr>
</tbody>
</table>
<p>Implementations: <a href="#a_dmodule_access">XML DTD</a></p>
<h2><a id="sec_4.1." name="sec_4.1.">4.1. The <code>access</code> element</a></h2>
<p>The <a class="eref" href="#edef_access">access</a> element assigns an accessibility mapping to elements within a document. Actuating the mapping results in the element gaining focus or,
optionally, in some other event being delivered.</p>
<p><em>Attributes</em></p>
<h3><a id="sec_4.1.1." name="sec_4.1.1.">4.1.1. <code>activate</code> = ( yes | no* )</a></h3>
<p>The <a class="aref" href="#adef_activate">activate</a> attribute indicates whether a target element should be activated or not once it obtains focus. The default value for this attribute is "no",
indicating that the element will not be "activated".</p>
<h3><a id="sec_4.1.2." name="sec_4.1.2.">4.1.2. <code>key</code> = <span class="datatype"><a href="http://www.w3.org/TR/xhtml-modularization/abstraction.html#dt_Character">
Character</a></span></a></h3>
<p>This attribute assigns a key mapping to an access shortcut. An access key is a single character from the document character set. <strong>Note:</strong> Authors should consider the input method of
the expected reader when specifying an accesskey.</p>
<p>Triggering an access key defined in an access element changes focus to the next element in navigation order from the current focus that has one of the the referenced role or id values. Note that
it is possible to deliver alternate events via [<a class="nref" href="#ref_XMLEVENTS">XMLEVENTS</a>]. It is also possible to have the target element activated through the use of the <a class="aref"
href="#adef_activate">activate</a> attribute. Also, it is possible to associate additional event handlers with target which might then perform additional actions once focus is changed.</p>
<p><span class="mustnot">If neither a <code>targetrole</code> nor a <code>targetid</code> attribute are specified, the user agent MUST NOT define a mapping nor deliver any events.</span></p>
<p><span class="must">An <code>access</code> element must have either a <code>targetrole</code> or a <code>targetid</code> attribute specified.</span></p>
<p>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.</p>
<p>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).</p>
<p>The character assigned to a key, and its relationship to a <a class="aref" href="#adef_role">role</a> or <a class="aref" href="#adef_id">id</a> attribute, are a suggestion of the author. <span
class="may">User agents may provide mechanisms for overriding, disabling, or re-assigning keys.</span> <span class="must">In such user agents, user-specified assignments must take precendence.</span>
<span class="should">If no key attribute is specified, the user agent SHOULD assign a key.</span></p>
<div class="issue">We talk about the id attribute, but we might also need to accomodate xml:id. How can we do that consistently?</div>
<h3><a id="sec_4.1.3." name="sec_4.1.3.">4.1.3. <code>targetid</code> = <span class="datatype"><a href="http://www.w3.org/TR/xhtml-modularization/abstraction.html#dt_IDREF">IDREF</a></span></a></h3>
<p>The <a class="aref" href="#adef_targetid">targetid</a> attribute specifies an <span class="datatype"><a href="http://www.w3.org/TR/xhtml-modularization/abstraction.html#dt_IDREF">IDREF</a></span>
of the target element for the associated event (i.e., the node to which the event should be delivered).</p>
<h3><a id="sec_4.1.4." name="sec_4.1.4.">4.1.4. <code>targetrole</code> = <code>basic-curie</code></a></h3>
<p>The <a class="aref" href="#adef_targetrole">targetrole</a> attribute specifies space separated list if <code>basic-curie</code> that maps to an element with a <a class="aref" href="#adef_role">
role</a> attribute with the same value.</p>
<p><span class="may">If no <code>key</code> attribute is specified, the user agent may assign an appropriate device mapping.</span></p>
<p><span class="must">If a <a class="aref" href="#adef_targetid">targetid</a> and a <a class="aref" href="#adef_targetrole">targetrole</a> are both specified for an element, the <a class="aref" href=
"#adef_targetid">targetid</a> attribute value must take precedence.</span></p>
<div class="example">
<p>Access element that focuses into a field</p>
<pre>
<access key="s"
title="Social Security Number"
targetrole="ss:number" />
</pre>
</div>
<div class="example">
<p>Accessing a table of contents</p>
<pre>
<access key="c"
title="Table of Contents"
targetrole="toc" />
</pre>
</div>
<div class="example">
<p>Access that moves to the main content</p>
<pre>
<access key="m"
title="Main content"
targetrole="main" />
</pre>
</div>
<div class="example">
<p>Access element that goes to a specific element</p>
<pre>
<access key="u"
title="Username"
targetid="username" />
</pre>
</div>
<div class="example">
<p>Access element with no specific key mapping</p>
<pre>
<access title="Navigation bar"
targetrole="navigation" />
</pre>
</div>
<!--OddPage-->
<h1><a id="a_Schema_definition" name="a_Schema_definition">A. Schema Implementation</a></h1>
<p>This appendix is <em>normative</em>.</p>
<p>The schema implementation of XHTML Access Module conforms to the requirements defined in [<a class="nref" href="#ref_XHTMLSCHEMAMOD">XHTMLSCHEMAMOD</a>].</p>
<h2><a id="a_schema_access" name="a_schema_access">A.1. Access Element Module</a></h2>
<!-- INCLUDING SCHEMA SCHEMA/xhtml-access-1.xsd.mhtml -->
<pre class="dtd">
Module SCHEMA/xhtml-access-1.xsd not found!
</pre>
<!-- END OF FILE SCHEMA/xhtml-access-1.xsd.mhtml --><!--OddPage-->
<h1><a id="a_DTD_definition" name="a_DTD_definition">B. DTD Implementation</a></h1>
<p>This appendix is <em>normative</em>.</p>
<p>The DTD implementation of XHTML Access Module conforms to the requirements defined in [<a class="nref" href="#ref_XHTMLMOD">XHTMLMOD</a>]. Consequently, it provides a Qualified Names sub-module,
and a module file for the XHTML Access Module module defined in this specification.</p>
<h2><a id="a_module_qname" name="a_module_qname">B.1. Qualified Names Module</a></h2>
<pre class="dtd">
Module DTD/xhtml-access-qname-1.mod not found!
</pre>
<h2><a id="a_DTD_module_xhtml_hyperAttributes" name="a_DTD_module_xhtml_hyperAttributes">B.2. XHTML Access Module</a></h2>
<pre class="dtd">
Module DTD/xhtml-hyperAttributes-1.mod not found!
</pre>
<!--OddPage-->
<h1><a id="a_DTD_example" name="a_DTD_example">C. DTD Markup Language Example</a></h1>
<p>This appendix is <em>informative</em>.</p>
<p>This appendix includes an example of a markup language created using the modules in this specification, coupled with other modules from [<a class="nref" href="#ref_XHTMLMOD">XHTMLMOD</a>]. The
resulting markup language, "xhtml-access" is provided solely as an example, and does not represent an intended direction in terms of a formal markup language from the W3C.</p>
<p>The following sample demonstrates some simple uses of the access element within an xhtml-access document.</p>
<pre class="dtd">
Module DTD/examples/sample.xml not found!
</pre>
<p>The actual markup language is created by combining the basics of XHTML 1.1 and the modules in this specification. This is done by using a content model module, and then a driver module:</p>
<h2><a id="a_example_DTD_content_model" name="a_example_DTD_content_model">C.1. XHTML+Access Content Model Module</a></h2>
<pre class="dtd">
Module DTD/examples/xhtml-access-model-1.mod not found!
</pre>
<h2><a id="a_example_DTD_driver" name="a_example_DTD_driver">C.2. XHTML+Access Driver Module</a></h2>
<pre class="dtd">
Module DTD/examples/xhtml-access-1.dtd not found!
</pre>
<!--OddPage-->
<h1><a id="s_refs" name="s_refs">D. References</a></h1>
<p>This appendix is <em>normative</em>.</p>
<h2><a id="s_norm-refs" name="s_norm-refs">D.1. Normative References</a></h2>
<dl>
<dt>[<a id="ref_DOM2EVENTS" name="ref_DOM2EVENTS" class="normref">DOM2EVENTS</a>]</dt>
<dd>"<cite><a href="http://www.w3.org/TR/DOM-Level-2-Events/">Document Object Model (DOM) Level 2 Events Specification</a></cite>", W3C Recommendation, T. Pixley, <i><abbr title="editor">
ed.</abbr></i>, 13 November 2000.<br />
Available at: http://www.w3.org/TR/DOM-Level-2-Events/<br />
The <a href="http://www.w3.org/TR/DOM-Level-2-Events">latest version</a> is available at: http://www.w3.org/TR/DOM-Level-2-Events</dd>
<dt><a id="ref_RFC2119" name="ref_RFC2119" class="normref">[RFC2119]</a></dt>
<dd>"<cite><a href="http://www.rfc-editor.org/rfc/rfc2119.txt">Key words for use in RFCs to indicate requirement levels</a></cite>", RFC 2119, S. Bradner, March 1997.<br />
Available at: http://www.rfc-editor.org/rfc/rfc2119.txt</dd>
<dt><a id="ref_XHTMLMOD" name="ref_XHTMLMOD">[XHTMLMOD]</a></dt>
<dd>"<cite><a href="http://www.w3.org/TR/2006/WD-xhtml-modularization-20060705">Modularization of XHTML™ 1.1</a></cite>", W3C Working Draft, D. Austin <i lang="lt" xml:lang="lt">et al.</i>, <i>
<abbr title="editors">eds.</abbr></i>, 5 July 2006.<br />
Available at: http://www.w3.org/TR/2006/WD-xhtml-modularization-20060705<br />
The <a href="http://www.w3.org/TR/xhtml-modularization">latest version</a> is available at: http://www.w3.org/TR/xhtml-modularization</dd>
<dt><a id="ref_XMLNAMES" name="ref_XMLNAMES" class="ref">[XMLNAMES]</a></dt>
<dd>"<cite><a href="http://www.w3.org/TR/1999/REC-xml-names-19990114">Namespaces in XML</a></cite>", W3C Recommendation, T. Bray <i lang="lt" xml:lang="lt">et al.</i>, <i><abbr title="editors">
eds.</abbr></i>, 14 January 1999.<br />
Available at: http://www.w3.org/TR/1999/REC-xml-names-19990114<br />
The <a href="http://www.w3.org/TR/REC-xml-names">latest version</a> is available at: http://www.w3.org/TR/REC-xml-names</dd>
<dt><a id="ref_XHTMLROLE" name="ref_XHTMLROLE" class="ref">[XHTMLROLE]</a></dt>
<dd>"<cite><a href="http://www.w3.org/TR/2006/WD-xhtml-role-20061113/">XHTML Role Attribute Module</a></cite>", W3C Working Draft, M. Birbeck <i lang="lt" xml:lang="lt">et al.</i>, <i><abbr title=
"editors">eds.</abbr></i>, 13 November 2006.<br />
Available at: http://www.w3.org/TR/2006/WD-xhtml-role-20061113/<br />
The <a href="http://www.w3.org/TR/xhtml-role">latest version</a> is available at: http://www.w3.org/TR/xhtml-role</dd>
</dl>
<h2><a id="s_other-refs" name="s_other-refs">D.2. Other References</a></h2>
<dl>
<dt><a id="ref_XHTML2" name="ref_XHTML2">[XHTML2]</a></dt>
<dd>"<cite><a href="http://www.w3.org/TR/2005/WD-xhtml2-20050527">XHTML™ 2.0</a></cite>". J. Axelsson <i lang="lt" xml:lang="lt">et al.</i>, 27 May 2005.<br />
Available at: http://www.w3.org/TR/2005/WD-xhtml2-20050527<br />
The <a href="http://www.w3.org/TR/xhtml2">latest version</a> is available at: http://www.w3.org/TR/xhtml2</dd>
<dt><a id="ref_XMLEVENTS" name="ref_XMLEVENTS" class="normref">[XMLEVENTS]</a></dt>
<dd>"<cite><a href="http://www.w3.org/TR/2003/REC-xml-events-20031014">XML Events</a></cite>", W3C Recommendation, S. McCarron <i lang="la" xml:lang="la">et al.</i>, <i><abbr title="editors">
eds.</abbr></i>, 14 October 2003.<br />
Available at: http://www.w3.org/TR/2003/REC-xml-events-20031014</dd>
</dl>
<!--OddPage-->
<h1><a id="s_acks" name="s_acks">E. Acknowledgments</a></h1>
<p><em>This section is informative.</em></p>
<p>At the time of publication, the participants in the W3C HTML Working Group were:</p>
</body>
</html>