Roles for Accessible Rich Internet Applications (WAI-ARIA Roles) Version 1.0

1.1 About This Draft

This section is informative.

This draft currently handles two aspects of roles: GUI functionality and structural relationships of the element. For more information see the Roadmap for Accessible Rich Internet Applications for the use of roles in making interactive content accessible.

This taxonomy is designed in-part to support the common roles found in platform accessibility APIs. Reference to roles found in this taxonomy by dynamic Web content may be used to support interoperability with assistive technologies.

The schema to support this standard has been designed to be extended so that custom roles can be created by extending base roles. This allows user agents to support at least the base role, and user agents that support the custom role can provide enhanced access. Note that much of this could be formalized in XML Schema [XSD]. However, being able to define similarities between roles, such as baseConcepts and more descriptive definitions would not be available in XSD. While this extensibility is possible, this version of the specification does not define how this extension is to be achieved.

1.2 Terms and Definitions

This section is informative.

While some terms are defined in place, the following definitions are used throughout this document. Familiarity with W3C XHTML 1.1 Recommendation [XHTML] and the W3C XML 1.0 Recommendation [XML] is highly recommended to understand these definitions.

Accessibility API

Operating systems and other platforms provide a set of interfaces that expose information about objects and events to assistive technology. Assistive technology uses these interfaces to get information about and interact with those controls. Examples of this are the Java Accessibility API [JAPI], Microsoft Active Accessibility [MSAA], Apple Accessibility for COCOA [AAC], the Gnome Accessibility Toolkit (ATK) [GAP], and IAccessible2 [IA2].

Assistive Technology

Hardware and/or software that acts as a user agent, or along with a mainstream user agent, to provide services to meet the requirements of users with disabilities that go beyond those offered by the mainstream user agents.

Services provided by assistive technology include alternative presentations (e.g., as synthesized speech or magnified content), alternative input methods (e.g., voice), additional navigation or orientation mechanisms, and content transformations (e.g., to make tables more accessible).

Assistive technologies often communicate data and messages with mainstream user agents by using and monitoring APIs.

The distinction between mainstream user agents and assistive technologies is not absolute. Many mainstream user agents provide some features to assist individuals with disabilities. The basic difference is that mainstream user agents target broad and diverse audiences that usually include people with and without disabilities. Assistive technologies target narrowly defined populations of users with specific disabilities. The assistance provided by an assistive technology is more specific and appropriate to the needs of its target users. The mainstream user agent may provide important services to assistive technologies like retrieving Web content from program objects or parsing markup into identifiable bundles.

Examples of assistive technologies that are important in the context of this document include the following:

• screen magnifiers, and other visual reading assistants, which are used by people with visual, perceptual and physical print disabilities to change text font, size, spacing, color, synchronization with speech, etc. in order to improve the visual readability of rendered text and images;
• screen readers, which are used by people who are blind to read textual information through synthesized speech or braille;
• text-to-speech software, which is used by some people with cognitive, language, and learning disabilities to convert text into synthetic speech;
• voice recognition software, which may be used by people who have some physical disabilities;
• alternative keyboards, which are used by people with certain physical disabilities to simulate the keyboard (including alternate keyboards that use headpointers, single switches, sip/puff and other special input devices.);
• alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activations

Attribute

In this specification, attribute is used as it is in markup languages. Attributes are structural features added to elements to provide information about the states and properties of the object represented by the element.

Characteristic

An assertion which can be a constraint.

Class

An abstract type of object.

Element

In this specfication, element is used as it is in markup languages. Elements are the structural elements in markup language that contains the data profile for objects.

Event

A programmatic message used to communicate discrete changes in the state of an object to other objects in a computational system. User input to a web page is commonly mediated through abstract events that describe the interaction and can provide notice of changes to the state of a document object.

Namespace

A collection of related names. Qualifying a name in terms of the namespace to which it belongs allows these names to be distinguished from names in other namespaces that are spelled alike. Namespaces in this document are used in accordance with Namespaces in XML [XML-NAMES].

Object

A "thing" in the perceptual user experience, instantiated in markup languages by one or more elements, and converted into the object-oriented pattern by user agents. Objects are instances of abstract classes, which defines the general characteristics of object instances. A single DOM object may or may not correspond with a single object in accessibility API. An object in accessibility API encapsulates one ore more DOM objects.

Property

Attributes that are essential to the nature of a given object. As such, they are less likely to change than states; a change of a property may significantly impact the meaning or presentation of an object. Properties mainly provide limitations on objects from the most general case implied by roles without properties applied.

Relationship

A fact connecting two distinct, articulable things. Relationships may be of various types to indicate which object labels another, controls another, etc.

Role

An indicator of type. The object's role is the class of objects of which it is a member. This semantic association allows tools to present and support interaction with the object in a manner that is consistent with user expectations about other objects of that type.

State

A state is a dynamic property expressing characteristics of an object that may change in response to user action or automated processes. States do not affect the essential nature of the object, but represent data associated with the object or user interaction possibilities.

User Agent

Any software that retrieves and renders Web content for users, such as Web browsers, media players, plug-ins, and other programs including assistive technologies that help retrieve and render Web content.

Value

A literal that concretizes the information expressed by a state or property.

1.3 Use Cases

This section is informative.

Alternate input devices are helped when all content is keyboard accessible. The tabindex changes achieve this. The new semantics when combined by our style guide work will allow alternate input solutions to facilitate command and control on via an alternate input solution.

