Skip to content

Commit

Permalink
Remove appendix "Schemata"
Browse files Browse the repository at this point in the history 
Fixes #977.
  • Loading branch information
@zcorpan
zcorpan committed May 17, 2019
1 parent 8194d29 commit c3be6fb
Showing 1 changed file with 1 addition and 89 deletions.
90 changes: 1 addition & 89 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -405,7 +405,7 @@ <h1>Important Terms</h1>
</section>
<section class="normative" id="roles">
<h1>The Roles Model</h1>
<p>This section defines the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a>role</a> <a>taxonomy</a> and describes the characteristics and properties of all <a>roles</a>. A formal <abbr title="Resource Description Framework">RDF</abbr>/<abbr title="Web Ontology Language">OWL</abbr> representation of all the information presented here is available in <a href="#a_schemata">Schemata Appendix</a>.</p>
<p>This section defines the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a>role</a> <a>taxonomy</a> and describes the characteristics and properties of all <a>roles</a>.</p>
<p>The roles, their characteristics, the states and properties they support, and specification of how they may be used in markup, shall be considered normative. The RDF/OWL representation used to model the taxonomy shall be considered informative. The RDF/OWL taxonomy may be used as a vehicle to extend <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> in the future or by tool manufacturers to validate states and properties applicable to roles per this specification.</p>
<p>Roles are element types and authors MUST NOT change role values over time or with user actions. Authors wishing to change a role MUST do so by deleting the associated element and its children and replacing it with a new element with the appropriate role. Typically, platform accessibility APIs do not provide a vehicle to notify assistive technologies of a role value change, and consequently, assistive technologies may not update their cache with the new role attribute value. </p>
<p>In order to reflect the content in the DOM, user agents SHOULD map the role attribute to the appropriate value in the implemented accessibility API, and user agents SHOULD update the mapping when the role attribute changes.</p>
Expand Down Expand Up @@ -12648,94 +12648,6 @@ <h2>Example IDL Attribute Usage</h2>
</section>

</section>
<section class="appendix informative" id="a_schemata">
<h1>Schemata</h1>
<p>WAI-ARIA roles, states, and properties are available in a number of machine-readable formats to support validation of content using WAI-ARIA attributes. WAI-ARIA is not finalized, however, so these files are subject to change without notice. <span class="todo">Todo: Remove disclaimers about not final at rec.</span></p>
<p>It is not appropriate to use these document types for live content. These are made available only for download, to support local use in development, evaluation, and validation tools. Using these versions directly from the W3C server could cause automatic blockage, preventing them from loading.</p>
<p>If it is necessary to use schemata in content, follow <a href="http://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic/">guidelines to avoid excessive DTD traffic</a>. For instance, use caching proxies to avoid fetching the schema each time it is used, or ensure software uses a local cache, such as with <a href="http://nwalsh.com/docs/articles/xml2003/">XML catalogs</a>.</p>
<section id="a_impl_roles">
<h3>Roles Implementation</h3>
<p>The taxonomy for WAI-ARIA expressed in RDF is available from <a href="http://www.w3.org/WAI/ARIA/schemata/aria-1.rdf">http://www.w3.org/WAI/ARIA/schemata/aria-1.rdf</a>.</p>
</section>
<section id="xhtml_mod">
<h3><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Attributes Module</h3>
<p>This module declares the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a>attributes</a> as a module that can be included in a modularized <abbr title="Document Type Definition">DTD</abbr>. A sample XHTML DTD using this module follows. Note the WAI-ARIA attributes are in no namespace, and the attribute name begins with "aria-" to reduce the likelihood of collision with existing attributes.</p>
<p>This module is available from <a href="http://www.w3.org/MarkUp/DTD/aria-attributes-1.mod">http://www.w3.org/MarkUp/DTD/aria-attributes-1.mod</a>.</p>
</section>
<section id="xhtml_dtd">
<h3><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> plus <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <abbr title="Document Type Definition">DTD</abbr></h3>
<p>This <abbr title="Document Type Definition">DTD</abbr> extends <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 1.1 and adds the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a>state</a> and <a>property</a> <a>attributes</a> to all its <a>elements</a>. In order to provide broader keyboard support and conform with the Focus Navigation section above, it also adds the <code>tabindex</code> attribute to a wider set of elements. </p>
<p>This is not a formal document type and may be obsoleted by future formal XHTML DTDs that support WAI-ARIA.</p>
<p>The XHTML 1.1 plus WAI-ARIA DTD is available from <a href="http://www.w3.org/WAI/ARIA/schemata/xhtml-aria-1.dtd">http://www.w3.org/WAI/ARIA/schemata/xhtml-aria-1.dtd</a>.</p>
<p>Documents written using this XHTML Family markup language can be validated using the above DTD. If a document author wants to facilitate such validation, they can include the following declaration at the top of their document: </p>
<pre>&lt;!DOCTYPE html PUBLIC &quot;-//W3C//DTD XHTML+ARIA 1.0//EN&quot;
&quot;http://www.w3.org/WAI/ARIA/schemata/xhtml-aria-1.dtd&quot;&gt;</pre>
<p>However, note that when this DOCTYPE is present in a document, most user agents treat the document as generic XML rather than HTML. This causes them to be unable to support named character entities defined by the DTD (e.g., &amp;copy;). Therefore, authors need to avoid use of named entities outside of the <cite><a href="https://www.w3.org/TR/xml11/#sec-predefined-ent">predefined entities in XML</a></cite> ([[XML11]], Section 4.6).</p>
<p>To avoid the above problem, authors can omit the above DOCTYPE statement. This causes user agents to treat the document as generic HTML with named character entity support as well as built-in ARIA support. However, it causes user agents to enter &quot;quirks&quot; mode which affects CSS rendering, and causes conformance checkers to fail the document due to the added ARIA attributes. </p>
<p>To avoid the issues of named character entity support and quirks mode, authors can instead use the following generic DOCTYPE declaration for HTML: </p>
<pre>&lt;!DOCTYPE html&gt;</pre>
<p>However, this still does not guarantee that documents will be validated by conformance checkers.</p>
</section>
<section id="xhtml-aria_cat">
<h3>SGML Open Catalog Entry for XHTML+ARIA</h3>
<p>This section contains the SGML Open Catalog-format definition [[SGML-CATALOG]] of the public identifiers for XHTML+ARIA 1.0.</p>
<pre>-- .......................................................................... --
-- File catalog ............................................................ --

