This section defines the WAI-ARIA role taxonomy and describes the characteristics and properties of all roles. A formal RDF/OWL representation of all the information presented here is available in Schemata Appendix.
+This section defines the WAI-ARIA role taxonomy and describes the characteristics and properties of all roles.
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 WAI-ARIA in the future or by tool manufacturers to validate states and properties applicable to roles per this specification.
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.
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.
@@ -12653,94 +12653,6 @@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. Todo: Remove disclaimers about not final at rec.
-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.
-If it is necessary to use schemata in content, follow guidelines to avoid excessive DTD traffic. 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 XML catalogs.
-The taxonomy for WAI-ARIA expressed in RDF is available from http://www.w3.org/WAI/ARIA/schemata/aria-1.rdf.
-This module declares the WAI-ARIA attributes as a module that can be included in a modularized DTD. 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.
-This module is available from http://www.w3.org/MarkUp/DTD/aria-attributes-1.mod.
-This DTD extends XHTML 1.1 and adds the WAI-ARIA state and property attributes to all its elements. In order to provide broader keyboard support and conform with the Focus Navigation section above, it also adds the tabindex attribute to a wider set of elements.
This is not a formal document type and may be obsoleted by future formal XHTML DTDs that support WAI-ARIA.
-The XHTML 1.1 plus WAI-ARIA DTD is available from http://www.w3.org/WAI/ARIA/schemata/xhtml-aria-1.dtd.
-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:
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+ARIA 1.0//EN" - "http://www.w3.org/WAI/ARIA/schemata/xhtml-aria-1.dtd">-
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., ©). Therefore, authors need to avoid use of named entities outside of the predefined entities in XML ([[XML11]], Section 4.6).
-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 "quirks" mode which affects CSS rendering, and causes conformance checkers to fail the document due to the added ARIA attributes.
-To avoid the issues of named character entity support and quirks mode, authors can instead use the following generic DOCTYPE declaration for HTML:
-<!DOCTYPE html>-
However, this still does not guarantee that documents will be validated by conformance checkers.
-This section contains the SGML Open Catalog-format definition [[SGML-CATALOG]] of the public identifiers for XHTML+ARIA 1.0.
--- .......................................................................... -- --- 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: - - <http://www.oasis-open.org/html/tr9401.html> - --- - --- .......................................................................... -- --- 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 ..................................................... -- --- .......................................................................... -- --
This module declares the WAI-ARIA attributes as an XML 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.
-This module is available from http://www.w3.org/MarkUp/SCHEMA/aria-attributes-1.xsd.
-This standalone DTD adds WAI-ARIA state and property attributes to all elements in HTML 4.01, as well as a role attribute. In order to provide broader keyboard support, it also adds the tabindex attribute to a wider set of elements.
The DTD is based on the HTML 4.01 Transitional DTD, and includes all entity references needed to make it a standalone file. This is not an official W3C DTD and should be considered a derivative work of HTML 4.01.
-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:
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML+ARIA 1.0//EN" - "http://www.w3.org/WAI/ARIA/schemata/html4-aria-1.dtd">-
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., ©). Therefore, authors need to avoid use of named entities outside of the predefined entities in XML ([[XML11]], Section 4.6).
-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 "quirks" mode which affects CSS rendering, and causes conformance checkers to fail the document due to the added ARIA attributes.
-To avoid the issues of named character entity support and quirks mode, authors can instead use the following generic DOCTYPE declaration for HTML:
-<!DOCTYPE html>-
However, this still does not guarantee that documents will be validated by conformance checkers.
-The HTML Working Group is incorporating WAI-ARIA into HTML5. Official support for WAI-ARIA in HTML will be provided in that specification. This DTD is made available only as a bridging solution for applications requiring DTD validation but not using HTML 5.
-This module is available from http://www.w3.org/WAI/ARIA/schemata/html4-aria-1.dtd.
-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 State and Property Attributes ([[HTML51]], section 3.2.7.3.2).