Commit 3ebb415

<rdef>command</rdef>

<div class="role-description">

<p>A form of widget that performs an action but does not receive input data.</p>

</div>

<table class="role-features">

<caption>Characteristics:</caption>

<div class="role-description">

<p>A <a>widget</a> that may contain navigable descendants or <a>owned</a> children.</p>

<p>Authors SHOULD ensure that a composite widget exists as a single navigation stop within the larger navigation system of the web page. Once the composite widget has focus, authors SHOULD provide a separate navigation mechanism for users to navigate to <a>elements</a> that are descendants or owned children of the composite element.</p>

</div>

<table class="role-features">

<caption>Characteristics:</caption>

<rdef>input</rdef>

<div class="role-description">

<p>A generic type of <a>widget</a> that allows user input.</p>

</div>

<table class="role-features">

<caption>Characteristics:</caption>

<rdef>landmark</rdef>

<div class="role-description">

<p>A perceivable <rref>section</rref> containing content that is relevant to a specific, author-specified purpose and sufficiently important that users will likely want to be able to navigate to the section easily and to have it listed in a summary of the page. Such a page summary could be generated dynamically by a user agent or assistive technology.</p>

<p>Authors designate the purpose of the content by assigning a role that is a subclass of the landmark role and, when needed, by providing a brief, descriptive label.</p>

<p><a>Assistive technologies</a> SHOULD enable users to quickly navigate to landmark regions.

<a>User agents</a> MAY enable users to quickly navigate to landmark regions.</p>

</div>

<table class="role-features">

<caption>Characteristics:</caption>

<rdef>range</rdef>

<div class="role-description">

<p>An element representing a range of values.</p>

</div>

<table class="role-features">

<caption>Characteristics:</caption>

<div class="role-description">

<p>The base <a>role</a> from which all other roles inherit.</p>

<p>Properties of this role describe the structural and functional purpose of <a>objects</a> that are assigned this role. A role is a concept that can be used to understand and operate instances.</p>

</div>

<table class="role-features">

<caption>Characteristics:</caption>

<rdef>section</rdef>

<div class="role-description">

<p>A renderable structural containment unit in a document or application.</p>

</div>

<table class="role-features">

<caption>Characteristics:</caption>

<rdef>sectionhead</rdef>

<div class="role-description">

<p>A structure that labels or summarizes the topic of its related section.</p>

</div>

<table class="role-features">

<caption>Characteristics:</caption>

<rdef>select</rdef>

<div class="role-description">

<p>A form widget that allows the user to make selections from a set of choices.</p>

</div>

<table class="role-features">

<caption>Characteristics:</caption>

<div class="role-description">

<p>A document structural <a>element</a>.</p>

<p><a>Roles</a> for document structure support the accessibility of dynamic web content by helping <a>assistive technologies</a> determine active content versus static document content. Structural roles by themselves do not all map to <a>accessibility <abbr title="Application Programing Interfaces">APIs</abbr></a>, but are used to create <a>widget</a> roles or assist content adaptation for assistive technologies.</p>

</div>

<table class="role-features">

<caption>Characteristics:</caption>

<div class="role-description">

<p>An interactive component of a graphical user interface (<abbr title="Graphical User Interface">GUI</abbr>).</p>

<p>Widgets are discrete user interface objects with which the user can interact. Widget <a>roles</a> map to standard features in <a>accessibility <abbr title="Application Programing Interfaces">APIs</abbr></a>. When the user navigates an element assigned any of the non-abstract subclass roles of <code>widget</code>, <a>assistive technologies</a> that typically intercept standard keyboard events SHOULD switch to an application browsing mode, and pass keyboard events through to the web application. The intent is to hint to certain <a>assistive technologies</a> to switch from normal browsing mode into a mode more appropriate for interacting with a web application; some <a>user agents</a> have a browse navigation mode where keys, such as up and down arrows, are used to browse the document, and this native behavior prevents the use of these keys by a web application.</p>

</div>

<table class="role-features">

<caption>Characteristics:</caption>

<div class="role-description">

<p>A browser or application window.</p>

<p><a>Elements</a> with this <a>role</a> have a window-like behavior in a graphical user interface (<abbr title="Graphical User Interface">GUI</abbr>) context, regardless of whether they are implemented as a native window in the operating system, or merely as a section of the document styled to look like a window.</p>

<p class="note">In the description of this role, the term "application" does not refer to the <rref>application</rref> role, which specifies specific assistive technology behaviors.</p>

</div>

<table class="role-features">

<caption>Characteristics:</caption>