-- XHTML+ARIA Catalog Data File

Revision: $Revision: 1.40 $

See "Entity Management", SGML Open Technical Resolution 9401 for detailed
information on supplying and using catalog data. This document is available
from OASIS at URL:

&lt;http://www.oasis-open.org/html/tr9401.html&gt;

--

-- .......................................................................... --
-- SGML declaration associated with XHTML .................................. --

OVERRIDE YES

SGMLDECL "xml1.dcl"

-- :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: --

-- XHTML+ARIA modules .............................................. --


PUBLIC "-//W3C//DTD XHTML+ARIA 1.0//EN" "xhtml-aria-1.dtd"


PUBLIC "-//W3C//ENTITIES XHTML ARIA Attributes 1.0//EN" "aria-attributes-1.mod"

-- End of catalog data ..................................................... --
-- .......................................................................... --
</pre>
</section>
<section id="xhtml_schema_mod">
<h3><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Attributes <abbr title="Extensible Markup Language">XML</abbr> Schema Module</h3>
<p>This module declares the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a>attributes</a> as an <abbr title="Extensible Markup Language">XML</abbr> Schema module that can be included in a modularized schema. Note the WAI-ARIA attributes are in no namespace, and the attribute name begins with "aria-" to reduce the likelihood of collision with existing attributes.</p>
<p>This module is available from <a href="http://www.w3.org/MarkUp/SCHEMA/aria-attributes-1.xsd">http://www.w3.org/MarkUp/SCHEMA/aria-attributes-1.xsd</a>.</p>
</section>
<section id="html_dtd">
<h3><abbr title="Accessible Rich Internet Applications">HTML 4.01 plus WAI-ARIA DTD</abbr></h3>
<p>This standalone DTD adds WAI-ARIA <a>state</a> and <a>property</a> <a>attributes</a> to all <a>elements</a> in HTML 4.01, as well as a <code>role</code> attribute. In order to provide broader keyboard support, it also adds the <code>tabindex</code> attribute to a wider set of elements. </p>
<p>The DTD is based on the HTML 4.01 Transitional DTD, and includes all entity references needed to make it a standalone file. <em>This is not an official W3C DTD</em> and should be considered a derivative work of HTML 4.01.</p>
<p>Documents written using this markup language can be validated using the above DTD. If a document author wants to facilitate such validation, they can include the following declaration at the top of their document: </p>
<pre>&lt;!DOCTYPE html PUBLIC &quot;-//W3C//DTD HTML+ARIA 1.0//EN&quot;
&quot;http://www.w3.org/WAI/ARIA/schemata/html4-aria-1.dtd&quot;&gt;</pre>
<p> However, note that when this DOCTYPE is present in a document, most user agents treat the document as generic XML rather than HTML. This causes them to be unable to support named character entities defined by the DTD (e.g., &amp;copy;). Therefore, authors need to avoid use of named entities outside of the <cite><a href="https://www.w3.org/TR/xml/#sec-predefined-ent">predefined entities in XML</a></cite> ([[XML11]], Section 4.6). </p>
<p> To avoid the above problem, authors can omit the above DOCTYPE statement. This causes user agents to treat the document as generic HTML with named character entity support as well as built-in ARIA support. However, it causes user agents to enter &quot;quirks&quot; mode which affects CSS rendering, and causes conformance checkers to fail the document due to the added ARIA attributes. </p>
<p>To avoid the issues of named character entity support and quirks mode, authors can instead use the following generic DOCTYPE declaration for HTML: </p>
<pre>&lt;!DOCTYPE html&gt;</pre>
<p>However, this still does not guarantee that documents will be validated by conformance checkers.</p>
<p>The <a href="http://www.w3.org/html/wg/">HTML Working Group</a> is incorporating WAI-ARIA into <a href="https://www.w3.org/TR/html5/">HTML5</a>. Official support for WAI-ARIA in HTML will be provided in that specification. This DTD is made available <em>only</em> as a bridging solution for applications requiring DTD validation but not using HTML 5.</p>
<p>This module is available from <a href="http://www.w3.org/WAI/ARIA/schemata/html4-aria-1.dtd">http://www.w3.org/WAI/ARIA/schemata/html4-aria-1.dtd</a>.</p>
</section>
</section>
<section class="informative appendix" id="typemapping">
<h2>Mapping WAI-ARIA Value types to languages</h2>
<p class="note">The HTML 5 column of the table below is advisory. Guidance on use of WAI-ARIA state and properties in HTML 5 is provided in <a href="https://www.w3.org/TR/html51/dom.html#state-and-property-attributes">State and Property Attributes</a> ([[HTML51]], section 3.2.7.3.2).</p>
Expand Down

0 comments on commit c3be6fb

Please sign in to comment.