Low vision solutions benefit from ARIA markup in that the improved keyboard navigation helps people with extremely low vision. Low vision solutions offer a degree of screen reading functionality (like AI Squared's Zoom text). Furthermore, ARIA introduces navigation landmarks both through our taxonomy and the XHTML role landmarks which dramatically improves keyboard navigation productivity. This is a huge benefit for alternate input solutions as well.

ARIA will also be used to assist people with cognitive impairments. The additional semantics will allow us to restructure and substitute alternative content in adaptive Web 2.0 solutions. We are doing this on the FLUID project. In FLUID we will be incorporating ARIA technology into uPortal and Sakai. Support for cognitive impairment is absolutely critical.

2.1 Introduction to using roles

This section is informative.

Complex user interfaces become inaccessible because assistive technologies that provide alternative access, are often left guessing at the semantics behind portions of a document (see the Roadmap for Accessible Rich Internet Applications [ARIA-ROADMAP]). Associating an element in the document to a role in this taxonomy associates all the information about that role that has been defined in this specification.

Roles defined in this specification descend from and complement the roles defined in the XHTML Role Attribute Module [XHTML-ROLES].

Roles in this specification are defined with RDF/OWL to build rich description of the expected behaviors of the role. For example:

• The roles taxonomy describes what states are supported for each role. For example, a checkbox supports being checked.
• The roles taxonomy describes the context of a role. For example a listitem should be inside a list.
• The role taxonomy defines a hierarchy of roles with related properties. For example a directory is a type of list.
• The role taxonomy makes use of OWL to provide a type hierarchy allowing for semantic inheritence similar to any class hierarchy.
• The role taxonomy makes references to related concepts in other specifications.
• The role taxonomy provides descriptions for each role.

Hence referencing a role from the role taxonomy to an element in the document gives assistive technology the information it needs to handle an element correctly.

xmlns:wairole="http://www.w3.org/2005/01/wai-rdf/GUIRoleTaxonomy#"

<html xmlns="http://www.w3.org/1999/xhtml"
    xmlns:wairole="http://www.w3.org/2005/01/wai-rdf/GUIRoleTaxonomy#"
    xmlns:aaa="http://www.w3.org/2005/07/aaa" >
  <head></head>
  <body>
    
    <span class="checkbox" id="chbox1" role="wairole:checkbox"  aaa:checked="mixed"
        onkeydown="return checkBoxEvent(event);" onclick="return checkBoxEvent(event);" tabindex="0" >
      A checkbox label
    </span>
    
  </body>
</html>

2.2 Building Accessible Applications with Roles

This section provides a brief introduction to the process of making applications accessible using the ARIA Roles specification. The choice and usage of roles can be complex and context dependent. It is beyond the scope of this document to explain all possible use cases. ARIA Best Practices will provide expanded usage recommendations.

An application becomes accessible when:

1. Each element or widget has full and correct semantics that fully describes its behavior (using element names or roles).
2. The relationships between elements and groups are known
3. States, properties, and container relationships are valid for each element's behavior and are accessible via the Document Object Model [DOM] and the platform accessibility API.
4. There is an element having the correct input focus.

Roles make the different elements in the application semantically rich. User agents use the role semantics to understand how to handle each element. Roles can be used to build accessible applications by providing any missing information that the assistive technology needs to anticipate the behavior of the elements inside the application.

2.3 Example: building a tree view in XHTML 1.0

This section is informative.

A basic tree view allows the user to select different list items and expand and collapse embedded lists. Arrow keys are used to navigate through a tree, including left/right to collapse/expand sub trees. Double clicking with the mouse also toggles expansion.

Building this user interface element with script could leave assistive technology guessing about the role of each element. To make this feature accessible we need to:

• Inform assistive technology about the role of each element, so they know how to handle it;
• Inform assistive technology about the relationships between tree items;
• Give a clear keyboard focus that will not confuse users with disabilities;
• Expose the changing states (e.g., open and closed) of the the tree items.

We can do that by following the steps below:

<div role="wairole:tree" >
  <div role="wairole:treeitem" >Veggies
    <div role="wairole:group">
      <div role="wairole:treeitem">Green
        <div role="wairole:group">
          <div role="wairole:treeitem">Asparagus</div>
          <div role="wairole:treeitem">Kale</div>
          <div role="wairole:treeitem" >Leafy
            <div role="wairole:group">
              <div role="wairole:treeitem">Lettuce</div>
              <div role="wairole:treeitem">Kale</div>
              <div role="wairole:treeitem">Spinach</div>
              <div role="wairole:treeitem">Chard</div>
            </div>
          </div> ---close leafy
          <div role="wairole:treeitem">Green beans</div>
        </div>
      </div> ---close green
      <div role="wairole:treeitem">Legumes</div>
      <div role="wairole:treeitem" >Yellow
        <div role="wairole:group">
          <div role="wairole:treeitem">Bell peppers</div>
          <div role="wairole:treeitem">Squash</div>
        </div>
      </div> ---close yellow
    </div>
  </div> ---close veggies
</div> ---close tree

<div role="wairole:treeitem" aaa:haschild="yellowtreegroup">Yellow<div>
…
<div id="yellowtreegroup" role="wairole:group">
<div role="wairole:treeitem">Bell peppers</div>
<div role="wairole:treeitem">Squash</div>
…
</div>

<div tabindex="-1" role="wairole:treeitem" aaa:expanded="true">Yellow</div>

<div role="wairole:tree" tabindex="-1"
  onfocus="return treeItemFocus(event);"
  onclick="return treeItemEvent(event);"
  ondblclick="return treeItemEvent(event);"
  onkeydown="return treeItemEvent(event);"
  onkeypress="return treeItemEvent(event);">

2.4 Applying roles to documents

This section is informative.

Roles are provided in XML-based languages using an attribute designated for the purpose. Roles from this ontology are indicated as values of that role attribute. In order to indicate that the roles are used as specified in this document, the document must use the following namespace in the attribute value: http://www.w3.org/2005/01/wai-rdf/GUIRoleTaxonomy#.

Generally this namespace is declared on the root element of the document as specified in XML Namespaces [XML-NAMES]. Examples in this document use the namespace prefix “wairole” to indicate this namespace.

For example, the start tag of a root element that includes the appropriate namespace declaration might look like:

<html xmlns="http://www.w3.org/1999/xhtml"
    xml:lang="en"
    xmlns:wairole="http://www.w3.org/2005/01/wai-rdf/GUIRoleTaxonomy#"
>

<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml
"xmlns:wairole="http://www.w3.org/2005/01/wai-rdf/GUIRoleTaxonomy#"><body>

<table id="table1" role="wairole:grid">

</table>

</body></html>

<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"
xmlns:xhtml10="http://www.w3.org/1999/xhtml"
xmlns:wairole="http://www.w3.org/2005/01/wai-rdf/GUIRoleTaxonomy#"><body>

<table id="table1" xhtml10:role="wairole:grid">

</table>
</body></html>

<html xmlns="http://www.w3.org/1999/xhtml"
    xmlns:wairole="http://www.w3.org/2005/01/wai-rdf/GUIRoleTaxonomy#"
>

3.1 Relationships between concepts

This section is normative.

The role taxonomy uses the following relationships to relate ARIA roles to each other and to concepts from other specifications, such as HTML and XForms.

Editorial note: The information below is presented with details arranged in a data table. Concerns about accessibility of this have been raised. An experimental alternate presentation is provided in Relationships between concepts in list form, using definition lists instead of tables to organize the details. We appreciate feedback about which form is more effective, or proposals for other forms.

3.2 Role Characteristics

This section is normative.

Roles are defined and described by their characteristics. Characteristics define the structural function of a role, such as what a role is, concepts behind it, what instances of the role can or must contain. In the case of widgets this also includes how it interacts with the user agent based on mapping to HTML forms and XForms. States and properties from ARIA States and Properties that are supported by the role are also indicated.

The Roles Taxonomy defines the following characteristics. These characteristics are implemented in RDF as properties of the OWL classes that describe the roles.

Editorial note: The information below is presented with details arranged in a data table. Concerns about accessibility of this have been raised. An experimental alternate presentation is provided in Role characteristics in list form, using definition lists instead of tables to organize the details. We appreciate feedback about which form is more effective, or proposals for other forms.

3.3 Global States and Properties

This section is normative.

Some states and properties are applicable to all roles, and most are applicable to all elements regardless of role. In addition to explicitly expressed supported states and properties, the following global states and properties are supported by all roles as well. These include:

• datatype
• describedby
• dropeffect
• flowto
• grab
• haspopup
• hidden
• labelledby
• owns
• tabindex

Global states and properties are applied to the role roletype, which is the base role, and therefore inherit into all roles. To facilitiate reading, they are not explicitly identified as either supported or inherited states and properties in the specification. Instead, the inheritance is indicated by a link to this section.

3.4 Roles

This section is normative.

To support the current user scenario, this specification defines roles that A, help define Widgets (For example, a tristate Checkbox) and B, help define page structure (for example, a section header).

Class diagram of the relationships described in the role data model

View larger version of class diagram

Roles are categorized as follows:

1. Taxonomy Roles
2. User Input Controls
3. User Interface Elements
4. Document Structure
5. Specialized Regions

Editorial note: The roles below are presented with details arranged in a data table. Concerns about accessibility of this have been raised. An experimental alternate presentation is provided in Role details in list form, using definition lists instead of tables to organize the details. We appreciate feedback about which form is more effective, or proposals for other forms.

Below is an alphabetical list of ARIA roles to be used by rich internet application authors (excluding abstract roles which are not used directly). A detailed definition of the taxonomy supporting these ARIA roles follows.

3.4.2 User Input Controls

These roles ...

Roles in this section include:

• checkbox
• combobox
• input
• listbox
• option
• radio
• radiogroup
• range
• select
• spinbutton
• textbox

Role: input

Generic type for widgets that can have a value.

Characteristics:

Is Abstract:	True
Parent Role:	widget
Child Roles:	select option textbox range
Base Concept:
Related Concepts:	XForms input
Supported States and Properties:	invalid required
Inherited States and Properties:	controls disabled Global States
Name From:	author
Accessible Name Required:
Inherits Name Required:
Children Presentational:
Inherits Presentational:

---

Role: select

A form control that allows the user to make selections from a set of choices. A select must contain an option.

Characteristics:

Is Abstract:	True
Parent Role:	composite group input
Child Roles:	listbox combobox radiogroup menu tree
Base Concept:
Related Concepts:
Supported States and Properties:
Inherited States and Properties:	activedescendent atomic busy channel controls disabled expanded invalid live relevant required templateid Global States
Name From:	author
Accessible Name Required:
Inherits Name Required:
Children Presentational:
Inherits Presentational:

---

Role: listbox

A list box is a widget that allows the user to select one or more items from a list. Items within the list are static and may contain images.

Characteristics:

Is Abstract:
Parent Role:	list select
Child Roles:
Base Concept:
Related Concepts:	HTML select XForms select
Parent Element:
Required Child Elements:
Supported States and Properties:	multiselectable
Inherited States and Properties:	activedescendent atomic busy channel controls disabled expanded invalid level live relevant required templateid Global States
Name From:	author
Accessible Name Required:	True
Inherits Name Required:
Children Presentational:
Inherits Presentational:

---

Role: combobox

Combobox is a presentation of a select, where users can type to locate a selected item.

Combobox is the combined presentation of a single line textbox with a drop down select widget. The combobox may be open or closed. An "open" combobox allows users to type freeform text into the textbox whereas a "closed" combobox only shows text in the textbox which can be retrieved from the select. Typically a "closed" text field will use the text entered to quickly search and fill the textfield with text from the select.

NOTE: In [XFORMS] the same select can have one of 3 appearances: combo-box, drop-down box or group of radio-buttons. Besides, many browsers (if not all of them) allow users to type in a drop-down select as well.

Characteristics:

Is Abstract:
Parent Role:	select
Child Roles:
Base Concept:
Related Concepts:	HTML select XForms select
Parent Element:
Required Child Elements:	option
Supported States and Properties:	autocomplete
Inherited States and Properties:	activedescendent atomic busy channel controls disabled expanded invalid live relevant required templateid Global States
Name From:	author
Accessible Name Required:	True
Inherits Name Required:
Children Presentational:
Inherits Presentational:

---

Role: option

A selectable item in a list represented by a select.

An option must appear inside an element with select role.

Characteristics:

Is Abstract:
Parent Role:	input
Child Roles:	checkbox menuitem treeitem
Base Concept:	HTML option
Related Concepts:	listitem XForms item
Parent Element:	select
Required Child Elements:
Supported States and Properties:	checked selected
Inherited States and Properties:	controls disabled invalid required Global States
Name From:	subtree author
Accessible Name Required:	True
Inherits Name Required:
Children Presentational:
Inherits Presentational:

---

Role: checkbox

A control that has three possible values, (true, false, mixed).

Many checkboxes do not use the mixed value, and thus are effectively boolean checkboxes. However, the checked state supports the "mixed" value to support cases such as installers where an option has been partially installed.

Characteristics:

Is Abstract:
Parent Role:	option
Child Roles:	radio menuitemcheckbox
Base Concept:
Related Concepts:	HTML input (type : checkbox)
Parent Element:
Required Child Elements:
Supported States and Properties:
Inherited States and Properties:	checked controls disabled invalid required selected Global States
Name From:	subtree author
Accessible Name Required:	True
Inherits Name Required:
Children Presentational:
Inherits Presentational:

---

Role: radio

A radio is an option in single-select list. Only one radio control in a radiogroup can be selected at the same time.

Characteristics:

Is Abstract:
Parent Role:	checkbox
Child Roles:	menuitemradio
Base Concept:
Related Concepts:	HTML input (type : radio)
Parent Element:
Required Child Elements:
Supported States and Properties:
Inherited States and Properties:	checked controls disabled invalid required selected Global States
Name From:	subtree author
Accessible Name Required:	True
Inherits Name Required:
Children Presentational:
Inherits Presentational:

---

Role: radiogroup

A group of radio controls.

Characteristics:

Is Abstract:
Parent Role:	select
Child Roles:
Base Concept:
Related Concepts:	list
Parent Element:
Required Child Elements:	radio
Supported States and Properties:
Inherited States and Properties:	activedescendent atomic busy channel controls disabled expanded invalid live relevant required templateid Global States
Name From:	author
Accessible Name Required:	True
Inherits Name Required:
Children Presentational:
Inherits Presentational:

---

Role: textbox

Inputs that allow free-form text as their value.

If the multiline property is true, the control accepts line breaks within the input, as in a HTML textarea. Otherwise this is a simple text box.

Intended use is in languages that do not have a text input object (such as SVG), or cases in which an element with different semantics is repurposed as an input box. The user would use this role when additional states or properties are applied to a standard text input control. This is to indicate to the user agent that it must process additional states and properties such as invalid and required.

Characteristics:

Is Abstract:
Parent Role:	input
Child Roles:
Base Concept:
Related Concepts:	XForms input HTML textarea
Supported States and Properties:	autocomplete multiline readonly secret
Inherited States and Properties:	controls disabled invalid required Global States
Name From:	author
Accessible Name Required:	True
Inherits Name Required:
Children Presentational:
Inherits Presentational:

---

Role: range

Represents a range of values that can be set by the user.

Characteristics:

Is Abstract:	True
Parent Role:	input
Child Roles:	spinbutton slider
Base Concept:
Related Concepts:
Supported States and Properties:	valuemax required valuemin required valuenow required
Inherited States and Properties:	controls disabled invalid required Global States
Name From:	author
Accessible Name Required:
Inherits Name Required:
Children Presentational:
Inherits Presentational:

---

Role: spinbutton

A form of Range that expects a user selecting from discrete choices.

A spinbutton allows the user to select from the given range through the use of an up and down button. Visibly, the current value is incremented or decremented until a maximum or minimum value is reached. This functionality should be accomplished programmatically through the use of up and down arrows on the keyboard.

Characteristics:

Is Abstract:
Parent Role:	composite range
Child Roles:
Base Concept:
Related Concepts:
Parent Element:
Required Child Elements:
Supported States and Properties:
Inherited States and Properties:	activedescendent controls disabled invalid required valuemax valuemin valuenow Global States
Name From:	author
Accessible Name Required:	True
Inherits Name Required:
Children Presentational:
Inherits Presentational:

4.1 Example: Grid

In this example, an XHTML table has been assigned the role of grid.

<table id="table1" role="wairole:grid" >

</table>

The role of grid maps this element to the appropriate feature in the platform accessibility infrastructure that enables it to be properly treated. In this case, the grid role means that the multiselectable property is supported and cells may be editable, allowing it to be treated as a spreadsheet.

A full spreadsheet example is available online at http://www.mozilla.org/access/dhtml/spreadsheet

Roles can be embedded in any host language, e.g. XHTML 1.1 [XHTML]. In many case Roles accompany other supporting technologies, such as States and Properties for Accessible Rich Internet Applications [ARIA-STATE] and XML Events [XML-EVENTS]

5.1 XHTML 1.1 Document Conformance

Roles for Accessible Rich Internet Applications is not a stand-alone document type. It is intended to be integrated into other host languages such as XHTML [XHTML]. A conforming document 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:

1. The document must conform to the constraints expressed in Appendix A - RDF Schema combined with the constraints expressed in its host language implementation.

2. The document must contain an xmlns declaration for the role Namespace [XML-NAMES]. The namespace name for the roles defined here is

   http://www.w3.org/2005/01/wai-rdf/GUIRoleTaxonomy#

5.2 User Agent Conformance

User agents that conform to Roles for Accessible Rich Internet Applications expose role information provided by the author to assistive technologies, and if they are assistive technologies themselves, use role information to enhance the presentation. Conformance requirements:

1. User agents MUST make all roles provided by the author available in the DOM, using the attribute name, namespace, and values defined in this specification. This requirement parallels User Agent Accessibility Guidelines 1.0 Section 6.2: DOM access to HTML/XML content [UAAG, Section 6.2].

2. User agents SHOULD expose role information provided by the author to the platform accessibility API. Refer to Mapping States and Properties to Accessibility APIs for guidance about how to expose this information. This requirement parallels User Agent Accessibility Guidelines 1.0 Section 6.3: Programmatic Access to non-HTML/XML Content [UAAG, Section 6.3], except that it applies even to HTML and XML content.

   Note: Not all platforms provide accessibility APIs, or provide interfaces that map to all the roles defined in this specification. User agents should expose those roles that are supported in order to support assistive technologies that work through the accessibility API. The remaining roles are available to assistive technologies via the DOM as per point 1 above, for those that provide explicit support for this specification.

3. User agents MUST override implicit roles of elements with roles provided by the author. This applies to elements that have particular default roles because of the semantics declared by the content technology. Processing and presentation must be appropriate to the declared role.

4. Assistive technologies that conform to this specification MUST use role information to present content to, and support interaction with, users in a manner appropriate to that role. The manner in which this is done is specific to each user agent but should be appropriate to the specified description of the role.

   Note: This does not specify how assistive technology obtains role information. Assistive technologies may obtain role information directly from content, through the DOM, or through the platform accessibility API. In the latter case, only incomplete role information may be available. This point only requires that assistive technology use the roles that are actually available to it to support the user.

6.1 Implementation

This section is informative.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rdf:RDF [
  <!ENTITY xsd "http://www.w3.org/2001/XMLSchema#">
  <!ENTITY dc "http://dublincore.org/2003/03/24/dces#">
  <!ENTITY owl "http://www.w3.org/2002/07/owl#">
  <!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#">
  <!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#">
  <!ENTITY states "http://www.w3.org/2005/07/aaa#">
]>
<rdf:RDF xmlns:role="http://www.w3.org/2005/01/wai-rdf/GUIRoleTaxonomy#"
         xmlns:states="http://www.w3.org/2005/07/aaa#"
         xmlns:html="http://www.w3.org/1999/xhtml"
         xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
         xmlns:dc="http://purl.org/dc/elements/1.1/#"
         xmlns:owl="http://www.w3.org/2002/07/owl#"
         xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
         xml:base="http://www.w3.org/2005/01/wai-rdf/GUIRoleTaxonomy"><!--==Objects==--><owl:ObjectProperty rdf:ID="relatedConcept">
      <rdfs:comment xml:lang="en">The URI of similar/related types from
		  other specifications (See SKOS). This has been replaced in the implementation
		  with rdfs:seeAlso.</rdfs:comment>
      <rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#anyURI"/>
      <rdfs:domain rdf:resource="#roletype"/>
   </owl:ObjectProperty>
   <owl:ObjectProperty rdf:ID="baseConcept">
      <rdfs:comment xml:lang="en">This is similar to type but without
		  inheritance of limitations and properties. role:baseConcepts are designed as
		  a substitute for inheritance for external concepts. </rdfs:comment>
      <rdfs:subpropertyOf rdf:resource="#relatedConcept"/>
   </owl:ObjectProperty>
   <owl:ObjectProperty rdf:ID="supportedState">
      <rdfs:comment xml:lang="en">A state that can be supported for this a
		  Role</rdfs:comment>
      <rdfs:domain rdf:resource="#roletype"/>
   </owl:ObjectProperty>
   <owl:ObjectProperty rdf:ID="scope">
      <rdfs:comment xml:lang="en">Context where this role is
		  allowed</rdfs:comment>
      <rdfs:domain rdf:resource="#roletype"/>
   </owl:ObjectProperty>
   <owl:ObjectProperty rdf:ID="mustContain">
      <rdfs:comment xml:lang="en">A child that must be contained by this
		  role</rdfs:comment>
      <rdfs:subpropertyOf rdf:resource="#scope"/>
   </owl:ObjectProperty>
   <owl:ObjectProperty rdf:ID="default">
      <rdfs:comment>Default value of a supported state in the context of
		  this role</rdfs:comment>
   </owl:ObjectProperty>
   <owl:ObjectProperty rdf:ID="nameFrom">
      <rdfs:comment>How a role type name is extracted and referenced 
		  inside a document. Values are "author": name comes from values 
		  provided by the author in explict markup features; and "subtree": 
		  name comes from the text value of the element node.</rdfs:comment>
      <rdfs:domain rdf:resource="#widget"/>
   </owl:ObjectProperty>
   <owl:ObjectProperty rdf:ID="childrenArePresentational">
      <rdfs:comment xml:lang="en">The children are presenational. Assistive
				technologies may choose to hid the children from the user.</rdfs:comment>
      <rdf:range rdf:resource="http://www.w3.org/2001/XMLSchema#boolean"/>
      <rdfs:domain rdf:resource="#roletype"/>
   </owl:ObjectProperty>
   <!--== Taxonomy Roles ==--><owl:Class rdf:ID="roletype">
      <rdfs:subClassOf>
         <owl:Restriction>
            <owl:onProperty rdf:resource="http://dublincore.org/2003/03/24/dces#description"/>
            <owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#string">1</owl:cardinality>
         </owl:Restriction>
      </rdfs:subClassOf>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/xhtml-role/#s_role_module_attributes"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/html401/struct/links.html#edef-LINK"/>
      <rdfs:seeAlso rdf:resource="http://purl.org/dc/elements/1.1/type"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#datatype"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#describedby"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#dropeffect">
         <role:default>none</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#flowto"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#grab">
         <role:default>false</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#haspopup">
         <role:default>false</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#hidden">
         <role:default>false</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#labelledby"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#owns"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#tabindex"/>
   </owl:Class>
   <owl:Class rdf:ID="widget">
      <rdfs:subClassOf rdf:resource="#roletype"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#controls"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#disabled">
         <role:default>false</role:default>
      </role:supportedState>
   </owl:Class>
   <owl:Class rdf:ID="structure">
      <rdfs:subClassOf rdf:resource="#roletype"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#atomic">
         <role:default>false</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#busy">
         <role:default>false</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#channel">
         <role:default>main</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#live">
         <role:default>off</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#relevant">
         <role:default>text</role:default>
      </role:supportedState>
   </owl:Class>
   <owl:Class rdf:ID="composite">
      <rdfs:subClassOf rdf:resource="#widget"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#activedescendent"/>
   </owl:Class>
   <owl:Class rdf:ID="window">
      <rdfs:subClassOf rdf:resource="#roletype"/>
   </owl:Class>
   <!--== User Input Controls ==--><owl:Class rdf:ID="input">
      <rdfs:subClassOf rdf:resource="#widget"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/xforms/slice8.html#ui-input"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#invalid">
         <role:default>false</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#required">
         <role:default>false</role:default>
      </role:supportedState>
   </owl:Class>
   <owl:Class rdf:ID="select">
      <rdfs:subClassOf rdf:resource="#composite"/>
      <rdfs:subClassOf rdf:resource="#group"/>
      <rdfs:subClassOf rdf:resource="#input"/>
   </owl:Class>
   <owl:Class rdf:ID="listbox">
      <rdfs:subClassOf rdf:resource="#list"/>
      <rdfs:subClassOf rdf:resource="#select"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/html401/interact/forms.html#edef-SELECT"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/2006/REC-xforms-20060314/slice8.html#ui-selectMany"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#multiselectable">
         <role:default>false</role:default>
      </role:supportedState>
   </owl:Class>
   <owl:Class rdf:ID="combobox">
      <rdfs:subClassOf rdf:resource="#select"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/html401/interact/forms.html#edef-SELECT"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/2006/REC-xforms-20060314/slice8.html#ui-selectMany"/>
      <role:mustContain rdf:resource="#option"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#autocomplete">
         <role:default>none</role:default>
      </role:supportedState>
   </owl:Class>
   <owl:Class rdf:ID="option">
      <rdfs:subClassOf rdf:resource="#input"/>
      <role:baseConcept rdf:resource="http://www.w3.org/TR/html4/interact/forms.html#edef-OPTION"/>
      <rdfs:seeAlso rdf:resource="#listitem"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/xforms/slice8.html#ui-common-elements-item"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#checked">
         <role:default/>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#selected">
         <role:default>undefined</role:default>
      </role:supportedState>
   </owl:Class>
   <owl:Class rdf:ID="checkbox">
      <rdfs:subClassOf rdf:resource="#option"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/html401/interact/forms.html#edef-INPUT"/>
   </owl:Class>
   <owl:Class rdf:ID="radio">
      <rdfs:subClassOf rdf:resource="#checkbox"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/html401/interact/forms.html#edef-INPUT"/>
   </owl:Class>
   <owl:Class rdf:ID="radiogroup">
      <rdfs:subClassOf rdf:resource="#select"/>
      <role:mustContain rdf:resource="#radio"/>
   </owl:Class>
   <owl:Class rdf:ID="textbox">
      <rdfs:subClassOf rdf:resource="#input"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/xforms/slice8.html#ui-input"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/html4/interact/forms.html#edef-TEXTAREA"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#autocomplete">
         <role:default>none</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#multiline">
         <role:default>false</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#readonly">
         <role:default>false</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#secret">
         <role:default>false</role:default>
      </role:supportedState>
   </owl:Class>
   <owl:Class rdf:ID="range">
      <rdfs:subClassOf rdf:resource="#input"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#valuemax"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#valuemin"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#valuenow"/>
   </owl:Class>
   <owl:Class rdf:ID="spinbutton">
      <rdfs:subClassOf rdf:resource="#composite"/>
      <rdfs:subClassOf rdf:resource="#range"/>
   </owl:Class>
   <!--== User Interface Elements ==--><owl:Class rdf:ID="button">
      <rdfs:subClassOf rdf:resource="#widget"/>
      <role:baseConcept rdf:resource="http://www.w3.org/TR/html4/interact/forms.html#edef-BUTTON"/>
      <rdfs:seeAlso rdf:resource="#link"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/xforms/slice8.html#ui-button"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#pressed">
         <role:default>undefined</role:default>
      </role:supportedState>
   </owl:Class>
   <owl:Class rdf:ID="link">
      <rdfs:subClassOf rdf:resource="#widget"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/html401/struct/links.html#edef-LINK"/>
   </owl:Class>
   <owl:Class rdf:ID="menu">
      <rdfs:subClassOf rdf:resource="#list"/>
      <rdfs:subClassOf rdf:resource="#select"/>
      <rdfs:seeAlso rdf:resource="http://www.loc.gov/nls/z3986/v100/dtbook110doc.htm#sidebar"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/xforms/slice8.html#ui-selectMany"/>
      <rdfs:seeAlso rdf:resource="http://java.sun.com/j2se/1.3/docs/api/javax/accessibility/AccessibleRole.html#MENU"/>
      <role:mustContain rdf:resource="#menuitem"/>
   </owl:Class>
   <owl:Class rdf:ID="menubar">
      <rdfs:subClassOf rdf:resource="#group"/>
      <rdfs:seeAlso rdf:resource="#toolbar"/>
   </owl:Class>
   <owl:Class rdf:ID="toolbar">
      <rdfs:subClassOf rdf:resource="#group"/>
      <rdfs:seeAlso rdf:resource="#menubar"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#multiselectable">
         <role:default>false</role:default>
      </role:supportedState>
   </owl:Class>
   <owl:Class rdf:ID="menuitem">
      <rdfs:subClassOf rdf:resource="#listitem"/>
      <rdfs:subClassOf rdf:resource="#option"/>
      <rdfs:seeAlso rdf:resource="http://java.sun.com/j2se/1.3/docs/api/javax/accessibility/AccessibleRole.html#MENU_ITEM"/>
      <role:scope rdf:resource="#menu"/>
   </owl:Class>
   <owl:Class rdf:ID="menuitemcheckbox">
      <rdfs:subClassOf rdf:resource="#checkbox"/>
      <rdfs:subClassOf rdf:resource="#menuitem"/>
      <rdfs:seeAlso rdf:resource="#menuitem"/>
      <role:scope rdf:resource="#menu"/>
   </owl:Class>
   <owl:Class rdf:ID="menuitemradio">
      <rdfs:subClassOf rdf:resource="#menuitem"/>
      <rdfs:subClassOf rdf:resource="#radio"/>
      <rdfs:seeAlso rdf:resource="#menuitem"/>
      <role:scope rdf:resource="#menu"/>
   </owl:Class>
   <owl:Class rdf:ID="slider">
      <rdfs:subClassOf rdf:resource="#range"/>
   </owl:Class>
   <owl:Class rdf:ID="tooltip">
      <rdfs:subClassOf rdf:resource="#description"/>
   </owl:Class>
   <owl:Class rdf:ID="tabpanel">
      <rdfs:subClassOf rdf:resource="#region"/>
   </owl:Class>
   <owl:Class rdf:ID="tablist">
      <rdfs:subClassOf rdf:resource="#directory"/>
      <rdfs:seeAlso rdf:resource="http://www.daisy.org/z3986/2005/z3986-2005.html#Guide"/>
   </owl:Class>
   <owl:Class rdf:ID="tab">
      <rdfs:subClassOf rdf:resource="#sectionhead"/>
      <rdfs:subClassOf rdf:resource="#widget"/>
      <role:scope rdf:resource="#tablist"/>
   </owl:Class>
   <owl:Class rdf:ID="tree">
      <rdfs:subClassOf rdf:resource="#select"/>
      <role:mustContain rdf:resource="#treeitem"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#multiselectable">
         <role:default>false</role:default>
      </role:supportedState>
   </owl:Class>
   <owl:Class rdf:ID="treeitem">
      <rdfs:subClassOf rdf:resource="#listitem"/>
      <rdfs:subClassOf rdf:resource="#option"/>
      <role:scope rdf:resource="#tree"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#expanded">
         <role:default>undefined</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#level"/>
   </owl:Class>
   <!--== Document Structure ==--><owl:Class rdf:ID="section">
      <rdfs:subClassOf rdf:resource="#structure"/>
      <rdfs:seeAlso rdf:resource="http://www.loc.gov/nls/z3986/v100/dtbook110doc.htm#frontmatter"/>
      <rdfs:seeAlso rdf:resource="http://www.loc.gov/nls/z3986/v100/dtbook110doc.htm#level"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/REC-smil/#par"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#templateid"/>
   </owl:Class>
   <owl:Class rdf:ID="sectionhead">
      <rdfs:subClassOf rdf:resource="#structure"/>
   </owl:Class>
   <owl:Class rdf:ID="document">
      <rdfs:subClassOf rdf:resource="#structure"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/di-gloss/#def-delivery-unit"/>
   </owl:Class>
   <owl:Class rdf:ID="region">
      <rdfs:subClassOf rdf:resource="#section"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/html401/present/frames.html#edef-FRAME"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/di-gloss/#def-perceivable-unit"/>
      <rdfs:seeAlso rdf:resource="#section"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#controls"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#expanded">
         <role:default>undefined</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#level"/>
   </owl:Class>
   <owl:Class rdf:ID="heading">
      <rdfs:subClassOf rdf:resource="#sectionhead"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/html4/struct/global.html#edef-H1"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/html4/struct/global.html#edef-H2"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/html4/struct/global.html#edef-H3"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/html4/struct/global.html#edef-H4"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/html4/struct/global.html#edef-H5"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/html4/struct/global.html#edef-H6"/>
      <rdfs:seeAlso rdf:resource="http://www.loc.gov/nls/z3986/v100/dtbook110doc.htm#levelhd"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#level"/>
   </owl:Class>
   <owl:Class rdf:ID="list">
      <rdfs:subClassOf rdf:resource="#region"/>
      <role:baseConcept rdf:resource="http://www.w3.org/TR/html4/struct/lists.html#edef-UL"/>
      <role:mustContain rdf:resource="#listitem"/>
   </owl:Class>
   <owl:Class rdf:ID="listitem">
      <rdfs:subClassOf rdf:resource="#section"/>
      <role:baseConcept rdf:resource="http://www.w3.org/TR/html4/struct/lists.html#edef-LI"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/xforms/slice8.html#ui-common-elements-item"/>
      <role:scope rdf:resource="#list"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#posinset"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#setsize"/>
   </owl:Class>
   <owl:Class rdf:ID="group">
      <rdfs:subClassOf rdf:resource="#section"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/html401/interact/forms.html#edef-FIELDSET"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#activedescendent"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#controls"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#expanded">
         <role:default>undefined</role:default>
      </role:supportedState>
   </owl:Class>
   <owl:Class rdf:ID="grid">
      <rdfs:subClassOf rdf:resource="#composite"/>
      <rdfs:subClassOf rdf:resource="#section"/>
      <role:baseConcept rdf:resource="http://www.w3.org/TR/html4/struct/tables.html#edef-TABLE"/>
      <role:mustContain rdf:resource="#row"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#level"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#multiselectable">
         <role:default>false</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#readonly">
         <role:default>false</role:default>
      </role:supportedState>
   </owl:Class>
   <owl:Class rdf:ID="row">
      <rdfs:subClassOf rdf:resource="#group"/>
      <role:baseConcept rdf:resource="http://www.w3.org/TR/html4/struct/tables.html#edef-TR"/>
      <role:scope rdf:resource="#grid"/>
      <role:scope rdf:resource="#treegrid"/>
      <role:mustContain rdf:resource="#gridcell"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#disabled">
         <role:default>false</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#level"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#selected">
         <role:default>undefined</role:default>
      </role:supportedState>
   </owl:Class>
   <owl:Class rdf:ID="gridcell">
      <rdfs:subClassOf rdf:resource="#section"/>
      <rdfs:subClassOf rdf:resource="#widget"/>
      <role:baseConcept rdf:resource="http://www.w3.org/TR/html4/struct/tables.html#edef-TD"/>
      <role:scope rdf:resource="#row"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#expanded">
         <role:default>undefined</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#readonly">
         <role:default>false</role:default>
      </role:supportedState>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#selected">
         <role:default>undefined</role:default>
      </role:supportedState>
   </owl:Class>
   <owl:Class rdf:ID="rowheader">
      <rdfs:subClassOf rdf:resource="#gridcell"/>
      <rdfs:subClassOf rdf:resource="#sectionhead"/>
      <role:baseConcept rdf:resource="http://www.w3.org/TR/html4/struct/tables.html#edef-TH"/>
      <role:scope rdf:resource="#row"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#sort">
         <role:default>none</role:default>
      </role:supportedState>
   </owl:Class>
   <owl:Class rdf:ID="columnheader">
      <rdfs:subClassOf rdf:resource="#gridcell"/>
      <rdfs:subClassOf rdf:resource="#sectionhead"/>
      <role:baseConcept rdf:resource="http://www.w3.org/TR/html4/struct/tables.html#edef-TH"/>
      <role:scope rdf:resource="#row"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#sort">
         <role:default>none</role:default>
      </role:supportedState>
   </owl:Class>
   <owl:Class rdf:ID="treegrid">
      <rdfs:subClassOf rdf:resource="#grid"/>
      <rdfs:subClassOf rdf:resource="#tree"/>
      <role:mustContain rdf:resource="#row"/>
   </owl:Class>
   <owl:Class rdf:ID="description">
      <rdfs:subClassOf rdf:resource="#section"/>
   </owl:Class>
   <owl:Class rdf:ID="directory">
      <rdfs:subClassOf rdf:resource="#list"/>
      <rdfs:seeAlso rdf:resource="http://www.daisy.org/z3986/2005/z3986-2005.html#Guide"/>
      <role:mustContain rdf:resource="#link"/>
   </owl:Class>
   <owl:Class rdf:ID="img">
      <rdfs:subClassOf rdf:resource="#section"/>
      <rdfs:seeAlso rdf:resource="http://www.loc.gov/nls/z3986/v100/dtbook110doc.htm#imggroup"/>
   </owl:Class>
   <owl:Class rdf:ID="presentation">
      <rdfs:subClassOf rdf:resource="#structure"/>
   </owl:Class>
   <owl:Class rdf:ID="separator">
      <rdfs:subClassOf rdf:resource="#structure"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/html401/present/graphics.html#edef-HR"/>
   </owl:Class>
   <!--== Specialized Regions ==--><owl:Class rdf:ID="application">
      <rdfs:subClassOf rdf:resource="#region"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/di-gloss/#def-delivery-unit"/>
   </owl:Class>
   <owl:Class rdf:ID="dialog">
      <rdfs:subClassOf rdf:resource="#window"/>
   </owl:Class>
   <owl:Class rdf:ID="alert">
      <rdfs:subClassOf rdf:resource="#status"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/xforms/slice8.html#ui-common-elements-alert"/>
   </owl:Class>
   <owl:Class rdf:ID="alertdialog">
      <rdfs:subClassOf rdf:resource="#alert"/>
      <rdfs:subClassOf rdf:resource="#dialog"/>
      <rdfs:seeAlso rdf:resource="http://www.w3.org/TR/xforms/slice8.html#ui-common-elements-alert"/>
   </owl:Class>
   <owl:Class rdf:ID="marquee">
      <rdfs:subClassOf rdf:resource="#section"/>
   </owl:Class>
   <owl:Class rdf:ID="log">
      <rdfs:subClassOf rdf:resource="#region"/>
   </owl:Class>
   <owl:Class rdf:ID="status">
      <rdfs:subClassOf rdf:resource="#composite"/>
      <rdfs:subClassOf rdf:resource="#region"/>
   </owl:Class>
   <owl:Class rdf:ID="progressbar">
      <rdfs:subClassOf rdf:resource="#status"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#valuemax"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#valuemin"/>
      <role:supportedState rdf:resource="http://www.w3.org/2005/07/aaa#valuenow"/>
   </owl:Class>
   <owl:Class rdf:ID="timer">
      <rdfs:subClassOf rdf:resource="#status"/>
   </owl:Class>
   <!--== Taxonomy Roles ==--><owl:Class rdf:ID="roletype-list"/>
   <owl:Class rdf:ID="widget-list"/>
   <owl:Class rdf:ID="structure-list"/>
   <owl:Class rdf:ID="composite-list"/>
   <owl:Class rdf:ID="window-list"/>
   <!--== User Input Controls ==--><owl:Class rdf:ID="input-list"/>
   <owl:Class rdf:ID="select-list"/>
   <owl:Class rdf:ID="listbox-list"/>
   <owl:Class rdf:ID="combobox-list"/>
   <owl:Class rdf:ID="option-list"/>
   <owl:Class rdf:ID="checkbox-list"/>
   <owl:Class rdf:ID="radio-list"/>
   <owl:Class rdf:ID="radiogroup-list"/>
   <owl:Class rdf:ID="textbox-list"/>
   <owl:Class rdf:ID="range-list"/>
   <owl:Class rdf:ID="spinbutton-list"/>
   <!--== User Interface Elements ==--><owl:Class rdf:ID="button-list"/>
   <owl:Class rdf:ID="link-list"/>
   <owl:Class rdf:ID="menu-list"/>
   <owl:Class rdf:ID="menubar-list"/>
   <owl:Class rdf:ID="toolbar-list"/>
   <owl:Class rdf:ID="menuitem-list"/>
   <owl:Class rdf:ID="menuitemcheckbox-list"/>
   <owl:Class rdf:ID="menuitemradio-list"/>
   <owl:Class rdf:ID="slider-list"/>
   <owl:Class rdf:ID="tooltip-list"/>
   <owl:Class rdf:ID="tabpanel-list"/>
   <owl:Class rdf:ID="tablist-list"/>
   <owl:Class rdf:ID="tab-list"/>
   <owl:Class rdf:ID="tree-list"/>
   <owl:Class rdf:ID="treeitem-list"/>
   <!--== Document Structure ==--><owl:Class rdf:ID="section-list"/>
   <owl:Class rdf:ID="sectionhead-list"/>
   <owl:Class rdf:ID="document-list"/>
   <owl:Class rdf:ID="region-list"/>
   <owl:Class rdf:ID="heading-list"/>
   <owl:Class rdf:ID="list-list"/>
   <owl:Class rdf:ID="listitem-list"/>
   <owl:Class rdf:ID="group-list"/>
   <owl:Class rdf:ID="grid-list"/>
   <owl:Class rdf:ID="row-list"/>
   <owl:Class rdf:ID="gridcell-list"/>
   <owl:Class rdf:ID="rowheader-list"/>
   <owl:Class rdf:ID="columnheader-list"/>
   <owl:Class rdf:ID="treegrid-list"/>
   <owl:Class rdf:ID="description-list"/>
   <owl:Class rdf:ID="directory-list"/>
   <owl:Class rdf:ID="img-list"/>
   <owl:Class rdf:ID="presentation-list"/>
   <owl:Class rdf:ID="separator-list"/>
   <!--== Specialized Regions ==--><owl:Class rdf:ID="application-list"/>
   <owl:Class rdf:ID="dialog-list"/>
   <owl:Class rdf:ID="alert-list"/>
   <owl:Class rdf:ID="alertdialog-list"/>
   <owl:Class rdf:ID="marquee-list"/>
   <owl:Class rdf:ID="log-list"/>
   <owl:Class rdf:ID="status-list"/>
   <owl:Class rdf:ID="progressbar-list"/>
   <owl:Class rdf:ID="timer-list"/>
</rdf:RDF>

6.2 Linearized version of data tables

6.2.3 Role details in list form

This is a linearized version of 3.4 Roles.

alert

A message with an alert or error information.

alertdialog

A separate window with an alert or error information.

application

A software unit executing a set of tasks for its users.

button

Allows for user-triggered actions.

checkbox

A control that has three possible values, (true, false, mixed).

columnheader

A table cell containing header information for a column.

combobox

Combobox is a presentation of a select, where users can type to locate a selected item.

description

Descriptive content for a page element which references this element via describedby.

dialog

A dialog is a small application window that sits above the application and is designed to interrupt the current processing of an application in order to prompt the user to enter information or require a response.

directory

A list of references to members of a single group.

document

Content that contains related information, such as a book.

grid

A grid contains cells of tabular data arranged in rows and columns (e.g., a table).

gridcell

A gridcell is a table cell in a grid. Gridcells may be active, editable, and selectable. Cells may have relationships such as controls to address the application of functional relationships.

group

A group is a section of user interface objects which would not be included in a page summary or table of contents by an assistive technology. See region for sections of user interface objects that should be included in a page summary or table of contents.

heading

A heading for a section of the page.

img

An img is a container for a collection elements that form an image.

link

Interactive reference to a resource (note, that in [XHTML] 2.0 any element can have an href attribute and thus be a link)

list

Group of small items.

listbox

A list box is a widget that allows the user to select one or more items from a list. Items within the list are static and may contain images.

listitem

A single item in a list.

log

A region where new information is added and old information may disappear such as chat logs, messaging, game log or an error log. In contrast to other regions, in this role there is a relationship between the arrival of new items in the log and the reading order. The log contains a meaningful sequence and new information is added only to the end of the log, not at arbitrary points.

marquee

A marquee is used to scroll text across the page.

menu

Offers a list of choices to the user.

menubar

A menubar is a container of menu items. Each menu item may activate a new sub-menu. Navigation behavior should be similar to the typical menu bar graphical user interface.

menuitem

A link in a menu. This is an option in a group of choices contained in a menu.

menuitemcheckbox

Defines a menuitem which is checkable (tri-state).

menuitemradio

Indicates a menu item which is part of a group of menuitemradio roles.

option

A selectable item in a list represented by a select.

presentation

An element whose role is presentational does not need to be mapped to the accessibility API.

progressbar

Used by applications for tasks that take a long time to execute, to show the execution progress.

radio

A radio is an option in single-select list. Only one radio control in a radiogroup can be selected at the same time.

radiogroup

A group of radio controls.

region

Region is a large perceivable section on the web page.

row

A row of table cells.

rowheader

A table cell containing header information for a row.

separator

A line or bar that separates and distinguishes sections of content.

slider

A user input where the user selects an input in a given range. This form of range expects an analog keyboard interface.

spinbutton

A form of Range that expects a user selecting from discrete choices.

status

This is a container for process advisory information to give feedback to the user.

tab

A header for a tabpanel.

tablist

A list of tabs, which are references to tabpanels.

tabpanel

Tabpanel is a container for the resources associated with a tab.

textbox

Inputs that allow free-form text as their value.

timer

A numerical counter which indicates an amount of elapsed time from a start point, or the time remaining until an end point.

toolbar

A toolbar is a collection of commonly used functions represented in compact visual form.

tooltip

A popup that displays a description for an element when a user passes over or rests on that element. Supplement to the normal tooltip processing of the user agent.

tree

A form of a list having groups inside groups, where sub trees can be collapsed and expanded.

treegrid

A grid whose rows can be expanded and collapsed in the same manner as for a tree.

treeitem

An option item of a tree. This is an element within a tree that may be expanded or collapsed

6.2.3.2 Taxonomy Roles

The following roles are used as base types for applied roles. Base classes are used to build a picture of the role taxonomy class hierarchy within the taxonomy. Note that while all roles in this section are abstract, not all abstract roles are in this section. This section includes only the most high-level abstractions in the taxonomy.

Roles in this section include:

• composite
• roletype
• structure
• widget
• window

Role: roletype

Base role from which all other roles in this taxonomy inherit.

Properties of this role describe the structural and functional purpose of objects that are assigned this role (known in RDF terms as "instances"). A Role is a concept that can be used to understand and operate instances.

6.2.3.2.1 Characteristics:

Is Abstract:

True

Child Roles:

• widget
• structure
• window

Related Concepts:

• XHTML role
• HTML link (rel & rev)
• Dublin Core type

Supported States and Properties:

• datatype
• describedby
• dropeffect
• flowto
• grab
• haspopup
• hidden
• labelledby
• owns
• tabindex

---

Role: widget

A component of a GUI (graphical user interface).

Widget Roles all map to accessibility APIs. Widgets are ... , see @@

6.2.3.2.1 Characteristics:

Is Abstract:

True

Parent Role:

roletype

Child Roles:

• composite
• input
• button
• link
• tab
• gridcell

Supported States and Properties:

• controls
• disabled

Inherited States and Properties:

• Global States

---

Role: structure

A document structural element.

Roles for document structure are also required to support the accessibility of dynamic Web content to assist assistive technology in determining active content vs. static document content. Structural Roles, by themselves do not all map to accessibility APIs, but are used to create widget roles or assist content adaptation.

This schema is likely to evolve as new use cases are added to the scope of this specification.

6.2.3.2.1 Characteristics:

Is Abstract:

True

Parent Role:

roletype

Child Roles:

• section
• sectionhead
• document
• presentation
• separator

Supported States and Properties:

• atomic
• busy
• channel
• live
• relevant

Inherited States and Properties:

• Global States

---

Role: composite

A widget that may contain navigable descendants.

Descendants of this role may not have the "nameFrom" value of "subtree" set.

6.2.3.2.1 Characteristics:

Is Abstract:

True

Parent Role:

widget

Child Roles:

• select
• spinbutton
• grid
• status

Supported States and Properties:

activedescendent

Inherited States and Properties:

• controls
• disabled
• Global States

Name From:

author

---

Role: window

Browser or application window

6.2.3.2.1 Characteristics:

Is Abstract:

True

Parent Role:

roletype

Child Roles:

• dialog

Inherited States and Properties:

• Global States

Name From:

• subtree
• author

6.2.3.3 User Input Controls

These roles ...

Roles in this section include:

• checkbox
• combobox
• input
• listbox
• option
• radio
• radiogroup
• range
• select
• spinbutton
• textbox

Role: input

Generic type for widgets that can have a value.

6.2.3.3.1 Characteristics:

Is Abstract:

True

Parent Role:

widget

Child Roles:

• select
• option
• textbox
• range

Related Concepts:

XForms input

Supported States and Properties:

• invalid
• required

Inherited States and Properties:

• controls
• disabled
• Global States

Name From:

author

---

Role: select

A form control that allows the user to make selections from a set of choices. A select must contain an option.

6.2.3.3.1 Characteristics:

Is Abstract:

True

Parent Role:

• composite
• group
• input

Child Roles:

• listbox
• combobox
• radiogroup
• menu
• tree

Inherited States and Properties:

• activedescendent
• atomic
• busy
• channel
• controls
• disabled
• expanded
• invalid
• live
• relevant
• required
• templateid
• Global States

Name From:

author

---

Role: listbox

A list box is a widget that allows the user to select one or more items from a list. Items within the list are static and may contain images.

6.2.3.3.1 Characteristics:

Parent Role:

• list
• select

Related Concepts:

• HTML select
• XForms select

Supported States and Properties:

multiselectable

Inherited States and Properties:

• activedescendent
• atomic
• busy
• channel
• controls
• disabled
• expanded
• invalid
• level
• live
• relevant
• required
• templateid
• Global States

Name From:

author

Accessible Name Required:

True

---

Role: combobox

Combobox is a presentation of a select, where users can type to locate a selected item.

Combobox is the combined presentation of a single line textbox with a drop down select widget. The combobox may be open or closed. An "open" combobox allows users to type freeform text into the textbox whereas a "closed" combobox only shows text in the textbox which can be retrieved from the select. Typically a "closed" text field will use the text entered to quickly search and fill the textfield with text from the select.

NOTE: In [XFORMS] the same select can have one of 3 appearances: combo-box, drop-down box or group of radio-buttons. Besides, many browsers (if not all of them) allow users to type in a drop-down select as well.

6.2.3.3.1 Characteristics:

Parent Role:

select

Related Concepts:

• HTML select
• XForms select

Required Child Elements:

option

Supported States and Properties:

autocomplete

Inherited States and Properties:

• activedescendent
• atomic
• busy
• channel
• controls
• disabled
• expanded
• invalid
• live
• relevant
• required
• templateid
• Global States

Name From:

author

Accessible Name Required:

True

---

Role: option

A selectable item in a list represented by a select.

An option must appear inside an element with select role.

6.2.3.3.1 Characteristics:

Parent Role:

input

Child Roles:

• checkbox
• menuitem
• treeitem

Base Concept:

HTML option

Related Concepts:

• listitem
• XForms item

Parent Element:

select

Supported States and Properties:

• checked
• selected

Inherited States and Properties:

• controls
• disabled
• invalid
• required
• Global States

Name From:

• subtree
• author

Accessible Name Required:

True

---

Role: checkbox

A control that has three possible values, (true, false, mixed).

Many checkboxes do not use the mixed value, and thus are effectively boolean checkboxes. However, the checked state supports the "mixed" value to support cases such as installers where an option has been partially installed.

6.2.3.3.1 Characteristics:

Parent Role:

option

Child Roles:

• radio
• menuitemcheckbox

Related Concepts:

HTML input (type : checkbox)

Inherited States and Properties:

• checked
• controls
• disabled
• invalid
• required
• selected
• Global States

Name From:

• subtree
• author

Accessible Name Required:

True

---

Role: radio

A radio is an option in single-select list. Only one radio control in a radiogroup can be selected at the same time.

6.2.3.3.1 Characteristics:

Parent Role:

checkbox

Child Roles:

• menuitemradio

Related Concepts:

HTML input (type : radio)

Inherited States and Properties:

• checked
• controls
• disabled
• invalid
• required
• selected
• Global States

Name From:

• subtree
• author

Accessible Name Required:

True

---

Role: radiogroup

A group of radio controls.

6.2.3.3.1 Characteristics:

Parent Role:

select

Related Concepts:

list

Required Child Elements:

radio

Inherited States and Properties:

• activedescendent
• atomic
• busy
• channel
• controls
• disabled
• expanded
• invalid
• live
• relevant
• required
• templateid
• Global States

Name From:

author

Accessible Name Required:

True

---

Role: textbox

Inputs that allow free-form text as their value.

If the multiline property is true, the control accepts line breaks within the input, as in a HTML textarea. Otherwise this is a simple text box.

Intended use is in languages that do not have a text input object (such as SVG), or cases in which an element with different semantics is repurposed as an input box. The user would use this role when additional states or properties are applied to a standard text input control. This is to indicate to the user agent that it must process additional states and properties such as invalid and required.

6.2.3.3.1 Characteristics:

Parent Role:

input

Related Concepts:

• XForms input
• HTML textarea

Supported States and Properties:

• autocomplete
• multiline
• readonly
• secret

Inherited States and Properties:

• controls
• disabled
• invalid
• required
• Global States

Name From:

author

Accessible Name Required:

True

---

Role: range

Represents a range of values that can be set by the user.

6.2.3.3.1 Characteristics:

Is Abstract:

True

Parent Role:

input

Child Roles:

• spinbutton
• slider

Supported States and Properties:

• valuemax required
• valuemin required
• valuenow required

Inherited States and Properties:

• controls
• disabled
• invalid
• required
• Global States

Name From:

author

---

Role: spinbutton

A form of Range that expects a user selecting from discrete choices.

A spinbutton allows the user to select from the given range through the use of an up and down button. Visibly, the current value is incremented or decremented until a maximum or minimum value is reached. This functionality should be accomplished programmatically through the use of up and down arrows on the keyboard.

6.2.3.3.1 Characteristics:

Parent Role:

• composite
• range

Inherited States and Properties:

• activedescendent
• controls
• disabled
• invalid
• required
• valuemax
• valuemin
• valuenow
• Global States

Name From:

author

Accessible Name Required:

True

6.2.3.4 User Interface Elements

These roles ...

Roles in this section include:

• button
• link
• menu
• menubar
• menuitem
• menuitemcheckbox
• menuitemradio
• slider
• tab
• tablist
• tabpanel
• toolbar
• tooltip
• tree
• treeitem

Role: button

Allows for user-triggered actions.

Buttons are mostly used for discrete, atomic actions. Its value is cognitive; the idea that this is a user action opportunity is made very clear by making it look like a front-panel button on a device. The animation of the button in response to indirect (by mouse) manipulation fosters the illusion of direct manipulation and keeps user cognition in sync with the user interface perception of user action events. Standardizing the appearance of buttons enhances recognition as buttons and arraying them compactly in toolbars, for example.

Buttons support the optional state pressed. Buttons with this state present are toggle buttons. When pressed is "true" the button is depressed, when pressed is "false" it is not depressed.

6.2.3.4.1 Characteristics:

Parent Role:

widget

Base Concept:

HTML button

Related Concepts:

• link
• XForms trigger

Supported States and Properties:

pressed

Inherited States and Properties:

• controls
• disabled
• Global States

Name From:

• subtree
• author

Accessible Name Required:

True

Children Presentational:

True

---

Role: link

Interactive reference to a resource (note, that in [XHTML] 2.0 any element can have an href attribute and thus be a link)

6.2.3.4.1 Characteristics:

Parent Role:

widget

Related Concepts:

HTML link

Inherited States and Properties:

• controls
• disabled
• Global States

Name From:

• subtree
• author

Accessible Name Required:

True

---

Role: menu

Offers a list of choices to the user.

A menu is often a list of links to important sections of a document or a site. The menu role is appropriate when the list of links is presented in a manner similar to a menu on a desktop appication.

6.2.3.4.1 Characteristics:

Parent Role:

• list
• select

Related Concepts:

• DTB sidebar
• XForms select
• JAPI MENU

Required Child Elements:

menuitem

Inherited States and Properties:

• activedescendent
• atomic
• busy
• channel
• controls
• disabled
• expanded
• invalid
• level
• live
• relevant
• required
• templateid
• Global States

Name From:

author

Accessible Name Required:

True

---

Role: menubar

A menubar is a container of menu items. Each menu item may activate a new sub-menu. Navigation behavior should be similar to the typical menu bar graphical user interface.

Menubar is used to create a menubar similar to those found in Windows, the Mac, and Gnome desktops. A menubar is used to create a consistent climate of frequently used commands.

6.2.3.4.1 Characteristics:

Parent Role:

group

Related Concepts:

toolbar

Inherited States and Properties:

• activedescendent
• atomic
• busy
• channel
• controls
• expanded
• live
• relevant
• templateid
• Global States

Name From:

author

---

Role: toolbar

A toolbar is a collection of commonly used functions represented in compact visual form.

The toolbar is often a subset of functions found in a menubar designed to reduced user effort in using these functions.

If this is not keyboard accessible the actions defined in the toolbar must be reproduced in an accessible, device independent fashion.

6.2.3.4.1 Characteristics:

Parent Role:

group

Related Concepts:

menubar

Supported States and Properties:

multiselectable

Inherited States and Properties:

• activedescendent
• atomic
• busy
• channel
• controls
• expanded
• live
• relevant
• templateid
• Global States

Name From:

author

---

Role: menuitem

A link in a menu. This is an option in a group of choices contained in a menu.

It may be disabled or active. It may also have a popup.

6.2.3.4.1 Characteristics:

Parent Role:

• listitem
• option

Child Roles:

• menuitemcheckbox
• menuitemradio

Related Concepts:

JAPI MENU_ITEM

Parent Element:

menu

Inherited States and Properties:

• atomic
• busy
• channel
• checked
• controls
• disabled
• invalid
• live
• posinset
• relevant
• required
• selected
• setsize
• templateid
• Global States

Name From:

• subtree
• author

Accessible Name Required:

True

---

Role: menuitemcheckbox

Defines a menuitem which is checkable (tri-state).

The checked state indicates whether the menu item is checked, unchecked, or mixed.

6.2.3.4.1 Characteristics:

Parent Role:

• checkbox
• menuitem

Related Concepts:

menuitem

Parent Element:

menu

Inherited States and Properties:

• atomic
• busy
• channel
• checked
• controls
• disabled
• invalid
• live
• posinset
• relevant
• required
• selected
• setsize
• templateid
• Global States

Name From:

• subtree
• author

Accessible Name Required:

True

---

Role: menuitemradio

Indicates a menu item which is part of a group of menuitemradio roles.

Checking of one menuitemradio in a group will unchecked the other group members.

Menuitems should also be separated into a group by a separator.

6.2.3.4.1 Characteristics:

Parent Role:

• menuitem (see structure)
• radio

Related Concepts:

menuitem

Parent Element:

menu

Inherited States and Properties:

• atomic
• busy
• channel
• checked
• controls
• disabled
• invalid
• live
• posinset
• relevant
• required
• selected
• setsize
• templateid
• Global States

Name From:

• subtree
• author

Accessible Name Required:

True

---

Role: slider

A user input where the user selects an input in a given range. This form of range expects an analog keyboard interface.

A slider has the added functionality of being able to select a value through the use of a visible slider. The slider would be keyboard accessible and provide a visible thumb position that represents the current position within the slider.

6.2.3.4.1 Characteristics:

Parent Role:

range

Inherited States and Properties:

• controls
• disabled
• invalid
• required
• valuemax
• valuemin
• valuenow
• Global States

Name From:

author

Accessible Name Required:

True

Children Presentational:

True

---

Role: tooltip

A popup that displays a description for an element when a user passes over or rests on that element. Supplement to the normal tooltip processing of the user agent.

Objects with this role must be referenced through the use of a describedby. If the tooltip has active elements it must be keyboard navigable.

6.2.3.4.1 Characteristics:

Parent Role:

description

Inherited States and Properties:

• atomic
• busy
• channel
• live
• relevant
• templateid
• Global States

Accessible Name Required:

True

---

Role: tabpanel

Tabpanel is a container for the resources associated with a tab.

Note: There must be a means to associate a tabpanel element with its associated tab in a tablist. Using the labelledby property on the tabpanel to reference the tab is the recommended way to achieve this.

6.2.3.4.1 Characteristics:

Parent Role:

region

Inherited States and Properties:

• atomic
• busy
• channel
• controls
• expanded
• level
• live
• relevant
• templateid
• Global States

Name From:

author

Accessible Name Required:

True

---

Role: tablist

A list of tabs, which are references to tabpanels.

6.2.3.4.1 Characteristics:

Parent Role:

directory

Related Concepts:

DAISY Guide

Inherited States and Properties:

• atomic
• busy
• channel
• controls
• expanded
• level
• live
• relevant
• templateid
• Global States

Name From:

• subtree
• author

---

Role: tab

A header for a tabpanel.

Tab is used as a grouping label, providing a link for selecting the tab content to be rendered to the user. The currently active tab is determined if the tab or an object in the associated tabpanel has focus.

Tabs appear in the container tablist. Only one tab may be selected at a time. At any time, one tab must be selected.

One of the tabs in tablist must be the current tab. The tabpanel associated with the current tab, must be rendered to the user. Other tabpanels are typically hidden from the user until the user selects the tab associated with that tabpanel.

6.2.3.4.1 Characteristics:

Parent Role:

• sectionhead
• widget

Parent Element:

tablist

Inherited States and Properties:

• atomic
• busy
• channel
• controls
• disabled
• live
• relevant
• Global States

Name From:

• subtree
• author

---

Role: tree

A form of a list having groups inside groups, where sub trees can be collapsed and expanded.

6.2.3.4.1 Characteristics:

Parent Role:

select

Child Roles:

• treegrid

Required Child Elements:

treeitem

Supported States and Properties:

multiselectable

Inherited States and Properties:

• activedescendent
• atomic
• busy
• channel
• controls
• disabled
• expanded
• invalid
• live
• relevant
• required
• templateid
• Global States

Name From:

• subtree
• author

Accessible Name Required:

True

---

Role: treeitem

An option item of a tree. This is an element within a tree that may be expanded or collapsed

6.2.3.4.1 Characteristics:

Parent Role:

• listitem
• option

Parent Element:

tree

Supported States and Properties:

• expanded
• level

Inherited States and Properties:

• atomic
• busy
• channel
• checked
• controls
• disabled
• invalid
• live
• posinset
• relevant
• required
• selected
• setsize
• templateid
• Global States

Name From:

• subtree
• author

Accessible Name Required:

True

6.2.3.5 Document Structure

These roles ...

These roles are similar to roles from the XHTML Roles Module [XHTML-ROLES]. See Introduction to using roles for more information.

Roles in this section include:

• columnheader
• description
• directory
• document
• grid
• gridcell
• group
• heading
• img
• list
• listitem
• presentation
• region
• row
• rowheader
• section
• sectionhead
• separator
• treegrid

Role: section

A base abstract class representing a renderable structural containment unit found in a document or application.

6.2.3.5.1 Characteristics:

Is Abstract:

True

Parent Role:

structure

Child Roles:

• region
• listitem
• group
• grid
• gridcell
• description
• img
• marquee

Related Concepts:

• DTB frontmatter
• DTB level
• SMIL par

Supported States and Properties:

templateid

Inherited States and Properties:

• atomic
• busy
• channel
• live
• relevant
• Global States

Name From:

• subtree
• author

---

Role: sectionhead

The section head labels or summarizes the topic of its related section

6.2.3.5.1 Characteristics:

Is Abstract:

True

Parent Role:

structure

Child Roles:

• tab
• heading
• rowheader
• columnheader

Inherited States and Properties:

• atomic
• busy
• channel
• live
• relevant
• Global States

Name From:

• subtree
• author

---

Role: document

Content that contains related information, such as a book.

The document role is used to tell the screen reader to use a document browsing mode, because screen readers use most of the keyboard navigation keys to provide their own keyboard user interface for this type of navigation.

Documents must also have an labelledby attribute leading to one or more elements with non-empty text content. This text should be suitable for use as a navigation preview or table-of-contents entry for the page section in question.

Exceptions: There may be a few exceptions where the host-language provides a useful label mechanism, such as:

• The root element in an HTML document may omit the labelledby attribute - if the title element has been used.
• Any group element in SVG may omit the labelledby attribute if it contains a non-empty title element.

6.2.3.5.1 Characteristics:

Parent Role:

structure

Related Concepts:

Device Independence Delivery Unit

Inherited States and Properties:

• atomic
• busy
• channel
• live
• relevant
• Global States

Name From:

author

Accessible Name Required:

True

---

Role: region

Region is a large perceivable section on the web page.

Region defines a group of elements that together form a large perceivable section, that the author feels should be included in a summary of page features. A region must have a heading, e.g., an instance of the heading role or a reference to an element with the labelledby property. A region does not necessarily follow the logical structure of the content, but follows the perceivable structure of the page.

When defining regions of a web page, authors should consider using standard document landmark roles defined by the XHTML Roles Module [XHTML-ROLES]. User agents and assistive technologies may treat these as standard navigation landmarks. If the definition of these regions are inadequate, authors should use the ARIA region role and provide the appropriate title text.

6.2.3.5.1 Characteristics:

Parent Role:

section

Child Roles:

• tabpanel
• list
• application
• log
• status

Related Concepts:

• HTML Frame
• Device Independence Glossary perceivable unit
• section

Supported States and Properties:

• controls
• expanded
• level

Inherited States and Properties:

• atomic
• busy
• channel
• live
• relevant
• templateid
• Global States

Name From:

author

---

Role: heading

A heading for a section of the page.

This indicates that an object serves as a header. Often, headings will be referenced with the labelledby property of the section for which they serve as a header. If headings are organized into a logical outline, the level property can be used to indicate the nesting level.

6.2.3.5.1 Characteristics:

Parent Role:

sectionhead

Related Concepts:

• HTML h1
• HTML h2
• HTML h3
• HTML h4
• HTML h5
• HTML h6
• DTD levelhd

Supported States and Properties:

level

Inherited States and Properties:

• atomic
• busy
• channel
• live
• relevant
• Global States

Accessible Name Required:

True

---

Role: list

Group of small items.

6.2.3.5.1 Characteristics:

Parent Role:

region

Child Roles:

• listbox
• menu
• directory

Base Concept:

HTML ul

Required Child Elements:

listitem

Inherited States and Properties:

• atomic
• busy
• channel
• controls
• expanded
• level
• live
• relevant
• templateid
• Global States

Name From:

author

---

Role: listitem

A single item in a list.

6.2.3.5.1 Characteristics:

Parent Role:

section

Child Roles:

• menuitem
• treeitem

Base Concept:

HTML li

Related Concepts:

XForms item

Parent Element:

list

Supported States and Properties:

• posinset
• setsize

Inherited States and Properties:

• atomic
• busy
• channel
• live
• relevant
• templateid
• Global States

Name From:

• subtree
• author

Accessible Name Required:

True

---

Role: group

A group is a section of user interface objects which would not be included in a page summary or table of contents by an assistive technology. See region for sections of user interface objects that should be included in a page summary or table of contents.

Authors should use a role of group to form logical collection of items in a widget such as a: row in a grid; children in a tree widget forming a collection of siblings in a hierarchy; or a collection of items having the same container in a directory. Therefore, proper handling of group by assistive technologies must be determined by the context in which it is provided. Group members that are outside the [DOM] subtree of the group would need to have explicit relationships assigned to participate in the group. Groups may also be nested. If the author believes a section is significant enough in terms of the entire delivery unit web page then the author should assign the section a role of region or a standard XHTML Role landmark.

6.2.3.5.1 Characteristics:

Parent Role:

section

Child Roles:

• select
• menubar
• toolbar
• row

Related Concepts:

HTML fieldset

Supported States and Properties:

• activedescendent
• controls
• expanded

Inherited States and Properties:

• atomic
• busy
• channel
• live
• relevant
• templateid
• Global States

Name From:

author

---

Role: grid

A grid contains cells of tabular data arranged in rows and columns (e.g., a table).

This does not necessarily imply presentation.The table role is used as a container for tabular data. The table construct describes relationships between data such that it may be used for different presentations.

Grids contain cells that may be focusable. Grids allow the user to move focus between grid cells with 2-D navigation. Grids may have row and column headers which also have functional value based on the implementation. Grid cells may have values determined by an equation.

Grids are single selectable or multiselectable. Properties for selectable or multiselectable must be provided by the author. Grids may be used for spreadsheets such as in Open Office, Microsoft Office, etc.

6.2.3.5.1 Characteristics:

Parent Role:

• composite
• section

Child Roles:

• treegrid

Base Concept:

HTML table

Required Child Elements:

row

Supported States and Properties:

• level
• multiselectable
• readonly

Inherited States and Properties:

• activedescendent
• atomic
• busy
• channel
• controls
• disabled
• live
• relevant
• templateid
• Global States

Name From:

author

Accessible Name Required:

True

---

Role: row

A row of table cells.

6.2.3.5.1 Characteristics:

Parent Role:

group

Base Concept:

HTML tr

Parent Element:

• grid
• treegrid

Required Child Elements:

gridcell

Supported States and Properties:

• disabled
• level
• selected

Inherited States and Properties:

• activedescendent
• atomic
• busy
• channel
• controls
• expanded
• live
• relevant
• templateid
• Global States

Name From:

• subtree
• author

---

Role: gridcell

A gridcell is a table cell in a grid. Gridcells may be active, editable, and selectable. Cells may have relationships such as controls to address the application of functional relationships.

Note: If the expanded property is provided, it applies only to the individual cell. It is not a proxy for the container row, which also can be expanded. The main use case for providing this property on a cell is pivot table type behavior.

6.2.3.5.1 Characteristics:

Parent Role:

• section
• widget

Child Roles:

• rowheader
• columnheader

Base Concept:

HTML td

Parent Element:

row

Supported States and Properties:

• expanded
• readonly
• selected

Inherited States and Properties:

• atomic
• busy
• channel
• controls
• disabled
• live
• relevant
• templateid
• Global States

Name From:

• subtree
• author

Accessible Name Required:

True

---

Role: rowheader

A table cell containing header information for a row.

Rowheader can be used as a row header in a table or grid. It also could be used in a pie chart to show a similar relationship in the data.

The rowheader establishes a relationship between it and all cells in the corresponding row. It is a structural equivalent to an [HTML] th element with a row scope.

6.2.3.5.1 Characteristics:

Parent Role:

• gridcell
• sectionhead

Base Concept:

HTML th with scope=row

Parent Element:

row

Supported States and Properties:

sort

Inherited States and Properties:

• atomic
• busy
• channel
• controls
• disabled
• expanded
• live
• readonly
• relevant
• selected
• templateid
• Global States

Name From:

• subtree
• author

Accessible Name Required:

True

---

Role: columnheader

A table cell containing header information for a column.

Columnheader can be used as a column header in a table or grid. It could also be used in a pie chart to show a similar relationship in the data.

The columnheader establishes a relationship between it and all cells in the corresponding row. It is a structural equivalent to an [HTML] th element with a column scope.

6.2.3.5.1 Characteristics:

Parent Role:

• gridcell
• sectionhead

Base Concept:

HTML th with scope=col

Parent Element:

row

Supported States and Properties:

sort

Inherited States and Properties:

• atomic
• busy
• channel
• controls
• disabled
• expanded
• live
• readonly
• relevant
• selected
• templateid
• Global States

Name From:

• subtree
• author

Accessible Name Required:

True

---

Role: treegrid

A grid whose rows can be expanded and collapsed in the same manner as for a tree.

6.2.3.5.1 Characteristics:

Parent Role:

• grid
• tree

Required Child Elements:

row

Inherited States and Properties:

• activedescendent
• atomic
• busy
• channel
• controls
• disabled
• expanded
• invalid
• level
• live
• multiselectable
• readonly
• relevant
• required
• templateid
• Global States

Name From:

author

Accessible Name Required:

True

---

Role: description

Descriptive content for a page element which references this element via describedby.

6.2.3.5.1 Characteristics:

Parent Role:

section

Child Roles:

• tooltip

Inherited States and Properties:

• atomic
• busy
• channel
• live
• relevant
• templateid
• Global States

---

Role: directory

A list of references to members of a single group.

People should use this role for static tables of contents. This includes tables of contents built with lists, including nested lists. Dynamic tables of contents, however, would be a tree.

Note: directories do not have to contain links. They can have simply unlinked references.

6.2.3.5.1 Characteristics:

Parent Role:

list

Child Roles:

• tablist

Related Concepts:

DAISY Guide

Required Child Elements:

link

Inherited States and Properties:

• atomic
• busy
• channel
• controls
• expanded
• level
• live
• relevant
• templateid
• Global States

Name From:

• subtree
• author

---

Role: img

An img is a container for a collection elements that form an image.

An img can contain captions, descriptive text as well as multiple image files that when viewed together give the impression of a single image. An img represents a single graphic within a document whether or not it is formed by a collection of drawing objects. Elements with a role of img must have a label or alternative text.

6.2.3.5.1 Characteristics:

Parent Role:

section

Related Concepts:

DTB imggroup

Inherited States and Properties:

• atomic
• busy
• channel
• live
• relevant
• templateid
• Global States

Name From:

author

Accessible Name Required:

True

Children Presentational:

True

---

Role: presentation

An element whose role is presentational does not need to be mapped to the accessibility API.

Intended use is when an element is used to change the look of the page but does not have all the functional, interactive, or structural relevance implied by the element type.

Example use cases:

• A layout table is a presentation.
• An object tag whose content is decorative like a white space image or decorative flash object
• An image used for white space

The user agent may remove all structural aspects of the element being repurposed. For example, a table marked as presentation would remove the table, td, th, tr, etc. elements while preserving the individual text elements within it. Because the user agent knows to ignore the structural aspects implied in a table, no harm is done by using a table for layout.

6.2.3.5.1 Characteristics:

Parent Role:

structure

Inherited States and Properties:

• atomic
• busy
• channel
• live
• relevant
• Global States

---

Role: separator

A line or bar that separates and distinguishes sections of content.

This is a visual separator between sections of content. For example, separators are found between lists of menu items in a menu.

6.2.3.5.1 Characteristics:

Parent Role:

structure

Related Concepts:

HTML hr

Inherited States and Properties:

• atomic
• busy
• channel
• live
• relevant
• Global States

Name From:

author

Children Presentational:

True

6.2.3.6 Specialized Regions

These roles ...

Roles in this section include:

• alert
• alertdialog
• application
• dialog
• log
• marquee
• progressbar
• status
• timer

Role: application

A software unit executing a set of tasks for its users.

The intent is to hint to the assistive technology to switch its normal browsing mode functionality to one in which they would for an application. To properly set the role of "application," an author should set the application role on a document element which encompasses the entirety of the web page for which assistive technology browser navigation mode is applied. Screen readers have a browse navigation mode where keys, such as up and down arrows, are consumed and used to browse the document. Consumption of these keys breaks use of these keys by the web application.

Use case: In an email application it has a document and an application in it. The author would want to use typical application navigation mode to cycle through the list of emails. Much of this navigation would be defined by the application author. However, when reading an email message the user may want to switch to a document mode where they control browsing navigation.

Applications must also have an labelledby attribute leading to one or more elements with non-empty text content. This text should be suitable for use as a navigation preview or table-of-contents entry for the page section in question.

Exceptions: There may be a few exceptions where the host-language provides a useful label mechanism, such as:

• The root element in an HTML document may omit the labelledby attribute - if the title element has been used.

Any group element in SVG may omit the labelledby attribute if it contains a non-empty title element.

6.2.3.6.1 Characteristics:

Parent Role:

region

Related Concepts:

Device Independence Delivery Unit

Inherited States and Properties:

• atomic
• busy
• channel
• controls
• expanded
• level
• live
• relevant
• templateid
• Global States

Name From:

author

Accessible Name Required:

True

---

Role: dialog

A dialog is a small application window that sits above the application and is designed to interrupt the current processing of an application in order to prompt the user to enter information or require a response.

Dialog boxes should have a title. They must have a focused item.

6.2.3.6.1 Characteristics:

Parent Role:

window

Child Roles:

• alertdialog

Inherited States and Properties:

• Global States

Name From:

author

Accessible Name Required:

True

---

Role: alert

A message with an alert or error information.

Alerts are used to convey messages to alert the user. In the case of audio warnings this is an accessible alternative for a hearing impaired user. The alert role goes on the container of the document subtree containing the alert message. Alerts are specialized forms of the status role which should be processed as an atomic live region. Alerts do not require user input and therefore should not receive focus. Alerts should not receive focus or require user input and therefore users should not be required to close an alert. The user agent may consider firing an accessibility alert event, when the alert is created, provided one is specified by the intended accessibility API.

If an alert requires focus to close the alert then it is suggested that an alertdialog be used.

6.2.3.6.1 Characteristics:

Parent Role:

status

Child Roles:

• alertdialog

Related Concepts:

XForms alert

Inherited States and Properties:

• activedescendent
• atomic
• busy
• channel
• controls
• disabled
• expanded
• level
• live
• relevant
• templateid
• Global States

Name From:

author

---

Role: alertdialog

A separate window with an alert or error information.

Alertdialogs are used to convey messages to alert the user. The alertdialog role goes on the container of the subtree containing the alert message. Unlike alert, alertdialog requires a response from the user such as to confirm that the user understands the alert being generated. It is expected that authors shall set focus to an active document element within the alertdialog such as a form edit field or an ok pushbutton. The user agent may consider firing an accessibility alert event, when the alert is created, provided one is specified by the intended accessibility API.

6.2.3.6.1 Characteristics:

Parent Role:

• alert
• dialog

Related Concepts:

XForms alert

Inherited States and Properties:

• activedescendent
• atomic
• busy
• channel
• controls
• disabled
• expanded
• level
• live
• relevant
• templateid
• Global States

Name From:

author

Accessible Name Required:

True

---

Role: marquee

A marquee is used to scroll text across the page.

A common usage is a stock ticker. A marquee behaves like a region with an assumed default aria live property value of polite. An example of a marquee is a stock ticker.

6.2.3.6.1 Characteristics:

Parent Role:

section

Inherited States and Properties:

• atomic
• busy
• channel
• live
• relevant
• templateid
• Global States

Accessible Name Required:

True

---

Role: log

A region where new information is added and old information may disappear such as chat logs, messaging, game log or an error log. In contrast to other regions, in this role there is a relationship between the arrival of new items in the log and the reading order. The log contains a meaningful sequence and new information is added only to the end of the log, not at arbitrary points.

6.2.3.6.1 Characteristics:

Parent Role:

region

Inherited States and Properties:

• atomic
• busy
• channel
• controls
• expanded
• level
• live
• relevant
• templateid
• Global States

Name From:

author

Accessible Name Required:

True

---

Role: status

This is a container for process advisory information to give feedback to the user.

A status object must have content within it to provide the actual status information. This object typically does not receive focus.

Status is a form of live region. It's assumed default value for the live property is "polite" and that it is not controlled by another part of the page. If another part of the page does control it then that part of the page should assign a controls relationship on the object controlling the live region with an ID reference to the the live region. In this instance the role of the live region should be set to "region" and the appropriate live region properties should be set (Michael: link the live region properties phrase to the equivalent section in the adaptable states and properties module).

Some cells of a Braille display may be reserved to render the status.

6.2.3.6.1 Characteristics:

Parent Role:

• composite
• region

Child Roles:

• alert
• progressbar
• timer

Inherited States and Properties:

• activedescendent
• atomic
• busy
• channel
• controls
• disabled
• expanded
• level
• live
• relevant
• templateid
• Global States

---

Role: progressbar

Used by applications for tasks that take a long time to execute, to show the execution progress.

This lets the user know that the user's action request has been accepted and that the application continues (or ceases, in the case of a static display) to make progress toward completing the requested action.

6.2.3.6.1 Characteristics:

Parent Role:

status

Supported States and Properties:

• valuemax required
• valuemin required
• valuenow required

Inherited States and Properties:

• activedescendent
• atomic
• busy
• channel
• controls
• disabled
• expanded
• level
• live
• relevant
• templateid
• Global States

Name From:

author

Accessible Name Required:

True

Children Presentational:

True

---

Role: timer

A numerical counter which indicates an amount of elapsed time from a start point, or the time remaining until an end point.

The text contents of the timer object indicate the current time measurement, and are updated as that amount changes. However, unless the datatype attribute is used, the timer value is not necessarily machine parseable. The text contents are updated at fixed intervals except when the timer is paused or reaches an end-point.

A timer is a form of polite live region.

6.2.3.6.1 Characteristics:

Parent Role:

status

Inherited States and Properties:

• activedescendent
• atomic
• busy
• channel
• controls
• disabled
• expanded
• level
• live
• relevant
• templateid
• Global States

Name From:

author

Accessible Name Required:

True