index.html

<!doctype html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
  <head>
    <title>Accessible Rich Internet Applications (WAI-ARIA) 1.3</title>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
    <meta name="color-scheme" content="light dark" />
    <script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove"></script>
    <script class="remove" src="common/script/aria.js"></script>
    <script src="common/script/resolveReferences.js" class="remove"></script>
    <script src="common/script/participants.js" class="remove"></script>
    <script class="remove">
      var respecConfig = {
        github: "w3c/aria",
        doJsonLd: true,
        // specification status (e.g., WD, LC, NOTE, etc.). If in doubt use ED.
        specStatus: "ED",
        //crEnd:                "2012-04-30",
        //perEnd:               "2013-07-23",
        //publishDate:          "2024-01-23",

        // the specifications short name, as in https://www.w3.org/TR/short-name/
        shortName: "wai-aria-1.3",

        // if you wish the publication date to be other than today, set this
        //publishDate:  "2014-12-11",
        copyrightStart: "2013",

        // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
        // and its maturity status
        //previousPublishDate:  "2014-06-12",
        //previousMaturity:  "WD",
        prevRecURI: "https://www.w3.org/TR/wai-aria/",
        //previousDiffURI: "https://www.w3.org/TR/2014/REC-wai-aria-20140320/",

        // if there a publicly available Editors Draft, this is the link
        edDraftURI: "https://w3c.github.io/aria/",

        // if this is a LCWD, uncomment and set the end of its review period
        // lcEnd: "2012-02-21",

        // editors, add as many as you like
        // only "name" is required
        editors: [
          {
            name: "James Nurthen",
            company: "Adobe",
            companyURL: "https://www.adobe.com/",
            w3cid: 37155,
          },
          {
            name: "Peter Krautzberger",
            company: "krautzource UG",
            companyURL: "https://www.krautzource.com",
            w3cid: 60398,
          },
          {
            name: "Daniel Montalvo",
            company: "W3C",
            companyURL: "http://www.w3.org",
            w3cid: 114058,
          },
        ],
        formerEditors: [
          {
            name: "Michael Cooper",
            company: "W3C",
            companyURL: "https://www.w3.org",
            w3cid: 34017,
            note: "Editor until 2023",
          },
          {
            name: "Joanmarie Diggs",
            company: "Igalia, S.L.",
            companyURL: "https://www.igalia.com",
            w3cid: 68182,
            note: "Editor until 2021",
          },
          {
            name: "Shane McCarron",
            company: "Spec-Ops",
            // companyURL: "https://www.spec-ops.io",
            w3cid: 89030,
            note: "Editor until 2018",
          },
          {
            name: "Richard Schwerdtfeger",
            company: "Knowbility",
            companyURL: "https://knowbility.org/",
            w3cid: 2460,
            note: "Editor until October 2017",
          },
          {
            name: "James Craig",
            company: "Apple Inc.",
            companyURL: "https://www.apple.com/accessibility",
            w3cid: 42459,
            note: "Editor until May 2016",
          },
        ],

        // authors, add as many as you like.
        // This is optional, uncomment if you have authors as well as editors.
        // only "name" is required. Same format as editors.

        //authors:  [
        //    { name: "Your Name", url: "http://example.org/",
        //      company: "Your Company", companyURL: "http://example.com/" },
        //],

        /*
		alternateFormats: [
			{ uri: 'aria-diff.html', label: "Diff from Previous Recommendation" } ,
			{ uri: 'aria.ps', label: "PostScript version" },
			{ uri: 'aria.pdf', label: "PDF version" }
		],
		*/

        // errata: 'http://www.w3.org/2010/02/rdfa/errata.html',

        // name of the WG
        group: "aria",
        maxTocLevel: 4,

        // Spec URLs
        ariaSpecURLs: {
          ED: "https://w3c.github.io/aria/",
          FPWD: "https://www.w3.org/TR/wai-aria-1.3/",
          WD: "https://www.w3.org/TR/wai-aria-1.3/",
          CR: "https://www.w3.org/TR/wai-aria-1.3/",
          REC: "https://www.w3.org/TR/wai-aria-1.3/",
        },
        accNameURLs: {
          ED: "https://w3c.github.io/accname/",
          WD: "https://www.w3.org/TR/accname-1.2/",
          FPWD: "https://www.w3.org/TR/accname-1.2/",
          CR: "https://www.w3.org/TR/accname-1.2/",
          REC: "https://www.w3.org/TR/accname-1.2/",
        },
        coreMappingURLs: {
          ED: "https://w3c.github.io/core-aam/",
          WD: "https://www.w3.org/TR/core-aam-1.2/",
          FPWD: "https://www.w3.org/TR/core-aam-1.2/",
          CR: "https://www.w3.org/TR/core-aam-1.2/",
          REC: "https://www.w3.org/TR/core-aam-1.2/",
        },
        dpubModURLs: {
          ED: "https://w3c.github.io/dpub-aria/",
          FPWD: "https://www.w3.org/TR/dpub-aria-1.1/",
          WD: "https://www.w3.org/TR/dpub-aria-1.1/",
          REC: "https://www.w3.org/TR/dpub-aria-1.1/",
        },
        graphicsMappingModURLs: {
          ED: "https://w3c.github.io/graphics-aam/",
          FPWD: "https://www.w3.org/TR/graphics-aam-1.0/",
          WD: "https://www.w3.org/TR/graphics-aam-1.0/",
          CR: "https://www.w3.org/TR/graphics-aam-1.0/",
          PR: "https://www.w3.org/TR/graphics-aam-1.0/",
          REC: "https://www.w3.org/TR/graphics-aam-1.0/",
        },
        graphicsModURLs: {
          ED: "https://w3c.github.io/graphics-aria/",
          FPWD: "https://www.w3.org/TR/graphics-aria/",
          WD: "https://www.w3.org/TR/graphics-aria/",
          REC: "https://www.w3.org/TR/graphics-aria/",
        },
        htmlMappingURLs: {
          ED: "https://w3c.github.io/html-aam/",
          FPWD: "https://www.w3.org/TR/html-aam-1.0/",
          WD: "https://www.w3.org/TR/html-aam/",
          REC: "https://www.w3.org/TR/html-aam/",
        },
        practicesURLs: {
          ED: "https://www.w3.org/WAI/ARIA/apg/",
          WD: "https://www.w3.org/WAI/ARIA/apg/",
          FPWD: "https://www.w3.org/WAI/ARIA/apg/",
          CR: "https://www.w3.org/WAI/ARIA/apg/",
          REC: "https://www.w3.org/WAI/ARIA/apg/",
        },

        preProcess: [linkCrossReferences, getParticipants],
        postProcess: [ariaAttributeReferences],
        xref: ["dom", "accname-1.2", "core-aam-1.2", "infra", "HTML"],
        definitionMap: [],
      };
      function respecChangelogFilter(commit) {
        // if (commit.message.toLowerCase().startsWith("generated by")) return false;
        // else if (commit.message.toLowerCase().startsWith("travis-ci")) return false;
        // else if (commit.message.toLowerCase().startsWith("fix")) return false;
        // else if (commit.message.toLowerCase().startsWith("editorial")) return false;
        // else if (commit.message.toLowerCase().includes("typo")) return false;
        // else return true;
        return !/^Merge pull|^tidy|^TRAVIS|^ADMIN|^Generated by|respec|(editorial)|.md|editorial|Editiorial|edtiorial|^chore|^refactor|^tests?|^docs|w3cgruntbot|index.html|typo|^nit/i.test(
          commit.message,
        );
      }
    </script>
    <script src="common/biblio.js" class="remove"></script>
  </head>
  <body>
    <section id="abstract">
      <p>
        Accessibility of web content requires semantic information about widgets, structures, and behaviors, in order to allow assistive technologies to convey appropriate information to persons with
        disabilities. This specification provides an ontology of roles, states, and properties that define accessible user interface elements and can be used to improve the accessibility and
        interoperability of web content and applications. These semantics are designed to allow an author to properly convey user interface behaviors and structural information to assistive
        technologies in document-level markup. This version adds features new since WAI-ARIA 1.1 [[wai-aria-1.1]] to improve interoperability with assistive technologies to form a more consistent
        accessibility model for [[HTML]] and [[SVG2]]. This specification complements both [[HTML]] and [[SVG2]].
      </p>
      <p>
        This document is part of the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> suite described in the
        <a href="https://www.w3.org/WAI/standards-guidelines/aria/"><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Overview</a>.
      </p>
    </section>
    <section id="sotd">
      <p>
        The Accessible Rich Internet Applications Working Group seeks feedback on any aspect of the specification. When submitting feedback, please consider issues in the context of the companion
        documents. To comment, <a href="https://github.com/w3c/aria/issues/new">file an issue in the <abbr title="World Wide Web Consortium">W3C</abbr> ARIA GitHub repository</a>. If this is not
        feasible, send email to <a href="mailto:public-aria@w3.org?subject=Comment%20on%20WAI-ARIA%201.2">public-aria@w3.org</a> (<a href="http://lists.w3.org/Archives/Public/public-aria/"
          >comment archive</a
        >). In-progress updates to the document can be viewed in the <a href="https://w3c.github.io/aria/">publicly visible editors' draft</a>.
      </p>
    </section>
    <section class="informative" id="introduction">
      <h1>Introduction</h1>
      <p>The goals of this specification include:</p>
      <ul>
        <li>expanding the accessibility information that can be supplied by the author;</li>
        <li>
          requiring that supporting host languages provide full keyboard support that can be implemented in a device-independent way, for example, by telephones, handheld devices, e-book readers, and
          televisions;
        </li>
        <li>improving the accessibility of dynamic content generated by scripts; and</li>
        <li>providing for interoperability with <a>assistive technologies</a>.</li>
      </ul>
      <p>
        WAI-ARIA is a technical specification that provides a framework to improve the accessibility and interoperability of web content and applications. This document is primarily for developers
        creating custom widgets and other web application components. Please see the <a href="http://www.w3.org/WAI/intro/aria">WAI-ARIA Overview</a> for links to related documents for other
        audiences, such as
        <cite
          ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite
        >
        [[WAI-ARIA-PRACTICES-1.2]] that introduces developers to the accessibility problems that WAI-ARIA is intended to solve, the fundamental concepts, and the technical approach of WAI-ARIA.
      </p>
      <p>
        This document currently handles two aspects of <a>roles</a>: user interface functionality and structural <a>relationships</a>. For more information and use cases, see
        <cite
          ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite
        >
        [[WAI-ARIA-PRACTICES-1.2]] for the use of roles in making interactive content accessible.
      </p>
      <p>
        Roles defined by this specification are designed to support the roles used by platform <a>accessibility <abbr title="Application Programing Interfaces">APIs</abbr></a
        >. Declaration of these roles on elements within dynamic web content is intended to support interoperability between the web content and assistive technologies that utilize
        <a>accessibility <abbr title="Application Programing Interfaces">APIs</abbr></a
        >.
      </p>
      <p>
        The schema to support this standard has been designed to be extensible 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 [[XMLSCHEMA11-2]]. However, being able to define similarities
        between roles, such as <a href="#baseConcept">baseConcepts</a> and more descriptive definitions, would not be available in <abbr title="Extensible Markup Language Schema Datatypes">XSD</abbr>.
      </p>
      <p>
        <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> 1.2 is a member of the
        <a href="https://www.w3.org/WAI/intro/aria"><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> 1.2 suite</a> that defines how to expose semantics of WAI-ARIA and other web
        content languages to <a>accessibility <abbr title="Application Programing Interfaces">APIs</abbr></a
        >.
      </p>
      <section class="section" id="intro_ria_accessibility">
        <h2>Rich Internet Application Accessibility</h2>
        <p>
          The domain of web accessibility defines how to make web content usable by persons with disabilities. Persons with certain types of disabilities use <a>assistive technologies</a> (<abbr
            title="Assistive Technologies"
            >AT</abbr
          >) to interact with content. Assistive technologies can transform the presentation of content into a format more suitable to the user, and can allow the user to interact in different ways.
          For example, the user might need to, or choose to, interact with a slider widget via arrow keys, instead of dragging and dropping with a mouse. In order to accomplish this effectively, the
          software needs to understand the <a>semantics</a> of the content. Semantics is the science of meaning; in this case, used to assign roles, states, and properties that apply to user interface
          and content elements as a human would understand. For instance, if a paragraph is semantically identified as such, assistive technologies can interact with it as a unit separable from the
          rest of the content, knowing the exact boundaries of that paragraph. An adjustable range slider or collapsible list (a.k.a. a tree <a>widget</a>) are more complex examples, in which various
          parts of the widget have semantics that need to be properly identified for assistive technologies to support effective interaction.
        </p>
        <p>
          New technologies often overlook semantics required for accessibility, and new authoring practices often misuse the intended semantics of those technologies. [=Elements=] that have one
          defined meaning in the language are used with a different meaning intended to be understood by the user.
        </p>
        <p>
          For example, web application developers create collapsible tree widgets in HTML using CSS and JavaScript even though HTML has no semantic <code>tree</code> element. To a non-disabled user,
          it might look and act like a collapsible tree widget, but without appropriate semantics, the tree widget might not be <a>perceivable</a> to, or <a>operable</a> by, a person with a disability
          because assistive technologies might not recognize the role. Similarly, web application developers create interactive button widgets in SVG using JavaScript even though SVG has no semantic
          <code>button</code> element. To a non-disabled user, it might look and act like a button widget, but without appropriate semantics, the button widget might not be <a>perceivable</a> to, or
          <a>operable</a> by, a person with a disability because assistive technologies might not recognize the role.
        </p>
        <p>
          The incorporation of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> is a way for an author to provide proper semantics for custom widgets to make these widgets
          accessible, usable, and interoperable with assistive technologies. This specification identifies the types of widgets and structures that are commonly recognized by accessibility products,
          by providing an <a>ontology</a> of corresponding <a>roles</a> that can be attached to content. This allows elements with a given role to be understood as a particular widget or structural
          type regardless of any semantics inherited from the implementing host language. Roles are a common property of platform
          <a>accessibility <abbr title="Application Programing Interfaces">APIs</abbr></a> which assistive technologies use to provide the user with effective presentation and interaction.
        </p>
        <p>
          The Roles Model includes interaction <a>widgets</a> and elements denoting document structure. The Roles Model describes inheritance and details the [=attributes=] each role supports.
          Information about mapping of roles to accessibility <abbr title="Application Programing Interfaces">APIs</abbr> is provided by the
          <cite><a href="" class="core-mapping">Core Accessibility API Mappings</a></cite> [[CORE-AAM-1.2]].
        </p>
        <p>
          Roles are element types and will not change with time or user actions. Role information is used by assistive technologies, through interaction with the user agent, to provide normal
          processing of the specified element type.
        </p>
        <p>
          States and properties are used to declare important attributes of an element that affect and describe interaction. They enable the <a>user agent</a> and operating system to properly handle
          the element even when the attributes are dynamically changed by client-side scripts. For example, alternative input and output technology, such as screen readers and speech dictation
          software, need to be able to recognize and effectively manipulate and communicate various interaction states (e.g., disabled, checked) to the user.
        </p>
        <p>
          While it is possible for assistive technologies to access these properties directly through the <cite><a href="https://www.w3.org/TR/dom/">Document Object Model</a></cite> [[DOM]], the
          preferred mechanism is for the user agent to map the states and properties to the accessibility <abbr title="Application Programing Interfaces">API</abbr> of the operating system. See the
          <cite><a href="" class="core-mapping">Core Accessibility API Mappings</a></cite> [[CORE-AAM-1.2]] and the
          <cite><a href="" class="accname">Accessible Name and Description Computation</a></cite> [[ACCNAME-1.2]] for details.
        </p>
        <p id="desc_contractmodel">
          <a href="#fig-contractmodel"></a> illustrates the relationship between user agents (e.g., browsers), accessibility APIs, and assistive technologies. It describes the "contract" provided by
          the user agent to assistive technologies, which includes typical accessibility information found in the accessibility <abbr title="Application Programing Interfaces">API</abbr> for many of
          our accessible platforms for GUIs (role, state, selection, <a>event</a> notification, <a>relationship</a> information, and descriptions). The DOM, usually HTML, acts as the data model and
          view in a typical model-view-controller relationship, and JavaScript acts as the controller by manipulating the style and content of the displayed data. The user agent conveys relevant
          information to the operating system's accessibility API, which can be used by any assistive technologies, such as screen readers.
        </p>
        <figure id="fig-contractmodel">
          <img alt="The contract model with accessibility APIs" height="389" src="img/accessibleelement.png" width="723" />
          <figcaption>The contract model with accessibility <abbr title="Application Programing Interfaces">APIs</abbr></figcaption>
        </figure>
        <p>
          For more information see
          <cite
            ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite
          >
          for the use of roles in making interactive content accessible.
        </p>
        <p>
          Users of alternate input devices need <a>keyboard accessible</a> content. The new semantics, when combined with the recommended keyboard interactions provided in
          <cite
            ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite
          >, will allow alternate input solutions to facilitate command and control via an alternate input solution.
        </p>
        <p>
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> introduces navigational <a>landmarks</a> through its Roles Model and the
          <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> role landmarks, which can help persons with dexterity and vision impairments by providing for improved keyboard navigation.
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> can also be used to assist persons with cognitive learning disabilities. The additional semantics allow authors to
          restructure and substitute alternative content as needed.
        </p>
        <p>
          <a>Assistive technologies</a> need the ability to support alternative inputs by getting and setting the current value of <a>widget</a> states and properties. Assistive technologies also need
          to determine what <a>objects</a> are selected and manage widgets that allow multiple selections, such as list boxes and grids.
        </p>
        <p>
          Speech-based command and control systems can benefit from <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics like the <code>role</code> attribute to assist in
          conveying audio information to the user. For example, upon encountering an element with a role of <rref>menu</rref> with child elements of role <rref>menuitem</rref> each containing text
          content representing a different flavor, a speech system might state to the user, "Select one of three choices: chocolate, strawberry, or vanilla."
        </p>
        <p>
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> is intended to be used as a supplement for native language semantics, not a replacement. When the host language provides a
          feature that provides equivalent accessibility to the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> feature, use the host language feature.
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> should only be used in cases where the host language lacks the needed <a>role</a>, <a>state</a>, and [=ARIA/property=]
          indicators. Use a host language feature that is as similar as possible to the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> feature, then refine the meaning by adding
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>. For instance, a multi-selectable grid could be implemented as a table, and then
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> used to clarify that it is an interactive grid, not just a static data table. This allows for the best possible fallback
          for user agents that do not support <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> and preserves the integrity of the host language semantics.
        </p>
      </section>
      <section id="target-audience">
        <h2>Target Audience</h2>
        <p>
          This specification defines the basic model for <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>, including roles, states, properties, and values. It impacts several
          audiences:
        </p>
        <ul>
          <li>[=user agents=] that process content containing <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> features;</li>
          <li><a>Assistive technologies</a> that present content in special ways to user with disabilities;</li>
          <li>Authors who create content;</li>
          <li>Authoring tools that help authors create conforming content; and</li>
          <li>Conformance checkers that verify appropriate use of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>.</li>
        </ul>
        <p>Each conformance requirement indicates the audience to which it applies.</p>
        <p>
          Although this specification is applicable to the above audiences, it is not specifically targeted to, nor is it intended to be the sole source of information for, any of these audiences. The
          following documents provide important supporting information:
        </p>
        <ul>
          <li>[[[WAI-ARIA-PRACTICES-1.2]]] addresses authoring recommendations for HTML, and is also of interest to developers of authoring tools and conformance checkers.</li>
          <li>[[[CORE-AAM-1.2]]] addresses developers of [=user agents=] and <a class="termref">assistive technologies</a>.</li>
          <li>[[[ACCNAME-1.2]]] also addresses developers of [=user agents=] and <a class="termref">assistive technologies</a>.</li>
        </ul>
      </section>
      <section id="ua-support">
        <h2>User Agent Support</h2>
        <p><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> relies on user agent support for its features in two ways:</p>
        <ul>
          <li>
            Mainstream [=user agents=] use <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> to alter how host language features are exposed to <a>accessibility APIs</a> in order to
            improve accessibility. The mechanism for this is defined in the <cite><a href="" class="core-mapping">Core Accessibility API Mappings</a></cite
            >.
          </li>
          <li>
            <a>Assistive technologies</a> use the enhanced information available in an accessibility API, or uses the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> markup
            directly via the <abbr title="Document Object Model">DOM</abbr>, to convey semantic and interaction information to the user.
          </li>
        </ul>
        <p>
          Aside from using <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> markup to improve what is exposed to accessibility APIs, user agents behave as they would natively.
          Assistive technologies react to the extra information in the accessibility API as they already do for the same information on non-web content. User agents that are not assistive
          technologies, however, need do nothing beyond providing appropriate updates to the accessibility API.
        </p>
        <p>
          The <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> specification neither requires nor forbids user agents from enhancing native presentation and interaction behaviors on
          the basis of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> markup. Mainstream user agents might expose
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> navigational landmarks (for example, as a dialog box or through a keyboard command) with the intention to facilitate
          navigation for all users. User agents are encouraged to maximize their usefulness to users, including users without disabilities.
        </p>
        <p>
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> is intended to provide missing semantics so that the intent of the author can be conveyed to assistive technologies.
          Generally, authors using <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> will provide the appropriate presentation and interaction features. Over time, host languages can
          add <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> equivalents, such as new form controls, that are implemented as standard accessible user interface controls by the
          user agent. This allows authors to use them instead of custom <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> enabled user interface components. In this case the user
          agent would support the native host language feature. Developers of host languages that implement <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> are advised to continue
          supporting <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics when they do not adversely conflict with implicit host language semantics, as
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics more clearly reflect the intent of the author if the host language features are inadequate to meet the author's
          needs.
        </p>
      </section>
      <section id="co-evolution">
        <h2>Co-Evolution of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> and Host Languages</h2>
        <p>
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> is intended to augment semantics in supporting languages like [[HTML]] and [[SVG2]], or to be used as an accessibility
          enhancement technology in other markup-based languages that do not explicitly include support for ARIA. It clarifies semantics to assistive technologies when authors create new types of
          objects, via style and script, that are not yet directly supported by the language of the page, because the invention of new types of objects is faster than standardized support for them
          appears in web languages.
        </p>
        <p>
          It is not appropriate to create objects with style and script when the host language provides a semantic element for that type of object. While
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> can improve the accessibility of these objects, accessibility is best provided by allowing the user agent to handle the
          object natively. For example, it's better to use an <code>h1</code> element in HTML than to use the <rref>heading</rref> role on a <code>div</code> element.
        </p>
        <p>
          It is expected that, over time, host languages will evolve to provide semantics for objects that currently can only be declared with
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>. This is natural and desirable, as one goal of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> is to
          help stimulate the emergence of more semantic and accessible markup. When native semantics for a given feature become available, it is appropriate for authors to use the native feature and
          stop using <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> for that feature. Legacy content can continue to use
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>, however, so the need for user agents to support
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> remains.
        </p>
        <p>
          While specific features of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> might lose importance over time, the general possibility of
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> to add semantics to web pages is expected to be a persistent need. Host languages might not implement all the semantics
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> provides, and various host languages can implement different subsets of the features. New types of objects are continually
          being developed, and one goal of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> is to provide a way to make such objects accessible, because authoring practices often
          advance faster than host language standards. In this way, <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> and host languages both evolve together but at different rates.
        </p>
        <p>
          Some host languages exist to create semantics for features other than the user interface. For example, SVG expresses the semantics behind production of graphical objects, not of user
          interface components that those objects can represent. Host languages might, by design, not provide native semantics that map to
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> features. In these cases, <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> could be adopted as a
          long-term approach to add semantic information to user interface components.
        </p>
      </section>
      <section id="authoring_practices">
        <h2>Authoring Practices</h2>
        <section id="authoring_tools">
          <h3>Authoring Tools</h3>
          <p>
            Many of the requirements in the definitions of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a>roles</a>, <a>states</a>, and [=ARIA/properties=] can be checked
            automatically during the development process, similar to other quality control processes used for validating code. To assist authors who are creating custom widgets, authoring tools can
            compare widget roles, states, and properties to those supported in <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> as well as those supported in related and
            cross-referenced roles, states, and properties. Authoring tools can notify authors of errors in widget design patterns, and can also prompt developers for information that cannot be
            determined from context alone. For example, a scripting library can determine the labels for the tree items in a tree view, but would need to prompt the author to label the entire tree. To
            help authors visualize a logical accessibility structure, an authoring environment might provide an outline view of a web resource based on the
            <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> markup.
          </p>
          <p>
            In both HTML and SVG, <code>tabindex</code> is an important way browsers support keyboard <a href="#host_general_focus">focus navigation</a> for implementations of
            <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>; authoring and debugging tools can check to make sure <code>tabindex</code> values are properly set. For example, error
            conditions can include cases where more than one treeitem in a tree has a <code>tabindex</code> value greater than or equal to 0, where <code>tabindex</code> is not set on any treeitem, or
            where <pref>aria-activedescendant</pref> is not defined when the element with the role tree has a <code>tabindex</code> value of greater than or equal to 0.
          </p>
        </section>
        <section id="authoring_testing">
          <h3>Testing Practices and Tools</h3>
          <p>
            The accessibility of interactive content cannot be confirmed by static checks alone. Developers of interactive content should test for device-independent access to <a>widgets</a> and
            applications, and should verify accessibility <abbr title="application programing interface">API</abbr> access to all content and changes during user interaction.
          </p>
        </section>
      </section>
      <section id="at_support">
        <h2>Assistive Technologies</h2>
        <p>
          Programmatic access to accessibility semantics is essential for assistive technologies. Most assistive technologies interact with user agents, like other applications, through a recognized
          accessibility API. Perceivable objects in the user interface are exposed to assistive technologies as accessible objects, defined by the accessibility API interfaces. To do this properly,
          accessibility information – role, states, properties as well as contextual information – needs to be accurately conveyed to the assistive technologies through the accessibility API. When a
          state change occurs, the user agent provides the appropriate event notification to the accessibility API. Contextual information, in many host languages like HTML, can be determined from the
          <abbr title="Document Object Model">DOM</abbr> itself as it provides a contextual tree hierarchy.
        </p>
        <p>
          While some assistive technologies interact with these accessibility APIs, others might access the content directly from the <abbr title="Document Object Model">DOM</abbr>. These technologies
          can restructure, simplify, style, or reflow the content to help a different set of users. Common use cases for these types of adaptations might be the aging population, persons with
          cognitive impairments, or persons in environments that interfere with use of their tools. For example, the availability of regional navigational landmarks can allow for a mobile device
          adaptation that shows only portions of the content at any one time based on its semantics. This could reduce the amount of information the user needs to process at any one time. In other
          situations it might be appropriate to replace a custom user interface control with something that is easier to navigate with a keyboard, or touch screen device.
        </p>
      </section>
    </section>
    <section class="informative" id="terms">
      <h1>Important Terms</h1>
      <div>
        <p>While some terms are defined in place, the following definitions are used throughout this document.</p>
        <dl class="termlist">
          <dt>
            <dfn data-export="">Accessibility <abbr title="Application Programming Interface">API</abbr></dfn>
          </dt>
          <dd>
            <p>
              Operating systems and other platforms provide a set of interfaces that expose information about <a class="termref">objects</a> and <a class="termref">events</a> to
              <a>assistive technologies</a>. Assistive technologies use these interfaces to get information about and interact with those <a class="termref">widgets</a>. Examples of accessibility APIs
              are <a href="https://docs.microsoft.com/en-us/windows/win32/winauto/microsoft-active-accessibility">Microsoft Active Accessibility</a> [[MSAA]],
              <a href="https://learn.microsoft.com/en-us/windows/win32/winauto/entry-uiauto-win32">Microsoft User Interface Automation</a> [[UI-AUTOMATION]],
              <abbr title="Microsoft Active Accessibility">MSAA</abbr> with
              <cite
                ><a href="https://learn.microsoft.com/en-us/windows/win32/winauto/iaccessibleex"><abbr title="User Interface Automation">UIA</abbr> Express</a></cite
              >
              [[UIA-EXPRESS]], the <a href="https://developer.apple.com/documentation/appkit/nsaccessibility">Mac <abbr title="OS Ten">OS X</abbr> Accessibility Protocol</a> [[AXAPI]], the
              <cite><a href="https://gnome.pages.gitlab.gnome.org/atk/">Linux/Unix Accessibility Toolkit</a></cite> [[ATK]] and
              <cite><a href="https://gnome.pages.gitlab.gnome.org/at-spi2-core/libatspi/">Assistive Technology Service Provider Interface</a></cite> [[AT-SPI]], and
              <a href="https://wiki.linuxfoundation.org/accessibility/iaccessible2/start">IAccessible2</a> [[IAccessible2]].
            </p>
          </dd>
          <dt><dfn data-export="">Accessible object</dfn></dt>
          <dd>
            <p>
              A [=nodes|node=] in the <a class="termref">accessibility tree</a> of a platform <a>accessibility <abbr title="application programming interface">API</abbr></a
              >. Accessible objects expose various <a class="termref">states</a>, [=ARIA/properties=], and <a class="termref">events</a> for use by <a>assistive technologies</a>. In the context of
              markup languages (e.g., HTML and SVG) in general, and of WAI-ARIA in particular, markup [=elements=] and their [=attributes=] are represented as accessible objects.
            </p>
          </dd>
          <dt><dfn data-export="">Assistive Technologies</dfn></dt>
          <dd>
            <p>Hardware and/or software that:</p>
            <ul>
              <li>relies on services provided by a <a>user agent</a> to retrieve and render Web content</li>
              <li>works with a user agent or web content itself through the use of APIs, and</li>
              <li>provides services beyond those offered by the user agent to facilitate user interaction with web content by people with disabilities</li>
            </ul>
            <p>This definition might differ from that used in other documents.</p>
            <p>Examples of assistive technologies that are important in the context of this document include the following:</p>
            <ul>
              <li>screen magnifiers, which are used to enlarge and improve the visual readability of rendered text and images;</li>
              <li>screen readers, which are most-often used to convey information through synthesized speech or a refreshable Braille display;</li>
              <li>text-to-speech software, which is used to convert text into synthetic speech;</li>
              <li>speech recognition software, which is used to allow spoken control and dictation;</li>
              <li>alternate input technologies (including head pointers, on-screen keyboards, single switches, and sip/puff devices), which are used to simulate the keyboard;</li>
              <li>alternate pointing devices, which are used to simulate mouse pointing and clicking.</li>
            </ul>
          </dd>
          <dt><dfn data-local-lt="deprecate|deprecation">Deprecated</dfn></dt>
          <dd>
            <p>
              A deprecated <a class="termref" href="#dfn-role">role</a>, <a class="termref" href="#dfn-state">state</a>, or <a class="termref" href="#dfn-property">property</a> is one which has been
              outdated by newer constructs or changed circumstances, and which might be removed in future versions of the
              <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> specification. [=user agents=] are encouraged to continue to support items identified as deprecated for backward
              compatibility. For more information, see <a href="#deprecated" class="specref">Deprecated Requirements</a> in the Conformance section.
            </p>
          </dd>
          <dt><dfn>Defines</dfn></dt>
          <dd>
            <p>
              Used in an attribute description to denote that the value <a href="#propcharacteristic_value">type</a> is an <a href="#valuetype_integer">integer</a>,
              <a href="#valuetype_number">number</a>, or <a href="#valuetype_string">string</a>.
            </p>
            <p>Related Terms: <a>Identifies</a>, <a>Indicates</a></p>
          </dd>
          <dt><dfn data-local-lt="desktop focus">Desktop focus event</dfn></dt>
          <dd>
            <p>Event from/to the host operating system via the accessibility <abbr title="application programming interface">API</abbr>, notifying of a change of input focus.</p>
          </dd>
          <dt><dfn>Event</dfn></dt>
          <dd>
            <p>
              A programmatic message used to communicate discrete changes in the <a>state</a> of an <a>object</a> 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. In some programming languages, events are more
              commonly known as notifications.
            </p>
          </dd>
          <dt><dfn>Expose</dfn></dt>
          <!--Not used-->
          <dd>
            <p>Translated to platform-specific <a class="termref">accessibility APIs</a> as defined in the <a href="" class="core-mapping">Core Accessibility API Mappings</a>.</p>
          </dd>
          <dt><dfn>Graphical Document</dfn></dt>
          <dd>
            <p>
              A document containing graphic representations with user-navigable parts. Charts, maps, diagrams, blueprints, and dashboards are examples of graphical documents. A graphical document is
              composed using any combination of symbols, images, text, and graphic primitives (shapes such as circles, points, lines, paths, rectangles, etc).
            </p>
          </dd>
          <dt><dfn data-dfn-for="element" data-export="">Hidden</dfn></dt>
          <dd>
            <p>Indicates that the <a>element</a> is excluded from the accessibility tree and therefore not exposed to accessibility APIs.</p>
            <p>Related: <a href="#tree_exclusion">Excluding Elements in the Accessibility Tree</a>, [=element/hidden from all users=], <sref>aria-hidden</sref>.</p>
          </dd>

          <dt><dfn data-dfn-for="element" data-lt="hide from all users" data-export="">Hidden From All Users</dfn></dt>
          <dd>
            <p>
              Indicates that the <a>element</a> is not visible, <a>perceivable</a>, or interactive for <em>any</em> user. Note that an <a>element</a> can be [=element/hidden=] but not [=element/hidden
              from all users=] by using <code>aria-hidden</code>.
            </p>
            <p>Related: <a href="#tree_exclusion">Excluding Elements in the Accessibility Tree</a>, [=element/hidden=], <sref>aria-hidden</sref>.</p>
            <p></p>
          </dd>
          <dt><dfn>Identifies</dfn></dt>
          <dd>
            <p>
              Used in an attribute description to denote that the value <a href="#propcharacteristic_value">type</a> is an <a href="#valuetype_idref">ID reference</a> (identifying a single element) or
              <a href="#valuetype_idref_list">ID reference list</a> (identifying one or more elements).
            </p>
            <p>Related Terms: <a>Defines</a>, <a>Indicates</a></p>
          </dd>
          <dt><dfn>Indicates</dfn></dt>
          <dd>
            <p>
              Used in an attribute description to denote that the value <a href="#propcharacteristic_value">type</a> is a named token or otherwise token-like, including the Boolean-like
              <a href="#valuetype_true-false">true/false</a>, <a href="#valuetype_true-false-undefined">true/false/undefined</a>, <a href="#valuetype_tristate">tristate (true/false/mixed)</a>, a
              single named <a href="#valuetype_token">token</a>, or a <a href="#valuetype_token_list">token list</a>.
            </p>
            <p>Related Terms: <a>Defines</a>, <a>Identifies</a></p>
          </dd>
          <dt><dfn>Keyboard Accessible</dfn></dt>
          <dd>
            <p>
              Accessible to the user using a keyboard or <a>assistive technologies</a> that mimic keyboard input, such as a sip and puff tube. References in this document relate to
              <cite
                ><a href="https://www.w3.org/TR/WCAG21/#keyboard-accessible"
                  ><abbr title="Web Content Accessibility Guidelines">WCAG</abbr> 2.1 Guideline 2.1: Make all functionality available from a keyboard</a
                ></cite
              >
              [[WCAG21]].
            </p>
          </dd>
          <dt><dfn>Landmark</dfn></dt>
          <dd>
            <p>
              A type of region on a page to which the user might want quick access. Content in such a region is different from that of other regions on the page and relevant to a specific user
              purpose, such as navigating, searching, perusing the primary content, etc.
            </p>
          </dd>
          <dt><dfn data-export="">Live Region</dfn></dt>
          <dd>
            <p>
              Live regions are perceivable regions of a web page that are typically updated as a result of an external event. These regions are not always updated as a result of a user interaction and
              can receive these updates even when they do not have focus. Examples of live regions include a chat log, stock ticker, or a sport scoring section that updates periodically to reflect
              game statistics. Since these asynchronous areas are expected to update outside the user's area of focus, assistive technologies such as screen readers have either been unaware of their
              existence or unable to process them for the user. WAI-ARIA has provided a collection of properties that allow the author to identify these live regions and process them: aria-live,
              aria-relevant, aria-atomic, and aria-busy.
            </p>
          </dd>
          <dt><dfn data-export="">Managed State</dfn></dt>
          <dd>
            <p>
              <a>Accessibility API</a> <a>state</a> that is controlled by the user agent, such as focus and selection. These are contrasted with &quot;unmanaged states&quot; that are typically
              controlled by the author. Nevertheless, authors can override some managed states, such as aria-posinset and aria-setsize. Many managed states have corresponding CSS pseudo-classes, such
              as :focus, and pseudo-elements, such as ::selection, that are also updated by the user agent.
            </p>
          </dd>
          <dt><dfn>Nemeth Braille</dfn></dt>
          <dd>
            <p>
              The Nemeth Braille Code for Mathematics is a braille code for encoding mathematical and scientific notation. See
              <cite><a href="https://en.wikipedia.org/wiki/Nemeth_Braille">Nemeth Braille on Wikipedia</a>.</cite>
            </p>
          </dd>
          <dt><dfn>Object</dfn></dt>
          <dd>
            <p>In the context of user interfaces, an item in the perceptual user experience, represented in markup languages by one or more [=elements=], and rendered by [=user agents=].</p>
            In the context of programming, the instantiation of one or more classes and interfaces which define the general characteristics of similar objects. An object in an
            <a>accessibility <abbr title="Application Programming Interfaces">API</abbr></a> can represent one or more DOM objects. <a class="termref">Accessibility APIs</a> have defined interfaces
            that are distinct from DOM interfaces.
          </dd>
          <dt><dfn>Ontology</dfn></dt>
          <dd>
            <p>A description of the characteristics of classes and how they relate to each other.</p>
          </dd>
          <dt><dfn>Operable</dfn></dt>
          <dd>
            <p>
              Usable by users in ways they can control. References in this document relate to
              <cite
                ><a href="https://www.w3.org/TR/WCAG21/#operable"><abbr title="Web Content Accessibility Guidelines">WCAG</abbr> 2.1 Principle 2: Content must be operable</a></cite
              >
              [[WCAG21]]. See <a>Keyboard Accessible</a>.
            </p>
          </dd>
          <dt><dfn data-export="">Perceivable</dfn></dt>
          <dd>
            <p>
              Presentable to users in ways they can sense. References in this document relate to
              <cite
                ><a href="https://www.w3.org/TR/WCAG21/#perceivable"><abbr title="Web Content Accessibility Guidelines">WCAG</abbr> 2.1 Principle 1: Content must be perceivable</a></cite
              >
              [[WCAG21]].
            </p>
          </dd>
          <dt><dfn data-export="" data-dfn-for="ARIA">Property</dfn></dt>
          <dd>
            <p>
              [=attributes=] that are essential to the nature of a given <a>object</a>, or that represent a data value associated with the object. A change of a property can significantly impact the
              meaning or presentation of an object. Certain properties (for example, <pref>aria-multiline</pref>) are less likely to change than <a class="termref" href="#dfn-state">states</a>, but
              note that the frequency of change difference is not a rule. A few properties, such as <pref>aria-activedescendant</pref>, <pref>aria-valuenow</pref>, and <pref>aria-valuetext</pref> are
              expected to change often. See <a class="specref" href="#statevsprop">clarification of states versus properties</a>.
            </p>
          </dd>
          <dt><dfn data-export="">Relationship</dfn></dt>
          <dd>
            <p>A connection between two distinct things. Relationships can be of various types to indicate which <a>object</a> labels another, controls another, etc.</p>
          </dd>
          <dt><dfn data-export="">Role</dfn></dt>
          <dd>
            <p>
              Main indicator of type.
              <!-- (removing, vague) The object's role is the class of <a class="termref">objects</a> of which it is a member. -->
              This <a class="termref" data-lt="semantics">semantic</a> 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.
            </p>
          </dd>
          <dt><dfn data-export="" data-local-lt="semantically">Semantics</dfn></dt>
          <dd>
            <p>
              The meaning of something as understood by a human, defined in a way that computers can process a representation of an <a>object</a>, such as [=elements=] and [=attributes=], and reliably
              represent the object in a way that various humans will achieve a mutually consistent understanding of the object.
            </p>
          </dd>
          <dt><dfn data-export="">State</dfn></dt>
          <dd>
            <p>
              A state is a dynamic <a class="termref" href="#dfn-property">property</a> expressing characteristics of an <a>object</a> that can 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. See
              <a class="specref" href="#statevsprop">clarification of states versus properties</a>.
            </p>
          </dd>
          <dt><dfn>Target Element</dfn></dt>
          <dd>
            <p>
              An element specified in a <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> relation. For example, in <code> &lt;div aria-controls=”elem1”&gt;</code>, where
              <code>“elem1”</code> is the ID for the target element.
            </p>
          </dd>
          <dt><dfn data-lt="unicode braille">Unicode Braille Patterns</dfn></dt>
          <dd>
            <p>
              In Unicode, braille is represented in a block called Braille Patterns (U+2800..U+28FF). The block contains all 256 possible patterns of an 8-dot braille cell; this includes the complete
              6-dot cell range which is represented by U+2800..U+283F. In all braille systems, the braille pattern dots-0 (U+2800) is used to represent a space or the lack of content; it is also
              called a blank Braille pattern. See <cite><a href="https://en.wikipedia.org/wiki/Braille_Patterns">Braille Patterns on Wikipedia</a>.</cite>
            </p>
          </dd>
          <dt><dfn data-export="">Widget</dfn></dt>
          <dd>
            <p>
              Discrete user interface <a class="termref" href="#dfn-object">object</a> with which the user can interact. Widgets range from simple objects that have one value or operation (e.g., check
              boxes and menu items), to complex objects that contain many managed sub-objects (e.g., trees and grids).
            </p>
          </dd>
        </dl>
      </div>
    </section>
    <section class="normative override" id="conformance">
      <h2>Conformance</h2>
      <p>
        The main content of Accessible Rich Internet Applications is normative and defines requirements that impact conformance claims. Introductory material, appendices, sections marked as
        "non-normative" and their subsections, diagrams, examples, and notes are informative (non-normative). Non-normative material provides advisory information to help interpret the guidelines but
        does not create requirements that impact a conformance claim.
      </p>
      <p>
        Normative sections provide requirements that authors and [=user agents=] must follow for an implementation to conform to this specification. The keywords <em class="rfc2119">MUST</em>,
        <em class="rfc2119">MUST NOT</em>, <em class="rfc2119">REQUIRED</em>, <em class="rfc2119">SHALL</em>, <em class="rfc2119">SHALL NOT</em>, <em class="rfc2119">SHOULD</em>,
        <em class="rfc2119">RECOMMENDED</em>, <em class="rfc2119">MAY</em>, and <em class="rfc2119">OPTIONAL</em> in this document are to be interpreted as described in
        <cite><a href="http://www.rfc-editor.org/rfc/rfc2119.txt">Keywords for use in RFCs to indicate requirement levels</a></cite> [[!RFC2119]]. RFC-2119 keywords are formatted in uppercase and
        contained in an element with <code>class="rfc2119"</code>. When the keywords shown above are used, but do not share this format, they do not convey formal information in the RFC 2119 sense,
        and are merely explanatory, i.e., informative. As much as possible, such usages are avoided in this specification.
      </p>
      <p>
        Non-normative (informative) sections provide information useful to understanding the specification. Such sections might contain examples of recommended practice, but it is not required to
        follow such recommendations in order to conform to this specification.
      </p>
      <section id="ua_noninterference">
        <h2>Non-interference with the Host Language</h2>
        <p>
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> processing by the <a>user agent</a> MUST NOT interfere with the normal operation of the built-in features of the host
          language.
        </p>
        <p>
          If a CSS selector includes a WAI-ARIA attribute (e.g., <code class="highlight lang-css">input[aria-invalid="true"]</code>), user agents MUST update the visual display of any elements
          matching (or no longer matching) the selector any time the attribute is added/changed/removed in the <abbr title="Document Object Model">DOM</abbr>. The user agent MAY alter the mapping of
          the host language features into an <a>accessibility <abbr title="Application Programing Interface">API</abbr></a
          >, but the user agent MUST NOT alter the <abbr title="Document Object Model">DOM</abbr> in order to remap <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> markup into host
          language features.
        </p>
      </section>
      <section id="ua_dom">
        <h2>All <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> in <abbr title="Document Object Model">DOM</abbr></h2>
        <p>
          A conforming <a>user agent</a> which implements a document object model that does not conform to the W3C DOM specification MUST include the content attribute for role and its
          <a href="#roles_categorization">WAI-ARIA role values</a>, as well as the <a href="#states_and_properties">WAI-ARIA States and Properties</a> in the DOM as specified by the author, even
          though processing might affect how the elements are exposed to accessibility APIs. Doing so ensures that each role attribute and all
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> states and properties, including their values, are in the document in an unmodified form so other tools, such as assistive
          technologies, can access them. A conforming W3C <abbr title="Document Object Model">DOM</abbr> meets this criterion.
        </p>
      </section>
      <section id="ua_domchanges">
        <h2>Assistive Technology Notifications Communicated to Web Applications</h2>
        <p>
          <a>Assistive technologies</a>, such as speech recognition systems and alternate input devices for users with mobility impairments, require the ability to control a web application in a
          device-independent way. <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a>states</a> and [=ARIA/properties=] reflect the current state of rich internet application
          components. The ability for assistive technologies to notify web applications of necessary changes is essential because it allows these alternative input solutions to control an application
          without being dependent on the standard input device which the user is unable to effectively control directly.
        </p>
        <p>
          User agents MUST provide a method to notify the web application when a change occurs to states or properties in the system accessibility API. Likewise, authors SHOULD update the web
          application accordingly when notified of a change request from the user agent or assistive technology.
        </p>
      </section>
      <section id="conformance_checkers">
        <h2>Conformance Checkers</h2>
        <p>
          Any application or script verifying document conformance or validity SHOULD include a test for all of the normative author requirements in this specification. If testing for a given
          requirement, conformance checkers MUST issue an error if an author "MUST" requirement isn't met, and MUST issue a warning if an author "SHOULD" requirement isn't met.
        </p>
      </section>
      <section id="deprecated">
        <!-- Deprecated requirements should begin with <p><em>This requirement is <a href="#deprecated">deprecated</a>.</em></p> -->
        <h2>Deprecated Requirements</h2>
        <p>
          As the technology evolves, sometimes new ways to meet a use case become available, that work better than a feature that was previously defined. But because of existing implementation of the
          older feature, that feature cannot be removed from the conformance model without rendering formerly conforming content non-conforming. In this case, the older feature is marked as
          "deprecated". This indicates that the feature is allowed in the conformance model and expected to be supported by user agents, but it is recommended that authors do not use it for new
          content. In future versions of the specification, if the feature is no longer widely used, the feature could be removed and no longer expected to be supported by user agents.
        </p>
      </section>
    </section>
    <section class="normative" id="usage">
      <h1>Using <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr></h1>
      <p>
        Complex web applications become inaccessible when <a>assistive technologies</a> cannot determine the <a>semantics</a> behind portions of a document or when the user is unable to effectively
        navigate to all parts of it in a usable way (see
        <cite
          ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite
        >). <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> divides the semantics into <a>roles</a> (the type defining a user interface element) and <a>states</a> and
        [=ARIA/properties=] supported by the roles.
      </p>
      <p>
        Authors need to associate [=elements=] in the document to a WAI-ARIA role and the appropriate states and properties (aria-* [=attributes=]) during its life-cycle, unless the elements already
        have the appropriate <a href="#implicit_semantics">implicit WAI-ARIA semantics</a> for states and properties. In these instances the equivalent host language states and properties take
        precedence to avoid a conflict while the role attribute will take precedence over the implicit role of the host language element.
      </p>
      <section id="introroles" class="normative">
        <h2><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Roles</h2>
        <p>
          A <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a>role</a> is set on an <a>element</a> using a <code>role</code> <a>attribute</a>, similar to the
          <code>role</code> attribute defined in <cite><a href="https://www.w3.org/TR/role-attribute/">Role Attribute</a></cite> [[ROLE-ATTRIBUTE]].
        </p>
        <pre class="example highlight">&lt;li role="menuitem"&gt;Open file…&lt;/li&gt;</pre>
        <p>The definition of each role in the model provides the following information :</p>
        <ul>
          <li>an informative description of the role;</li>
          <li>hierarchical information about related roles (e.g., a <rref>searchbox</rref> is a type of <rref>textbox</rref>);</li>
          <li>context of the role (e.g., a <rref>listitem</rref> is contained inside a <rref>list</rref>);</li>
          <li>references to related concepts in other specifications;</li>
          <li>supported <a>states</a> and [=ARIA/properties=] for each role (e.g., a <rref>checkbox</rref> supports being checked via <sref>aria-checked</sref>).</li>
        </ul>
        <p>
          Attaching a role gives <a>assistive technologies</a> information about how to handle each element. When <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> roles override host
          language semantics, there are no changes in the <abbr title="Document Object Model">DOM</abbr>, only in the <a class="termref">accessibility tree</a>.
        </p>
        <p>
          User agents MUST use the first token in the sequence of tokens in the <code>role</code> <a>attribute</a> value that matches the name of any non-abstract
          <abbr title="Accessible Internet Application">WAI-ARIA</abbr> <a>role</a>. Refer to the section on <a href="#host_general_role">`role` attribute implementation in Host Languages</a> for
          further details.
        </p>
      </section>
      <section id="introstates">
        <h2><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> States and Properties</h2>
        <p>
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> provides a collection of accessibility <a>states</a> and [=ARIA/properties=] which are used to support platform
          <a>accessibility <abbr title="Application Programing Interfaces">APIs</abbr></a> on various operating system platforms. <a>Assistive technologies</a> can access this information through an
          exposed <a>user agent</a> DOM or through a mapping to the platform accessibility <abbr title="Application Programing Interfaces">API</abbr>. When combined with <a>roles</a>, the user agent
          can supply the assistive technologies with user interface information to convey to the user at any time. Changes in states or properties will result in a notification to assistive
          technologies, which could alert the user that a change has occurred.
        </p>
        <p>
          In the following example, a list item (<code>html:li</code>) has been used to create a checkable menu item, and JavaScript <a>events</a> will capture mouse and keyboard events to toggle the
          value of <sref>aria-checked</sref>. A role is used to make the behavior of this simple <a>widget</a> known to the user agent. [=attribute|Attributes=] that change with user actions (such as
          <sref>aria-checked</sref>) are defined in the <a href="#states_and_properties">states and properties</a> section.
        </p>
        <pre class="example highlight">&lt;li role=&quot;menuitemcheckbox&quot; aria-checked=&quot;true&quot;&gt;Sort by Last Modified&lt;/li&gt;</pre>
        <p>
          Some accessibility states, called <em><a>managed states</a></em
          >, are controlled by the user agent. Examples of managed state include keyboard focus and selection. Managed states often have corresponding
          <abbr title="Cascading Style Sheets">CSS</abbr> pseudo-classes (such as <code>:focus</code> and <code>::selection</code>) to define style changes. In contrast, the states in this
          specification are typically controlled by the author and are called <em>unmanaged states.</em> Some states are managed by the user agent, such as <pref>aria-posinset</pref> and
          <pref>aria-setsize</pref>, but the author can override them if the <abbr title="Document Object Model">DOM</abbr> is incomplete and would cause the user agent calculation to be incorrect.
          User agents map both managed and unmanaged states to the platform accessibility <abbr title="Application Programing Interfaces">APIs</abbr>.
        </p>
        <p>
          Most modern user agents support
          <cite
            ><a href="https://www.w3.org/TR/css3-selectors/#attribute-selectors"><abbr title="Cascading Style Sheets">CSS</abbr> attribute selectors</a></cite
          >
          ([[CSS3-SELECTORS]]), and can allow the author to create <abbr title="User Interface">UI</abbr> changes based on <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> attribute
          information, reducing the amount of scripts necessary to achieve equivalent functionality. In the following example, a <abbr title="Cascading Style Sheets">CSS</abbr> selector is used to
          determine whether or not the text is bold and an image of a check mark is shown, based on the value of the <sref>aria-checked</sref> attribute.
        </p>
        <pre class="example highlight lang-css">
[aria-checked=&quot;true&quot;] { font-weight: bold; }
[aria-checked=&quot;true&quot;]::before { background-image: url(checked.gif); }</pre
        >
        <p>
          If CSS is not used to toggle the visual representation of the check mark, the author could include additional markup and scripts to manage an image that represents whether or not the
          <rref>menuitemcheckbox</rref> is checked.
        </p>
        <pre class="example highlight">&lt;li role=&quot;menuitemcheckbox&quot; aria-checked=&quot;true&quot;&gt;
  &lt;img src=&quot;checked.gif&quot; alt=&quot;&quot;&gt;
  <span class="comment">&lt;!-- note: additional scripts required to toggle image source --&gt;</span>
  Sort by Last Modified
&lt;/li&gt;</pre>
      </section>
      <section id="managingfocus" class="normative">
        <h2>Managing Focus and Supporting Keyboard Navigation</h2>
        <p>
          When using standard <abbr title="Hypertext Markup Language">HTML</abbr> interactive elements and simple <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a>widgets</a>,
          application developers can manipulate the tab order or associate keyboard shortcuts with elements in the document.
        </p>
        <p>
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> includes a number of &quot;managing container&quot; widgets, also known as &quot;composite&quot; widgets. When
          appropriate, the container is responsible for tracking the last descendant that was active (the default is usually the first item in the container). It is essential that a container maintain
          a usable and consistent strategy when focus leaves a container and is then later refocused. While there can be exceptions, it is recommended that when a previously focused container is
          refocused, the active descendant be the same element as the active descendant when the container was last focused. Exceptions include cases where the contents of a container widget have
          changed, and widgets like a menubar where the user expects to always return to the first item when focus leaves the menu bar. For example, if the second item of a tree group was the active
          descendant when the user tabbed out of the tree group, then the second item of the tree group remains the active descendant when the tree group gets focus again. The user can also activate
          the container by clicking on one of the descendants within it. When the container or its active descendant has focus, the user can navigate through the container by pressing additional keys,
          such as the arrow keys, to change the currently active descendant. Any additional press of the main navigation key (generally the <kbd>TAB</kbd> key) will move out of the container to the
          next widget.
        </p>
        <p>
          Usable keyboard navigation in a rich internet application is different from the tabbing paradigm among interactive elements, such as links and form controls, in a static document. In rich
          internet applications, the user tabs to significantly complex <a class="termref">widgets</a>, such as a menu or spreadsheet, and uses the arrow keys to navigate within the widget. The
          changes that <abbr title="accessible rich internet applications">WAI-ARIA</abbr> introduces to keyboard navigation make this enhanced accessibility possible. In
          <abbr title="accessible rich internet applications">WAI-ARIA</abbr>, any element can be keyboard focusable. In addition to host language mechanisms such as <code>tabindex</code>,
          <pref>aria-activedescendant</pref> provides another mechanism for keyboard operation. Most other aspects of <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> widget
          development depend on keyboard navigation functioning properly.
        </p>
        <p>
          When implementing <pref>aria-activedescendant</pref> as described below, the user agent keeps the <abbr title="Document Object Model">DOM</abbr> focus on the container element or on an input
          element that controls the container element. However, the user agent communicates <a>desktop focus events</a> and states to the assistive technology as if the element referenced by
          <pref>aria-activedescendant</pref> has focus. User agents are not expected to validate that the active descendant is a descendant of the container element. It is the responsibility of the
          user agent to ensure that keyboard events are processed at the <a>element</a> that has <abbr title="Document Object Model">DOM</abbr> focus. Any keyboard events directed at the active
          descendant bubble up to the <abbr title="Document Object Model">DOM</abbr> element with focus for processing.
        </p>
        <section id="managingfocus_authors">
          <h3>Information for Authors</h3>
          <p>
            If the author removes the element with focus, the author SHOULD move focus to a logical element. Similarly, authors SHOULD not scroll the element with focus off screen unless the user
            performed a scrolling action.
          </p>
          <p>
            Authors SHOULD ensure that all interactive [=elements=] are focusable and that all parts of composite widgets are either focusable or have a documented alternative method to achieve their
            function.
          </p>
          <p>Authors MUST manage focus on the following container roles:</p>
          <ul>
            <li><rref>grid</rref></li>
            <li><rref>listbox</rref></li>
            <li><rref>menu</rref></li>
            <li><rref>menubar</rref></li>
            <li><rref>radiogroup</rref></li>
            <li><rref>tree</rref></li>
            <li><rref>treegrid</rref></li>
            <li><rref>tablist</rref></li>
          </ul>
          <p>
            User agents that support <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> expand the usage of host language mechanisms such as <code>tabindex</code>, <code>focus</code>,
            and <code>blur</code> to allow them on all [=elements=]. Where the host language supports it, authors MAY add any element such as a <code>div</code>, <code>span</code>, or
            <code>img</code> to the default tab order by setting <code>tabindex=&quot;0&quot;</code>. In addition, any item with <code>tabindex</code> equal to a negative integer is focusable via
            script or a mouse click, but is not part of the default tab order. This is supported in both [[HTML]] and [[SVG2]].
          </p>
          <p>
            Authors MAY use <pref>aria-activedescendant</pref> to inform <a>assistive technologies</a> which descendant of a <rref>widget</rref> element is treated as having keyboard focus in the user
            interface if the role of the widget element supports <code>aria-activedescendant</code>. This is often a more convenient way of providing keyboard navigation within widgets, such as a
            <rref>listbox</rref>, where the widget occupies only one stop in the page <kbd>Tab</kbd> sequence and other keys, typically arrow keys, are used to focus elements inside the widget.
          </p>
          <p>
            Typically, the author will use host language <a>semantics</a> to put the widget in the <kbd>Tab</kbd> sequence (e.g., <code>tabindex="0"</code> in HTML) and
            <code>aria-activedescendant</code> to point to the ID of the currently active descendant. The author, not the user agent, is responsible for styling the currently active descendant to show
            it has keyboard focus. The author cannot use <code>:<span class="css-selector">focus</span></code> to style the currently active descendant since the actual focus is on the container.
          </p>
          <p>
            More information on managing focus can be found in the <a href="practices/keyboard-interface" class="practices">Developing a Keyboard Interface</a> section of the
            <cite><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Authoring Practices</cite>.
          </p>
        </section>
        <section id="managingfocus_useragents">
          <h3>Information for User Agents</h3>
          <p>The user agent MUST do the following to implement <pref>aria-activedescendant</pref>:</p>
          <ol>
            <li>Implement the host language method for keyboard navigation so that widgets that support <code>aria-activedescendant</code> can be included in the tab order.</li>
            <li>
              For platforms that expose <a>desktop focus</a> or <a>accessibility <abbr title="Application Programing Interfaces">API</abbr></a> focus separately from
              <abbr title="Document Object Model">DOM</abbr> focus, do not expose the focused state in the accessibility <abbr title="application programming interface">API</abbr> for any element when
              it has <abbr title="Document Object Model">DOM</abbr> focus and also has <pref>aria-activedescendant</pref> which points to a valid <a href="#valuetype_idref">ID reference</a>.
            </li>
            <li>
              When the <pref>aria-activedescendant</pref> attribute changes on an element that currently has <abbr title="Document Object Model">DOM</abbr> focus, remove the focused state from the
              previously focused object and fire an accessibility <abbr title="application programming interface">API</abbr> <a>desktop focus event</a> on the new element referenced by
              <code>aria-activedescendant</code>. If <pref>aria-activedescendant</pref> is cleared or does not point to an element in the current document, fire a desktop focus event for the
              <a>object</a> that had the attribute change.
            </li>
            <li>
              Apply the following accessibility <abbr title="Application Programming Interface">API</abbr> states to any element with an ID attribute that can be referenced by an element with both an
              <pref>aria-activedescendant</pref> attribute and has <abbr title="Document Object Model">DOM</abbr> focus. There are two ways an element can be referenced by
              <pref>aria-activedescendant</pref>. One way is when it is an <a>accessibility descendant</a> of the element with <pref>aria-activedescendant</pref> and the other is when it is an
              <a>accessibility descendant</a> of an element that is controlled by an element with role of <rref>combobox</rref>, <rref>textbox</rref> or <rref>searchbox</rref> with an
              <pref>aria-activedescendant</pref> attribute:
              <ol>
                <li>
                  Focusable, if the element also has a <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> <a class="termref">role</a>. The element needs to be focusable because it
                  could be referenced by the <pref>aria-activedescendant</pref> attribute. Native elements that have no <a class="termref">role</a> attribute do not need to be checked; their native
                  semantics determine the focusable state.
                </li>
                <li>
                  Focused, whenever the element is the target of the <pref>aria-activedescendant</pref> attribute and the element with the <pref>aria-activedescendant</pref> attribute has
                  <abbr title="Document Object Model">DOM</abbr> focus.
                </li>
              </ol>
            </li>
          </ol>
          <p>
            When an assistive technology uses its platform's accessibility <abbr title="Application Programming Interfaces">API</abbr> to request a change of focus, user agents MUST do the following:
          </p>
          <ol>
            <li>Remove the platform's focused state from the previously focused object.</li>
            <li>
              Set the <abbr title="Document Object Model">DOM</abbr> focus:
              <ol>
                <li>
                  If the <a class="termref">element</a> can take <abbr title="Document Object Model">DOM</abbr> focus, the <a class="termref">user agent</a> MUST set the
                  <abbr title="Document Object Model">DOM</abbr> focus to it.
                </li>
                <li>
                  Otherwise, if the element being focused has an ID and the ID is referenced by the <pref>aria-activedescendant</pref> attribute of an element that is focusable, the user agent MUST
                  set <abbr title="Document Object Model">DOM</abbr> focus to the element that has the <pref>aria-activedescendant</pref> attribute.
                  <p class="note">
                    An element with an ID can be referenced when it is an <a>accessibility descendant</a> of a container element that has the <pref>aria-activedescendant</pref> attribute or by a
                    container element that is controlled by an element that has the <pref>aria-activedescendant</pref> attribute (e.g. see <rref>combobox</rref>). Otherwise the
                    <pref>aria-activedescendant</pref> attribute reference indicates an author error.
                  </p>
                  <p class="note">The inability to set <abbr title="Document Object Model">DOM</abbr> focus to the containing element indicates an author error.</p>
                </li>
                <li>Otherwise, the user agent MAY attempt to set <abbr title="Document Object Model">DOM</abbr> focus to the child element itself.</li>
              </ol>
            </li>
            <li>
              If the element being focused has an ID and is an <a>accessibility descendant</a> of either a container element with both an <code>aria-activedescendant</code> attribute and has
              <abbr title="Document Object Model">DOM</abbr> focus, or by a container element that is controlled by an element with both an <pref>aria-activedescendant</pref> attribute and has
              <abbr title="Document Object Model">DOM</abbr> focus, the user agent MUST set the accessibility <abbr title="Application Programming Interface">API</abbr> focused state and fire an
              accessibility <abbr title="Application Programming Interface">API</abbr> focus <a>event</a> on the element identified by the value of <code>aria-activedescendant</code>.
            </li>
          </ol>
        </section>
      </section>
    </section>
    <section class="normative" id="roles">
      <h1>The Roles Model</h1>
      <p>This section defines <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a>roles</a> and describes their characteristics and properties.</p>
      <p>The roles, their characteristics, the states and properties they support, and specification of how they can be used in markup, shall be considered normative.</p>
      <p>
        In order to reflect the content in the DOM, user agents SHOULD map the role attribute to the appropriate value in the implemented accessibility API, and user agents SHOULD update the mapping
        when the role attribute changes.
      </p>
      <section id="relationshipsconcepts">
        <h2>Relationships Between Concepts</h2>
        <p>
          The Roles Model uses the following relationships to relate <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> roles to each other and to concepts from other specifications,
          such as HTML.
        </p>
        <section id="superclassrole">
          <h3>Superclass Role</h3>
          <p>
            The <a>role</a> that the current subclassed role extends in the Roles Model. This extension causes all the states and properties of the superclass role to propagate to the subclass role.
            Other than well known stable specifications, inheritance can be restricted to items defined inside this specification, so that external items cannot be changed and affect inherited
            classes.
          </p>
        </section>
        <section id="subclassroles">
          <h3>Subclass Roles</h3>
          <p>Informative list of <a>roles</a> for which this role is the superclass. This is provided to facilitate reading of the specification but adds no new information.</p>
        </section>
        <section id="relatedConcept">
          <h3>Related Concepts</h3>
          <p>
            Informative data about a similar or related idea from other specifications. Concepts that are related are not necessarily identical. Related concepts do not inherit properties from each
            other. Hence if the definition of one concept changes, the properties, behavior, and definition of its related concept is not affected.
          </p>
          <p>
            For example, a progress bar is like a status indicator. Therefore, the <rref>progressbar</rref> <a>widget</a> has a related concept which includes <rref>status</rref>. However, if the
            definition of <rref>status</rref> is modified, the definition of a <rref>progressbar</rref> is not affected.
          </p>
        </section>
        <section id="baseConcept">
          <h3>Base Concept</h3>
          <p>
            Informative data about <a>objects</a> that are considered prototypes for the <a>role</a>. Base concept is similar to type, but without inheritance of limitations and properties. Base
            concepts are designed as a substitute for inheritance for external concepts. A base concept is like a <a href="#relatedConcept">related concept</a> except that the base concept is almost
            identical to the role definition.
          </p>
          <p>
            For example, the <rref>checkbox</rref> defined in this document has similar functionality and anticipated behavior to a <code>&lt;input type="[^input/type/checkbox^]"&gt;</code> defined in
            HTML. Therefore, a <rref>checkbox</rref> has an [[HTML]] <code>checkbox</code> as a <code>baseConcept</code>. However, if the original [[HTML]] checkbox baseConcept definition is modified,
            the definition of a <rref>checkbox</rref> in this document will not be affected, because there is no actual inheritance of the respective type.
          </p>
        </section>
      </section>
      <section id="Properties">
        <h2>Characteristics of Roles</h2>
        <p>
          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, and what instances the role
          can or must contain. In the case of <a>widgets</a> this also includes how it interacts with the <a>user agent</a> based on mapping to HTML forms. States and properties from
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> that are supported by the role are also indicated.
        </p>
        <p>Roles define the following characteristics.</p>
        <section id="isAbstract">
          <h3>Abstract Roles</h3>
          <dl class="runin">
            <dt>Values</dt>
            <dd>Boolean</dd>
          </dl>
          <p>
            Abstract <a>roles</a> are the foundation upon which all other <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> roles are built. Authors MUST NOT use abstract roles
            because they are not implemented in the <abbr title="application programing interface">API</abbr> binding. User agents MUST NOT map abstract roles to the standard role mechanism of the
            accessibility API. Abstract roles are provided to help with the following:
          </p>
          <ol>
            <li>Organize the Roles Model and provide roles with a meaning in the context of known concepts.</li>
            <li>Streamline the addition of roles that include necessary features.</li>
          </ol>
        </section>
        <section id="requiredState">
          <h3>Required States and Properties</h3>
          <p>
            <a>States</a> and [=ARIA/properties=] specifically required for the <a>role</a> and subclass roles. Authors MUST provide a non-empty <span>value</span> for required states and properties.
            Authors MUST NOT use the value <code>undefined</code> for required states and properties, unless <code>undefined</code> is an explicitly-supported value of that state or property.
          </p>
          <p>
            When an <a>object</a> inherits from multiple ancestors and one ancestor indicates that property is supported while another ancestor indicates that it is required, the property is required
            in the inheriting object.
          </p>
          <p class="note">A host language attribute with the appropriate <a href="#implicit_semantics">implicit WAI-ARIA semantic</a> fulfills this requirement.</p>
        </section>
        <section id="supportedState">
          <h3>Supported States and Properties</h3>
          <p>
            <a>States</a> and [=ARIA/properties=] specifically applicable to the <a>role</a> and child roles. Authors MAY provide <span>values</span> for supported states and properties, but need not
            in cases where default values are sufficient. [=user agents=] MUST map all supported states and properties for the role to an accessibility API. If the state or property is undefined and
            it has a default value for the role, [=user agents=] SHOULD expose the default value.
          </p>
          <p class="note">A host language attribute with the appropriate <a href="#implicit_semantics">implicit WAI-ARIA semantic</a> fulfills this requirement.</p>
        </section>
        <section id="inheritedattributes">
          <h3>Inherited States and Properties</h3>
          <p>
            Informative list of properties that are inherited by a <a>role</a> from superclass roles. <a>States</a> and [=ARIA/properties=] are inherited from superclass roles in the Roles Model, not
            from ancestor [=elements=] in the <abbr title="Document Object Model">DOM</abbr> tree. These properties are not explicitly defined on the role, as the inheritance of properties is
            automatic. This information is provided to facilitate reading of the specification. The set of supported states and properties combined with inherited states and properties forms the full
            set of states and properties supported by the role.
          </p>
        </section>
        <section id="prohibitedattributes">
          <h3><dfn>Prohibited</dfn> States and Properties</h3>
          <p>List of states and properties that are prohibited on a <a>role</a>. Authors MUST NOT specify a prohibited state or property.</p>
          <p class="note">A host language attribute with the appropriate <a href="#implicit_semantics">implicit WAI-ARIA semantic</a> would also prohibit a state or property in this section.</p>
        </section>
        <section id="mustContain">
          <h3>Allowed Accessibility Child Roles</h3>
          <p>
            A list of roles which are allowed on an <a>accessibility child</a> (simplified as "child") of the element with this <a>role</a>. Authors MUST only add child element with allowed roles. For
            example, an element with the role <rref>list</rref> can own child elements with the role <rref>listitem</rref>, but cannot own elements with the role <rref>option</rref>.
          </p>
          <p>To determine whether an element is the <a>child</a> of an element, <a>user agents</a> MUST ignore any intervening elements with the role <rref>generic</rref> or <rref>none</rref>.</p>
          <p>
            Descendants which are not children of an element ancestor are not constrained by <em>allowed accessibility child roles</em>. For example, an <code>image</code> is not an allowed child of a
            <code>list</code>, but it is a valid descendant if it is also a descendant of the <code>list</code>'s allowed child <code>listitem</code>.
          </p>
          <p class="note">
            A role that has 'allowed accessibility child roles' does not imply the reverse relationship. Elements with roles in this list do not always have to be found within elements of the given
            role. See <a href="#scope">required accessibility parent roles</a> for requirements about the context where elements of a given role will be contained.
          </p>
          <p class="note">
            An element with a <a href="#subclassroles">subclass role</a> of the 'allowed accessibility child role' does not fulfill this requirement. For example, the <rref>listbox</rref> role allows
            a child element using the <rref>option</rref> or <rref>group</rref> role. Although the <rref>group</rref> role is the superclass of <rref>row</rref>, adding a child element with a role of
            <rref>row</rref> will not fulfill the requirement that <rref>listbox</rref> allows children with <rref>option</rref> or <rref>group</rref> roles.
          </p>
          <p class="note">An element with the appropriate <a href="#implicit_semantics">implicit WAI-ARIA semantic</a> fulfills this requirement.</p>
          <p class="note">Examples of valid ways to mark up allowed accessibility child roles include:</p>
          <ol>
            <li>
              Direct DOM child:
              <!-- ReSpec needs these examples to be unindented. -->
              <pre>
&lt;div role="listbox"&gt;
	&lt;div role="option"&gt;option text&lt;/div&gt;
&lt;/div&gt;</pre
              >
            </li>
            <li>
              DOM child with generics intervening:
              <!-- ReSpec needs these examples to be unindented. -->
              <pre>
&lt;div role="listbox"&gt;
	&lt;div&gt;
		&lt;div role="option"&gt;option text&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;</pre
              >
            </li>
            <li>
              Direct <code>aria-owns</code> relationship:
              <!-- ReSpec needs these examples to be unindented. -->
              <pre>
&lt;div role="listbox" aria-owns="id1"&gt;&lt;/div&gt;
&lt;div role="option" id="id1"&gt;option text&lt;/div&gt;</pre
              >
            </li>
            <li>
              <code>aria-owns</code> relationship with generics intervening:
              <!-- ReSpec needs these examples to be unindented. -->
              <pre>
&lt;div role="listbox" aria-owns="id1"&gt;&lt;/div&gt;
&lt;div id="id1"&gt;
	&lt;div&gt;
		&lt;div role="option"&gt;option text&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;</pre
              >
            </li>
          </ol>
        </section>
        <section id="scope">
          <h3>Required Accessibility Parent Role</h3>
          <p>
            The required <a>accessibility parent</a> (simplified as "parent") role defines the container where this <a>role</a> is allowed. If a role has a required accessibility parent, authors MUST
            ensure that an element with the role is an <a>accessibility child</a> of an element with the required accessibility parent role. For example, an element with role <code>listitem</code> is
            only meaningful when it is a child of an element with role <code>list</code>.
          </p>
          <p>To determine whether an element has a parent with the required role, <a>user agents</a> MUST ignore any elements with the role <rref>generic</rref> or <rref>none</rref>.</p>
          <p class="note">An element with the appropriate <a href="#implicit_semantics">implicit WAI-ARIA semantic</a> fulfills this requirement.</p>
        </section>
        <section id="namecalculation">
          <h3>Accessible Name Calculation</h3>
          <dl class="runin">
            <dt>Values</dt>
            <dd>
              One of the following values:
              <ol>
                <li>
                  author: name comes from values provided by the author in explicit markup features such as the <pref>aria-label</pref> attribute, the <pref>aria-labelledby</pref> attribute, or the
                  host language labeling mechanism, such as the <code>alt</code> or <code>title</code> attributes in HTML, with HTML <code>title</code> attribute having the lowest precedence for
                  specifying a text alternative.
                </li>
                <li>
                  contents: name comes from the text value of the <a>element</a> node. Although this might be allowed in addition to "author" in some <a>roles</a>, this is used in content only if
                  higher priority "author" features are not provided. Priority is defined by the
                  <a href="#mapping_additional_nd_te" class="accname">accessible name and description computation</a> algorithm [[ACCNAME-1.2]].
                </li>
                <li>prohibited: the element does not support name from author. Authors MUST NOT use the <pref>aria-label</pref> or <pref>aria-labelledby</pref> attributes to name the element.</li>
              </ol>
            </dd>
          </dl>
          <section id="namecomputation">
            <h4>Name Computation</h4>
            <p><a href="#mapping_additional_nd_name" class="accname">Name Computation</a> is defined in the Accessible Name and Description specification.</p>
          </section>
          <section id="descriptioncomputation">
            <h4>Description Computation</h4>
            <p><a href="#mapping_additional_nd_description" class="accname">Description Computation</a> is defined in the Accessible Name and Description specification.</p>
          </section>
          <section id="textalternativecomputation">
            <h4>Accessible Name and Description Computation</h4>
            <p><a href="#mapping_additional_nd_te" class="accname">Accessible Name and Description Computation</a> is defined in the Accessible Name and Description specification.</p>
          </section>
          <section id="namefromauthor">
            <h4>Roles Supporting Name from Author</h4>
            <div id="index_fromauthor"></div>
          </section>
          <section id="namefromcontent">
            <h4>Roles Supporting Name from Content</h4>
            <div id="index_fromcontent"></div>
          </section>
          <section id="namefromprohibited">
            <h4>Roles which cannot be named (Name prohibited)</h4>
            <div id="index_fromprohibited"></div>
          </section>
        </section>
        <section id="childrenArePresentational">
          <h3>Presentational Children</h3>
          <dl class="runin">
            <dt>Values</dt>
            <dd>
              <p>Boolean (<code>true</code> | <code>false</code>)</p>
            </dd>
          </dl>
          <p>
            The <abbr title="Document Object Model">DOM</abbr> descendants are presentational. [=user agents=] SHOULD NOT expose descendants of this <a>element</a> through the platform
            <a>accessibility <abbr title="Application Programing Interface">API</abbr></a
            >. If [=user agents=] do not hide the descendant nodes, some information might be read twice.
          </p>
          <p>Authors MUST NOT specify <pref>aria-owns</pref> on an element which has Presentational Children.</p>
        </section>
        <section id="implictValueForRole">
          <h3>Implicit Value for Role</h3>
          <p>
            Many states and properties have default values. Occasionally, the default value when used on a given role should be different from the usual default. Roles that require a state or property
            to have a non-standard default value indicate this in the "Implicit Value for Role". This is expressed in the form "Default for <code>state or property name</code> is
            <code>new default value</code>". Roles that define this have the new default value for the state or property if the author does not provide an explicit value.
          </p>
        </section>
      </section>
      <section id="roles_categorization">
        <h2>Categorization of Roles</h2>
        <p>
          To support the current user scenario, this specification categorizes <a>roles</a> that define user interface <a>widgets</a> (sliders, tree controls, etc.) and those that define page
          structure (sections, navigation, etc.). Note that some assistive technologies provide special modes of interaction for regions marked with role <code>application</code> or
          <code>document</code>.
        </p>
        <p>A visual description of the relationships among roles is available in the <a href="https://www.w3.org/WAI/ARIA/1.2/class-diagram/">ARIA 1.2 Class Diagram</a>.</p>
        <p>Roles are categorized as follows:</p>
        <ol>
          <li><a href="#abstract_roles">Abstract Roles</a></li>
          <li><a href="#widget_roles">Widget Roles</a></li>
          <li><a href="#document_structure_roles">Document Structure Roles</a></li>
          <li><a href="#landmark_roles">Landmark Roles</a></li>
          <li><a href="#live_region_roles">Live Region Roles</a></li>
          <li><a href="#window_roles">Window Roles</a></li>
        </ol>
        <section id="abstract_roles">
          <h3>Abstract Roles</h3>
          <p>The following <a>roles</a> are used to support the WAI-ARIA Roles Model for the purpose of defining general role concepts.</p>
          <p>Abstract roles are used for the ontology. Authors MUST NOT use abstract roles in content.</p>
          <ul>
            <li><rref>command</rref></li>
            <li><rref>composite</rref></li>
            <li><rref>input</rref></li>
            <li><rref>landmark</rref></li>
            <li><rref>range</rref></li>
            <li><rref>roletype</rref></li>
            <li><rref>section</rref></li>
            <li><rref>sectionhead</rref></li>
            <li><rref>select</rref></li>
            <li><rref>structure</rref></li>
            <li><rref>widget</rref></li>
            <li><rref>window</rref></li>
          </ul>
        </section>
        <section id="widget_roles">
          <h3>Widget Roles</h3>
          <p>The following roles act as standalone user interface widgets or as part of larger, composite widgets.</p>
          <ul>
            <li><rref>button</rref></li>
            <li><rref>checkbox</rref></li>
            <li><rref>gridcell</rref></li>
            <li><rref>link</rref></li>
            <li><rref>menuitem</rref></li>
            <li><rref>menuitemcheckbox</rref></li>
            <li><rref>menuitemradio</rref></li>
            <li><rref>option</rref></li>
            <!-- FIXME: This is commented out because the ARIA Working Group agreed to move the password role to ARIA 2.0,
     but we've not branched for 1.1 yet. Once we have branched, this section should be deleted from the 1.1
     branch and uncommented for the master branch (pending discussion and consensus).
				<li><rref>password</rref></li>
-->
            <li><rref>progressbar</rref></li>
            <li><rref>radio</rref></li>
            <li><rref>scrollbar</rref></li>
            <li><rref>searchbox</rref></li>
            <li><rref>separator</rref> (when focusable)</li>
            <li><rref>slider</rref></li>
            <li><rref>spinbutton</rref></li>
            <li><rref>switch</rref></li>
            <li><rref>tab</rref></li>
            <li><rref>tabpanel</rref></li>
            <li><rref>textbox</rref></li>
            <li><rref>treeitem</rref></li>
          </ul>
          <p>The following roles act as composite user interface widgets. These roles typically act as containers that manage other, contained widgets.</p>
          <ul>
            <li><rref>combobox</rref></li>
            <li><rref>grid</rref></li>
            <li><rref>listbox</rref></li>
            <li><rref>menu</rref></li>
            <li><rref>menubar</rref></li>
            <li><rref>radiogroup</rref></li>
            <li><rref>tablist</rref></li>
            <li><rref>tree</rref></li>
            <li><rref>treegrid</rref></li>
          </ul>
        </section>
        <section id="document_structure_roles">
          <h3>Document Structure Roles</h3>
          <p>The following <a>roles</a> describe structures that organize content in a page. Document structures are not usually interactive.</p>
          <ul>
            <li><rref>application</rref></li>
            <li><rref>article</rref></li>
            <li><rref>blockquote</rref></li>
            <li><rref>caption</rref></li>
            <li><rref>cell</rref></li>
            <li><rref>code</rref></li>
            <li><rref>columnheader</rref></li>
            <li><rref>comment</rref></li>
            <li><rref>definition</rref></li>
            <li><rref>deletion</rref></li>
            <li><rref>directory</rref></li>
            <li><rref>document</rref></li>
            <li><rref>emphasis</rref></li>
            <li><rref>feed</rref></li>
            <li><rref>figure</rref></li>
            <li><rref>generic</rref></li>
            <li><rref>group</rref></li>
            <li><rref>heading</rref></li>
            <li><rref>img</rref></li>
            <li><rref>insertion</rref></li>
            <li><rref>list</rref></li>
            <li><rref>listitem</rref></li>
            <li><rref>mark</rref></li>
            <li><rref>math</rref></li>
            <li><rref>meter</rref></li>
            <li><rref>none</rref></li>
            <li><rref>note</rref></li>
            <li><rref>paragraph</rref></li>
            <li><rref>presentation</rref></li>
            <li><rref>row</rref></li>
            <li><rref>rowgroup</rref></li>
            <li><rref>rowheader</rref></li>
            <li><rref>separator</rref> (when not focusable)</li>
            <li><rref>strong</rref></li>
            <li><rref>subscript</rref></li>
            <li><rref>suggestion</rref></li>
            <li><rref>superscript</rref></li>
            <li><rref>table</rref></li>
            <li><rref>term</rref></li>
            <li><rref>time</rref></li>

            <!-- FIXME: This is commented out because the ARIA Working Group agreed to move the text role to ARIA 2.0,
     but we've not branched for 1.1 yet. Once we have branched, this entire section should be deleted from
     the 1.1 branch and uncommented for the master branch.
				<li><rref>text</rref></li>
-->
            <li><rref>toolbar</rref></li>
            <li><rref>tooltip</rref></li>
          </ul>
        </section>
        <section id="landmark_roles">
          <h3>Landmark Roles</h3>
          <p>
            The following <a>roles</a> are regions of the page intended as navigational <a>landmarks</a>. All of these roles inherit from the <code>landmark</code> base type and all are imported from
            the <cite><a href="https://www.w3.org/TR/role-attribute/#s_role_module_attributes">Role Attribute</a></cite> [[ROLE-ATTRIBUTE]]. The roles are included here in order to make them clearly
            part of the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Roles Model.
          </p>
          <ul>
            <li><rref>banner</rref></li>
            <li><rref>complementary</rref></li>
            <li><rref>contentinfo</rref></li>
            <li><rref>form</rref></li>
            <li><rref>main</rref></li>
            <li><rref>navigation</rref></li>
            <li><rref>region</rref></li>
            <li><rref>search</rref></li>
          </ul>
        </section>
        <section id="live_region_roles">
          <h3>Live Region Roles</h3>
          <p>The following <a>roles</a> are <a>live regions</a> and can be modified by <a href="#attrs_liveregions">live region attributes</a>.</p>
          <ul>
            <li><rref>alert</rref></li>
            <li><rref>log</rref></li>
            <li><rref>marquee</rref></li>
            <li><rref>status</rref></li>
            <li><rref>timer</rref></li>
          </ul>
        </section>
        <section id="window_roles">
          <h3>Window Roles</h3>
          <p>The following <a>roles</a> act as windows within the browser or application.</p>
          <ul>
            <li><rref>alertdialog</rref></li>
            <li><rref>dialog</rref></li>
          </ul>
        </section>
      </section>
      <section id="role_definitions">
        <h2>Definition of Roles</h2>
        <p>Below is an alphabetical list of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a>roles</a>.</p>
        <p>Abstract roles are used for the ontology. Authors MUST NOT use abstract roles in content.</p>
        <p id="index_role">Placeholder for compact list of roles</p>
        <div class="role" id="alert">
          <rdef>alert</rdef>
          <div class="role-description">
            <p>A type of <a>live region</a> with important, and usually time-sensitive, information. See related <rref>alertdialog</rref> and <rref>status</rref>.</p>
            <p>
              Alerts are used to convey messages that might be immediately important to users. In the case of audio warnings, alerts provide an accessible alternative for hearing-impaired users. The
              <code>alert</code> <a>role</a> is applied to the element containing the alert message. An <code>alert</code> is a specialized form of the <rref>status</rref> role, which is processed as
              an atomic <a>live region</a>.
            </p>
            <p>
              Alerts are assertive live regions, which means they cause immediate notification for assistive technology users. If the operating system allows, the <a>user agent</a> SHOULD fire a
              system alert <a>event</a> through the accessibility API when the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> alert is created.
            </p>
            <p>
              Neither authors nor user agents are required to set or manage focus to an alert in order for it to be processed. Since alerts are not required to receive focus, authors SHOULD NOT
              require users to close an alert. If an author desires focus to move to a message when it is conveyed, the author SHOULD use <rref>alertdialog</rref> instead of <code>alert</code>.
            </p>
            <p>
              Elements with the role <code>alert</code> have an implicit <pref>aria-live</pref> value of <code>assertive</code>, and an implicit <pref>aria-atomic</pref> value of <code>true</code>.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head">Implicit Value for Role:</th>
                <td class="implicit-values">
                  Default for <pref>aria-live</pref> is <code class="default">assertive</code>.<br />
                  Default for <pref>aria-atomic</pref> is <code class="default">true</code>.
                </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="alertdialog">
          <rdef>alertdialog</rdef>
          <div class="role-description">
            <p>A type of dialog that contains an alert message, where initial focus goes to an <a>element</a> within the dialog. See related <rref>alert</rref> and <rref>dialog</rref>.</p>
            <p>
              Alert dialogs are used to convey messages to alert the user. The <code>alertdialog</code> <a>role</a> goes on the [=nodes|node=] containing both the alert message and the rest of the
              dialog. Authors SHOULD make alert dialogs modal by ensuring that, while the <code>alertdialog</code> is shown, keyboard and mouse interactions only operate within the dialog. See
              <pref>aria-modal</pref>.
            </p>
            <p>
              Unlike <rref>alert</rref>, <code>alertdialog</code> can receive a response from the user. For example, to confirm that the user understands the alert being generated. When the alert
              dialog is displayed, authors SHOULD set focus to an active element within the alert dialog, such as a form control or confirmation button. The <a>user agent</a> SHOULD fire a system
              alert <a>event</a> through the accessibility API when the alert is created, provided one is specified by the intended
              <a>accessibility <abbr title="Application Programing Interfaces">API</abbr></a
              >.
            </p>
            <p>Authors SHOULD provide an accessible name for an <code>alertdialog</code>, which can be done with the <pref>aria-label</pref> or <pref>aria-labelledby</pref> attribute.</p>
            <p>
              Authors SHOULD use <pref>aria-describedby</pref> on an <code>alertdialog</code> to reference the alert message element in the dialog. If they do not, an <a>assistive technology</a> can
              resort to its internal recovery mechanism to determine the contents of the alert message.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>alert</rref></li>
                    <li><rref>dialog</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="application">
          <rdef>application</rdef>
          <div class="role-description">
            <p>
              A <rref>structure</rref> containing one or more focusable elements requiring user input, such as keyboard or gesture events, that do not follow a standard interaction pattern supported
              by a <rref>widget</rref> role.
            </p>
            <p>
              Some [=user agents=] and <a>assistive technologies</a> have a browse mode where standard input events, such as up and down arrow key events, are intercepted and used to control a reading
              cursor. This browse mode behavior prevents elements that do not have a <rref>widget</rref> role from receiving and using such keyboard and gesture events to provide interactive
              functionality.
            </p>
            <p>
              When there is a need to create an element with an interaction model that is not supported by any of the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>
              <rref>widget</rref> roles, authors MAY give that element role <code>application</code>. And, when a user navigates into an element with role <code>application</code>,
              <a>assistive technologies</a> that intercept standard input events SHOULD switch to a mode that passes most or all standard input events through to the web application.
            </p>
            <p>
              For example, a presentation slide editor uses arrow keys to change the positions of textbox and image elements on the slide. There are not any WAI-ARIA <rref>widget</rref> roles that
              correspond to such an interaction model so an author could give the slide container role <code>application</code>, an <pref>aria-roledescription</pref> of &quot;Slide Editor&quot;, and
              use <pref>aria-describedby</pref> to provide instructions.
            </p>
            <p>
              Because only the focusable elements contained in an <code>application</code> element are accessible to users of some assistive technologies, authors MUST use one of the following
              techniques to ensure all non-decorative static text or image content inside an application is accessible:
            </p>
            <ol>
              <li>Associate the content with a focusable element using <pref>aria-labelledby</pref> or <pref>aria-describedby</pref>.</li>
              <li>Place the content in a focusable element that has role <rref>document</rref> or <rref>article</rref>.</li>
              <li>
                Manage focus of <a>accessibility descendants</a> as described in <a href="#managingfocus">Managing Focus</a>, updating the value of <pref>aria-activedescendant</pref> to reference the
                <a>element</a> containing the focused content.
              </li>
            </ol>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>structure</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-activedescendant</pref></li>
                    <li><sref>aria-disabled</sref></li>
                    <li><pref>aria-errormessage</pref></li>
                    <li><sref>aria-expanded</sref></li>
                    <li><pref>aria-haspopup</pref></li>
                    <li><sref>aria-invalid</sref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="article">
          <rdef>article</rdef>
          <div class="role-description">
            <p>A section of a page that consists of a composition that forms an independent part of a document, page, or site.</p>
            <p>
              An article is not a navigational <a>landmark</a>, but can be nested to form a discussion where assistive technologies could pay attention to article nesting to assist the user in
              following the discussion. An article could be a forum post, a magazine or newspaper article, a web log entry, a user-submitted comment, or any other independent item of content. It is
              <em>independent</em> in that its contents could stand alone, for example in syndication. However, the <a>element</a> is still associated with its ancestors; for instance, contact
              information that applies to a parent body element still covers the article as well. When nesting articles, the child articles represent content that is related to the content of the
              parent article. For instance, a web log entry on a site that accepts user-submitted comments could represent the comments as articles nested within the article for the web log entry.
              Author, heading, date, or other information associated with an article does not apply to nested articles.
            </p>
            <p>
              When the user navigates to an element assigned the role of <code>article</code>, <a>assistive technologies</a> that typically intercept standard keyboard events SHOULD switch to document
              browsing mode, as opposed to passing keyboard events through to the web application. Some assistive technologies provide a feature allowing the user to navigate the hierarchy of any
              nested <code>article</code> elements.
            </p>
            <p>When an <code>article</code> is in the context of a <rref>feed</rref>, the author MAY specify values for <pref>aria-posinset</pref> and <pref>aria-setsize</pref>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>document</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^article^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-posinset</pref></li>
                    <li><pref>aria-setsize</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="banner">
          <rdef>banner</rdef>
          <div class="role-description">
            <p>A <rref>landmark</rref> that contains mostly site-oriented content, rather than page-specific content.</p>
            <p>
              Site-oriented content typically includes things such as the logo or identity of the site sponsor, and a site-specific search tool. A banner usually appears at the top of the page and
              typically spans the full width.
            </p>
            <p>
              <a>Assistive technologies</a> SHOULD enable users to quickly navigate to elements with role <code>banner</code>. [=user agents=] SHOULD treat elements with role <code>banner</code> as
              navigational <a>landmarks</a>. [=user agents=] MAY enable users to quickly navigate to elements with role <code>banner</code>.
            </p>
            <!-- keep the following paragraphs synced with the similar paragraphs in #main and #contentinfo-->
            <p>The author SHOULD mark no more than one <a>element</a> on a page with the <code>banner</code> <a>role</a>.</p>
            <p class="note">
              Because <code>document</code> and <code>application</code> elements can be nested in the <abbr title="Document Object Model">DOM</abbr>, they can have multiple
              <code>banner</code> elements as <abbr title="Document Object Model">DOM</abbr> descendants, assuming each of those is associated with different document nodes, either by a DOM nesting
              (e.g., <rref>document</rref> within <rref>document</rref>) or by use of the <pref>aria-owns</pref> <a>attribute</a>.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>landmark</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^header^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="blockquote">
          <rdef>blockquote</rdef>
          <div class="role-description">
            <p>A section of content that is quoted from another source.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^blockquote^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="button">
          <rdef>button</rdef>
          <div class="role-description">
            <p>An input that allows for user-triggered actions when clicked or pressed. See related <rref>link</rref>.</p>
            <p>
              Buttons are mostly used for discrete actions. Standardizing the appearance of buttons enhances the user's recognition of the <a>widgets</a> as buttons and allows for a more compact
              display in toolbars.
            </p>
            <p>
              Buttons support the optional <a>attribute</a> <sref>aria-pressed</sref>. Buttons with a non-empty <sref>aria-pressed</sref> attribute are toggle buttons. When
              <sref>aria-pressed</sref> is <code>true</code> the button is in a "pressed" <a>state</a>, when <sref>aria-pressed</sref> is <code>false</code> it is not pressed. If the attribute is not
              present, the button is a simple command button.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>command</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"><code>&lt;[^button^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related">
                  <rref>link</rref>
                </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><sref>aria-disabled</sref></li>
                    <li><pref>aria-haspopup</pref></li>
                    <li><sref>aria-expanded</sref></li>
                    <li><sref>aria-pressed</sref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational">True</td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="caption">
          <rdef>caption</rdef>
          <div class="role-description">
            <p>Visible content that names, or describes a <rref>figure</rref>, <rref>grid</rref>, <rref>group</rref>, <rref>radiogroup</rref>, <rref>table</rref> or <rref>treegrid</rref>.</p>
            <p>When using <code>caption</code> authors SHOULD ensure:</p>
            <ul>
              <li>The <code>caption</code> is a descendant of a <rref>figure</rref>, <rref>grid</rref>, <rref>group</rref>, <rref>radiogroup</rref>, <rref>table</rref>, or <rref>treegrid</rref>.</li>
              <li>
                The <code>caption</code> is the first non-<code>generic</code> descendant of a <rref>grid</rref>, <rref>group</rref>, <rref>radiogroup</rref>, <rref>table</rref> or
                <rref>treegrid</rref>.
              </li>
              <li>The <code>caption</code> is the first or last non-<code>generic</code> descendant of a <rref>figure</rref>.</li>
            </ul>
            <p>
              If the <code>caption</code> represents an accessible name for its containing element, authors SHOULD specify <pref>aria-labelledby</pref> on the containing element to reference the
              element with role <code>caption</code>.
            </p>

            <pre class="example highlight">
					&lt;div role="radiogroup" aria-labelledby="cap"&gt;
				    &lt;div role="caption" id="cap"&gt;
				      Choose your favorite fruit
				    &lt;/div&gt;
				    &lt;!-- ... --&gt;
				</pre
            >

            <p>
              If a <code>caption</code> contains content that serves as both a name and description for its containing element, authors MAY instead specify <pref>aria-labelledby</pref> to reference an
              element within the <code>caption</code> that represents the "name" of the containing element, and specify <pref>aria-describedby</pref> to reference an element within the
              <code>caption</code> that represents the descriptive content.
            </p>

            <pre class="example highlight">
					&lt;div role="table" aria-labelledby="name" aria-describedby="desc"&gt;
				    &lt;div role="caption"&gt;
				      &lt;div id="name"&gt;Contest Entrants&lt;/div&gt;
				      &lt;div id="desc"&gt;
				        This table shows the total number of entrants (500) the
				        contest accepted over the past four weeks.
				      &lt;/div&gt;
				    &lt;/div&gt;
				    &lt;!-- ... --&gt;
				</pre
            >

            <p>
              If the <code>caption</code> represents a long-form description, or if the description contains semantic elements which are important in understanding the description, authors MAY instead
              specify <pref>aria-labelledby</pref> to reference an element within the <code>caption</code> that represents the "name" of the containing element, and specify
              <pref>aria-details</pref> to reference an element within the <code>caption</code> that represents the descriptive content.
            </p>

            <pre class="example highlight">
					&lt;div role="figure" aria-labelledby="name" aria-details="details"&gt;
					  &lt;!-- figure content here, such as a complex data viz SVG -->
				    &lt;div role="caption"&gt;
				      &lt;div id="name"&gt;Sales information for 20XX&lt;/div&gt;
				      &lt;div id="details"&gt;
				        This barchart represents the total amount of sales over the course
				        of five years. &lt;a href="...">Sales information for last year&lt;/a> can
				        be reviewed, or you can overlay &lt;button aria-pressed="false">previous year&lt;/button>
				        information in this graphic.
				      &lt;/div&gt;
				    &lt;/div&gt;
				    &lt;!-- ... --&gt;
				</pre
            >

            <p>
              If a <code>caption</code> contains only a description, without a suitable text string to serve as the accessible name for its containing element, then <pref>aria-label</pref> or
              <pref>aria-labelledby</pref> MAY be used to provide an accessible name, and the <code>caption</code> MAY be treated solely as descriptive content, referenced via
              <pref>aria-details</pref>.
            </p>

            <pre class="example highlight">
					&lt;div role="figure" aria-label="Sales information" aria-details="details"&gt;
					  &lt;!-- figure content here, such as a complex data viz SVG -->
				    &lt;div role="caption" id="details"&gt;
				      This barchart represents the total amount of sales over the course
				      of five years. &lt;a href="...">Sales information for last year&lt;/a> can
				      be reviewed, or you can overlay &lt;button aria-pressed="false">previous year&lt;/button>
				      information in this graphic.
				    &lt;/div&gt;
				    &lt;!-- ... --&gt;
				</pre
            >
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related">
                  <ul>
                    <li><code>&lt;[^caption^]&gt;</code> in HTML</li>
                    <li><code>&lt;[^figcaption^]&gt;</code> in HTML</li>
                    <li><code>&lt;[^legend^]&gt;</code> in HTML</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope">
                  <ul>
                    <li><rref>figure</rref></li>
                    <li><rref>grid</rref></li>
                    <li><rref>group</rref></li>
                    <li><rref>radiogroup</rref></li>
                    <li><rref>table</rref></li>
                    <li><rref>treegrid</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
                <td class="role-disallowed">
                  <ul>
                    <li><pref>aria-braillelabel</pref></li>
                    <li><pref>aria-label</pref></li>
                    <li><pref>aria-labelledby</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">prohibited</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="cell">
          <rdef>cell</rdef>
          <div class="role-description">
            <p>A cell in a tabular container. See related <rref>gridcell</rref>.</p>
            <p>Authors MUST ensure [=elements=] with <a>role</a> cell are the <a>accessibility children</a> of an element with the <a>role</a> <rref>row</rref>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"><code>&lt;[^td^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"><rref>row</rref></td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"></td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-colindex</pref></li>
                    <li><pref>aria-colindextext</pref></li>
                    <li><pref>aria-colspan</pref></li>
                    <li><pref>aria-rowindex</pref></li>
                    <li><pref>aria-rowindextext</pref></li>
                    <li><pref>aria-rowspan</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="checkbox">
          <rdef>checkbox</rdef>
          <div class="role-description">
            <p>A checkable input that has three possible <span>values</span>: <code>true</code>, <code>false</code>, or <code>mixed</code>.</p>
            <p>
              The <sref>aria-checked</sref> <a>attribute</a> of a <code>checkbox</code> indicates whether the input is checked (<code>true</code>), unchecked (<code>false</code>), or represents a
              group of [=elements=] that have a mixture of checked and unchecked values (<code>mixed</code>). Many checkboxes do not use the <code>mixed</code> value, and thus are effectively boolean
              checkboxes.
            </p>
            <p class="note">
              Due to the strong native semantics of HTML's native checkbox, authors are advised against using <code>aria-checked</code> on an <code>input type=checkbox</code>. Rather, use the native
              <code>checked</code> attribute or the <code>indeterminate</code> IDL attribute to specify the checkbox's "checked" or "mixed" state, respectively.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>input</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related">
                  <ul>
                    <li><code>&lt;input type="[^input/type/checkbox^]"&gt;</code> in HTML</li>
                    <li><rref>option</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties">
                  <ul>
                    <li><sref>aria-checked</sref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-errormessage</pref></li>
                    <li><sref>aria-expanded</sref></li>
                    <li><sref>aria-invalid</sref></li>
                    <li><pref>aria-readonly</pref></li>
                    <li><pref>aria-required</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational">True</td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values"></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="code">
          <rdef>code</rdef>
          <div class="role-description">
            <p>A section whose content represents a fragment of computer code.</p>
            <p>
              The primary purpose of the code role is to inform assistive technologies that the content is computer code and thus might require special presentation, in particular with respect to
              synthesized speech. More specifically, screen readers and other tools which provide text-to-speech presentation of content SHOULD prefer full punctuation verbosity to ensure common
              symbols (e.g. "-") are spoken.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <rref>section</rref>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^code^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"></td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"></td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
                <td class="role-disallowed">
                  <ul>
                    <li><pref>aria-braillelabel</pref></li>
                    <li><pref>aria-label</pref></li>
                    <li><pref>aria-labelledby</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">prohibited</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values"></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="columnheader">
          <rdef>columnheader</rdef>
          <div class="role-description">
            <p>A cell containing header information for a column.</p>
            <p><code>columnheader</code> 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 <a>relationship</a> in the data.</p>
            <p>
              The <code>columnheader</code> establishes a relationship between it and all cells in the corresponding column. It is the structural equivalent to an HTML <code>th</code>
              <a>element</a> with a column scope.
            </p>
            <p>Authors MUST ensure [=elements=] with <a>role</a> <code>columnheader</code> are the <a>accessibility children</a> of an element with the role <rref>row</rref>.</p>
            <p>
              Applying the <sref>aria-selected</sref> state on a columnheader MUST not cause the user agent to automatically propagate the <sref>aria-selected</sref> state to all the cells in the
              corresponding column. An author MAY choose to propagate selection in this manner depending on the specific application.
            </p>
            <p>
              While the <code>columnheader</code> role can be used in both interactive grids and non-interactive tables, the use of <pref>aria-readonly</pref> and <pref>aria-required</pref> is only
              applicable to interactive elements. Therefore, authors SHOULD NOT use <pref>aria-required</pref> or <pref>aria-readonly</pref> in a <code>columnheader</code> that descends from a
              <rref>table</rref>, and user agents SHOULD NOT expose either property to <a>assistive technologies</a> unless the <code>columnheader</code> descends from a <rref>grid</rref>.
            </p>
            <p class="note">
              Because cells are organized into rows, there is not a single container element for the column. The column is the set of <rref>gridcell</rref> elements in a particular position within
              their respective <rref>row</rref> containers.
            </p>
            <p class="note" title="Usage of aria-disabled">
              While <sref>aria-disabled</sref> is currently supported on <rref>columnheader</rref>, in a future version the working group plans to prohibit its use on elements with role
              <rref>columnheader</rref> except when the element is in the context of a <rref>grid</rref> or <rref>treegrid</rref>.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>cell</rref></li>
                    <li><rref>gridcell</rref></li>
                    <li><rref>sectionhead</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td><code>&lt;th scope="[^th/scope/col^]"&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"><rref>row</rref></td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"><pref>aria-sort</pref></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="combobox">
          <rdef>combobox</rdef>
          <div class="role-description">
            <p>
              An <rref>input</rref> that controls another element, such as a <rref>listbox</rref> or <rref>grid</rref>, that can dynamically pop up to help the user set the value of the
              <rref>input</rref>.
            </p>
            <p class="ednote" title="Major Changes to combobox role in ARIA 1.2">
              The Guidance for <rref>combobox</rref> has changed significantly in ARIA 1.2 due to problems with implementation of the previous patterns. Authors and developers of User Agents,
              Assistive Technologies, and Conformance Checkers are advised to review this section carefully to understand the changes. Explanation of the changes is available in the
              <a href="https://github.com/w3c/aria/wiki/Resolving-ARIA-1.1-Combobox-Issues">ARIA repository wiki</a>.
            </p>
            <p>
              A <code>combobox</code> functionally combines a named input field with the ability to assist value selection via a supplementary popup element. A <code>combobox</code> input MAY be
              either a single-line text field that supports editing and typing or an element that only displays the current value of the <code>combobox</code>. If the <code>combobox</code> supports
              text input and provides autocompletion behavior as described in <pref>aria-autocomplete</pref>, authors MUST set <pref>aria-autocomplete</pref> on the <code>combobox</code> element to
              the value that corresponds to the provided behavior.
            </p>
            <p>
              Typically, the initial state of a <code>combobox</code> is collapsed. In the collapsed state, only the <code>combobox</code> element and a separate, optional popup control
              <rref>button</rref> are visible. A <code>combobox</code> is said to be expanded when both the <code>combobox</code> element showing its current value and its associated popup element are
              visible. Authors MUST set <sref>aria-expanded</sref> to <code>true</code> on an element with role <code>combobox</code> when it is expanded and <code>false</code> when it is collapsed.
            </p>
            <p>
              Elements with the role <code>combobox</code> have an implicit <pref>aria-haspopup</pref> value of <code>listbox</code>. If the <code>combobox</code> popup element has a role other than
              <rref>listbox</rref>, authors MUST specify an <pref>aria-haspopup</pref> value of <rref>tree</rref>, <rref>grid</rref>, or <rref>dialog</rref> that corresponds to the role of its popup.
            </p>
            <p>
              If the user interface includes an additional icon that allows the visibility of the popup to be controlled via pointer and touch events, authors SHOULD ensure that element has role
              <rref>button</rref>, that it is focusable but not included in the page <kbd>Tab</kbd> sequence, and that it is not a descendant of the element with role <code>combobox</code>. In
              addition, to be keyboard accessible, authors SHOULD provide keyboard mechanisms for moving focus between the <code>combobox</code> element and elements contained in the popup. For
              example, one common convention is that <kbd>Down Arrow</kbd> moves focus from the input to the first focusable descendant of the popup element. If the popup element supports
              <pref>aria-activedescendant</pref>, in lieu of moving focus, such keyboard mechanisms can control the value of <pref>aria-activedescendant</pref> on the <code>combobox</code> element.
              When a descendant of the popup element is active, authors MAY set <pref>aria-activedescendant</pref> on the <code>combobox</code> to a value that refers to the active element within the
              popup while focus remains on the <code>combobox</code> element.
            </p>
            <p>
              User agents MUST expose the value of elements with role <code>combobox</code> to <a>assistive technologies</a>. The value of a <code>combobox</code> is represented by one of the
              following:
            </p>
            <ul>
              <li>
                If the <code>combobox</code> element is a host language element that provides a value, such as an HTML <code>input</code> element, the value of the combobox is the value of that
                element.
              </li>
              <li>
                Otherwise, the value of the <code>combobox</code> is represented by its descendant elements and can be determined using the same method used to compute the name of a
                <rref>button</rref> from its descendant content.
              </li>
            </ul>
            <pre class="example highlight">
          &lt;label id="tag_label" for="tag_combo">Tag&lt;/label>
		      &lt;input type="text" id="tag_combo"
            role="combobox" aria-autocomplete="list"
            aria-haspopup="listbox" aria-expanded="true"
            aria-controls="popup_listbox" aria-activedescendant="selected_option"&gt;
				  &lt;ul role="listbox" id="popup_listbox" aria-labelledby="tag_label"&gt;
			      &lt;li role="option"&gt;Zebra&lt;/li&gt;
			      &lt;li role="option" id="selected_option"&gt;Zoom&lt;/li&gt;
				  &lt;/ul&gt;
				</pre
            >
            <p class="ednote" title="Validity changes combobox for ARIA 1.2">
              Please review the following carefully. As a result of these changes a combobox following the ARIA 1.1 combobox specification will no longer conform with the ARIA specification.
            </p>
            <div class="note">
              <p>The structural requirements for <code>combobox</code> defined by this version of the specification are different from the requirements defined by ARIA 1.0 and ARIA 1.1:</p>
              <ul>
                <li>
                  The ARIA 1.0 specification required the input element with the <code>combobox</code> role to be a single-line text field and reference the popup element with
                  <pref>aria-owns</pref> instead of <pref>aria-controls</pref>.
                </li>
                <li>
                  The ARIA 1.1 specification, which was not broadly supported by assistive technologies, required the <code>combobox</code> to be a non-focusable element with two required
                  <a>accessibility children</a> -- a focusable <rref>textbox</rref> and a popup element controlled by the <rref>textbox</rref>.
                </li>
                <li>
                  The changes introduced in ARIA 1.2 improve interoperability with assistive technologies and enable authors to create presentations of combobox that more closely imitate a native HTML
                  <code>select</code> element.
                </li>
              </ul>
            </div>
            <p>
              The features and behaviors of combobox implementations vary widely. Consequently, there are many important authoring considerations. See the
              <cite
                ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite
              >
              for additional details on implementing combobox design patterns.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>input</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^select^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"></td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties">
                  <sref>aria-expanded</sref>
                </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-activedescendant</pref></li>
                    <li><pref>aria-autocomplete</pref></li>
                    <li><pref>aria-controls</pref></li>
                    <li><pref>aria-errormessage</pref></li>
                    <li><pref>aria-haspopup</pref></li>
                    <li><sref>aria-invalid</sref></li>
                    <li><pref>aria-readonly</pref></li>
                    <li><pref>aria-required</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">Default for <pref>aria-haspopup</pref> is <code class="default">listbox</code>.<br /></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="command">
          <rdef>command</rdef>
          <div class="role-description">
            <p>A form of widget that performs an action but does not receive input data.</p>
            <p><code>command</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>command</code> role in content.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract">True</td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>widget</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom"></td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="comment">
          <rdef>comment</rdef>
          <div class="role-description">
            <p>A comment contains content expressing reaction to other content.</p>
            <p>
              Comments can annotate any visible content, from small spans of text, to other comments, to entire articles. Authors SHOULD identify the relationships between comments and the commented
              content, as follows:
            </p>
            <ol>
              <li>
                If the comment is a reply to another <code>comment</code>:
                <ul>
                  <li>
                    If all ancestor comments are available in the DOM, make each reply <code>comment</code> a semantic descendant of the <code>comment</code> to which it is replying, either by making
                    it a DOM descendant element or by using <pref>aria-owns</pref>.
                  </li>
                  <li>
                    Alternatively, if all ancestor comments are not in the DOM, such as when comments are paginated, the hierarchical level MAY be indicated via <pref>aria-level</pref>. Additional
                    group positional information MAY be indicated via <pref>aria-posinset</pref> and <pref>aria-setsize</pref>.
                  </li>
                </ul>
              </li>
              <li>
                Otherwise, if the comment relates to other content in the page:
                <ul>
                  <li>Provide <pref>aria-details</pref> on the element containing the commented content with a value refering to the element with role <code>comment</code>.</li>
                  <li>
                    If there are multiple comments related to the same commented content, either provide a value for <pref>aria-details</pref> on the commented content that refers to each individual
                    comment, or use <pref>aria-details</pref> to refer to a parent container of the comments. If <pref>aria-details</pref> refers to an element containing comments rather than
                    <code>comment</code> elements, authors SHOULD assign a role of <rref>group</rref> or <rref>region</rref> to the referenced container.
                  </li>
                </ul>
              </li>
            </ol>
            <p>
              If the author has not explicitly declared <pref>aria-level</pref>, <pref>aria-posinset</pref>, or <pref>aria-setsize</pref> for a <code>comment</code> element, user agents MUST
              automatically compute the missing values and expose them to assistive technologies.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>article</rref></td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"></td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-level</pref></li>
                    <li><pref>aria-posinset</pref></li>
                    <li><pref>aria-setsize</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="complementary">
          <rdef>complementary</rdef>
          <div class="role-description">
            <p>
              A <rref>landmark</rref> that is designed to be complementary to the main content that it is a sibling to, or a direct descendant of. The contents of a complementary landmark would be
              expected to remain meaningful if it were to be separated from the main content it is relevant to.
            </p>
            <p>
              There are various types of content that would appropriately have this <a>role</a>. For example, in the case of a portal, this can include but not be limited to show times, current
              weather, related articles, or stocks to watch. If the complementary content is completely separable from the main content, it might be appropriate to use a more general role.
            </p>
            <p>
              <a>Assistive technologies</a> SHOULD enable users to quickly navigate to elements with role <code>complementary</code>. [=user agents=] SHOULD treat elements with role
              <code>complementary</code> as navigational <a>landmarks</a>. [=user agents=] MAY enable users to quickly navigate to elements with role <code>complementary</code>.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>landmark</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^aside^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="composite">
          <rdef>composite</rdef>
          <div class="role-description">
            <p>A <a>widget</a> that can contain navigable <a>accessibility descendants</a>.</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 [=elements=] that are <a>accessibility descendants</a> of the composite element.
            </p>
            <p><code>composite</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>composite</code> role in content.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract">True</td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>widget</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-activedescendant</pref></li>
                    <li><sref>aria-disabled</sref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="contentinfo">
          <rdef>contentinfo</rdef>
          <div class="role-description">
            <p>A <rref>landmark</rref> that contains information about the parent document.</p>
            <p>Examples of information included in this region of the page are copyrights and links to privacy statements.</p>
            <p>
              <a>Assistive technologies</a> SHOULD enable users to quickly navigate to elements with role <code>contentinfo</code>. [=user agents=] SHOULD treat elements with role
              <code>contentinfo</code> as navigational <a>landmarks</a>. [=user agents=] MAY enable users to quickly navigate to elements with role <code>contentinfo</code>.
            </p>
            <!-- keep the following paragraphs synced with the similar paragraphs in #banner and #main -->
            <p>The author SHOULD mark no more than one <a>element</a> on a page with the <code>contentinfo</code> role.</p>
            <p class="note">
              Because <code>document</code> and <code>application</code> elements can be nested in the <abbr title="Document Object Model">DOM</abbr>, they can have multiple
              <code>contentinfo</code> elements as <abbr title="Document Object Model">DOM</abbr> descendants, assuming each of those is associated with different document nodes, either by a DOM
              nesting (e.g., <rref>document</rref> within <rref>document</rref>) or by use of the <pref>aria-owns</pref> attribute.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>landmark</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^footer^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="definition">
          <rdef>definition</rdef>
          <div class="role-description">
            <p>A definition of a term or concept. See related <rref>term</rref>.</p>
            <p>Authors MUST identify the <a>element</a> being defined and assign that element a role of <rref>term</rref>.</p>
            <p>
              Authors SHOULD NOT use the <code>definition</code> role on interactive elements such as form controls because doing so could prevent users of assistive technologies from interacting with
              those elements.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
                <td class="role-disallowed">
                  <ul>
                    <li><pref>aria-braillelabel</pref></li>
                    <li><pref>aria-label</pref></li>
                    <li><pref>aria-labelledby</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">prohibited</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="deletion">
          <rdef>deletion</rdef>
          <div class="role-description">
            <p>
              A deletion represents content that is marked as removed, content that is being suggested for removal, or content that is no longer relevant in the context of its accompanying content.
              See related <rref>insertion</rref>.
            </p>
            <p>
              Deletions are typically used to either mark differences between two versions of content or to designate content suggested for removal in scenarios where multiple people are revising
              content.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related">
                  <ul>
                    <li><code>&lt;[^del^]&gt;</code> in HTML</li>
                    <li><code>&lt;[^s^]&gt;</code> in HTML</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
                <td class="role-disallowed">
                  <ul>
                    <li><pref>aria-braillelabel</pref></li>
                    <li><pref>aria-label</pref></li>
                    <li><pref>aria-labelledby</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">prohibited</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="dialog">
          <rdef>dialog</rdef>
          <div class="role-description">
            <p>A dialog is a descendant window of the primary window of a web application. For HTML pages, the primary application window is the entire web document.</p>
            <p>
              Dialogs are often used to prompt the user to enter or respond to information, or can represent content related to understanding or modifying the content of the primary application
              window. A dialog that is designed to interrupt workflow and prevent users from interacting with the primary web application is usually modal. See related <rref>alertdialog</rref>. A
              dialog that allows for the user to switch between interacting with the content of the primary web application and the content the dialog is usually modeless (i.e., non-modal). In lieu of
              using robust host language features for marking content of the primary web application as <code>inert</code>, authors SHOULD use the <pref>aria-modal</pref> attribute, and constrain
              focus to dialogs. See the <a href="https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/">WAI-ARIA Authoring Practices: Dialog (modal) pattern</a> for additional details on implementing
              modal dialog design patterns.
            </p>
            <p>Authors SHOULD provide an accessible name for a dialog, which can be done with the <pref>aria-label</pref> or <pref>aria-labelledby</pref> attribute.</p>
            <p>
              Authors SHOULD ensure that all dialogs (both modal and non-modal) have at least one focusable descendant element. Authors SHOULD focus an element in the modal dialog when it is
              displayed, and authors SHOULD constrain keyboard focus to focusable elements within a modal dialog, until dismissed.
            </p>
            <p>
              Authors SHOULD provide a dialog an accessible description, with the <pref>aria-describedby</pref> attribute, for instances where authors have set initial keyboard focus on an element
              that follows content that outlines the purpose of the dialog. Assistive technology SHOULD give precedence to exposing author defined dialog accessible descriptions when a dialog is
              invoked and user focus is moved to a descendant of the dialog element.
            </p>
            <div class="note">
              <p>
                Authors are strongly encouraged to use <pref>aria-describedby</pref>, rather than <pref>aria-description</pref>, to provide descriptions to dialogs. While
                <code>aria-description</code> could be used to provide an accessible description for a dialog, it will provide a better and more consistent user experience to reference visible content
                that can also be independently read by all users. Doing so will help ensure important descriptive information is less likely to be missed.
              </p>
            </div>
            <aside class="example">
              <p>
                In the following example, the first text field will receive initial focus when the dialog is rendered. As this means focus will be set "after" the preceding content that provides
                instructions for the form fields, an <code>aria-describedby</code> attribute is used to expose this content as a description for the <code>dialog</code>.
              </p>
              <pre>
&lt;div role="dialog" aria-labelledby="h" aria-describedby="d" aria-modal="true" ...>
  &lt;h2 id="h">Add Shipping Address&lt;/h2>
  &lt;p id="d">By placing an order on this website, you acknowledge we will be sending you tons of junk mail for you to immediately recycle. Thanks!&lt;/p>
  &lt;label>
    Street: &lt;input autofocus ...>
  &lt;/label>
  ...
&lt/div></pre
              >
            </aside>
            <p class="note">
              In the description of this role, the term "web application" does not refer to the <rref>application</rref> role, which specifies specific assistive technology behaviors.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>window</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="directory">
          <rdef>directory</rdef>
          <div class="role-description">
            <p>[Deprecated in ARIA 1.2] A list of references to members of a group, such as a static table of contents.</p>
            <p class="note">
              As exposed by accessibility APIs, the <code>directory</code> <a>role</a> is essentially equivalent to the <code>list</code> <a>role</a>. So, using <code>directory</code> does not provide
              any additional benefits to assistive technology users. Authors are advised to treat <code>directory</code> as deprecated and to use <code>list</code>, or a host language's equivalent
              semantics instead.
            </p>
            <p>
              A <code>directory</code> is a static table of contents, whether linked or unlinked. This includes tables of contents built with lists, including nested lists. Dynamic tables of contents,
              however, might use a <rref>tree</rref> role instead.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>list</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="document">
          <rdef>document</rdef>
          <div class="role-description">
            <p>An <a>element</a> containing content that <a>assistive technology</a> users might want to browse in a reading mode.</p>
            <p>
              When <a>user agent</a> focus moves to an element assigned the role of <code>document</code>, <a>assistive technologies</a> having a reading mode for browsing static content MAY switch to
              that reading mode and intercept standard input events, such as Up or Down arrow keyboard events, to control the reading cursor.
            </p>
            <p>
              Because <a>assistive technologies</a> that have a reading mode default to that mode for all elements except for those with either a <rref>widget</rref> or <rref>application</rref> role,
              the only circumstance where the <code>document</code> role is useful for changing assistive technology behavior is when the element with role <code>document</code> is a focusable child
              element of a <rref>widget</rref> or <rref>application</rref>. For example, given an <rref>application</rref> element which contains some static rich text, the author can apply role
              <code>document</code> to the element containing the text and give it a <code>tabindex</code> of <code>0</code>. When a screen reader user presses the Tab key and places focus on the
              <code>document</code> element, the user will be able to read the text with the screen reader's reading cursor.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>structure</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="emphasis">
          <rdef>emphasis</rdef>
          <div class="role-description">
            <p>One or more emphasized characters. See related <rref>strong</rref>.</p>
            <p>
              The purpose of the <code>emphasis</code> role is to stress or emphasize content. It is not for communicating changes in typographical presentation that do not impact the meaning of the
              content. Authors SHOULD use the <code>emphasis</code> role only if its absence would change the meaning of the content.
            </p>
            <p>The <code>emphasis</code> role is not intended to convey importance; for that purpose, the <rref>strong</rref> role is more appropriate.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^em^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
                <td class="role-disallowed">
                  <ul>
                    <li><pref>aria-braillelabel</pref></li>
                    <li><pref>aria-label</pref></li>
                    <li><pref>aria-labelledby</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">prohibited</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="feed">
          <rdef>feed</rdef>
          <div class="role-description">
            <p>
              A scrollable <rref>list</rref> of <rref data-lt="article">articles</rref> where scrolling might cause <rref data-lt="article">articles</rref> to be added to or removed from either end of
              the list.
            </p>
            <p>
              A <code>feed</code> enables users of <a>assistive technologies</a> that have a document browse mode, such as screen readers, to use the browse mode reading cursor to both read and scroll
              through a stream of rich content that might continue scrolling infinitely by loading more content as the user reads. In a <code>feed</code>, <a>assistive technologies</a> provide a web
              application with signals of the user's reading cursor movement by moving <a>user agent</a> focus, enabling the application to both add new content and visually position content as the
              user browses the page. The <code>feed</code> also lets authors inform assistive technologies when additions and removals are occurring so assistive technologies can more reliably update
              their reading view without disrupting reading or degrading performance.
            </p>
            <p>
              For example, a <code>feed</code> could be used to present a stream of news stories where each <rref>article</rref> contains a story with text, links, images, and comments as well as
              widgets for sharing and commenting. As a screen reader user reads and interacts with each story and moves the screen reader reading cursor from story to story, each story scrolls into
              view and, as needed, new stories are loaded.
            </p>
            <p>
              A <code>feed</code> is a container element whose children have role <rref>article</rref>. When <rref data-lt="article">articles</rref> are added or removed from either or both ends of a
              <code>feed</code>, authors SHOULD set <sref>aria-busy</sref> to <code>true</code> on the <code>feed</code> element before the changes are made and set it to <code>false</code> after the
              changes are complete. Authors SHOULD avoid inserting or removing <rref data-lt="article">articles</rref> in the middle of a <code>feed</code>. These requirements help
              <a>assistive technologies</a> gracefully respond to changes in the <code>feed</code> content that occur simultaneously with user commands to move the reading cursor within the
              <code>feed</code>.
            </p>
            <p>
              Authors SHOULD make each <rref>article</rref> in a <code>feed</code> focusable and ensure that the application scrolls an <rref>article</rref> into view when <a>user agent</a> focus is
              set on the <rref>article</rref> or one of its descendant elements. For example, in HTML, each <rref>article</rref> element should have a <code>tabindex</code> value of either
              <code>-1</code> or <code>0</code>.
            </p>
            <p>
              When an <a>assistive technology</a> reading cursor moves from one <rref>article</rref> to another, <a>assistive technologies</a> SHOULD set user agent focus on the
              <rref>article</rref> that contains the reading cursor. If the reading cursor lands on a focusable element inside the <rref>article</rref>, the assistive technology MAY set focus on that
              element in lieu of setting focus on the containing <rref>article</rref>.
            </p>
            <p>
              Because the ability to scroll to another <rref>article</rref> with an <a>assistive technology</a> reading cursor depends on the presence of another <rref>article</rref> in the page,
              authors SHOULD attempt to load additional <rref data-lt="article">articles</rref> before <a>user agent</a> focus reaches an <rref>article</rref> at either end of the set of
              <rref data-lt="article">articles</rref> that has been loaded. Alternatively, authors MAY include an <rref>article</rref> at either or both ends of the loaded set of
              <rref data-lt="article">articles</rref> that includes an element, such as a <rref>button</rref>, that lets the user request more <rref data-lt="article">articles</rref> to be loaded.
            </p>
            <p>
              In addition to providing a brief label, authors MAY apply <pref>aria-describedby</pref> to <rref>article</rref> elements in a <code>feed</code> to suggest to screen readers which
              elements to speak after the label when users navigate by <rref>article</rref>. Screen readers MAY provide users with a way to quickly scan <code>feed</code> content by speaking both the
              label and <a class="informative">accessible description</a> when navigating by <rref>article</rref>, enabling the user to ignore repetitive or less important elements, such as embedded
              interaction widgets, that the author has left out of the description.
            </p>
            <p>
              Authors SHOULD provide keyboard commands for moving focus among <rref data-lt="article">articles</rref> in a <code>feed</code> so users who do not utilize an assistive technology that
              provides <rref>article</rref> navigation features can use the keyboard to navigate the <code>feed</code>.
            </p>
            <p>
              If the number of articles available in a <code>feed</code> supply is static, authors MAY specify <pref>aria-setsize</pref> on <rref>article</rref> elements in that <code>feed</code>.
              However, if the total number is extremely large, indefinite, or changes often, authors MAY set <pref>aria-setsize</pref> to <code>-1</code> to communicate the unknown size of the set.
            </p>
            <p>
              See the
              <cite
                ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite
              >
              for additional details on implementing a feed design pattern.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>list</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"><rref>article</rref></td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="figure">
          <rdef>figure</rdef>
          <div class="role-description">
            <p>
              A perceivable <rref>section</rref> of content that typically contains a <a>graphical document</a>, images, media player, code snippets, or example text. The parts of a
              <code>figure</code> MAY be user-navigable.
            </p>
            <p>
              Authors SHOULD provide a reference to the <code>figure</code> from the main text, but the <code>figure</code> need not be displayed at the same location as the referencing element.
              Authors MAY provide a <code>figure</code> a <rref>caption</rref> which can include its name, descriptive text, or both. If a <code>caption</code> is provided, and it serves as a
              description to the contents of the <code>figure</code>, authors SHOULD associate it to the <code>figure</code> element using <pref>aria-details</pref>.
            </p>
            <p>
              Authors MAY provide a <code>figure</code> an accessible name using <pref>aria-label</pref> or use <pref>aria-labelledby</pref> to reference other text in the page to serve as the
              element's label and accessible name.
            </p>
            <p>Please refer to the <rref>caption</rref> role for more information on how to associate a <code>figure</code> with its <code>caption</code>.</p>
            <p><a>Assistive technologies</a> SHOULD enable users to quickly navigate to figures. <a>User agents</a> MAY enable users to quickly navigate to figures.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^figure^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="form">
          <rdef>form</rdef>
          <div class="role-description">
            <p>A <rref>landmark</rref> region that contains a collection of items and objects that, as a whole, combine to create a form. See related <rref>search</rref>.</p>
            <p>
              A form can contain a mix of host language form controls, scripted controls, and hyperlinks. Authors are reminded to use native host language semantics to create form controls whenever
              possible. If the purpose of a form is to submit search criteria, authors SHOULD use the <rref>search</rref> role instead of the generic <code>form</code> role.
            </p>
            <p>
              Authors SHOULD give each element with role <code>form</code> a brief label that describes the purpose of the form. Authors SHOULD reference a visible label with
              <pref>aria-labelledby</pref> if a visible label is present. Authors SHOULD include the label inside of a heading whenever possible. The heading MAY be an instance of the standard host
              language heading element or an instance of an element with role <rref>heading</rref>.
            </p>
            <p>
              If an author uses a script to submit a form based on a user action that would otherwise not trigger an <code>onsubmit</code> event (for example, a form submission triggered by the user
              changing a form element's value), the author SHOULD provide the user with advance notification of the behavior.
            </p>
            <p>
              <a>Assistive technologies</a> SHOULD enable users to quickly navigate to elements with role <code>form</code>. [=User agents=] SHOULD treat elements with role <code>form</code> and an
              accessible name as navigational <a>landmarks</a>. [=User agents=] MAY enable users to quickly navigate to elements with role <code>form</code>.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>landmark</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"><code>&lt;[^form^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"></td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"></td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="generic">
          <rdef>generic</rdef>
          <div class="role-description">
            <p>A nameless container <a>element</a> that has no semantic meaning on its own.</p>
            <p>
              The <code>generic</code> role is intended for use as the implicit role of generic elements in host languages (such as HTML <code>div</code> or <code>span</code>), so is primarily for
              implementors of user agents. Authors SHOULD NOT use this role in content. Authors MAY use <rref>presentation</rref> or <rref>none</rref> to remove implicit accessibility semantics, or a
              semantic container role such as <rref>group</rref> to semantically group descendants in a named container.
            </p>
            <p>
              Like an element with role <rref>presentation</rref>, an element with role <code>generic</code> can provide a limited number of accessible states and properties for its descendants, such
              as <pref>aria-live</pref> attributes.
            </p>
            <p>
              However, unlike elements with role <code>presentation</code>, user agents expose <code>generic</code> elements in <a>accessibility APIs</a> when permitted accessibility attributes have
              been specified. User agents MAY otherwise ignore <code>generic</code> elements if such permitted attributes have not been specified.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>structure</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related">HTML <code>[^div^]</code>, HTML <code>[^span^]</code></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
                <td class="role-disallowed">
                  <ul>
                    <li><pref>aria-braillelabel</pref></li>
                    <li><pref>aria-brailleroledescription</pref></li>
                    <li><pref>aria-label</pref></li>
                    <li><pref>aria-labelledby</pref></li>
                    <li><pref>aria-roledescription</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">prohibited</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="grid">
          <rdef>grid</rdef>
          <div class="role-description">
            <p>
              A composite <rref>widget</rref> containing a collection of one or more rows with one or more cells where some or all cells in the grid are focusable by using methods of two-dimensional
              navigation, such as directional arrow keys.
            </p>
            <p>
              The <code>grid</code> role does not imply a specific visual, e.g., tabular, presentation. It describes <a>relationships</a> among [=elements=]. It can be used for purposes as simple as
              grouping a collection of checkboxes or navigation links or as complex as creating a full-featured spreadsheet application.
            </p>
            <p>
              The cell elements of a <code>grid</code> have role <rref>gridcell</rref>. Authors MAY designate a cell as a row or column header by using either the <rref>rowheader</rref> or
              <rref>columnheader</rref> <a>role</a> in lieu of the <rref>gridcell</rref> role. Authors MUST ensure elements with role <rref>gridcell</rref>, <rref>columnheader</rref>, or
              <rref>rowheader</rref> are <a>accessibility children</a> of elements with role <rref>row</rref>, which are in turn are <a>accessibility children</a> of an element with role
              <rref>rowgroup</rref>, or <code>grid</code>.
            </p>
            <p>
              To be <a>keyboard accessible</a>, authors SHOULD manage focus of descendants of a <code>grid</code> as described in <a href="#managingfocus">Managing Focus</a>. When a user is navigating
              the <code>grid</code> content with a keyboard, authors SHOULD set focus as follows:
            </p>
            <ul>
              <li>
                If a <rref>gridcell</rref> contains a single interactive <rref>widget</rref> that will not consume arrow key presses when it receives focus, such as a <rref>checkbox</rref>,
                <rref>button</rref>, or <rref>link</rref>, authors MAY set focus on the interactive element contained in that cell. This allows the contained widget to be directly operable.
              </li>
              <li>Otherwise, authors SHOULD ensure the element that receives focus is a <rref>gridcell</rref>, <rref>rowheader</rref>, or <rref>columnheader</rref> element.</li>
            </ul>
            <p>
              Authors SHOULD provide a mechanism for changing to an interaction or edit mode that allows users to navigate and interact with content contained inside a focusable cell if that focusable
              cell contains any of the following:
            </p>
            <ul>
              <li>a widget that requires arrow keys to operate, e.g., a <rref>combobox</rref> or <rref>radiogroup</rref></li>
              <li>multiple interactive elements</li>
              <li>editable content</li>
            </ul>
            <p>
              For example, if a cell in a spreadsheet contains a <rref>combobox</rref> or editable text, the <kbd>Enter</kbd> key might be used to activate a cell interaction or editing mode when that
              cell has focus so the directional arrow keys can be used to operate the contained <rref>combobox</rref> or <rref>textbox</rref>. Depending on the implementation, pressing
              <kbd>Enter</kbd> again, <kbd>Tab</kbd>, <kbd>Escape</kbd>, or another key might switch the application back to the grid navigation mode.
            </p>
            <p>
              Authors MAY use a <rref>gridcell</rref> to display the result of a formula, which could be editable by the user. In a spreadsheet application, for example, a <rref>gridcell</rref> might
              show a value calculated from a formula until the user activates the <rref>gridcell</rref> for editing when a <rref>textbox</rref> appears in the <rref>gridcell</rref> containing the
              formula in an editable state.
            </p>
            <!-- make sure the following para remains synced with its counterpart in #treegrid -->
            <p>
              If <pref>aria-readonly</pref> is set on an element with role <code>grid</code>, [=user agents=] MUST propagate the value to all <rref>gridcell</rref> elements that are
              <a>accessibility descendants</a> of that <code>grid</code> and expose the value in the accessibility API. An author MAY override the propagated value of <pref>aria-readonly</pref> for an
              individual <rref>gridcell</rref> element.
            </p>
            <p>
              In a <code>grid</code> that provides cell content editing functions, if the content of a focusable <rref>gridcell</rref> element is not editable, authors MAY set
              <pref>aria-readonly</pref> to <code>true</code> on the <code>gridcell</code> element. However, the value of <pref>aria-readonly</pref>, whether specified for a <code>grid</code> or
              individual cells, only indicates whether the content contained in cells is editable. It does not represent availability of functions for navigating or manipulating the
              <code>grid</code> itself.
            </p>
            <p>
              An unspecified value for <pref>aria-readonly</pref> does not imply that a <code>grid</code> or a <rref>gridcell</rref> contains editable content. For example, if a
              <code>grid</code> presents a collection of elements that are not editable, such as a collection of <rref>link</rref> elements representing dates in a datepicker, it is not necessary for
              the author to specify a value for <pref>aria-readonly</pref>.
            </p>
            <p>
              Authors MAY indicate that a focusable <rref>gridcell</rref> is selectable as the object of an action with the <sref>aria-selected</sref> attribute. If the <code>grid</code> allows
              multiple <rref>gridcell</rref>s to be selected, the author SHOULD set <pref>aria-multiselectable</pref> to <code>true</code> on the element with role <code>grid</code>.
            </p>
            <p>
              Since <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> can augment an element of the host language, a <code>grid</code> can reuse the elements and attributes of a
              native table, such as an HTML <code>table</code> element. For example, if an author applies the <code>grid</code> role to an HTML <code>table</code> element, the author does not need to
              apply the <rref>row</rref> and <rref>gridcell</rref> roles to the descendant HTML <code>tr</code> and <code>td</code> elements because the <a>user agent</a> will automatically make the
              appropriate translations. When the author is reusing a native host language table element and needs a <rref>gridcell</rref> element to span multiple rows or columns, the author SHOULD
              apply the appropriate host language attributes instead of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <pref>aria-rowspan</pref> or
              <pref>aria-colspan</pref> properties.
            </p>
            <p>
              Authors SHOULD provide an accessible name for a <code>grid</code>, which can be done with the <pref>aria-label</pref> or <pref>aria-labelledby</pref> attribute. Authors SHOULD reference
              a visible label with <pref>aria-labelledby</pref> if a visible label is present for the <code>grid</code>.
            </p>
            <p>
              See the
              <cite
                ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite
              >
              for additional details on implementing grid design patterns.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>composite</rref></li>
                    <li><rref>table</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"><code>&lt;[^table^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain">
                  <ul>
                    <li><rref>caption</rref></li>
                    <li><rref>row</rref></li>
                    <li><rref>rowgroup</rref> with <a>accessibility child</a> <rref>row</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-multiselectable</pref></li>
                    <li><pref>aria-readonly</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="gridcell">
          <rdef>gridcell</rdef>
          <div class="role-description">
            <p>A <rref>cell</rref> in a <rref>grid</rref> or <rref>treegrid</rref>.</p>
            <p>
              A <code>gridcell</code> can be focusable, editable, and selectable. A <code>gridcell</code> can have <a>relationships</a> such as <pref>aria-controls</pref> to address the application of
              functional relationships.
            </p>
            <p>
              If an author intends a <code>gridcell</code> to have a row header, column header, or both, and if the relevant headers cannot be determined from the
              <abbr title="Document Object Model">DOM</abbr> structure, authors SHOULD explicitly indicate which header cells are relevant to the <code>gridcell</code> by applying
              <pref>aria-describedby</pref> on the <code>gridcell</code> and referencing [=elements=] with <a>role</a> <rref>rowheader</rref> or <rref>columnheader</rref>.
            </p>
            <p>
              In a <rref>treegrid</rref>, authors MAY define a <code>gridcell</code> as expandable by using the <sref>aria-expanded</sref> attribute. If the <sref>aria-expanded</sref> attribute is
              provided, it applies only to the individual cell. It is not a proxy for the container <rref>row</rref>, which also can be expanded. The main use case for providing this attribute on a
              <code>gridcell</code> is pivot table behavior.
            </p>
            <p>Authors MUST ensure [=elements=] with <a>role</a> gridcell are <a>accessibility children</a> of an element with the <a>role</a> <rref>row</rref>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>cell</rref></li>
                    <li><rref>widget</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"><code>&lt;[^td^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"><rref>row</rref></td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"></td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><sref>aria-disabled</sref></li>
                    <li><pref>aria-errormessage</pref></li>
                    <li><sref>aria-expanded</sref></li>
                    <li><pref>aria-haspopup</pref></li>
                    <li><sref>aria-invalid</sref></li>
                    <li><pref>aria-readonly</pref></li>
                    <li><pref>aria-required</pref></li>
                    <li><sref>aria-selected</sref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="group">
          <rdef>group</rdef>
          <div class="role-description">
            <p>A set of user interface <a>objects</a> that is not intended to be included in a page summary or table of contents by <a>assistive technologies</a>.</p>
            <p>Contrast with <rref>region</rref>, which is a grouping of user interface objects that will be included in a page summary or table of contents.</p>
            <p>
              Authors SHOULD use a <code>group</code> to form a logical collection of items in a <a>widget</a>, such as children in a tree widget forming a collection of siblings in a hierarchy.
              However, when a <code>group</code> is used in the context of a <rref>listbox</rref>, for example, authors MUST limit its children to <rref>option</rref> elements. Therefore, proper
              handling of <code>group</code> by authors and assistive technologies is determined by the context in which it is provided.
            </p>
            <p>
              Authors MAY nest <code>group</code> elements. If a section is significant enough to warrant inclusion in the web page's table of contents, the author SHOULD assign it a <a>role</a> of
              <rref>region</rref> or a <a href="#landmark_roles">standard landmark role</a>.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^fieldset^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-activedescendant</pref></li>
                    <li><sref>aria-disabled</sref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="heading">
          <rdef>heading</rdef>
          <div class="role-description">
            <p>A heading for a section of the page.</p>
            <p>
              To ensure elements with a role of <code>heading</code> are organized into a logical outline, authors MUST use the <pref>aria-level</pref> attribute to indicate the proper nesting level.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>sectionhead</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related">
                  <code>&lt;[^h1^]&gt;</code>, <code>&lt;[^h2^]&gt;</code>, <code>&lt;[^h3^]&gt;</code>, <code>&lt;[^h4^]&gt;</code>, <code>&lt;[^h5^]&gt;</code>, and
                  <code>&lt;[^h6^]&gt;</code>
                  in HTML
                </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"><pref>aria-level</pref></td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="image">
          <rdef>image</rdef>
          <div class="role-description">
            <p>A container for a collection of [=elements=] that form an image. See synonym <rref>img</rref>.</p>
            <p>
              An <code>img</code> can contain captions and descriptive text, as well as multiple image files that when viewed together give the impression of a single image. An
              <code>img</code> represents a single graphic within a document, whether or not it is formed by a collection of drawing <a>objects</a>. In order for an element with a <a>role</a> of
              <code>img</code> to be <a>perceivable</a>, authors MUST provide the element with an <a class="informative">accessible name</a>. This can be done using the <pref>aria-label</pref> or
              <pref>aria-labelledby</pref> attribute.
            </p>
            <div class="note" id="role-image-note-image">
              Note regarding the ARIA 1.3 <code>image</code> role.
              <p>
                The <code>image</code> role was added to ARIA in version 1.3 as a synonym of the ARIA 1.0 <rref>img</rref> role. The <code>image</code> role improves syntactic consistency with the
                names of other roles, which are complete words or concatenations of complete words.
              </p>
            </div>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^img^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational">True</td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="img">
          <rdef>img</rdef>
          <div class="role-description">
            <p>A container for a collection of [=elements=] that form an image. See synonym <rref>image</rref>.</p>
          </div>
        </div>
        <div class="role" id="input">
          <rdef>input</rdef>
          <div class="role-description">
            <p>A generic type of <a>widget</a> that allows user input.</p>
            <p><code>input</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>input</code> role in content.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract">True</td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>widget</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"></td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"><sref>aria-disabled</sref></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom"></td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="insertion">
          <rdef>insertion</rdef>
          <div class="role-description">
            <p>An insertion contains content that is marked as added or content that is being suggested for addition. See related <rref>deletion</rref>.</p>
            <p>
              Insertions are typically used to either mark differences between two versions of content or to designate content suggested for addition in scenarios where multiple people are revising
              content.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^ins^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
                <td class="role-disallowed">
                  <ul>
                    <li><pref>aria-braillelabel</pref></li>
                    <li><pref>aria-label</pref></li>
                    <li><pref>aria-labelledby</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">prohibited</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="landmark">
          <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><code>landmark</code> is an abstract role used for the ontology. Authors MUST NOT use <code>landmark</code> role in content.</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>Elements with a role that is a subclass of the landmark role are known as <a>landmark</a> regions or navigational landmark regions.</p>
            <p><a>Assistive technologies</a> SHOULD enable users to quickly navigate to landmark regions. [=user agents=] MAY enable users to quickly navigate to landmark regions.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract">True</td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom"></td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="link">
          <rdef>link</rdef>
          <div class="role-description">
            <p>An interactive reference to an internal or external resource that, when activated, causes the user agent to navigate to that resource. See related <rref>button</rref>.</p>
            <p>
              If this is a native link in the host language (such as an HTML anchor with an <code>href</code> value), activating the link causes the <a>user agent</a> to navigate to that resource. If
              this is a simulated link, the author is responsible for managing navigation.
            </p>
            <p class="note">
              If pressing the link triggers an action but does not change browser focus or page location, authors are advised to consider using the <rref>button</rref> role instead of the
              <code>link</code> role.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>command</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related">
                  <ul>
                    <li><code>&lt;[^a^]&gt;</code> in HTML</li>
                    <li><code>&lt;[^link^]&gt;</code> in HTML</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><sref>aria-disabled</sref></li>
                    <li><sref>aria-expanded</sref></li>
                    <li><pref>aria-haspopup</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="list">
          <rdef>list</rdef>
          <div class="role-description">
            <p>A <rref>section</rref> containing <rref>listitem</rref> elements. See related <rref>listbox</rref>.</p>
            <p>Lists contain children whose <a>role</a> is <rref>listitem</rref>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base">
                  <ul>
                    <li><code>&lt;[^ol^]&gt;</code> in HTML</li>
                    <li><code>&lt;[^ul^]&gt;</code> in HTML</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"><rref>listitem</rref></td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="listbox">
          <rdef>listbox</rdef>
          <div class="role-description">
            <p>A <a>widget</a> that allows the user to select one or more items from a list of choices. See related <rref>combobox</rref> and <rref>list</rref>.</p>
            <p>
              Items within the list are static and, unlike standard HTML <code>select</code> [=elements=], can contain images. List boxes contain children whose <a>role</a> is <rref>option</rref> or
              elements whose <a>role</a> is <rref>group</rref> which in turn contain children whose <a>role</a> is <rref>option</rref>.
            </p>
            <p>
              To be <a>keyboard accessible</a>, authors SHOULD manage focus of <rref>option</rref> descendants for all instances of this <a>role</a>, as described in
              <a href="#managingfocus">Managing Focus</a>.
            </p>
            <p>Elements with the role <code>listbox</code> have an implicit <pref>aria-orientation</pref> value of <code>vertical</code>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>select</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related">
                  <ul>
                    <li><rref>list</rref></li>
                    <li><code>&lt;[^select^]&gt;</code> in HTML</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain">
                  <ul>
                    <li><rref>group</rref> with <a>accessibility child</a> <rref>option</rref></li>
                    <li><rref>option</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-errormessage</pref></li>
                    <li><sref>aria-expanded</sref></li>
                    <li><sref>aria-invalid</sref></li>
                    <li><pref>aria-multiselectable</pref></li>
                    <li><pref>aria-readonly</pref></li>
                    <li><pref>aria-required</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">Default for <pref>aria-orientation</pref> is <code class="default">vertical</code>.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="listitem">
          <rdef>listitem</rdef>
          <div class="role-description">
            <p>A single item in a list or directory.</p>
            <p>Authors MUST ensure [=elements=] whose <a>role</a> is <code>listitem</code> are <a>accessibility children</a> of an <a>element</a> whose <a>role</a> is <rref>list</rref>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"><code>&lt;[^li^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope">
                  <ul>
                    <li><rref>directory</rref></li>
                    <li><rref>list</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-posinset</pref></li>
                    <li><pref>aria-setsize</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="log">
          <rdef>log</rdef>
          <div class="role-description">
            <p>A type of <a>live region</a> where new information is added in meaningful order and old information can disappear. See related <rref>marquee</rref>.</p>
            <p>
              Examples include chat logs, messaging history, game log, or an error log. In contrast to other live regions, in this <a>role</a> there is a <a>relationship</a> 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.
            </p>
            <p>Elements with the role <code>log</code> have an implicit <pref>aria-live</pref> value of <code>polite</code>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">Default for <pref>aria-live</pref> is <code class="default">polite</code>.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="main">
          <rdef>main</rdef>
          <div class="role-description">
            <p>A <rref>landmark</rref> containing the main content of a document.</p>
            <p>
              This marks the content that is directly related to or expands upon the central topic of the document. The <code>main</code> <a>role</a> is a non-obtrusive alternative for "skip to main
              content" links, where the navigation option to go to the main content (or other <a>landmarks</a>) is provided by <a>assistive technologies</a>, or by a <a>user agent</a> or browser
              extension, through a keyboard shortcut or <abbr title="User Interface">UI</abbr> feature such as a side panel or dialog.
            </p>
            <p>
              <a>Assistive technologies</a> SHOULD enable users to quickly navigate to elements with role <code>main</code>. [=user agents=] SHOULD treat elements with role <code>main</code> as
              navigational <a>landmarks</a>. [=user agents=] MAY enable users to quickly navigate to elements with role <code>main</code>.
            </p>
            <!-- keep the following paragraphs synced with the similar paragraphs in #banner and #contentinfo -->
            <p>The author SHOULD mark no more than one <a>element</a> on a page with the <code>main</code> role.</p>
            <p class="note">
              Because <code>document</code> and <code>application</code> elements can be nested in the <abbr title="Document Object Model">DOM</abbr>, they can have multiple <code>main</code> elements
              as <abbr title="Document Object Model">DOM</abbr> descendants, assuming each of those is associated with different document nodes, either by a DOM nesting (e.g.,
              <rref>document</rref> within <rref>document</rref>) or by use of the <pref>aria-owns</pref> attribute.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>landmark</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^main^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="mark">
          <rdef>mark</rdef>
          <div class="role-description">
            <p>Content which is marked or highlighted for reference or notation purposes, due to the content's relevance in the enclosing context.</p>
            <p>Example uses for <code>mark</code> include:</p>
            <ul>
              <li>
                Highlighting text in a quotation which is of special interest but is not marked in the original source material, comparable to using a highlighter pen to mark passages of a print
                article.
              </li>
              <li>Indicating portions of the content that are relevant to the user's current activity, such as highlighting text matches found by a search feature.</li>
            </ul>
            <p>Authors SHOULD NOT use <code>mark</code> for purely decorative styling such as syntax highlighting.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^mark^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
                <td class="role-disallowed">
                  <ul>
                    <li><pref>aria-braillelabel</pref></li>
                    <li><pref>aria-label</pref></li>
                    <li><pref>aria-labelledby</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">prohibited</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="marquee">
          <rdef>marquee</rdef>
          <div class="role-description">
            <p>A type of <a>live region</a> where non-essential information changes frequently. See related <rref>log</rref>.</p>
            <p>
              Common usages of <code>marquee</code> include stock tickers and ad banners. The primary difference between a <code>marquee</code> and a <rref>log</rref> is that logs usually have a
              meaningful order or sequence of important content changes.
            </p>
            <p>Elements with the role <code>marquee</code> have an implicit <pref>aria-live</pref> value of <code>off</code>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="math">
          <rdef>math</rdef>
          <div class="role-description">
            <p>Content that represents a mathematical expression.</p>
            <p>
              Content with the role <code>math</code> is intended to be marked up in an accessible format such as <cite><a href="https://www.w3.org/TR/MathML3/">MathML</a></cite> [[MathML3]], or with
              another type of textual representation such as TeX or LaTeX, which can be converted to an accessible format by native browser implementations or a polyfill library.
            </p>
            <p>
              While it is not ideal to use an image of a mathematical expression, there exists a significant amount of legacy content where images are used to represent mathematical expressions.
              Authors SHOULD ensure that images of math are labeled by text that describes the mathematical expression as it might be spoken.
            </p>
            <div class="note">
              <p>
                Browsers that support native implementations of MathML are able to provide a more robust, accessible math experience than can be accomplished with plain text approximations of math.
                Some rendering engines have close integration with screen readers that allow spacial touch exploration of the formula and refreshable braille display output in the
                <a>Nemeth Braille</a> format. This level of integration is not supported with images of mathematical formulas, even if the author provides a plain text approximation.
              </p>
              <p>
                At the time of this writing, some mainstream browsers do not support MathML natively, and must be retrofit using a JavaScript polyfill library. When authoring math content, use native
                MathML wherever possible, and test thoroughly. Use a polyfill library or provide a fallback image with a text alternative approximation if necessary.
              </p>
            </div>
            <h4><abbr title="Mathematical Markup Language">MathML</abbr> Example with Embedded TeX Annotation</h4>
            <pre class="example highlight">
					&lt;!-- Note: Use a JavaScript polyfill library to ensure
					     this renders in user agents that do not support MathML. --&gt;
					&lt;!-- The math element has an implicit role="math". --&gt;
					&lt;math xmlns="http://www.w3.org/1998/Math/MathML"&gt;
					  &lt;mrow&gt;
					    &lt;mi&gt;x&lt;/mi&gt;
					    &lt;mo&gt;=&lt;/mo&gt;
					    &lt;mfrac&gt;
					      &lt;mrow&gt;
					        &lt;mo form="prefix"&gt;&#x2212;&lt;/mo&gt;
					        &lt;mi&gt;b&lt;/mi&gt;
					        &lt;mo&gt;&#x00B1;&lt;/mo&gt;
					        &lt;msqrt&gt;
					          &lt;msup&gt;
					            &lt;mi&gt;b&lt;/mi&gt;
					            &lt;mn&gt;2&lt;/mn&gt;
					          &lt;/msup&gt;
					          &lt;mo&gt;&#x2212;&lt;/mo&gt;
					          &lt;mn&gt;4&lt;/mn&gt;
					          &lt;mo&gt;&amp;#x2062;&lt;!-- &amp;InvisibleTimes; --&gt;&lt;/mo&gt;
					          &lt;mi&gt;a&lt;/mi&gt;
					          &lt;mo&gt;&amp;#x2062;&lt;!-- &amp;InvisibleTimes; --&gt;&lt;/mo&gt;
					          &lt;mi&gt;c&lt;/mi&gt;
					        &lt;/msqrt&gt;
					      &lt;/mrow&gt;
					      &lt;mrow&gt;
					        &lt;mn&gt;2&lt;/mn&gt;
					        &lt;mo&gt;&amp;#x2062;&lt;!-- &amp;InvisibleTimes; --&gt;&lt;/mo&gt;
					        &lt;mi&gt;a&lt;/mi&gt;
					      &lt;/mrow&gt;
					    &lt;/mfrac&gt;
					  &lt;/mrow&gt;
					  &lt;annotation encoding="TeX"&gt;
					    x=\frac{-b\pm\sqrt{b^2-4ac}}{2a}
					  &lt;/annotation&gt;
					&lt;/math&gt;
				</pre
            >
            <h4>Plain HTML or Polyfill DOM Result of the MathML Quadratic Formula</h4>
            <p>
              If a rendering engine does not support a native math format such as MathML, authors MAY use JavaScript to downgrade the content to a format the browser can display, such as this HTML
              image using a data URI and plain text alternative.
            </p>
            <pre class="example highlight">
					&lt;img role="math" src="..." alt="x=&#x27ee;&#x2212;b&#x00B1;&#8730;&#x27ee;b²&#x2212;4ac&#x27ef;&#x27ef;&#247;2a"&gt;
				</pre
            >
            <!--
				<p class="ednote">Editor's note: Might need an RFC-2119 "should" requirement here to encourage AT to speak math approximations with high punctuation verbosity. Otherwise ambiguous characters like a forward slash (/) might not be spoken even when intended to be used interchangeably with the division sign character (&#247;).</p>
				-->
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"></td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="menu">
          <rdef>menu</rdef>
          <div class="role-description">
            <p>A type of <a>widget</a> that offers a list of choices to the user.</p>
            <p>
              A menu is a container, generally rendered as a popup or overlay, for a set of menu items that can be invoked to perform an action or function. The function is almost always closely
              related or directly related to the element that the user activated to invoke the menu. Activating a menu item both performs the associated function of the menu item, and results in the
              automatic dismissal of the menu.
            </p>
            <p>
              The <code>menu</code> <a>role</a> is appropriate when a set of menu items is presented in a manner similar to a popup menu. For instance, a menu could be used to represent a context menu
              for its invoking element, or it would be used to render sub-menus for items of a <rref>menubar</rref> or another <code>menu</code> popup.
            </p>
            <p>To be <a>keyboard accessible</a>, authors SHOULD manage focus of descendants for all instances of this <a>role</a>, as described in <a href="#managingfocus">Managing Focus</a>.</p>
            <p>Elements with the role <code>menu</code> have an implicit <pref>aria-orientation</pref> value of <code>vertical</code>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>select</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><rref>list</rref></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain">
                  <ul>
                    <!-- keep in sync with #menubar -->
                    <li><rref>group</rref> with <a>accessibility child</a> <rref>menuitem</rref></li>
                    <li><rref>group</rref> with <a>accessibility child</a> <rref>menuitemradio</rref></li>
                    <li><rref>group</rref> with <a>accessibility child</a> <rref>menuitemcheckbox</rref></li>
                    <li><rref>menuitem</rref></li>
                    <li><rref>menuitemcheckbox</rref></li>
                    <li><rref>menuitemradio</rref></li>
                    <li><rref>separator</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">Default for <pref>aria-orientation</pref> is <code class="default">vertical</code>.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="menubar">
          <rdef>menubar</rdef>
          <div class="role-description">
            <p>A presentation of <rref>menu</rref> that usually remains visible and is usually presented horizontally.</p>
            <p>
              The <code>menubar</code> <a>role</a> is used to create a menu bar similar to those found in Windows, Mac, and Gnome desktop applications. A menu bar is used to create a consistent set of
              frequently used commands. Authors SHOULD ensure that <code>menubar</code> interaction is similar to the typical menu bar interaction in a desktop graphical user interface.
            </p>
            <p>To be <a>keyboard accessible</a>, authors SHOULD manage focus of descendants for all instances of this <a>role</a>, as described in <a href="#managingfocus">Managing Focus</a>.</p>
            <p>Elements with the role <code>menubar</code> have an implicit <pref>aria-orientation</pref> value of <code>horizontal</code>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>menu</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><rref>toolbar</rref></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain">
                  <ul>
                    <!-- keep in sync with #menu -->
                    <li><rref>group</rref> with <a>accessibility child</a> <rref>menuitem</rref></li>
                    <li><rref>group</rref> with <a>accessibility child</a> <rref>menuitemradio</rref></li>
                    <li><rref>group</rref> with <a>accessibility child</a> <rref>menuitemcheckbox</rref></li>
                    <li><rref>menuitem</rref></li>
                    <li><rref>menuitemcheckbox</rref></li>
                    <li><rref>menuitemradio</rref></li>
                    <li><rref>separator</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">Default for <pref>aria-orientation</pref> is <code class="default">horizontal</code>.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="menuitem">
          <rdef>menuitem</rdef>
          <div class="role-description">
            <p>An option in a set of choices contained by a <rref>menu</rref> or <rref>menubar</rref>.</p>
            <p>
              Authors MUST ensure [=elements=] with <a>role</a> <code>menuitem</code> are <a>accessibility children</a> of an element with role <rref>menu</rref>, <rref>menubar</rref>, or an element
              with role <rref>group</rref> that is an <a>accessibility child</a> of an element with role <rref>menu</rref> or <rref>menubar</rref>.
            </p>
            <p>
              Authors MAY disable a menu item with the <sref>aria-disabled</sref> attribute. If the menu item has its <pref>aria-haspopup</pref> attribute set to <code>true</code>, it indicates that
              the menu item can be used to launch a sub-level menu, and authors SHOULD display a new sub-level menu when the menu item is activated.
            </p>
            <p>
              In order to identify that they are related <a>widgets</a>, authors MUST ensure that menu items are <a>accessibility descendants</a> of an element with role <rref>menu</rref> or
              <rref>menubar</rref>. Authors MAY separate menu items into sets by use of a <rref>separator</rref> or an element with an equivalent role from the native markup language.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>command</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related">
                  <ul>
                    <li><rref>listitem</rref></li>
                    <li><rref>option</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope">
                  <ul>
                    <li><rref>menu</rref></li>
                    <li><rref>menubar</rref></li>
                    <li><rref>group</rref> with <a>accessibility parent</a> <rref>menu</rref></li>
                    <li><rref>group</rref> with <a>accessibility parent</a> <rref>menubar</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><sref>aria-disabled</sref></li>
                    <li><sref>aria-expanded</sref></li>
                    <li><pref>aria-haspopup</pref></li>
                    <li><pref>aria-posinset</pref></li>
                    <li><pref>aria-setsize</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="menuitemcheckbox">
          <rdef>menuitemcheckbox</rdef>
          <div class="role-description">
            <p>A <rref>menuitem</rref> with a checkable state whose possible <span>values</span> are <code>true</code>, <code>false</code>, or <code>mixed</code>.</p>
            <p>
              Authors MUST ensure [=elements=] with <a>role</a> <code>menuitemcheckbox</code> are <a>accessibility children</a> of an element with role <rref>menu</rref>, <rref>menubar</rref>, or an
              element with role <rref>group</rref> that is an <a>accessibility child</a> of an element with role <rref>menu</rref> or <rref>menubar</rref>.
            </p>
            <p>
              The <sref>aria-checked</sref> <a>attribute</a> of a <code>menuitemcheckbox</code> indicates whether the menu item is checked (<code>true</code>), unchecked (<code>false</code>), or
              represents a sub-level menu of other menu items that have a mixture of checked and unchecked values (<code>mixed</code>).
            </p>
            <p>
              In order to identify that they are related <a>widgets</a>, authors MUST ensure that menu item checkboxes are the <a>accessibility descendants</a> of an element with role
              <rref>menu</rref> or <rref>menubar</rref>. Authors MAY separate menu items into sets by use of a <rref>separator</rref> or an element with an equivalent role from the native markup
              language.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>menuitem</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><rref>menuitemradio</rref></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope">
                  <ul>
                    <li><rref>menu</rref></li>
                    <li><rref>menubar</rref></li>
                    <li><rref>group</rref> with <a>accessibility parent</a> <rref>menu</rref></li>
                    <li><rref>group</rref> with <a>accessibility parent</a> <rref>menubar</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties">
                  <ul>
                    <li><sref>aria-checked</sref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational">True</td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="menuitemradio">
          <rdef>menuitemradio</rdef>
          <div class="role-description">
            <p>A checkable <rref>menuitem</rref> in a set of elements with the same role, only one of which can be checked at a time.</p>
            <p>
              Authors MUST ensure [=elements=] with <a>role</a> <code>menuitemradio</code> are <a>accessibility children</a> of an element with role <rref>menu</rref>, <rref>menubar</rref>, or an
              element with role <rref>group</rref> that is an <a>accessibility child</a> of an element with role <rref>menu</rref> or <rref>menubar</rref>.
            </p>
            <p>
              Authors SHOULD enforce that only one <code>menuitemradio</code> in a group can be checked at the same time. When one item in the group is checked, the previously checked item becomes
              unchecked (its <sref>aria-checked</sref> <a>attribute</a> becomes <code>false</code>).
            </p>
            <!-- keep previous sentence synced with radiogroup, etc. -->
            <p>
              In order to identify that they are related <a>widgets</a>, authors MUST ensure that menu item radios are <a>accessibility descendants</a> of an element with role <rref>menu</rref> or
              <rref>menubar</rref>.
            </p>
            <p>
              If a <rref>menu</rref> or <rref>menubar</rref> contains more than one group of <code>menuitemradio</code> elements, or if the menu contains one group and other, unrelated menu items,
              authors SHOULD contain each set of related <code>menuitemradio</code> elements in an element using the <rref>group</rref> role. Authors MAY also delimit the group from other menu items
              with an element using the <rref>separator</rref> role, or an element with an equivalent role from the native markup language.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>menuitem</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><rref>menuitemcheckbox</rref></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope">
                  <ul>
                    <li><rref>menu</rref></li>
                    <li><rref>menubar</rref></li>
                    <li><rref>group</rref> with <a>accessibility parent</a> <rref>menu</rref></li>
                    <li><rref>group</rref> with <a>accessibility parent</a> <rref>menubar</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties">
                  <ul>
                    <li><sref>aria-checked</sref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational">True</td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="meter">
          <rdef>meter</rdef>
          <div class="role-description">
            <p>An <a>element</a> that represents a scalar measurement within a known range, or a fractional value. See related <rref>progressbar</rref>.</p>
            <p>
              Authors MAY set <pref>aria-valuemin</pref> and <pref>aria-valuemax</pref> to indicate the minimum and maximum values for the <code>meter</code>. Otherwise, their implicit values follow
              the same rules as <code>&lt;input type="[^input/type/range^]"&gt;</code> in HTML:
            </p>
            <ul>
              <li>If <code>aria-valuemin</code> is missing or not a <a href="#valuetype_number">number</a>, it defaults to 0 (zero).</li>
              <li>If <code>aria-valuemax</code> is missing or not a <a href="#valuetype_number">number</a>, it defaults to 100.</li>
            </ul>
            <p>The value of <pref>aria-valuenow</pref> MUST NOT fall below or exceed the computed values of <code>aria-valuemin</code> and <code>aria-valuemax</code>, respectively.</p>
            <p>Authors SHOULD NOT use the <code>meter</code> role to indicate progress; the <rref>progressbar</rref> role exists to address that need.</p>
            <p class="note">
              Presently, there are no <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> properties corresponding to the <code>[^meter/low^]</code>, <code>[^meter/optimum^]</code>,
              and <code>[^meter/high^]</code> attributes supported on the <code>&lt;[^meter^]&gt;</code> element in HTML. The addition of these properties will be considered for ARIA version 1.3.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>range</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^meter^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"><pref>aria-valuenow</pref></td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational">True</td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">
                  Default for <pref>aria-valuemin</pref> is <code class="default">0</code>. <br />
                  Default for <pref>aria-valuemax</pref> is <code class="default">100</code>.
                </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="navigation">
          <rdef>navigation</rdef>
          <div class="role-description">
            <p>A <rref>landmark</rref> containing a collection of navigational [=elements=] (usually links) for navigating the document or related documents.</p>
            <p>
              <a>Assistive technologies</a> SHOULD enable users to quickly navigate to elements with role <code>navigation</code>. [=user agents=] SHOULD treat elements with role
              <code>navigation</code> as navigational <a>landmarks</a>. [=user agents=] MAY enable users to quickly navigate to elements with role <code>navigation</code>.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>landmark</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^nav^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="none">
          <rdef>none</rdef>
          <div class="role-description">
            <p>
              An <a>element</a> whose implicit native role semantics will not be mapped to the <a>accessibility <abbr title="Application Programing Interfaces">API</abbr></a
              >. See synonym <rref>presentation</rref>.
            </p>
            <div class="note" id="role-none-note-none">
              Note regarding the ARIA 1.1 <rref>none</rref> role.
              <p>
                In ARIA 1.1, the working group introduced <rref>none</rref> as a synonym to the <code>presentation</code> role, due to author confusion surrounding the intended meaning of the word
                "presentation" or "presentational." Many individuals erroneously consider <code>role="presentation"</code> to be synonymous with <code>aria-hidden="true"</code>, and we believe
                <code>role="none"</code> conveys the actual meaning more unambiguously.
              </p>
            </div>
            <p>
              The 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, or can
              be used to provide for an accessible fallback in older browsers that do not support <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>.
            </p>
            <p>Example use cases:</p>
            <ul>
              <li>An element whose content is completely presentational (like a spacer image, decorative graphic, or clearing element);</li>
              <li>
                An image that is in a container with the <rref>img</rref> <a>role</a> and where the full text alternative is available and is marked up with <pref>aria-labelledby</pref> and (if
                needed) <pref>aria-describedby</pref>;
              </li>
              <li>An element used as an additional markup "hook" for <abbr title="Cascading Style Sheets">CSS</abbr>; or</li>
              <li>A layout table and/or any of its associated rows, cells, etc.</li>
            </ul>
            <p>
              For any element with a role of <rref>none</rref>/<rref>presentation</rref> and which is not focusable, the user agent MUST NOT expose the implicit native semantics of the element (the
              role and its states and properties) to accessibility <abbr title="Application Programing Interfaces">APIs</abbr>. However, the user agent MUST expose content and descendant elements that
              do not have an explicit or inherited role of <rref>none</rref>/<rref>presentation</rref>. Thus, the <rref>none</rref>/<rref>presentation</rref> role causes a given element to be treated
              as having no role or to be removed from the <a>accessibility tree</a>, but does not cause the content contained within the element to be removed from the accessibility tree.
            </p>
            <p>For example, the following two markup snippets will be exposed similarly to an accessibility <abbr title="Application Programing Interface">API</abbr>.</p>
            <pre
              class="example highlight"
            ><span class="comment">&lt;!-- 1. role="none" negates the implicit 'heading' role semantics but does not affect the contents, including the nested hyperlink. --&gt;</span>
&lt;h1 role="none"&gt; Sample Content &lt;a href="...">let's go!&lt;/a> &lt;/h1&gt;

<span class="comment">&lt;!-- 2. A span has an implicit 'generic' role and no other attributes important to accessibility, so only its content is exposed, including the hyperlink. --&gt;</span>
&lt;span&gt; Sample Content &lt;a href="...">let's go!&lt;/a> &lt;/span&gt;
</pre>
            <p>
              In HTML, the <code>&lt;img&gt;</code> <a>element</a> is treated as a single entity regardless of the type of image file. Consequently, using <code>role="none"</code> or
              <code>role="presentation"</code> on an HTML <code>img</code> is equivalent to using <code>aria-hidden="true"</code>. In order to make the image contents accessible, authors can embed the
              object using an <code>&lt;object&gt;</code> or <code>&lt;iframe&gt;</code> <a>element</a>, or use inline <abbr title="Scalable Vector Graphics">SVG</abbr> code, and follow the
              accessibility guidelines for the image content.
            </p>
            <p>
              Authors SHOULD NOT provide a meaningful text alternative (for example, use <code>alt=""</code> in HTML) when the <code>none</code>/<code>presentation</code> role is applied to an image.
            </p>
            <p>
              In the following code sample, the containing <rref>img</rref> and is appropriately labeled by the caption paragraph. In this example the <code>img</code> element can be marked as
              <rref>none</rref>/<rref>presentation</rref> because the role and the text alternatives are provided by the containing element.
            </p>
            <pre class="example highlight">
&lt;div role="img" aria-labelledby="caption"&gt;
  &lt;img src="example.png" role="none" alt=""&gt;
  &lt;p id="caption"&gt;A visible text caption labeling the image.&lt;/p&gt;
&lt;/div&gt;</pre
            >
            <p>
              In the following code sample, because the anchor (HTML <code>a</code> element) is acting as the treeitem, the list item (HTML <code>li</code> element) is assigned an explicit
              <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role of <rref>none</rref>/<rref>presentation</rref> to override the user agent's implicit native semantics for list
              items.
            </p>
            <pre class="example highlight">
&lt;ul role="tree"&gt;
  &lt;li role="none"&gt;
	&lt;a role="treeitem" aria-expanded="true"&gt;An expanded tree node&lt;/a&gt;
  &lt;/li&gt;
  …
&lt;/ul&gt;</pre
            >
            <h5>Presentational Role Inheritance</h5>
            <p>
              The <rref>none</rref>/<rref>presentation</rref> role is used on an element that has implicit native semantics, meaning that there is a default accessibility
              <abbr title="Application Programing Interface">API</abbr> role for the element. Some elements are only complete when additional descendant elements are provided. For example, in HTML,
              table elements (matching the <rref>table</rref> role) require <code>tr</code> descendants (which have an implicit <rref>row</rref> <a>role</a>), which in turn require <code>th</code> or
              <code>td</code> children (the <rref>columnheader</rref> or <rref>rowheader</rref> and <rref>cell</rref> roles, respectively). Similarly, lists require list item children. The descendant
              elements that complete the semantics of an element are described in <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> as
              <a href="#mustContain">Allowed Accessibility Child Roles</a>.
            </p>
            <p>
              When an explicit or inherited role of <rref>none</rref>/<rref>presentation</rref> is applied to an element with the implicit semantic of a
              <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role that has <a href="#mustContain">Allowed Accessibility Child Roles</a>, in addition to the element with the
              explicit role of <rref>none</rref>/<rref>presentation</rref>, the user agent MUST apply an inherited role of <rref>none</rref> to any <a>accessibility descendants</a> that do not have an
              explicit role defined. Also, when an explicit or inherited role of <rref>none</rref>/<rref>presentation</rref> is applied to a host language element which has specifically allowed
              children as defined by the host language specification, in addition to the element with the explicit role of <rref>none</rref>/<rref>presentation</rref>, the user agent MUST apply an
              inherited role of <rref>none</rref> to any specifically allowed children that do not have an explicit role defined.
            </p>
            <p>
              For any element with an explicit or inherited role of <rref>none</rref>/<rref>presentation</rref> and which is not focusable, user agents MUST ignore role-specific
              <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> states and properties for that element. For example, in HTML, a <code>ul</code> or <code>ol</code> element with a role
              of <rref>none</rref>/<rref>presentation</rref> will have the implicit native semantics of its <code>li</code> elements removed because the <rref>list</rref> role to which the
              <code>ul</code> or <code>ol</code> corresponds has an <a href="#mustContain">Allowed Accessibility Child Role</a> of <rref>listitem</rref>. Likewise, the implicit native semantics of an
              HTML <code>table</code> element's <code>thead</code>/<code>tbody</code>/<code>tfoot</code>/<code>tr</code>/<code>th</code>/<code>td</code> descendants will also be removed, because the
              HTML specification indicates that these are required structural descendants of the <code>table</code> element.
            </p>
            <p class="note">
              Only the implicit native semantics of elements that correspond to <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>
              <a href="#mustContain">Allowed Accessibility Child Roles</a> are removed. All other content remains intact, including nested tables or lists, unless those elements also have an explicit
              role of <rref>none</rref>/<rref>presentation</rref> specified.
            </p>
            <p>
              For example, according to an accessibility <abbr title="Application Programing Interface">API</abbr>, the following markup elements might have identical or very similar role semantics
              (generic or none role) and identical content.
            </p>
            <pre class="example highlight"><span class="comment">&lt;!-- 1. [role="none"] negates the implicit 'list' and 'listitem' role semantics but does not affect the contents. --&gt;</span>
&lt;ul role="none"&gt;
  &lt;li&gt; Sample Content &lt;/li&gt;
  &lt;li&gt; More Sample Content &lt;/li&gt;
&lt;/ul&gt;

<span class="comment">&lt;!-- 2. There is no implicit role for "foo", so only the contents are exposed. --&gt;</span>
&lt;foo&gt;
  &lt;foo&gt; Sample Content &lt;/foo&gt;
  &lt;foo&gt; More Sample Content &lt;/foo&gt;
&lt;/foo&gt;</pre>
            <p class="note">
              There are other <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> roles with specific allowed children for which this situation is applicable (e.g., feeds and
              listboxes), but tables and lists are the most common real-world cases in which the none/presentation inheritance is likely to apply.
            </p>
            <p>
              For any element with an explicit or inherited role of <rref>none</rref>/<rref>presentation</rref>, user agents MUST apply an inherited role of <rref>none</rref> to all
              host-language-specific labeling elements for the presentational element. For example, a <code>table</code> element with a role of <rref>none</rref>/<rref>presentation</rref> will have
              the implicit native semantics of its <code>caption</code> element removed, because the caption is merely a label for the presentational table.
            </p>
            <p class="ednote">
              Information about <a href="#conflict_resolution_presentation_none">resolving conflicts in the none/presentation role</a> has been moved to
              <a href="#document-handling_author-errors">Handling Author Errors</a>
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>structure</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
                <td class="role-disallowed">
                  <ul>
                    <li><pref>aria-braillelabel</pref></li>
                    <li><pref>aria-label</pref></li>
                    <li><pref>aria-labelledby</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">prohibited</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="note">
          <rdef>note</rdef>
          <div class="role-description">
            <p>A <rref>section</rref> whose content represents additional information or parenthetical context to the primary content it supplements.</p>
            <p>
              A <code>note</code> is content provided by the author of the page or document, it is not to be used for providing reactions or suggestions. For these purposes, please review
              <rref>comment</rref> and <rref>suggestion</rref>.
            </p>
            <p>
              When used within the normal flow of a page's content, a <code>note</code> has an implicit association with the content that it supplements. The following example demonstrates using a
              <code>note</code> to call out additional information in the natural reading order of a page:
            </p>
            <pre class="example highlight">
					&lt;p>... the following results outline support for the tested features.&lt;/p>
					&lt;div role="note">
					  &lt;p>Please keep in mind that at the time of publishing this page all results were accurate.&lt;/p>
					  &lt;p>If you find any variations in results, please let us know!&lt;/p>
					&lt;/div>
					&lt;p>...&lt;/p>
				</pre
            >
            <p>
              In cases where an element with role <rref>note</rref> has been determined to need a programmatic association with the content it supplements, authors can use one of the following
              mechanisms to associate the elements:
            </p>
            <ul>
              <li>If the <code>note</code> contains structured or interactive content (for example, a link, button, list, table, etc.) use <pref>aria-details</pref>.</li>
              <li>If the <code>note</code> is brief and consists of static text, use <pref>aria-describedby</pref>.</li>
            </ul>
            <pre class="example highlight">
				  &lt;!-- using aria-details to reference a note containing a link -->
				  ...
					&lt;button aria-details="info-note">Get Started&lt;/button>
					...
					&lt;div role="note" id="info-note">
					  &lt;p>Need more information before you get started?&lt;/p>
					  &lt;p>Visit our &lt;a href="...">product description page&lt;/a> to get all the information you need.&lt;/p>
					&lt;/div>
				</pre
            >
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="option">
          <rdef>option</rdef>
          <div class="role-description">
            <p>An item in a <rref>listbox</rref>.</p>
            <p>
              Authors MUST ensure [=elements=] with <a>role</a> <code>option</code> are <a>accessibility children</a> of an element with <a>role</a> <rref>listbox</rref> or of an element with
              <a>role</a> <rref>group</rref> that is the <a>accessibility child</a> of an element with <a>role</a> <code>listbox</code>. Options not associated with a <rref>listbox</rref> might not be
              correctly mapped to an <a>accessibility <abbr title="Application Programing Interfaces">API</abbr></a
              >.
            </p>
            <p>
              In certain conditions, a user agent MAY provide an implicit value for <sref>aria-selected</sref> for each <rref>option</rref> in a <rref>listbox</rref>, and if it does, the user agent
              MUST ensure the following conditions are met before providing an implicit value:
            </p>
            <ul>
              <li>The value of <pref>aria-multiselectable</pref> on the <rref>listbox</rref> is <code>false</code> or <code>undefined</code>.</li>
              <li>None of the <rref>option</rref> elements in the <rref>listbox</rref> have an explicitly declared value for <sref>aria-selected</sref> or <sref>aria-checked</sref>.</li>
            </ul>
            <p>
              If a user agent provides an implicit <sref>aria-selected</sref> value for an <rref>option</rref>, the value SHOULD be <code>true</code> if the <rref>option</rref> has DOM focus or the
              <rref>listbox</rref> has DOM focus and the <rref>option</rref> is referenced by <pref>aria-activedescendant</pref>. Otherwise, if a user agent provides an implicit
              <sref>aria-selected</sref> value for an <rref>option</rref>, the value SHOULD be <code>false</code>.
            </p>
            <p>Authors SHOULD indicate selection for <rref>option</rref> elements using one of the following:</p>
            <ul>
              <li>
                An <sref>aria-selected</sref> value of <code>true</code> on the selected option within a single-select <rref>listbox</rref>, and optionally <sref>aria-selected</sref> values of
                <code>false</code> on unselected options.
              </li>
              <li>
                Either <sref>aria-selected</sref> or <sref>aria-checked</sref> on all options within a multi-select <rref>listbox</rref>, with a value of <code>true</code> on selected options, and a
                value of <code>false</code> on unselected options.
              </li>
            </ul>
            <p>
              Authors SHOULD NOT specify both <sref>aria-selected</sref> and <sref>aria-checked</sref> on <rref>option</rref> elements contained by the same <rref>listbox</rref> except in the
              extremely rare circumstances where all the following conditions are met:
            </p>
            <ul>
              <li>The meaning and purpose of <sref>aria-selected</sref> is different from the meaning and purpose of <sref>aria-checked</sref> in the user interface.</li>
              <li>The user interface makes the meaning and purpose of each state apparent.</li>
              <li>The user interface provides a separate method for controlling each state.</li>
            </ul>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>input</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"><code>&lt;[^option^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related">
                  <rref>listitem</rref>
                </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope">
                  <ul>
                    <li><rref>listbox</rref></li>
                    <li><rref>group</rref> with parent <rref>listbox</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"></td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><sref>aria-checked</sref></li>
                    <li><pref>aria-posinset</pref></li>
                    <li><sref>aria-selected</sref></li>
                    <li><pref>aria-setsize</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational">True</td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values"></td>
              </tr>
            </tbody>
          </table>
        </div>
        <!-- FIXME: This is commented out because the ARIA Working Group agreed to move the password role to ARIA 2.0,
     but we've not branched for 1.1 yet. Once we have branched, this entire section should be deleted from
     the 1.1 branch and uncommented for the master branch (pending discussion and consensus).
		<div class="role" id="password">
			<rdef>password</rdef>
			<div class="role-description">
				<p>An <rref>input</rref> for entering a password.</p>
				<div class="ednote">
					<p>The Working Group is still considering implications of the <code>password</code> role:</p>
					<ul>
						<li>It might create security or privacy risks that custom password fields without the role would not;</li>
						<li>The use of such fields might not be widespread enough to justify the risks;</li>
						<li>Mitigating risks might require specific assisitve technology support that is not normally specified in ARIA.</li>
					</ul>
					<p>The role has been included in this Working Draft to solicit wide review on these questions. The ARIA Working Group particularly seeks input from <strong>security</strong> and <strong>privacy</strong> experts, <strong>assistive technology</strong> developers, and <strong>authors</strong> who potentially would use the role.</p>
					<p>If input suggests excessive risks or insufficient need, the role might be removed from the next publication of this specification.</p>
				</div>
				<p class="warning">The <code>password</code> <a>role</a> does not convey or apply any of the security or privacy considerations found in native password fields. Authors are responsible for making sure that custom password fields have robust security and privacy protection, as befits their use.</p>
				<p>The <code>password</code> <a>role</a> makes it possible for <a>assistive technologies</a> to customize their behavior in order to not inadvertently expose private information. For instance, a screen reader which normally echoes key presses might instead remain silent or echo each displayed character as it is inserted. In order to facilitate the latter behavior, authors SHOULD set the <code>password</code> element's text to characters which obscure the real value, when that value is obscured on screen. Authors SHOULD also update that text each time a character is inserted or deleted by the user.</p>
				<p>In order to ensure that passwords will not be overheard during input, assistive technologies SHOULD NOT echo key presses of printable characters when an element with role <code>password</code> has focus, unless the user has explicitly enabled this option. If the user has enabled key echo, assistive technologies SHOULD present each rendered character as it is inserted rather than speaking a predetermined character, such as &quot;star.&quot; Presenting the rendered characters ensures that all users receive the same information, including notification when the value is being entered into an unobscured <code>password</code> field.</p>
				<p>Authors SHOULD limit the use of the <code>password</code> role to single-line [=elements=] which are editable. Authors MAY use the <code>password</code> role on elements which are not currently editable due to application-specific conditions. However, in that instance, authors MUST indicate that the element is read only by setting <pref>aria-readonly</pref> to <code>true</code> or using the appropriate native host language attribute. User agents MUST ignore the <code>password</code> role when it is applied to elements which are neither editable nor explicitly marked as read only. Host languages SHOULD document that the <code>password</code> role can only be used on elements that are editable and not permanently read only.</p>
			</div>
			<table class="def">
				<caption>Characteristics:</caption>
				<thead>
					<tr>
						<th scope="col">Characteristic</th>
						<th scope="col">Value</th>
					</tr>
				</thead>
				<tbody>
					<tr>
						<th class="role-abstract-head" scope="row">Is Abstract:</th>
						<td class="role-abstract"> </td>
					</tr>
					<tr>
						<th class="role-parent-head" scope="row">Superclass Role:</th>
						<td class="role-parent"><rref>input</rref></td>
					</tr>
					<tr>
						<th class="role-children-head" scope="row">Subclass Roles:</th>
						<td class="role-children">Placeholder</td>
					</tr>
					<tr>
						<th class="role-base-head" scope="row">Base Concept:</th>
						<td class="role-base"><a href="https://www.w3.org/tr/html5/forms.html#password-state-(type=password)">HTML <code>input[type="password"]</code></a></td>
					</tr>
					<tr>
						<th class="role-related-head" scope="row">Related Concepts:</th>
						<td class="role-related"> </td>
					</tr>
					<tr>
						<th class="role-required-properties-head">Required States and Properties:</th>
						<td class="role-required-properties"> </td>
					</tr>
					<tr>
						<th class="role-properties-head" scope="row">Supported States and Properties:</th>
						<td class="role-properties">
							<ul>
								<li><pref>aria-placeholder</pref></li>
								<li><pref>aria-readonly</pref></li>
								<li><pref>aria-required</pref></li>
							</ul>
						</td>
					</tr>
					<tr>
						<th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
						<td class="role-inherited">Placeholder</td>
					</tr>
					<tr>
						<th class="role-namefrom-head" scope="row">Name From:</th>
						<td class="role-namefrom">author</td>
					</tr>
					<tr>
						<th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
						<td class="role-namerequired">True</td>
					</tr>
					<tr>
						<th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
						<td class="role-namerequired-inherited"> </td>
					</tr>
					<tr>
						<th class="role-childpresentational-head" scope="row">Children Presentational:</th>
						<td class="role-childpresentational"> </td>
					</tr>
					<tr>
						<th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
						<td class="role-presentational-inherited"> </td>
					</tr>
				</tbody>
			</table>
		</div>
		-->
        <div class="role" id="paragraph">
          <rdef>paragraph</rdef>
          <div class="role-description">
            <p>A paragraph of content.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^p^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
                <td class="role-disallowed">
                  <ul>
                    <li><pref>aria-braillelabel</pref></li>
                    <li><pref>aria-label</pref></li>
                    <li><pref>aria-labelledby</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">prohibited</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="presentation">
          <rdef>presentation</rdef>
          <div class="role-description">
            <p>
              An <a>element</a> whose implicit native role semantics will not be mapped to the <a>accessibility <abbr title="Application Programing Interfaces">API</abbr></a
              >. See synonym <rref>none</rref>.
            </p>
            <div class="note" id="role-presentation-note-none">
              Note regarding the ARIA 1.1 <rref>none</rref> role.
              <p>
                In ARIA 1.1, the working group introduced <rref>none</rref> as the preferred synonym to the <rref>presentation</rref> role, due to author confusion surrounding the intended meaning of
                the word "presentation" or "presentational." Many individuals erroneously consider <code>role="presentation"</code> to be synonymous with <code>aria-hidden="true"</code>, and the ARIA
                Working Group believes <code>role="none"</code> conveys the actual meaning more unambiguously.
              </p>
            </div>
          </div>
        </div>
        <div class="role" id="progressbar">
          <rdef>progressbar</rdef>
          <div class="role-description">
            <p>An <a>element</a> that displays the progress status for tasks that take a long time.</p>
            <p>A progressbar indicates that the user's request has been received and the application is making progress toward completing the requested action.</p>
            <p>
              Authors MAY set <pref>aria-valuemin</pref> and <pref>aria-valuemax</pref> to indicate the minimum and maximum progress indicator values. Otherwise, their implicit values follow the same
              rules as <code>&lt;input type="[^input/type/range^]"&gt;</code> in HTML:
            </p>
            <ul>
              <li>If <code>aria-valuemin</code> is missing or not a <a href="#valuetype_number">number</a>, it defaults to 0 (zero).</li>
              <li>If <code>aria-valuemax</code> is missing or not a <a href="#valuetype_number">number</a>, it defaults to 100.</li>
            </ul>
            <p>
              The author SHOULD supply a <span>value</span> for <pref>aria-valuenow</pref> unless the value is indeterminate, in which case the author SHOULD omit the
              <pref>aria-valuenow</pref> attribute. Authors SHOULD update this value when the visual progress indicator is updated. If the <code>progressbar</code> is describing the loading progress
              of a particular region of a page, authors SHOULD both use <pref>aria-describedby</pref> to reference the progressbar status, and set the <sref>aria-busy</sref> attribute to
              <code>true</code> on the region until it is finished loading. It is not possible for the user to alter the value of a <code>progressbar</code> because it is always read-only.
            </p>
            <p class="note">
              Assistive technologies generally will render the value of <pref>aria-valuenow</pref> as a percent of a range between the value of <pref>aria-valuemin</pref> and
              <pref>aria-valuemax</pref>, unless <pref>aria-valuetext</pref> is specified.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>range</rref></li>
                    <li><rref>widget</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><rref>status</rref></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational">True</td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">
                  Default for <pref>aria-valuemin</pref> is <code class="default">0</code>. <br />
                  Default for <pref>aria-valuemax</pref> is <code class="default">100</code>. <br />
                </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="radio">
          <rdef>radio</rdef>
          <div class="role-description">
            <p>A checkable input in a group of elements with the same role, only one of which can be checked at a time.</p>
            <p>
              Authors SHOULD ensure that [=elements=] with role <code>radio</code> are explicitly grouped in order to indicate which ones affect the same value. This is achieved by enclosing the radio
              elements in an element with role <rref>radiogroup</rref>. If it is not possible to make the radio buttons <abbr title="Document Object Model">DOM</abbr> children of the
              <rref>radiogroup</rref>, authors SHOULD use the <pref>aria-owns</pref> <a>attribute</a> on the <rref>radiogroup</rref> element to indicate the <a>relationship</a> to its children.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>input</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;input type="[^input/type/radio^]"&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties">
                  <ul>
                    <li><sref>aria-checked</sref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-posinset</pref></li>
                    <li><pref>aria-setsize</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational">True</td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="radiogroup">
          <rdef>radiogroup</rdef>
          <div class="role-description">
            <p>A group of <rref>radio</rref> buttons.</p>
            <p>
              A <code>radiogroup</code> is a type of <rref>select</rref> list that can only have a single entry checked at any one time. Authors SHOULD enforce that only one radio button in a group
              can be checked at the same time. When one item in the group is checked, the previously checked item becomes unchecked (its <sref>aria-checked</sref> <a>attribute</a> becomes
              <code>false</code>).
            </p>
            <!-- keep previous sentence synced with menuitemradio, etc. -->
            <p>
              Authors SHOULD provide an accessible name for a <code>radiogroup</code>, which can be done with the <pref>aria-label</pref> or <pref>aria-labelledby</pref> attribute. Authors SHOULD
              reference a visible label with <pref>aria-labelledby</pref> if a visible label is present for the <code>radiogroup</code>.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>select</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td><rref>list</rref></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-errormessage</pref></li>
                    <li><sref>aria-invalid</sref></li>
                    <li><pref>aria-readonly</pref></li>
                    <li><pref>aria-required</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="range">
          <rdef>range</rdef>
          <div class="role-description">
            <p>An element representing a range of values.</p>
            <p><code>range</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>range</code> role in content.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract">True</td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>structure</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-valuemax</pref></li>
                    <li><pref>aria-valuemin</pref></li>
                    <li><pref>aria-valuenow</pref></li>
                    <li><pref>aria-valuetext</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom"></td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="region">
          <rdef>region</rdef>
          <div class="role-description">
            <p>
              A <rref>landmark</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 SHOULD limit use of the region role to sections containing content with a purpose that is not accurately described by one of the other
              <a href="#landmark_roles">landmark roles</a>, such as <rref>main</rref>, <rref>complementary</rref>, or <rref>navigation</rref>.
            </p>
            <p>
              Authors MUST give each element with role region a brief label that describes the purpose of the content in the region. Authors SHOULD reference a visible label with
              <pref>aria-labelledby</pref> if a visible label is present. Authors SHOULD include the label inside of a heading whenever possible. The heading MAY be an instance of the standard host
              language heading element or an instance of an element with role <rref>heading</rref>.
            </p>
            <p>
              <a>Assistive technologies</a> SHOULD enable users to quickly navigate to elements with role <code>region</code>. [=User agents=] SHOULD treat elements with role <code>region</code> and
              an accessible name as navigational <a>landmarks</a>. [=User agents=] MAY enable users to quickly navigate to elements with role <code>region</code>.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>landmark</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^section^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="roletype">
          <rdef>roletype</rdef>
          <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>
            <p><code>roletype</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>roletype</code> role in content.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract">True</td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"> </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"></td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"><span class="placeholder">Placeholder for global states and properties</span></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom"></td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="row">
          <rdef>row</rdef>
          <div class="role-description">
            <p>A row of cells in a tabular container.</p>
            <p>Rows contain <rref>cell</rref> or <rref>gridcell</rref> [=elements=], and thus serve to organize a <rref>table</rref>, <rref>grid</rref>, or <rref>treegrid</rref>.</p>
            <p>
              While the row role can be used in a <rref>table</rref>, <rref>grid</rref>, or <rref>treegrid</rref>, the semantics of <sref>aria-expanded</sref>, <pref>aria-posinset</pref>,
              <pref>aria-setsize</pref>, and <pref>aria-level</pref> are only applicable to the hierarchical structure of an interactive tree grid. Therefore, authors MUST NOT apply
              <sref>aria-expanded</sref>, <pref>aria-posinset</pref>, <pref>aria-setsize</pref>, and <pref>aria-level</pref> to a <rref>row</rref> that descends from a <rref>table</rref> or
              <rref>grid</rref>, and user agents SHOULD NOT expose any of these four properties to assistive technologies unless the <rref>row</rref> descends from a <rref>treegrid</rref>.
            </p>
            <p>
              Authors MUST ensure [=elements=] with <a>role</a> <code>row</code> are <a>accessibility children</a> of an element with the role <rref>table</rref>, <rref>grid</rref>,
              <rref>rowgroup</rref>, or <rref>treegrid</rref>.
            </p>
            <p class="note" title="Usage of aria-disabled">
              While <sref>aria-disabled</sref> is currently supported on <rref>row</rref>, in a future version the working group plans to prohibit its on elements with role <rref>row</rref> except
              when the element is in the context of a <rref>grid</rref> or <rref>treegrid</rref>.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>group</rref></li>
                    <li><rref>widget</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"><code>&lt;[^tr^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope">
                  <ul>
                    <li><rref>grid</rref></li>
                    <li><rref>table</rref></li>
                    <li><rref>treegrid</rref></li>
                    <li><rref>rowgroup</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain">
                  <ul>
                    <li><rref>cell</rref></li>
                    <li><rref>columnheader</rref></li>
                    <li><rref>gridcell</rref></li>
                    <li><rref>rowheader</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-colindex</pref></li>
                    <li><sref>aria-expanded</sref></li>
                    <li><pref>aria-level</pref></li>
                    <li><pref>aria-posinset</pref></li>
                    <li><pref>aria-rowindex</pref></li>
                    <li><pref>aria-rowindextext</pref></li>
                    <li><pref>aria-setsize</pref></li>
                    <li><sref>aria-selected</sref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="rowgroup">
          <rdef>rowgroup</rdef>
          <div class="role-description">
            <p>A structure containing one or more row elements in a tabular container.</p>
            <p>
              The <code>rowgroup</code> role establishes a <a>relationship</a> with its <a>accessibility children</a> of role <rref>row</rref>. It is a structural equivalent to the <code>thead</code>,
              <code>tfoot</code>, and <code>tbody</code> elements in an HTML <code>table</code> <a>element</a>.
            </p>
            <p>
              Authors MUST ensure [=elements=] with <a>role</a> <code>rowgroup</code> are <a>accessibility children</a> of an element with the role <rref>grid</rref>, <rref>table</rref>, or
              <rref>treegrid</rref>.
            </p>
            <p class="note">
              The <code>rowgroup</code> role exists, in part, to support role symmetry in HTML, and allows for the propagation of presentation inheritance on HTML <code>table</code> elements with an
              explicit <code>presentation</code> role applied.
            </p>
            <p class="note">
              This role does not differentiate between types of row groups (e.g., <code>thead</code> vs. <code>tbody</code>), but an issue has been raised for
              <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> 2.0.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>structure</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"><code>&lt;[^tbody^]&gt;</code>, <code>&lt;[^tfoot^]&gt;</code> and <code>&lt;[^thead^]&gt;</code>in HTML</td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope">
                  <ul>
                    <li><rref>grid</rref></li>
                    <li><rref>table</rref></li>
                    <li><rref>treegrid</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"><rref>row</rref></td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="rowheader">
          <rdef>rowheader</rdef>
          <div class="role-description">
            <p>A cell containing header information for a row.</p>
            <p>
              The <rref>rowheader</rref> role can be used to identify a cell as a header for a row in a <rref>table</rref>, <rref>grid</rref>, or <rref>treegrid</rref>. The rowheader establishes a
              <a>relationship</a> between it and all cells in the corresponding row. It is a structural equivalent to setting <code>scope="row"</code> on an HTML <code>th</code> <a>element</a>.
            </p>
            <p>Authors MUST ensure [=elements=] with <a>role</a> <code>rowheader</code> are <a>accessibility children</a> of an element with the role <rref>row</rref>.</p>
            <p>
              Applying the <sref>aria-selected</sref> state on a rowheader MUST NOT cause the user agent to automatically propagate the <sref>aria-selected</sref> state to all the cells in the
              corresponding row. An author MAY choose to propagate selection in this manner depending on the specific application.
            </p>
            <p>
              While the <code>rowheader</code> role can be used in both interactive grids and non-interactive tables, the use of <sref>aria-expanded</sref>, <pref>aria-readonly</pref>, and
              <pref>aria-required</pref> is only applicable to interactive elements. Therefore, authors SHOULD NOT use <sref>aria-expanded</sref>, <pref>aria-readonly</pref>, or
              <pref>aria-required</pref> in a <code>rowheader</code> that descends from a <rref>table</rref>, and user agents SHOULD NOT expose these properties to <a>assistive technologies</a> unless
              the <code>rowheader</code> descends from a <rref>grid</rref> or <rref>treegrid</rref>.
            </p>
            <p class="note" title="Usage of aria-disabled">
              While <sref>aria-disabled</sref> is currently supported on <rref>rowheader</rref>, in a future version the working group plans to prohibit its use on elements with role
              <rref>rowheader</rref> except when the element is in the context of a <rref>grid</rref> or <rref>treegrid</rref>.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>cell</rref></li>
                    <li><rref>gridcell</rref></li>
                    <li><rref>sectionhead</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"><code>&lt;th scope="[^th/scope/row^]"&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"><rref>row</rref></td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><sref>aria-expanded</sref></li>
                    <li><pref>aria-sort</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="scrollbar">
          <rdef>scrollbar</rdef>
          <div class="role-description">
            <p>A graphical object that controls the scrolling of content within a viewing area, regardless of whether the content is fully displayed within the viewing area.</p>
            <p>
              A scrollbar represents the current value and range of possible values via the size of the scrollbar and position of the thumb with respect to the visible range of the orientation
              (horizontal or vertical) it controls. Its orientation represents the orientation of the scrollbar and the scrolling effect on the viewing area controlled by the scrollbar. It is
              typically possible to add to or subtract from the current value by using directional keys such as arrow keys.
            </p>
            <p>Authors MUST set the <pref>aria-controls</pref> attribute on the scrollbar element to reference the scrollable area it controls.</p>
            <p>
              Authors MAY set <pref>aria-valuemin</pref> and <pref>aria-valuemax</pref> to indicate the minimum and maximum thumb position. Otherwise, their implicit values follow the same rules as
              <code>&lt;input type="[^input/type/range^]"&gt;</code> in HTML:
            </p>
            <ul>
              <li>If <code>aria-valuemin</code> is missing or not a <a href="#valuetype_number">number</a>, it defaults to 0 (zero).</li>
              <li>If <code>aria-valuemax</code> is missing or not a <a href="#valuetype_number">number</a>, it defaults to 100.</li>
            </ul>
            <p>
              Authors MUST set the <pref>aria-valuenow</pref> attribute to indicate the current thumb position. If aria-valuenow is missing or has an unexpected value, <a>user agents</a> MAY implement the
              repair techniques specified in the <a href="#authorErrorDefaultValuesTable">section describing handling author errors in states and properties</a>, which are equivalent to the repair
              techniques for <code>&lt;input type="[^input/type/range^]"&gt;</code> in HTML.
            </p>
            <p>Elements with the role <code>scrollbar</code> have an implicit <pref>aria-orientation</pref> value of <code>vertical</code>.</p>
            <p class="note">
              Assistive technologies generally will render the value of <pref>aria-valuenow</pref> as a percent of a range between the value of <pref>aria-valuemin</pref> and
              <pref>aria-valuemax</pref>, unless <pref>aria-valuetext</pref> is specified. It is best to set the values for <pref>aria-valuemin</pref>, <pref>aria-valuemax</pref>, and
              <pref>aria-valuenow</pref> in a manner that is appropriate for this calculation.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>range</rref></li>
                    <li><rref>widget</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties">
                  <ul>
                    <li><pref>aria-controls</pref></li>
                    <li><pref>aria-valuenow</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><sref>aria-disabled</sref></li>
                    <li><pref>aria-orientation</pref></li>
                    <li><pref>aria-valuemax</pref></li>
                    <li><pref>aria-valuemin</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational">True</td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">
                  Default for <pref>aria-orientation</pref> is <code class="default">vertical</code>. <br />
                  Default for <pref>aria-valuemin</pref> is <code class="default">0</code>. <br />
                  Default for <pref>aria-valuemax</pref> is <code class="default">100</code>. <br />
                </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="search">
          <rdef>search</rdef>
          <div class="role-description">
            <p>
              A <rref>landmark</rref> region that contains a collection of items and objects that, as a whole, combine to create a search facility. See related <rref>form</rref> and
              <rref>searchbox</rref>.
            </p>
            <p>A search region can be a mix of host language form controls, scripted controls, and hyperlinks.</p>
            <p>
              <a>Assistive technologies</a> SHOULD enable users to quickly navigate to elements with role <code>search</code>. [=user agents=] SHOULD treat elements with role <code>search</code> as
              navigational <a>landmarks</a>. [=user agents=] MAY enable users to quickly navigate to elements with role <code>search</code>.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>landmark</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"><abbr title="Hypertext Markup Language">HTML</abbr> <code>[^search^]</code></td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="searchbox">
          <rdef>searchbox</rdef>
          <div class="role-description">
            <p>A type of textbox intended for specifying search criteria. See related <rref>textbox</rref> and <rref>search</rref>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>textbox</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"><code>&lt;input type="[^input/type/search^]"&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="section">
          <rdef>section</rdef>
          <div class="role-description">
            <p>A renderable structural containment unit on a page.</p>
            <p><code>section</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>section</code> role in content.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract">True</td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>structure</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"></td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom"></td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="sectionfooter">
          <rdef>sectionfooter</rdef>
          <div class="role-description">
            <p>
              A set of user interface objects and information representing information about its closest ancestral content group. For instance, a <code>sectionfooter</code> can include information
              about who wrote the specific section of content, such as an <rref>article</rref>. It can contain links to related documents, copyright information or other indices and colophon specific
              to the current section of the page.
            </p>
            <p>
              A <code>sectionfooter</code> does not represent information about the parent document, or globally repeating content found across multiple pages related to the website. For such content,
              the <rref>contentinfo</rref> role would be more appropriate.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"><code>&lt;[^footer^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="sectionhead">
          <rdef>sectionhead</rdef>
          <div class="role-description">
            <p>A structure that labels or summarizes the topic of its related section.</p>
            <p><code>sectionhead</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>sectionhead</code> role in content.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract">True</td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>structure</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom"></td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="sectionheader">
          <rdef>sectionheader</rdef>
          <div class="role-description">
            <p>
              A set of user interface objects and information that represents a collection of introductory items for the element's closest ancestral content group. For instance, a
              <code>sectionheader</code> can include the heading, introductory statement and related meta data for a section of content, for instance a <rref>region</rref> or <rref>article</rref>,
              within a web page.
            </p>
            <p>
              A <code>sectionheader</code> does not represent site-oriented or globally repeating content found across multiple pages of a website. For such content, the <rref>banner</rref> role would
              be more appropriate.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"><code>&lt;[^header^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="select">
          <rdef>select</rdef>
          <div class="role-description">
            <p>A form widget that allows the user to make selections from a set of choices.</p>
            <p><code>select</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>select</code> role in content.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract">True</td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>composite</rref></li>
                    <li><rref>group</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"><pref>aria-orientation</pref></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom"></td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="separator">
          <rdef>separator</rdef>
          <div class="role-description">
            <p>A divider that separates and distinguishes sections of content or groups of menuitems.</p>
            <p>
              There are two types of separators: a static <rref>structure</rref> that provides only a visible boundary and a focusable, interactive <rref>widget</rref> that is also moveable. If a
              <code>separator</code> is not focusable, it is revealed to <a>assistive technologies</a> as a static structural element. For example, a static <code>separator</code> can be used to help
              visually divide two groups of menu items in a menu or to provide a horizontal rule between two sections of a page.
            </p>
            <p>
              Authors MAY make a <code>separator</code> focusable to create a <rref>widget</rref> that both provides a visible boundary between two sections of content and enables the user to change
              the relative size of the sections by changing the position of the <code>separator</code>. A variable <code>separator</code> widget can be moved continuously within a range, whereas a
              fixed <code>separator</code> widget supports only two discrete positions. Typically, a fixed <code>separator</code> widget is used to toggle one of the sections between expanded and
              collapsed states.
            </p>
            <p>
              If the <code>separator</code> is focusable, authors MUST set the value of <pref>aria-valuenow</pref> to a <a href="#valuetype_number">number</a> reflecting the current position of the
              <code>separator</code> and update that value when it changes. Authors SHOULD also provide the value of <pref>aria-valuemin</pref> if it is not <code>0</code> and the value of
              <pref>aria-valuemax</pref> if it is not <code>100</code>. If missing or not a number, the implicit values of these attributes are as follows:
            </p>
            <ul>
              <li>The implicit value of <code>aria-valuemin</code> is <code>0</code>.</li>
              <li>The implicit value of <code>aria-valuemax</code> is <code>100</code>.</li>
            </ul>
            <p>In applications where there is more than one focusable <code>separator</code>, authors SHOULD provide an accessible name for each one.</p>
            <p>Elements with the role <code>separator</code> have an implicit <pref>aria-orientation</pref> value of <code>horizontal</code>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>structure</rref> (if not focusable)</li>
                    <li><rref>widget</rref> (if focusable)</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^hr^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"><pref>aria-valuenow</pref> (if focusable)</td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><sref>aria-disabled</sref> (if focusable)</li>
                    <li><pref>aria-orientation</pref></li>
                    <li><pref>aria-valuemax</pref> (if focusable)</li>
                    <li><pref>aria-valuemin</pref> (if focusable)</li>
                    <li><pref>aria-valuetext</pref> (if focusable)</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational">True</td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">
                  Default for <pref>aria-orientation</pref> is <code class="default">horizontal</code>.<br />
                  Default for <pref>aria-valuemin</pref> is <code>0</code>.<br />
                  Default for <pref>aria-valuemax</pref> is <code>100</code>.
                </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="slider">
          <rdef>slider</rdef>
          <div class="role-description">
            <p>An input where the user selects a value from within a given range.</p>
            <p>
              A slider represents the current value and range of possible values via the size of the slider and position of the thumb. It is typically possible to add to or subtract from the current
              value by using directional keys such as arrow keys.
            </p>
            <p>
              Authors MAY set the <pref>aria-valuemin</pref> and <pref>aria-valuemax</pref> attributes. Otherwise, their implicit values follow the same rules as
              <code>&lt;input type="[^input/type/range^]"&gt;</code> in HTML:
            </p>
            <ul>
              <li>If <code>aria-valuemin</code> is missing or not a <a href="#valuetype_number">number</a>, it defaults to 0 (zero).</li>
              <li>If <code>aria-valuemax</code> is missing or not a <a href="#valuetype_number">number</a>, it defaults to 100.</li>
            </ul>
            <p>
              Authors MUST set the <pref>aria-valuenow</pref> attribute. If aria-valuenow is missing or has an unexpected value, browsers MAY implement the repair techniques specified in the
              <a href="#authorErrorDefaultValuesTable">section describing handling author errors in states and properties</a>, which are equivalent to the repair techniques for
              <code>&lt;input type="[^input/type/range^]"&gt;</code> in HTML.
            </p>
            <p>Elements with the role <code>slider</code> have an implicit <pref>aria-orientation</pref> value of <code>horizontal</code>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>input</rref></li>
                    <li><rref>range</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties">
                  <ul>
                    <li><pref>aria-valuenow</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-errormessage</pref></li>
                    <li><pref>aria-haspopup</pref></li>
                    <li><sref>aria-invalid</sref></li>
                    <li><pref>aria-orientation</pref></li>
                    <li><pref>aria-readonly</pref></li>
                    <li><pref>aria-valuemax</pref></li>
                    <li><pref>aria-valuemin</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational">True</td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">
                  Default for <pref>aria-orientation</pref> is <code class="default">horizontal</code>. <br />
                  Default for <pref>aria-valuemin</pref> is <code class="default">0</code>. <br />
                  Default for <pref>aria-valuemax</pref> is <code class="default">100</code>.
                </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="spinbutton">
          <rdef>spinbutton</rdef>
          <div class="role-description">
            <p>A form of <rref>range</rref> that expects the user to select from among discrete choices.</p>
            <p>
              A <code>spinbutton</code> typically allows users to change its displayed value by activating increment and decrement buttons that step through a set of allowed values. Some
              implementations display the value in an text field that allows editing and typing but typically limits input in ways that help prevent invalid values.
            </p>
            <p>
              Although a <code>spinbutton</code> is similar in appearance to many presentations of <code>select</code>, it is advisable to use <code>spinbutton</code> when working with known ranges
              (especially in the case of large ranges) as opposed to distinct options. For example, a <code>spinbutton</code> representing a range from 1 to 1,000,000 would provide much better
              performance than a <code>select</code> <a>widget</a> representing the same values.
            </p>
            <p>
              Authors MAY create a <code>spinbutton</code> with <a>accessibility children</a>, but MUST limit those elements to a <rref>textbox</rref> and/or two <rref title="button">buttons</rref>.
              Alternatively, authors MAY apply the <rref>spinbutton</rref> role to a text input and create sibling buttons to support the increment and decrement functions.
            </p>
            <p>
              To be <a>keyboard accessible</a>, authors SHOULD manage focus of descendants for all instances of this <a>role</a>, as described in <a href="#managingfocus">Managing Focus</a>. When a
              <code>spinbutton</code> receives focus, authors SHOULD ensure focus is placed on the <rref>textbox</rref> element if one is present, and on the <code>spinbutton</code> itself otherwise.
              Authors SHOULD also ensure the <kbd>up</kbd> and <kbd>down</kbd> arrows on a keyboard perform the increment and decrement functions and that the increment and decrement
              <rref>button</rref> elements are <em>NOT</em> included in the primary navigation ring, e.g., the Tab ring in HTML.
            </p>
            <p>
              Authors SHOULD set the <pref>aria-valuenow</pref> attribute when the <rref>spinbutton</rref> has a value. Authors SHOULD set the <pref>aria-valuemin</pref> attribute when there is a
              minimum value, and the <pref>aria-valuemax</pref> attribute when there is a maximum value.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>composite</rref></li>
                    <li><rref>input</rref></li>
                    <li><rref>range</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"></td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-errormessage</pref></li>
                    <li><sref>aria-invalid</sref></li>
                    <li><pref>aria-readonly</pref></li>
                    <li><pref>aria-required</pref></li>
                    <li><pref>aria-valuemax</pref></li>
                    <li><pref>aria-valuemin</pref></li>
                    <li><pref>aria-valuenow</pref></li>
                    <li><pref>aria-valuetext</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">
                  Default for <pref>aria-valuemin</pref> is that there is no minimum value.<br />
                  Default for <pref>aria-valuemax</pref> is that there is no maximum value.<br />
                  Default for <pref>aria-valuenow</pref> is that there is no current value.<br />
                </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="status">
          <rdef>status</rdef>
          <div class="role-description">
            <p>
              A type of <a>live region</a> whose content is advisory information for the user but is not important enough to justify an <rref>alert</rref>, often but not necessarily presented as a
              status bar.
            </p>
            <p>Authors SHOULD ensure an element with role <code>status</code> does not receive focus as a result of change in status.</p>
            <p>
              Status is a form of <a>live region</a>. If another part of the page controls what appears in the status, authors SHOULD make the <a>relationship</a> explicit with the
              <pref>aria-controls</pref> <a>attribute</a>.
            </p>
            <p><a>Assistive technologies</a> MAY reserve some cells of a Braille display to render the status.</p>
            <p>Elements with the role <code>status</code> have an implicit <pref>aria-live</pref> value of <code>polite</code> and an implicit <pref>aria-atomic</pref> value of <code>true</code>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^output^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">
                  Default for <pref>aria-live</pref> is <code class="default">polite</code>.<br />
                  Default for <pref>aria-atomic</pref> is <code class="default">true</code>.
                </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="strong">
          <rdef>strong</rdef>
          <div class="role-description">
            <p>Content that is important, serious, or urgent. See related <rref>emphasis</rref>.</p>
            <p>
              The purpose of the <code>strong</code> role is to communicate strong importance, seriousness, or urgency. It is not for communicating changes in typographical presentation that are not
              important to the meaning of the content. Authors SHOULD use the <code>strong</code> role only if its absence would change the meaning of the content.
            </p>
            <p>The <code>strong</code> role is not intended to convey stress or emphasis; for that purpose, the <rref>emphasis</rref> role is more appropriate.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^strong^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
                <td class="role-disallowed">
                  <ul>
                    <li><pref>aria-braillelabel</pref></li>
                    <li><pref>aria-label</pref></li>
                    <li><pref>aria-labelledby</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">prohibited</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="structure">
          <rdef>structure</rdef>
          <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>
            <p><code>structure</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>structure</code> role in content.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract">True</td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>roletype</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom"></td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="subscript">
          <rdef>subscript</rdef>
          <div class="role-description">
            <p>One or more subscripted characters. See related <rref>superscript</rref>.</p>
            <p>
              The <code>subscript</code> role is intended to be used only to mark up typographical conventions that have specific meanings; not for typographical presentation for presentation's sake.
              In general, authors SHOULD use this role only if the absence of the subscript would change the meaning of the content.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^sub^]&gt;</code> and <code>&lt;[^sup^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
                <td class="role-disallowed">
                  <ul>
                    <li><pref>aria-braillelabel</pref></li>
                    <li><pref>aria-label</pref></li>
                    <li><pref>aria-labelledby</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">prohibited</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="suggestion">
          <rdef>suggestion</rdef>
          <div class="role-description">
            <p>A single proposed change to content.</p>
            <p>For example, in an editing system that supports multiple users, one user can suggest a change, and another user would be responsible for accepting or rejecting the suggestion.</p>
            <p>
              Authors MUST ensure that a <code>suggestion</code> contains either one <rref>insertion</rref> child or one <rref>deletion</rref> child or ensure that it contains two children where one
              is an <rref>insertion</rref> and the other is a <rref>deletion</rref>. Authors MUST ensure a <code>suggestion</code> does not contain any other children.
            </p>
            <p>
              Authors MAY use <pref>aria-details</pref> or <pref>aria-description</pref> to associate the <code>suggestion</code> with related information such as comments, authoring info, and time
              stamps.
            </p>
            <pre class="example highlight">
						&lt;p&gt;
						  The best pet is a
						  &lt;span role="suggestion"&gt;
						    &lt;span role="deletion"&gt;cat&lt;/span&gt;
						    &lt;span role="insertion"&gt;dog&lt;/span&gt;
						  &lt;/span&gt;
						&lt;/p&gt;
					</pre
            >
            <p>
              When a suggestion is accepted, authors SHOULD remove the <code>suggestion</code> role, indicating that the proposed revision has been made. After the <code>suggestion</code> role is
              removed, child <rref>insertion</rref> and <rref>deletion</rref> elements can either be retained to document the revision or replaced with the revised content.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain">
                  <ul>
                    <li><rref>insertion</rref></li>
                    <li><rref>deletion</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
                <td class="role-disallowed">
                  <ul>
                    <li><pref>aria-braillelabel</pref></li>
                    <li><pref>aria-label</pref></li>
                    <li><pref>aria-labelledby</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">prohibited</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="superscript">
          <rdef>superscript</rdef>
          <div class="role-description">
            <p>One or more superscripted characters. See related <rref>subscript</rref>.</p>
            <p>
              The <code>superscript</code> role is intended to be used only to mark up typographical conventions that have specific meanings; not for typographical presentation for presentation's
              sake. In general, authors SHOULD use this role only if the absence of the superscript would change the meaning of the content.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^sub^]&gt;</code> and <code>&lt;[^sup^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
                <td class="role-disallowed">
                  <ul>
                    <li><pref>aria-braillelabel</pref></li>
                    <li><pref>aria-label</pref></li>
                    <li><pref>aria-labelledby</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">prohibited</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="switch">
          <rdef>switch</rdef>
          <div class="role-description">
            <p>A type of checkbox that represents on/off values, as opposed to checked/unchecked values. See related <rref>checkbox</rref>.</p>
            <p>
              The <sref>aria-checked</sref> <a>attribute</a> of a <code>switch</code> indicates whether the input is on (<code>true</code>) or off (<code>false</code>). The <code>mixed</code> value is
              invalid, and user agents MUST treat a <code>mixed</code> value as equivalent to <code>false</code> for this role.
            </p>
            <p class="note">
              A <code>switch</code> provides approximately the same functionality as a <code>checkbox</code> and toggle <code>button</code>, but makes it possible for assistive technologies to present
              the widget in a fashion consistent with its on-screen appearance.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>checkbox</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><rref>button</rref></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties">
                  <ul>
                    <li><sref>aria-checked</sref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational">True</td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="tab">
          <rdef>tab</rdef>
          <div class="role-description">
            <p>A grouping label providing a mechanism for selecting the tab content that is to be rendered to the user.</p>
            <p>
              If a <rref>tabpanel</rref> or item in a <rref>tabpanel</rref> has focus, the associated <code>tab</code> is the currently active tab in the <rref>tablist</rref>, as defined in
              <a href="#managingfocus">Managing Focus</a>. <rref>tablist</rref> elements, which contain a set of associated <rref>tab</rref> elements, are typically placed near a series of
              <rref>tabpanel</rref> elements, usually preceding it. See the
              <cite
                ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite
              >
              for details on implementing a tab set design pattern.
            </p>
            <p>Authors MUST ensure [=elements=] with <a>role</a> <rref>tab</rref> are <a>accessibility children</a> of an element with the role <rref>tablist</rref>.</p>
            <p>Authors SHOULD ensure the <rref>tabpanel</rref> associated with the currently active tab is <a>perceivable</a> to the user.</p>
            <!-- keep following para synced with its counterpart in #tablist -->
            <p>
              For a single-selectable <rref>tablist</rref>, authors SHOULD [=element/hide from all users=] other <code>tabpanel</code> [=elements=] until the user selects the tab associated with that
              tabpanel. For a multi-selectable <rref>tablist</rref>, authors SHOULD ensure that the <rref>tab</rref> for each visible <rref>tabpanel</rref> has the <sref>aria-expanded</sref>
              <a>attribute</a> set to <code>true</code>, and that the <code>tabs</code> associated with the remaining [=element/hidden from all users=] <code>tabpanel</code> elements have their
              <sref>aria-expanded</sref> attributes set to <code>false</code>.
            </p>
            <p>
              Authors SHOULD ensure that a selected tab has its <sref>aria-selected</sref> attribute set to <code>true</code>, that inactive tab elements have their
              <sref>aria-selected</sref> attribute set to <code>false</code>, and that the currently selected tab provides a visual indication that it is selected.
            </p>
            <p>
              In certain conditions, a user agent MAY provide an implicit value for <sref>aria-selected</sref> for each <rref>tab</rref> in a <rref>tablist</rref>, and if it does, the user agent MUST
              ensure the following conditions are met before providing an implicit value:
            </p>
            <ul>
              <li>The value of <pref>aria-multiselectable</pref> on the <rref>tablist</rref> is <code>false</code> or <code>undefined</code>.</li>
              <li>None of the <rref>tab</rref> elements in the <rref>tablist</rref> have an explicitly declared value for <sref>aria-selected</sref> or <sref>aria-expanded</sref>.</li>
            </ul>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>sectionhead</rref></li>
                    <li><rref>widget</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"><rref>tablist</rref></td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><sref>aria-disabled</sref></li>
                    <li><sref>aria-expanded</sref></li>
                    <li><pref>aria-haspopup</pref></li>
                    <li><pref>aria-posinset</pref></li>
                    <li><sref>aria-selected</sref></li>
                    <li><pref>aria-setsize</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational">True</td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">Default for <sref>aria-selected</sref> is <code class="default">false</code>.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="table">
          <rdef>table</rdef>
          <div class="role-description">
            <p>A <rref>section</rref> containing data arranged in rows and columns. See related <rref>grid</rref>.</p>
            <p>
              The <code>table</code> role is intended for tabular containers which are not interactive. If the tabular container maintains a selection state, provides its own two-dimensional
              navigation, or allows the user to rearrange or otherwise manipulate its contents or the display thereof, authors SHOULD use <rref>grid</rref> or <rref>treegrid</rref> instead.
            </p>
            <p>
              Authors SHOULD provide an accessible name for a <code>table</code>, which can be done with the <pref>aria-label</pref> or <pref>aria-labelledby</pref> attribute. Authors SHOULD reference
              a visible label with <pref>aria-labelledby</pref> if a visible label is present for the <code>table</code>.
            </p>
            <p>Authors SHOULD prefer the use of the host language's semantics for table whenever possible, such as the <code>&lt;[^table^]&gt;</code> element in HTML.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"><code>&lt;[^table^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain">
                  <ul>
                    <li><rref>caption</rref></li>
                    <li><rref>row</rref></li>
                    <li><rref>rowgroup</rref> with <a>accessibility child</a> <rref>row</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-colcount</pref></li>
                    <li><pref>aria-rowcount</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="tablist">
          <rdef>tablist</rdef>
          <div class="role-description">
            <p>A list of <rref>tab</rref> [=elements=], which are references to <rref>tabpanel</rref> elements.</p>
            <p>To be <a>keyboard accessible</a>, authors SHOULD manage focus of descendants for all instances of this <a>role</a>, as described in <a href="#managingfocus">Managing Focus</a>.</p>

            <!-- keep following para synced with its counterpart in #tab -->
            <p>
              For a single-selectable <rref>tablist</rref>, authors SHOULD [=element/hide from all users=] other <code>tabpanel</code> [=elements=] until the user selects the tab associated with that
              tabpanel. For a multi-selectable <rref>tablist</rref>, authors SHOULD ensure that the <rref>tab</rref> for each visible <rref>tabpanel</rref> has the <sref>aria-expanded</sref>
              <a>attribute</a> set to <code>true</code>, and that the <code>tabs</code> associated with the remaining [=element/hidden from all users=] <code>tabpanel</code> elements have their
              <sref>aria-expanded</sref> attributes set to <code>false</code>.
            </p>

            <!-- keep following para synced with its counterpart in #tabpanel -->
            <p>
              <rref>tablist</rref> elements are typically placed near usually preceding, a series of <rref>tabpanel</rref> elements. See the
              <cite
                ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite
              >
              for details on implementing a tab set design pattern.
            </p>

            <p>Elements with the role <rref>tablist</rref> have an implicit <pref>aria-orientation</pref> value of <code>horizontal</code>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>composite</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"><rref>tab</rref></td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-multiselectable</pref></li>
                    <li><pref>aria-orientation</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">Default for <pref>aria-orientation</pref> is <code class="default">horizontal</code>.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="tabpanel">
          <rdef>tabpanel</rdef>
          <div class="role-description">
            <p>A container for the resources associated with a <rref>tab</rref>, where each <rref>tab</rref> is contained in a <rref>tablist</rref>.</p>
            <p>
              Authors SHOULD associate a <code>tabpanel</code> <a>element</a> with its <rref>tab</rref>, by using the <pref>aria-controls</pref> attribute on the tab to reference the tab panel, and/or
              by using the <pref>aria-labelledby</pref> attribute on the tab panel to reference the tab.
            </p>
            <!-- keep following para synced with its counterpart in #tablist -->
            <p>
              <rref>tablist</rref> elements are typically placed near, usually preceding, a series of <rref>tabpanel</rref> elements. See the
              <cite
                ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite
              >
              for details on implementing a tab set design pattern.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="term">
          <rdef>term</rdef>
          <div class="role-description">
            <p>A word or phrase with an optional corresponding definition. See related <rref>definition</rref>.</p>
            <p>
              The <code>term</code> role is used to explicitly identify a word or phrase for which a <rref>definition</rref> has been provided by the author or is expected to be provided by the user.
              If there is an existing <rref>definition</rref>, or a form or form control to enter a definition, authors SHOULD set <pref>aria-details</pref> to point to the related element.
            </p>
            <p>
              Authors SHOULD NOT use the <code>term</code> role on interactive elements such as links because doing so could prevent users of <a>assistive technologies</a> from interacting with those
              elements.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^dfn^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
                <td class="role-disallowed">
                  <ul>
                    <li><pref>aria-braillelabel</pref></li>
                    <li><pref>aria-label</pref></li>
                    <li><pref>aria-labelledby</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">prohibited</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <!-- FIXME: This is commented out because the ARIA Working Group agreed to move the text role to ARIA 2.0,
     but we've not branched for 1.1 yet. Once we have branched, this entire section should be deleted from
     the 1.1 branch and uncommented for the master branch.
		<div class="role" id="text">
			<rdef>text</rdef>
			<div class="role-description">
				<p>An element whose entire subtree should be exposed to accessibility APIs as plain text.</p>
				<p>The <code>text</code> role allows authors to mark an element and all of its subtree contents as plain text.</p>
				<p>Authors SHOULD NOT use the <code>text</code> role on interactive controls (buttons, links, etc.) or ancestors of those controls, because it could prevent users of assistive technologies from accessing the controls. Authors wishing to retain the semantics of subtree contents could consider the ARIA 1.0 <rref>presentation</rref> or ARIA 1.1 <rref>none</rref> role instead.</p>
				<div class="note">
					<p>As with any ARIA 1.1 role, authors can provide a fallback ARIA 1.0 role.</p>
					<pre class="example highlight">
						&lt;p&gt;I &lt;span role="text img" aria-label="love"&gt;♥︎&lt;/span&gt; New York.&lt;/p&gt;
						&lt;p&gt;My &lt;span role="text img" aria-label="heart"&gt;♥︎&lt;/span&gt; bleeds.&lt;/p&gt;
						&lt;p&gt;&lt;span role="text img" aria-label="3 of 5 stars"&gt;★★★☆☆︎&lt;/span&gt;&lt;/p&gt;
					</pre>
					<p>In a screen reader using an ARIA 1.1-capable browsers, the user would hear "I love New York." In an ARIA 1.0-capable browser, the user might hear "I, love image, New York."</p>
				</div>
				<div class="note">
					<p>It is not necessary to use the fallback role if the implicit role for the element provides sufficient fallback. In this example, an ARIA 1.0-capable browser would not recognize the "text" role token, and fall back to the default image role.</p>
					<pre class="example highlight">
						&lt;p&gt;I &lt;img src="icon.gif" alt="love" role="text"&gt; New York.︎&lt;/p&gt;
						&lt;p&gt;My &lt;img src="icon.gif" alt="heart" role="text"&gt; bleeds.︎&lt;/p&gt;
					</pre>
				</div>
				<div class="note">
					<p>The text role can also be used to flatten structural semantics without providing an explicit label. The following example would be presented to assistive technologies as one static text element ("I like turtles") rather than three separate paragraphs.</p>
					<pre class="example highlight">
						&lt;div role="text"&gt;
						  &lt;p&gt;I&lt;/p&gt;
						  &lt;p&gt;like&lt;/p&gt;
						  &lt;p&gt;turtles&lt;/p&gt;
						&lt;/div&gt;
					</pre>
					<p>Use caution when using the text role on structural elements. In particular, avoid using the text role on elements with interactive descendants.</p>
					<pre class="example highlight">
						&lt;p role="text"&gt;
						  &lt;!&dash;&dash; Example of incorrect usage. &dash;&dash;&gt;
						  This &lt;a href="#"&gt;link&lt;/a&gt; becomes presentational, so
						  it is no longer a link. The paragraph is just plain text.
						  This is probably not what the author intended.
						&lt;/p&gt;
					</pre>
				</div>
			</div>
			<table class="def">
				<caption>Characteristics:</caption>
				<thead>
					<tr>
						<th scope="col">Characteristic</th>
						<th scope="col">Value</th>
					</tr>
				</thead>
				<tbody>
					<tr>
						<th class="role-abstract-head" scope="row">Is Abstract:</th>
						<td class="role-abstract"> </td>
					</tr>
					<tr>
						<th class="role-parent-head" scope="row">Superclass Role:</th>
						<td class="role-parent"><rref>structure</rref></td>
					</tr>
					<tr>
						<th class="role-children-head" scope="row">Subclass Roles:</th>
						<td class="role-children">Placeholder</td>
					</tr>
					<tr>
						<th class="role-base-head" scope="row">Base Concept:</th>
						<td class="role-base"> </td>
					</tr>
					<tr>
						<th class="role-related-head" scope="row">Related Concepts:</th>
						<td class="role-related"> </td>
					</tr>
					<tr>
						<th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
						<td class="role-scope"> </td>
					</tr>
					<tr>
						<th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
						<td class="role-mustcontain"> </td>
					</tr>
					<tr>
						<th class="role-required-properties-head">Required States and Properties:</th>
						<td class="role-required-properties"> </td>
					</tr>
					<tr>
						<th class="role-properties-head" scope="row">Supported States and Properties:</th>
						<td class="role-properties"> </td>
					</tr>
					<tr>
						<th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
						<td class="role-inherited">Placeholder</td>
					</tr>
					<tr>
						<th class="role-namefrom-head" scope="row">Name From:</th>
						<td class="role-namefrom">
							<ul>
								<li>contents</li>
								<li>author</li>
							</ul>
						</td>
					</tr>
					<tr>
						<th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
						<td class="role-namerequired"> </td>
					</tr>
					<tr>
						<th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
						<td class="role-namerequired-inherited"> </td>
					</tr>
					<tr>
						<th class="role-childpresentational-head" scope="row">Children Presentational:</th>
						<td class="role-childpresentational">True</td>
					</tr>
					<tr>
						<th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
						<td class="role-presentational-inherited"> </td>
					</tr>
				</tbody>
			</table>
		</div>
		-->
        <div class="role" id="textbox">
          <rdef>textbox</rdef>
          <div class="role-description">
            <p>A type of input that allows free-form text as its value.</p>
            <p>
              If the <pref>aria-multiline</pref> <a>attribute</a> is <code>true</code>, the <a>widget</a> accepts line breaks within the input, as in an HTML <code>textarea</code>. Otherwise, this is
              a simple text box. The intended use is for languages that do not have a text input <a>element</a>, or cases in which an element with different <a>semantics</a> is repurposed as a text
              field.
            </p>
            <p>
              Authors MUST limit the children of a textbox to non-interactive, entirely presentational elements such as icons used to visually convey information that is already exposed in an
              accessible manner. Examples include:
            </p>
            <ul>
              <li>an error icon, where the containing textbox has been provided an <sref>aria-invalid</sref>, <sref>aria-errormessage</sref>, or both attributes;</li>
              <li>an icon of a user silhouette, where the textbox is also visibly labeled or provided an accessible name of "name" or "username"; and</li>
              <li>a graphical status indicator, such as a gauge to represent characters remaining, which represents dynamically updating text available outside of the textbox.</li>
            </ul>
            <!-- keep the following para synced with its equivalent in #aria-multiline -->
            <p class="note">
              In most user agent implementations, the default behavior of the <kbd>ENTER</kbd> or <kbd>RETURN</kbd> key is different between the single-line and multi-line text fields in HTML. When
              user has focus in a single-line <code>&lt;input type="text"&gt;</code> element, the keystroke usually submits the form. When user has focus in a multi-line
              <code>&lt;textarea&gt;</code> element, the keystroke inserts a line break. The <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <code>textbox</code> role
              differentiates these types of boxes with the <pref>aria-multiline</pref> attribute, so authors are advised to be aware of this distinction when designing the field.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>input</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related">
                  <ul>
                    <li><code>&lt;[^textarea^]&gt;</code> in HTML</li>
                    <li><code>&lt;input type="[^input/type/text^]"&gt;</code> in HTML</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-activedescendant</pref></li>
                    <li><pref>aria-autocomplete</pref></li>
                    <li><pref>aria-errormessage</pref></li>
                    <li><pref>aria-haspopup</pref></li>
                    <li><sref>aria-invalid</sref></li>
                    <li><pref>aria-multiline</pref></li>
                    <li><pref>aria-placeholder</pref></li>
                    <li><pref>aria-readonly</pref></li>
                    <li><pref>aria-required</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"></td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="time">
          <rdef>time</rdef>
          <div class="role-description">
            <p>An element that represents a specific point in time.</p>
            <p class="note">
              At the present time, there are no <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> properties corresponding to the <code>datetime</code> attribute supported on
              <code>&lt;[^time^]&gt;</code> in HTML. The addition of this property will be considered for ARIA version 1.3.
            </p>
            <p>
              Authors SHOULD limit text contents to a valid date- or time-related string, or apply this future <code>datetime</code>-equivalent property to the element which has role
              <code>time</code>.
            </p>
            <aside class="example">
              <p>Examples of valid date- or time-related strings as text contents of an element with the <code>time</code> role:</p>
              <ul>
                <li>A valid month string: <code>&lt;span role="time"&gt;2019-11&lt;/span&gt;</code></li>
                <li>A valid date string: <code>&lt;span role="time"&gt;2019-11-18&lt;/span&gt;</code></li>
                <li>A valid yearless date string: <code>&lt;span role="time"&gt;11-18&lt;/span&gt;</code></li>
                <li>A valid time string: <code>&lt;span role="time"&gt;09:54:39&lt;/span&gt;</code></li>
                <li>A valid floating date and time string: <code>&lt;span role="time"&gt;2019-11-18T14:54&lt;/span&gt;</code></li>
                <li>A valid time-zone offset string: <code>&lt;span role="time"&gt;-08:00&lt;/span&gt;</code></li>
                <li>A valid global date and time string: <code>&lt;span role="time"&gt;2019-11-18T14:54Z&lt;/span&gt;</code></li>
                <li>A valid week string: <code>&lt;span role="time"&gt;2019-W47&lt;/span&gt;</code></li>
                <li>Four or more ASCII digits, at least one of which is not U+0030 DIGIT ZERO (0): <code>&lt;span role="time"&gt;0001&lt;/span&gt;</code></li>
                <li>A valid duration string: <code>&lt;span role="time"&gt;4h 18m 3s&lt;/span&gt;</code></li>
              </ul>
            </aside>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children"></td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><code>&lt;[^time^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
                <td class="role-disallowed">
                  <ul>
                    <li><pref>aria-braillelabel</pref></li>
                    <li><pref>aria-label</pref></li>
                    <li><pref>aria-labelledby</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">prohibited</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="timer">
          <rdef>timer</rdef>
          <div class="role-description">
            <p>A type of <a>live region</a> containing a numerical counter which indicates an amount of elapsed time from a start point, or the time remaining until an end point.</p>
            <p>
              The text contents of the timer <a>object</a> indicate the current time measurement, and are updated as that amount changes. The timer value is not necessarily machine parsable, but
              authors SHOULD update the text contents at fixed intervals, except when the timer is paused or reaches an end-point.
            </p>
            <p>Elements with the role <code>timer</code> have an implicit <pref>aria-live</pref> value of <code>off</code>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>status</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">Default for <pref>aria-live</pref> is <code class="default">off</code>.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="toolbar">
          <rdef>toolbar</rdef>
          <div class="role-description">
            <p>A collection of commonly used function buttons or controls represented in compact visual form.</p>
            <p>
              The toolbar is often a subset of functions found in a <rref>menubar</rref>, designed to reduce user effort in using these functions. Authors MUST supply a label on each toolbar when the
              application contains more than one toolbar.
            </p>
            <p>Authors MAY manage focus of descendants for all instances of this <a>role</a>, as described in <a href="#managingfocus">Managing Focus</a>.</p>
            <p>Elements with the role <code>toolbar</code> have an implicit <pref>aria-orientation</pref> value of <code>horizontal</code>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>group</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"><rref>menubar</rref></td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <pref>aria-orientation</pref>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">Default for <pref>aria-orientation</pref> is <code class="default">horizontal</code>.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="tooltip">
          <rdef>tooltip</rdef>
          <div class="role-description">
            <p>A contextual popup that displays a description for an element.</p>
            <p>
              The <code>tooltip</code> typically becomes visible, after a short delay, in response to a mouse hover, or after the <a>accessibility parent</a> receives keyboard focus. The use of a
              <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> tooltip is a supplement to the normal tooltip behavior of the user agent.
            </p>
            <p class="note">Typical tooltip delays last from one to five seconds.</p>
            <p>
              Authors SHOULD ensure that elements with the <a>role</a> <code>tooltip</code> are referenced through the use of <pref>aria-describedby</pref> before or at the time the tooltip is
              displayed.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>section</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"></td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="tree">
          <rdef>tree</rdef>
          <div class="role-description">
            <p>A <rref>widget</rref> that allows the user to select one or more items from a hierarchically organized collection.</p>
            <p>To be <a>keyboard accessible</a>, authors SHOULD manage focus of descendants for all instances of this <a>role</a>, as described in <a href="#managingfocus">Managing Focus</a>.</p>
            <p>Elements with the role <code>tree</code> have an implicit <pref>aria-orientation</pref> value of <code>vertical</code>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>select</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"><rref>treeitem</rref></td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><pref>aria-errormessage</pref></li>
                    <li><sref>aria-invalid</sref></li>
                    <li><pref>aria-multiselectable</pref></li>
                    <li><pref>aria-required</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
              <tr>
                <th class="implicit-values-head" scope="row">Implicit Value for Role:</th>
                <td class="implicit-values">Default for <pref>aria-orientation</pref> is <code class="default">vertical</code>.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="treegrid">
          <rdef>treegrid</rdef>
          <div class="role-description">
            <p>A <rref>grid</rref> whose rows can be expanded and collapsed in the same manner as for a <rref>tree</rref>.</p>
            <!-- make sure the following para remains synced with its counterpart in #grid -->
            <p>
              If <pref>aria-readonly</pref> is set on an <a>element</a> with <a>role</a> <code>treegrid</code>, [=user agents=] MUST propagate the value to all <rref>gridcell</rref> elements that are
              <a>accessibility descendants</a> of the <code>treegrid</code> and expose the value in the accessibility API. An author MAY override the propagated value of <pref>aria-readonly</pref> for
              an individual <rref>gridcell</rref> element.
            </p>
            <p>
              When the <pref>aria-readonly</pref> attribute is applied to a focusable <rref>gridcell</rref>, it indicates whether the content contained in the <rref>gridcell</rref> is editable. The
              <pref>aria-readonly</pref> attribute does not represent availability of functions for navigating or manipulating the <code>treegrid</code> itself.
            </p>
            <p>
              In a <code>treegrid</code> that provides content editing functions, if the content of a focusable <rref>gridcell</rref> element is not editable, authors MAY set
              <pref>aria-readonly</pref> to <code>true</code> on the <rref>gridcell</rref> element. However, if a <code>treegrid</code> presents a collection of elements that do not support
              <pref>aria-readonly</pref>, such as a collection of <rref>link</rref> elements, it is not necessary for the author to specify a value for <pref>aria-readonly</pref>.
            </p>
            <p>To be <a>keyboard accessible</a>, authors SHOULD manage focus of descendants for all instances of this <a>role</a>, as described in <a href="#managingfocus">Managing Focus</a>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>grid</rref></li>
                    <li><rref>tree</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope"> </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain">
                  <ul>
                    <li><rref>caption</rref></li>
                    <li><rref>row</rref></li>
                    <li><rref>rowgroup</rref> with <a>accessibility child</a> <rref>row</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">author</td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="treeitem">
          <rdef>treeitem</rdef>
          <div class="role-description">
            <p>An item in a <rref>tree</rref>.</p>
            <p>
              A <rref>treeitem</rref> <a>element</a> can contain a sub-level group of elements that can be expanded or collapsed. An expandable collection of <code>treeitem</code> elements are
              enclosed in an element with the <rref>group</rref> <a>role</a>.
            </p>
            <p>
              Authors MUST ensure [=elements=] with <a>role</a> <code>treeitem</code> are <a>accessibility children</a> of an element with role <rref>tree</rref> or an element with role
              <rref>group</rref> that is the <a>accessibility child</a> of an element with role <rref>treeitem</rref>.
            </p>
            <p>
              In certain conditions, a user agent MAY provide an implicit value for <sref>aria-selected</sref> for each <rref>treeitem</rref> in a <rref>tree</rref>, and if it does, the user agent
              MUST ensure the following conditions are met before providing an implicit value:
            </p>
            <ul>
              <li>The value of <pref>aria-multiselectable</pref> on the <rref>tree</rref> is <code>false</code> or <code>undefined</code>.</li>
              <li>None of the <rref>treeitem</rref> elements in the <rref>tree</rref> have an explicitly declared value for <sref>aria-selected</sref> or <sref>aria-checked</sref>.</li>
            </ul>
            <p>
              If a user agent provides an implicit <sref>aria-selected</sref> value for a <rref>treeitem</rref>, the value SHOULD be <code>true</code> if the <rref>treeitem</rref> has DOM focus or the
              <rref>tree</rref> has DOM focus and the <rref>treeitem</rref> is referenced by <pref>aria-activedescendant</pref>. Otherwise, if a user agent provides an implicit
              <sref>aria-selected</sref> value for a <rref>treeitem</rref>, the value SHOULD be <code>false</code>.
            </p>
            <p>
              Authors MAY indicate selection for <rref>treeitem</rref> elements using either <sref>aria-selected</sref> or <sref>aria-checked</sref>. Some user interfaces indicate selection with
              <sref>aria-selected</sref> in single-select trees and with <sref>aria-checked</sref> in multi-select trees. Authors SHOULD NOT specify both <sref>aria-selected</sref> and
              <sref>aria-checked</sref> on <rref>treeitem</rref> elements contained by the same <rref>tree</rref> except in the extremely rare circumstances where all the following conditions are met:
            </p>
            <ul>
              <li>The meaning and purpose of <sref>aria-selected</sref> is different from the meaning and purpose of <sref>aria-checked</sref> in the user interface.</li>
              <li>The user interface makes the meaning and purpose of each state apparent.</li>
              <li>The user interface provides a separate method for controlling each state.</li>
            </ul>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract"> </td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent">
                  <ul>
                    <li><rref>listitem</rref></li>
                    <li><rref>option</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-scope-head" scope="row">Required Accessibility Parent Roles:</th>
                <td class="role-scope">
                  <ul>
                    <li><rref>tree</rref></li>
                    <li><rref>group</rref> with <a>accessibility parent</a> <rref>treeitem</rref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-mustcontain-head" scope="row">Allowed Accessibility Child Roles:</th>
                <td class="role-mustcontain"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties">
                  <ul>
                    <li><sref>aria-expanded</sref></li>
                    <li><pref>aria-haspopup</pref></li>
                    <li><pref>aria-level</pref></li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom">
                  <ul>
                    <li>contents</li>
                    <li>author</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired">True</td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="widget">
          <rdef>widget</rdef>
          <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 [=user agents=] 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>
            <p><code>widget</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>widget</code> role in content.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract">True</td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>roletype</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"> </td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom"></td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="role" id="window">
          <rdef>window</rdef>
          <div class="role-description">
            <p>A browser or application window.</p>
            <p>
              [=element|Elements=] 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><code>window</code> is an <a href="#isAbstract">abstract role</a> used for the ontology. Authors MUST NOT use <code>window</code> role in content.</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="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="role-abstract-head" scope="row">Is Abstract:</th>
                <td class="role-abstract">True</td>
              </tr>
              <tr>
                <th class="role-parent-head" scope="row">Superclass Role:</th>
                <td class="role-parent"><rref>roletype</rref></td>
              </tr>
              <tr>
                <th class="role-children-head" scope="row">Subclass Roles:</th>
                <td class="role-children">Placeholder</td>
              </tr>
              <tr>
                <th class="role-base-head" scope="row">Base Concept:</th>
                <td class="role-base"> </td>
              </tr>
              <tr>
                <th class="role-related-head" scope="row">Related Concepts:</th>
                <td class="role-related"> </td>
              </tr>
              <tr>
                <th class="role-required-properties-head">Required States and Properties:</th>
                <td class="role-required-properties"> </td>
              </tr>
              <tr>
                <th class="role-properties-head" scope="row">Supported States and Properties:</th>
                <td class="role-properties"><pref>aria-modal</pref></td>
              </tr>
              <tr>
                <th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
                <td class="role-inherited">Placeholder</td>
              </tr>
              <tr>
                <th class="role-namefrom-head" scope="row">Name From:</th>
                <td class="role-namefrom"></td>
              </tr>
              <tr>
                <th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
                <td class="role-namerequired"> </td>
              </tr>
              <tr>
                <th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
                <td class="role-namerequired-inherited"> </td>
              </tr>
              <tr>
                <th class="role-childpresentational-head" scope="row">Children Presentational:</th>
                <td class="role-childpresentational"> </td>
              </tr>
              <tr>
                <th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
                <td class="role-presentational-inherited"> </td>
              </tr>
            </tbody>
          </table>
        </div>
      </section>
    </section>
    <section class="normative" id="states_and_properties">
      <h1>Supported States and Properties</h1>
      <section id="statevsprop">
        <h2>Clarification of States versus Properties</h2>
        <p>
          The terms "states" and "properties" refer to similar features. Both provide specific information about an <a>object</a>, and both form part of the definition of the nature of <a>roles</a>.
          In this document, states and properties are both treated as aria-prefixed markup [=attributes=]. However, they are maintained conceptually distinct to clarify subtle differences in their
          meaning. One major difference is that the <span>values</span> of properties (such as <pref>aria-labelledby</pref>) are often less likely to change throughout the application life-cycle than
          the values of states (such as <sref>aria-checked</sref>) which might change frequently due to user interaction. Note that the frequency of change difference is not a rule; a few properties,
          such as <pref>aria-valuetext</pref> are expected to change often. Because the distinction between states and properties is of little consequence to most authors, this specification refers to
          both "states" and "properties" simply as "attributes" whenever possible. See the definitions of <a class="termref" href="#dfn-state">state</a> and
          <a class="termref" href="#dfn-property">property</a> for more information.
        </p>
      </section>
      <section id="state_prop_att">
        <h2>Characteristics of States and Properties</h2>
        <p>States and properties have the characteristics described in the following sections.</p>
        <section id="propcharacteristic_relatedconcept">
          <h3>Related Concepts</h3>
          <p>
            Advisory information about features from this or other languages that correspond to this <a>state</a> or [=ARIA/property=]. While the correspondence might not be exact, it is useful to
            help understand the intent of the state or property.
          </p>
        </section>
        <section id="propcharacteristic_usedinrole">
          <h3>Used in Roles</h3>
          <p>
            Advisory information about <a href="#role_definitions">roles</a> that use this <a>state</a> or [=ARIA/property=]. This information is provided to help understand the appropriate usage of
            the state or property. Use of a given state or property is not defined when used on roles other than those listed.
          </p>
        </section>
        <section id="propcharacteristic_inheritsintoroles">
          <h3>Inherits into Roles</h3>
          <p>Advisory information about <a href="#role_definitions">roles</a> that inherit the <a>state</a> or [=ARIA/property=] from an ancestor role.</p>
        </section>
        <section id="propcharacteristic_value">
          <h3>Value</h3>
          <p>Value type of the <a>state</a> or [=ARIA/property=]. The value is one of the following types:</p>
          <dl>
            <dt id="valuetype_true-false">true/false</dt>
            <dd>Value representing either <code>true</code> or <code>false</code>. The default value for this value type is <code>false</code> unless otherwise specified.</dd>
            <dt id="valuetype_tristate">tristate</dt>
            <dd>
              Value representing <code>true</code>, <code>false</code>, <code>mixed</code>, or <code>undefined</code> values. The default value for this value type is <code>undefined</code> unless
              otherwise specified.
            </dd>
            <dt id="valuetype_true-false-undefined">true/false/undefined</dt>
            <dd>
              Value representing <code>true</code>, <code>false</code>, or <code>undefined</code> (not applicable). The default value for this value type is <code>undefined</code> unless otherwise
              specified. For example, an element with <sref>aria-expanded</sref> set to <code>false</code> is not currently expanded; an element with <sref>aria-expanded</sref> set to
              <code>undefined</code> is not expandable.
            </dd>
            <dt id="valuetype_idref">ID reference</dt>
            <dd>Reference to the ID of another <a>element</a> in the same document</dd>
            <dt id="valuetype_idref_list">ID reference list</dt>
            <dd>A list of one or more ID references.</dd>
            <dt id="valuetype_integer">integer</dt>
            <dd>A numerical value without a fractional component.</dd>
            <dt id="valuetype_number">number</dt>
            <dd>Any real numerical value.</dd>
            <dt id="valuetype_string">string</dt>
            <dd>Unconstrained value type.</dd>
            <dt id="valuetype_token">token</dt>
            <dd>
              One of a limited set of allowed values. The default value is defined in each attribute's Values table, as specified in the
              <a href="#enumerated-attribute-values">Attribute Values</a> section.
            </dd>
            <dt id="valuetype_token_list"><dfn>token list</dfn></dt>
            <dd>A list of one or more tokens.</dd>
          </dl>
          <p>
            These are generic types for states and properties, but do not define specific representation. See <a href="#state_property_processing">State and Property Attribute Processing</a> for
            details on how these values are expressed and handled in host languages.
          </p>
        </section>
      </section>
      <section data-cite="webidl">
        <h2>ARIA Attributes</h2>
        <section id="enumerated-attribute-values">
          <h3>Multi-value Attribute Values</h3>
          <p>
            When the ARIA attribute definition includes a table listing the attribute's allowed <span>values</span>, that attribute is a multi-value nullable attribute. Each value in the table is a
            keyword for the attribute, mapping to a state of the same name.
          </p>
        </section>
        <section id="idl-reflection-attribute-values">
          <h3>IDL reflection of ARIA attributes</h3>
          <p>
            All ARIA attributes reflect in IDL as [=nullable type|nullable=] {{DOMString}} attributes. This includes the boolean-like <a href="#valuetype_true-false">true/false</a> type, and all other
            ARIA attributes.
          </p>
          <p>
            Default values from the ARIA values tables MUST NOT reflect to IDL as the <a data-cite="html/common-microsyntaxes.html#missing-value-default">missing value default</a> or the
            <a data-cite="html/common-microsyntaxes.html#invalid-value-default">invalid value default</a> for the attribute. On getting, a missing ARIA attribute will return <code>null</code>. ARIA
            attributes are not validated on get. If an ARIA value is invalid, on getting, it will return its set value as a literal string, and will not return an invalid value default.
          </p>
        </section>
        <section id="os-aapi-attribute-mapping">
          <h3>Operating System Accessibility API mapping of multi-value ARIA attributes</h3>
          <p>
            Unlike IDL reflection, operating system accessibility API mappings of ARIA attributes can have defaults. Any default values from the ARIA values tables are exposed to the operating system
            accessibility API as described in [[[#supportedState]]], and in [[[CORE-AAM]]].
          </p>
        </section>
        <section id="enumerated-attribute-values-html">
          <h3>ARIA nullable DOMString Attributes</h3>
          <p>As noted in [[[#typemapping]]], attributes are included in host languages, and the syntax for representation of WAI-ARIA types is governed by the host language.</p>
          <p>The following algorithm should be used for ARIA nullable {{DOMString}} attributes in HTML:</p>
          <p>
            On getting, if the corresponding content attribute is not present, then the IDL attribute must return null, otherwise, the IDL attribute must get the value in a transparent,
            case-preserving manner. On setting, if the new value is null, the content attribute must be removed, and otherwise, the content attribute must be set to the specified new value in a
            transparent, case-preserving manner.
          </p>
          <p class="note">
            Note: As of ARIA 1.2, all ARIA attributes exposed via IDL are defined as nullable {{DOMString}}s. This matches the current implementation of all major rendering engines. This specification
            change should result in no implementation changes; it will merely represent the current reality of web engines. However, in a future draft, the ARIA Working Group intends to change several
            ARIA attributes to non-nullable DOMStrings, and seek implementations. The proposed change will bring ARIA into alignment with the HTML’s usage of
            <a data-cite="html/common-microsyntaxes.html#enumerated-attribute">enumerated attributes</a>.
          </p>
          <section class="informative" id="enumeration-example">
            <h4>Example Attribute Usage</h4>
            <aside class="example">
              <!-- ReSpec needs these examples to be unindented. -->
              <pre>
// HTML hidden="" example (not aria-hidden="true")
// Actual boolean type; defaults to false.

// Note: Actual boolean assignment and return value.
el.hidden = true;
el.hidden; // true

// Removal of content attribute results in missing value default: boolean false.
el.removeAttribute("hidden");
el.hidden; // false</pre
              >
            </aside>
            <aside class="example">
              <!-- ReSpec needs these examples to be unindented. -->
              <pre>
// aria-busy example
// true/false ~ boolean-like nullable string; returns null unless set

el.ariaBusy; // null

// Note: String assignment and return value.
el.ariaBusy = "true";
el.ariaBusy; // "true"

// Removal of content attribute results in missing value default: string "false".
el.removeAttribute("aria-busy");
el.ariaBusy; // null

// Assignment of invalid "busy" value. Not validated on set or get and the literal string value "busy" is returned.
el.setAttribute("aria-busy", "busy");
el.ariaBusy; // "busy"</pre
              >
            </aside>
            <aside class="example">
              <!-- ReSpec needs these examples to be unindented. -->
              <pre>
// aria-pressed example
// Tristate ~ true/false/mixed/undefined string; null if unspecified

// no value has been defined
button.ariaPressed; // null

// A value of "true", "false", or "mixed" for aria-pressed on a button denotes a toggle button.
button.setAttribute("aria-pressed", "true"); // Content attribute assignment.
button.ariaPressed; // "true"
button.ariaPressed = "false"; // DOM property assignment.
button.ariaPressed; // "false"

// Assignment of invalid "foo" value. Not validated on set or get and the literal string value "foo" is returned.
button.ariaPressed = "foo";
button.ariaPressed; // "foo" (Note: button is no longer a toggle button.)

// Removal of content attribute results in a null value
button.removeAttribute("aria-pressed");
button.ariaPressed; // null</pre
              >
            </aside>
          </section>
        </section>
      </section>
      <section>
        <h2>Translatable Attributes</h2>
        <p>
          The HTML specification states that other specifications can define <a data-cite="html/dom.html#translatable-attributes">translatable attributes</a>. The language and directionality of each
          attribute value is the same as the <a data-cite="html/dom.html#language">language</a> and <a data-cite="html/dom.html#the-directionality">directionality</a> of the element.
        </p>
        <p>
          To be understandable by assistive technology users, the values of the following <a>states</a> and [=ARIA/properties=] are
          <a data-cite="html/dom.html#translatable-attributes">translatable attributes</a> and should be translated when a page is localized:
        </p>
        <ul>
          <li><pref>aria-braillelabel</pref></li>
          <li><pref>aria-brailleroledescription</pref></li>
          <li><pref>aria-colindextext</pref></li>
          <li><pref>aria-description</pref></li>
          <li><pref>aria-label</pref></li>
          <li><pref>aria-placeholder</pref></li>
          <li><pref>aria-roledescription</pref></li>
          <li><pref>aria-rowindextext</pref></li>
          <li><pref>aria-valuetext</pref></li>
        </ul>
      </section>
      <section id="global_states">
        <h2><dfn>Global</dfn> States and Properties</h2>
        <p>
          Some <a>states</a> and [=ARIA/properties=] are applicable to all host language [=elements=] regardless of whether a <a>role</a> is applied. The following global states and properties are
          supported by all roles and by all base markup elements unless otherwise prohibited. If a role prohibits use of any global states or properties, those states or properties are listed as
          prohibited in the characteristics table included in the section that defines the role.
        </p>
        <p class="placeholder">Placeholder for global states and properties</p>
      </section>
      <section id="state_prop_taxonomy">
        <h2>Taxonomy of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> States and Properties</h2>
        <p>States and properties are categorized as follows:</p>
        <ol>
          <li><a href="#attrs_widgets">Widget Attributes</a></li>
          <li><a href="#attrs_liveregions">Live Region Attributes</a></li>
          <li><a href="#attrs_dragdrop">Drag-and-Drop Attributes</a></li>
          <li><a href="#attrs_relationships">Relationship Attributes</a></li>
        </ol>
        <section id="attrs_widgets">
          <h3>Widget Attributes</h3>
          <p>
            This section contains [=attributes=] specific to common user interface [=elements=] found on <abbr title="Graphical User Interface">GUI</abbr> systems or in rich internet applications
            which receive user input and process user actions. These attributes are used to support the <a href="#widget_roles">widget roles</a>.
          </p>
          <ul>
            <li><pref>aria-autocomplete</pref></li>
            <li><sref>aria-checked</sref></li>
            <li><sref>aria-disabled</sref></li>
            <li><pref>aria-errormessage</pref></li>
            <li><sref>aria-expanded</sref></li>
            <li><pref>aria-haspopup</pref></li>
            <li><sref>aria-hidden</sref></li>
            <li><sref>aria-invalid</sref></li>
            <li><pref>aria-label</pref></li>
            <li><pref>aria-level</pref></li>
            <li><pref>aria-modal</pref></li>
            <li><pref>aria-multiline</pref></li>
            <li><pref>aria-multiselectable</pref></li>
            <li><pref>aria-orientation</pref></li>
            <li><pref>aria-placeholder</pref></li>
            <li><sref>aria-pressed</sref></li>
            <li><pref>aria-readonly</pref></li>
            <li><pref>aria-required</pref></li>
            <li><sref>aria-selected</sref></li>
            <li><pref>aria-sort</pref></li>
            <li><pref>aria-valuemax</pref></li>
            <li><pref>aria-valuemin</pref></li>
            <li><pref>aria-valuenow</pref></li>
            <li><pref>aria-valuetext</pref></li>
          </ul>
          <p>
            Widget attributes might be mapped by a <a>user agent</a> to platform <a>accessibility <abbr title="Application Programing Interfaces">API</abbr></a> <a>state</a>, for access by
            <a>assistive technologies</a>, or they might be accessed directly from the <abbr title="Document Object Model">DOM</abbr>.
          </p>
        </section>
        <section id="attrs_liveregions">
          <h3>Live Region Attributes</h3>
          <p>
            This section contains [=attributes=] specific to <a>live regions</a> in rich internet applications. These attributes MAY be applied to any <a>element</a>. The purpose of these attributes
            is to indicate that content changes might occur without the element having focus, and to provide <a>assistive technologies</a> with information on how to process those content updates.
            Some <a>roles</a> specify a default value for the <pref>aria-live</pref> attribute specific to that role. An example of a live region is a ticker section that lists updating stock quotes.
            User agents MAY ignore changes triggered by direct user action on an <a>element</a> inside a live region (e.g., editing the value of a text field).
          </p>
          <ul>
            <li><pref>aria-atomic</pref></li>
            <li><sref>aria-busy</sref></li>
            <li><pref>aria-live</pref></li>
            <li><pref>aria-relevant</pref></li>
          </ul>
        </section>
        <section id="attrs_dragdrop">
          <h3>Drag-and-Drop Attributes</h3>
          <p>
            This section lists [=attributes=] which indicate information about drag-and-drop interface [=elements=], such as draggable elements and their drop targets. Drop target information will be
            rendered visually by the author and provided to <a>assistive technologies</a> through an alternate modality.
          </p>
          <ul>
            <li><pref>aria-dropeffect</pref></li>
            <li><sref>aria-grabbed</sref></li>
          </ul>
        </section>
        <section id="attrs_relationships">
          <h3>Relationship Attributes</h3>
          <p>This section lists [=attributes=] that indicate <a>relationships</a> or associations between [=elements=] which cannot be readily determined from the document structure.</p>
          <ul>
            <li><pref>aria-activedescendant</pref></li>
            <li><pref>aria-colcount</pref></li>
            <li><pref>aria-colindex</pref></li>
            <li><pref>aria-colindextext</pref></li>
            <li><pref>aria-colspan</pref></li>
            <li><pref>aria-controls</pref></li>
            <li><pref>aria-describedby</pref></li>
            <li><pref>aria-details</pref></li>
            <li><pref>aria-errormessage</pref></li>
            <li><pref>aria-flowto</pref></li>
            <li><pref>aria-labelledby</pref></li>
            <li><pref>aria-owns</pref></li>
            <li><pref>aria-posinset</pref></li>
            <li><pref>aria-rowcount</pref></li>
            <li><pref>aria-rowindex</pref></li>
            <li><pref>aria-rowindextext</pref></li>
            <li><pref>aria-rowspan</pref></li>
            <li><pref>aria-setsize</pref></li>
          </ul>
        </section>
      </section>
      <section id="state_changes">
        <h3>State change notification</h3>
        <p>
          User agents MUST provide a way for assistive technologies to be notified when states change, either through <abbr title="Document Object Model">DOM</abbr> attribute change <a>events</a> or
          platform accessibility <abbr title="Application Programing Interfaces">API</abbr> events.
        </p>
      </section>
      <section id="state_prop_def">
        <h2>Definitions of States and Properties (all aria-* attributes)</h2>
        <p>
          Below is an alphabetical list of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a>states</a> and [=ARIA/properties=] to be used by authors. A detailed definition of
          each <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> state and [=ARIA/property=] follows this compact list.
        </p>
        <p id="index_state_prop" class="placeholder">Placeholder for index of states and properties</p>
        <div class="property" id="aria-activedescendant">
          <pdef>aria-activedescendant</pdef>
          <div class="property-description">
            <p>
              <a>Identifies</a> the currently active element when DOM focus is on a <rref>composite</rref> widget, <rref>combobox</rref>, <rref>textbox</rref>, <rref>group</rref>, or
              <rref>application</rref>.
            </p>
            <p>
              The <code>aria-activedescendant</code> property provides an alternative method of managing focus for interactive elements that might contain multiple focusable descendants, such as
              menus, grids, and toolbars. Instead of moving DOM focus among <a>accessibility descendants</a>, authors MAY set DOM focus on a container <a>element</a> that supports
              <code>aria-activedescendant</code> and then use <code>aria-activedescendant</code> to refer to the element that is active.
            </p>
            <p>Authors MUST ensure that one of the following two sets of conditions is met when setting the value of <code>aria-activedescendant</code> on an element with DOM focus:</p>
            <ol>
              <li>The value of <code>aria-activedescendant</code> refers to an <a>accessibility descendant</a>.</li>
              <li>
                The element with DOM focus is a <rref>combobox</rref>, <rref>textbox</rref> or <rref>searchbox</rref> with <pref>aria-controls</pref> referring to an element that supports
                <code>aria-activedescendant</code>, and the value of <code>aria-activedescendant</code> refers to an <a>accessibility descendant</a> of the controlled element. For example, in a
                <rref>combobox</rref>, focus can remain on the <rref>combobox</rref> while the value of <code>aria-activedescendant</code> on the <rref>combobox</rref> element refers to a descendant
                of a popup <rref>listbox</rref> that is controlled by the <rref>combobox</rref>.
              </li>
            </ol>
            <p>Authors SHOULD also ensure that the currently active descendant is visible and in view (or scrolls into view) when focused.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related">
                  <cite
                    ><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite
                  >
                  [[SVG2]] and
                  <cite
                    ><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite
                  >
                  [[DOM]] active
                </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_idref">ID reference</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-atomic">
          <pdef>aria-atomic</pdef>
          <div class="property-description">
            <p>
              <a>Indicates</a> whether <a>assistive technologies</a> will present all, or only parts of, the changed region based on the change notifications defined by the
              <pref>aria-relevant</pref> attribute.
            </p>
            <p>
              Both <a>accessibility <abbr title="Application Programing Interfaces">APIs</abbr></a> and the <cite><a href="https://www.w3.org/TR/dom/">Document Object Model</a></cite> [[DOM]] provide
              events to allow the assistive technologies to determine changed areas of the document.
            </p>
            <p>
              When the content of a <a>live region</a> changes, user agents SHOULD examine the changed <a>element</a> and traverse the ancestors to find the first element with
              <pref>aria-atomic</pref> set, and apply the appropriate behavior for the cases below.
            </p>
            <ol>
              <li>
                If none of the ancestors have explicitly set <pref>aria-atomic</pref>, the default is that <pref>aria-atomic</pref> is <code>false</code>, and assistive technologies will only present
                the changed node to the user.
              </li>
              <li>
                If <pref>aria-atomic</pref> is explicitly set to <code>false</code>, assistive technologies will stop searching up the ancestor chain and present only the changed node to the user.
              </li>
              <li>
                If <pref>aria-atomic</pref> is explicitly set to <code>true</code>, assistive technologies will present the entire contents of the element, including the author-defined live region
                label if one exists.
              </li>
            </ol>
            <p>When <pref>aria-atomic</pref> is <code>true</code>, assistive technologies can choose to combine several changes and present the entire changed region at once.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">All elements of the base markup</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_true-false">true/false</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row">false</th>
                <td class="value-description">Assistive technologies will present only the changed node or nodes.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">Assistive technologies will present the entire changed region as a whole, including the author-defined label if one exists.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-autocomplete">
          <pdef>aria-autocomplete</pdef>
          <div class="property-description">
            <p>
              <a>Indicates</a> whether inputting text could trigger display of one or more predictions of the user's intended value for a <rref>combobox</rref>, <rref>searchbox</rref>, or
              <rref>textbox</rref> and specifies how predictions would be presented if they were made.
            </p>
            <p>
              The <code>aria-autocomplete</code> property describes the type of interaction model a <rref>textbox</rref>, <rref>searchbox</rref>, or <rref>combobox</rref> employs when dynamically
              helping users complete text input. It distinguishes between two models: the inline model (<code>aria-autocomplete="inline"</code>) that presents a value completion prediction inside the
              text input and the list model (<code>aria-autocomplete="list"</code>) that presents a collection of possible values in a separate element that pops up adjacent to the text input. It is
              possible for an input to offer both models at the same time (<code>aria-autocomplete="both"</code>).
            </p>
            <p>
              The <code>aria-autocomplete</code> property is limited to describing predictive behaviors of an input element. Authors SHOULD either omit specifying a value for
              <code>aria-autocomplete</code> or set <code>aria-autocomplete</code> to <code>none</code> if an input element provides one or more input proposals where none of the proposals are
              dependent on the specific input provided by the user. For instance, a combobox where the value of <code>aria-autocomplete</code> would be <code>none</code> is a search field that
              displays suggested values by listing the 5 most recently used search terms without any filtering of the list based on the user's input. Elements with a role that supports
              <code>aria-autocomplete</code> have a default value for <code>aria-autocomplete</code> of <code>none</code>.
            </p>
            <p>
              When an inline suggestion is made as a user types in an input, suggested text for completing the value of the field dynamically appears in the field after the input cursor, and the
              suggested value is accepted as the value of the input if the user performs an action that causes focus to leave the field. When an element has <code>aria-autocomplete</code> set to
              <code>inline</code> or <code>both</code>, authors SHOULD ensure that the automatically suggested portion of the text is presented as selected text. This enables assistive technologies to
              distinguish between a user's input and the automatic suggestion and, in the event that the suggestion is not the desired value, enables the user to easily delete the suggestion or
              replace it by continuing to type.
            </p>
            <p>If an element has <code>aria-autocomplete</code> set to <code>list</code> or <code>both</code>, authors MUST ensure both of the following conditions are met:</p>
            <ol>
              <li>The element has a value specified for <pref>aria-controls</pref> that refers to the element that contains the collection of suggested values.</li>
              <li>The element has a value for <pref>aria-haspopup</pref> that matches the role of the element that contains the collection of suggested values.</li>
            </ol>
            <p>
              Some implementations of the list model require the user to perform an action, such as moving focus to the suggestion with the <kbd>Down Arrow</kbd> or clicking on the suggestion, in
              order to choose the suggestion. In such implementations, authors MAY manage focus by either using <pref>aria-activedescendant</pref> if the collection container supports it or by moving
              DOM focus to the suggestion. However, other implementations of the list model automatically highlight one suggestion as the selected value that will be accepted when the field loses
              focus, e.g., when the user presses the <kbd>Tab</kbd> key or clicks on a different field. If an element has <code>aria-autocomplete</code> set to <code>list</code> or <code>both</code>,
              and if a suggestion is automatically selected as the user provides input, authors MUST ensure all the following conditions are met:
            </p>
            <ol>
              <li>The collection of suggestions is presented in an element with a role that supports <pref>aria-activedescendant</pref>.</li>
              <li>
                The value of <code>aria-activedescendant</code> set on the input field is dynamically adjusted to refer to the element containing the selected suggestion as described in the definition
                of <pref>aria-activedescendant</pref>.
              </li>
              <li>DOM focus remains on the text input while the suggestions are displayed.</li>
            </ol>
            <p>
              The <code>aria-autocomplete</code> property is not intended to indicate the presence of a completion suggestion, and authors SHOULD NOT dynamically change its value in order to
              communicate the presence of a suggestion. When an element has <code>aria-autocomplete</code> set to <code>list</code> or <code>both</code>, authors SHOULD use the
              <sref>aria-expanded</sref> state to communicate whether the element that presents the suggestion collection is displayed.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"></td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_token">token</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row">inline</th>
                <td class="value-description">When a user is providing input, text suggesting one way to complete the provided input might be dynamically inserted after the caret.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">list</th>
                <td class="value-description">When a user is providing input, an element containing a collection of values that could complete the provided input might be displayed.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">both</th>
                <td class="value-description">
                  When a user is providing input, an element containing a collection of values that could complete the provided input might be displayed. If displayed, one value in the collection is
                  automatically selected, and the text needed to complete the automatically selected value appears after the caret in the input.
                </td>
              </tr>
              <tr>
                <th class="value-name" scope="row"><strong class="default">none (default)</strong></th>
                <td class="value-description">When a user is providing input, an automatic suggestion that attempts to predict how the user intends to complete the input is not displayed.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-braillelabel">
          <pdef>aria-braillelabel</pdef>
          <div class="property-description">
            <p><a>Defines</a> a string value that labels the current element, which is intended to be converted into Braille. See related <pref>aria-label</pref>.</p>
            <p>The purpose of <pref>aria-braillelabel</pref> is similar to that of <pref>aria-label</pref>. It provides the user with a recognizable name of the object in Braille.</p>
            <p>
              The <pref>aria-braillelabel</pref> property gives authors the ability to override how assistive technologies localize and express the accessible name of an element in Braille. Thus
              inappropriately using <pref>aria-braillelabel</pref> might inhibit users' ability to understand an element on braille interfaces. Authors SHOULD limit use of
              <pref>aria-braillelabel</pref> to instances where the name of an element when converted to Braille is not the desired user experience.
            </p>
            <p>When using <code>aria-braillelabel</code>, authors SHOULD also ensure that:</p>
            <ol>
              <li>The element to which <code>aria-braillelabel</code> is applied has a valid accessible name.</li>
              <li>The value of <code>aria-braillelabel</code> is not empty or does not contain only [=ascii whitespace|whitespace=] characters.</li>
              <li>
                The value of <code>aria-braillelabel</code> does not contain any characters in <a>Unicode Braille Patterns</a> or consists of only characters in <a>Unicode Braille Patterns</a>; the
                value does not only contain Braille Pattern dots-0.
              </li>
              <li>The value of <code>aria-braillelabel</code> is not identical to the element's accessible name.</li>
            </ol>
            <p>
              Authors MUST NOT specify <code>aria-braillelabel</code> on an element which has an explicit or implicit WAI-ARIA role where <code>aria-braillelabel</code> is
              <a href="#prohibitedattributes">prohibited</a>.
            </p>
            <p class="note">
              Note that <a>Assistive Technologies</a> with braille support can convert the accessible name to Braille. In addition, assistive technologies will be able to customize such braille output
              according to user preferences. Using only the accessible name, e.g., from content or via <code>aria-label</code> is <strong>almost always</strong> the better user experience and authors
              are <strong>strongly discouraged</strong> from using <code>aria-braillelabel</code> to replicate <code>aria-label</code>. Instead, <code>aria-braillelabel</code> is meant to be used only
              if the accessible name cannot provide an adequate braille representation, i.e., when a specialized braille description is very different from a text description converted to Braille. It
              is very important to note that when using <code>aria-braillelabel</code>, authors are solely responsible for localizing the attribute value so that it aligns with the document language.
              In addition, authors need to design a way to clearly communicate the use of this attribute to the user. For example, this could be done in the product documentation. This is even more
              important when the value consists of Unicode Braille Patterns because <a>Assistive Technologies</a> will pass such content directly to the user without applying user specific braille
              translations; in general, authors are <strong>strongly discouraged</strong> from using Unicode Braille Patterns in <code>aria-braillelabel</code>.
            </p>
            <p>
              <a>Assistive technologies</a> SHOULD use the value of <code>aria-braillelabel</code> when presenting the accessible name of an element in Braille, but SHOULD NOT change other
              functionality. For example, an assistive technology that provides aural rendering SHOULD use the accessible name.
            </p>
            <p><a>Assistive technologies</a> SHOULD expose the <code>aria-braillelabel</code> property as follows:</p>
            <ol>
              <li>
                If the value of <code>aria-braillelabel</code> does not contain characters in <a>Unicode Braille Patterns</a>, translate the value according to the user's preferred translation table.
              </li>
              <li>Otherwise, pass the value to the user without translation.</li>
            </ol>
            <p>The following example shows the use of <code>aria-braillelabel</code> to customize a button's name in braille output.</p>
            <pre class="example highlight">
&lt;button aria-braillelabel="****"&gt;
  &lt;img alt="4 stars" src="images/stars.jpg"&gt;
&lt;/button&gt;</pre
            >
            <p>In the previous example, a braille display would display "btn ****" in Braille rather than the verbose "btn gra 4 stars".</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">All elements of the base markup except for some roles or elements that prohibit its use</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_string">string</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-brailleroledescription">
          <pdef>aria-brailleroledescription</pdef>
          <div class="property-description">
            <p>
              <a>Defines</a> a human-readable, author-localized abbreviated description for the <a>role</a> of an <a>element</a>, which is intended to be converted into Braille. See related
              <pref>aria-roledescription</pref>.
            </p>
            <p>
              Some <a>assistive technologies</a>, such as screen readers, present the role of an element as part of the user experience. Such assistive technologies typically localize the name of the
              role, and they might customize it as well. Users of these assistive technologies depend on the presentation of the role name, such as "region," "button," or "slider," for an
              understanding of the purpose of the element and, if it is a widget, how to interact with it.
            </p>
            <p>
              The <code>aria-brailleroledescription</code> property gives authors the ability to override how <a>assistive technologies</a> localize and express the name of a role in Braille. Thus
              inappropriately using <code>aria-brailleroledescription</code> might inhibit users' ability to understand or interact with an element on braille interfaces. Authors SHOULD limit use of
              <code>aria-brailleroledescription</code> to clarifying the purpose of non-interactive container roles like <rref>group</rref> or <rref>region</rref>, or to providing a
              <em>more specific</em> description of a <rref>widget</rref> in a braille context.
            </p>
            <p>
              Authors MUST NOT use <code>aria-brailleroledescription</code> without providing <code>aria-roledescription</code>. Additionally, as with <code>aria-roledescription</code>, authors MUST
              NOT specify <code>aria-brailleroledescription</code> on an element which has an explicit or implicit WAI-ARIA role where <code>aria-brailleroledescription</code> is
              <a href="#prohibitedattributes">prohibited</a>.
            </p>
            <p>In general, <code>aria-brailleroledescription</code> is only meant to be used in rare cases when a <code>aria-roledescription</code> is excessively verbose when rendered in Braille.</p>
            <p>When using <code>aria-brailleroledescription</code>, authors SHOULD also ensure that:</p>
            <ol>
              <li>
                The element to which <code>aria-brailleroledescription</code> is applied has a valid <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role or has an implicit
                WAI-ARIA role semantic.
              </li>
              <li>The value of <code>aria-brailleroledescription</code> is not empty or does not contain only [=ascii whitespace|whitespace=] characters.</li>
              <li>
                The value of <code>aria-brailleroledescription</code> does not contain any characters in <a>Unicode Braille Patterns</a> or consists of only characters in
                <a>Unicode Braille Patterns</a>; the value does not only contain Braille Pattern dots-0.
              </li>
              <li>
                The value of <code>aria-brailleroledescription</code> should not be identical to the element's WAI-ARIA <code>aria-roledescription</code>, WAI-ARIA <code>role</code> or implicit
                WAI-ARIA role semantic.
              </li>
            </ol>
            <p class="note">
              Note that <a>Assistive Technologies</a> with braille support can convert <code>aria-roledescription</code> content to Braille. In addition, assistive technologies will be able to
              customize such braille output according to user preferences. Using only <code>aria-roledescription</code> is <strong>almost always</strong> the better user experience and authors are
              <strong>strongly discouraged</strong> from using <code>aria-brailleroledescription</code> to replicate <code>aria-roledescription</code>. Instead,
              <code>aria-brailleroledescription</code> is meant to be used only when <code>aria-roledescription</code> cannot provide an adequate braille representation, i.e., when a specialized
              braille description is very different from a text description converted to Braille. It is very important to note that when using <code>aria-brailleroledescription</code>, authors are
              solely responsible for localizing the attribute value so that it aligns with the document language. In addition, authors need to design a way to clearly communicate the use of this
              attribute to the user. For example, this could be done in the product documentation. This is even more important when the value consists of Unicode Braille Patterns because
              <a>Assistive Technologies</a> will pass such content directly to the user without applying user specific braille translations; in general, authors are
              <strong>strongly discouraged</strong> from using Unicode Braille Patterns in <code>aria-brailleroledescription</code>.
            </p>
            <p>User agents MUST NOT expose the <code>aria-brailleroledescription</code> property if any of the following conditions exist:</p>
            <ol>
              <li>
                The value of <code>aria-brailleroledescription</code> is empty or contains only whitespace characters, which includes standard [=ascii whitespace|whitespace=] and the empty Braille
                pattern: dots-0 (U+2800).
              </li>
              <li>
                The element to which <code>aria-brailleroledescription</code> is applied has an explicit or implicit WAI-ARIA role where <code>aria-brailleroledescription</code> is
                <a href="#prohibitedattributes">prohibited</a>.
              </li>
              <li>The element to which <code>aria-brailleroledescription</code> is applied does not have a valid WAI-ARIA <code>aria-roledescription</code>.</li>
            </ol>
            <p>
              <a>Assistive technologies</a> SHOULD use the value of <code>aria-brailleroledescription</code> when presenting the role of an element in Braille, but SHOULD NOT change other
              functionality based on the role of an element that has a value for <code>aria-brailleroledescription</code>. For example, an assistive technology that provides functions for navigating
              to the next <rref>region</rref> or <rref>button</rref> SHOULD allow those functions to navigate to regions and buttons that have an <code>aria-brailleroledescription</code>.
            </p>
            <p><a>Assistive technologies</a> SHOULD expose the <code>aria-brailleroledescription</code> property as follows:</p>
            <ol>
              <li>
                If the value of <code>aria-brailleroledescription</code> does not contain characters in <a>Unicode Braille Patterns</a>, translate the value according to the user's preferred
                translation table.
              </li>
              <li>Otherwise, pass the value to the user without translation.</li>
            </ol>

            <p>
              The following two examples show the use of <code>aria-brailleroledescription</code> to abbreviate the role of a repeated non-interactive "slide" container in a web-based presentation
              application.
            </p>
            <pre class="example highlight">
&lt;div role="article" aria-roledescription="slide" aria-brailleroledescription="sld" id="slide" aria-labelledby="slideheading"&gt;
&lt;h1 id="slideheading">Quarterly Report&lt;/h1&gt;
&lt;!-- remaining slide contents --&gt;
&lt;/div&gt;</pre
            >
            <pre class="example highlight">
&lt;article aria-roledescription="slide" aria-brailleroledescription="sld" id="slide" aria-labelledby="slideheading"&gt;
&lt;h1 id="slideheading">Quarterly Report&lt;/h1&gt;
&lt;!-- remaining slide contents --&gt;
&lt;/div&gt;</pre
            >
            <p>In the previous examples, a braille screen reader user would read "sld Quarterly Report" rather than the more verbose "slide Quarterly Report."</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">All elements of the base markup except for some roles or elements that prohibit its use</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_string">string</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="state" id="aria-busy">
          <sdef>aria-busy</sdef>
          <div class="state-description">
            <p><a>Indicates</a> an element is being modified and that assistive technologies could wait until the modifications are complete before exposing them to the user.</p>
            <p>
              The default value of <code>aria-busy</code> is <code>false</code> for all elements. When <code>aria-busy</code> is <code>true</code> for an element, assistive technologies can ignore
              changes to content that is an <a>accessibility descendant</a> that element and then process all changes made during the busy period as a single, atomic update when
              <code>aria-busy</code> becomes <code>false</code>.
            </p>
            <p>
              If it is necessary to make multiple additions, modifications, or removals within a container element that is already either partially or fully rendered, authors MAY set
              <code>aria-busy</code> to <code>true</code> on the container element before the first change, and then set it to <code>false</code> when the last change is complete. For example, if
              multiple changes to a <a>live region</a> should be spoken as a single unit of speech, authors MAY set <code>aria-busy</code> to <code>true</code> while the changes are being made and
              then set it to <code>false</code> when the changes are complete and ready to be spoken.
            </p>
            <p>
              If an element with role <rref>feed</rref> is marked busy, assistive technologies might defer rendering changes that occur inside the <code>feed</code> with the exception of
              user-initiated changes that occur inside the <rref>article</rref> that the user is reading during the busy period.
            </p>
            <p>
              If changes to a rendered <rref>widget</rref> would create a state where the <rref>widget</rref> is modifying <a href="#mustContain">Allowed Accessibility Child Roles</a> during script
              execution, authors MAY set <code>aria-busy</code> to <code>true</code> on the <rref>widget</rref> during the update process. For example, if a rendered tree grid required a set of
              simultaneous updates to multiple discontiguous branches, an alternative to replacing the complete tree element with a single update would be to mark the tree busy while each of the
              branches are modified.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="state-related-head" scope="row">Related Concepts:</th>
                <td class="state-related"> </td>
              </tr>
              <tr>
                <th class="state-applicability-head" scope="row">Used in Roles:</th>
                <td class="state-applicability">All elements of the base markup</td>
              </tr>
              <tr>
                <th class="state-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="state-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="state-value-head" scope="row">Value:</th>
                <td class="state-value"><a href="#valuetype_true-false">true/false</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row"><strong class="default">false (default)</strong>:</th>
                <td class="value-description">There are no expected updates for the element.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">The element is being updated.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="state" id="aria-checked">
          <sdef>aria-checked</sdef>
          <div class="state-description">
            <p><a>Indicates</a> the current "checked" <a>state</a> of checkboxes, radio buttons, and other <a>widgets</a>. See related <sref>aria-pressed</sref> and <sref>aria-selected</sref>.</p>
            <p>
              The <sref>aria-checked</sref> [=attribute=] indicates whether the <a>element</a> is checked (<code>true</code>), unchecked (<code>false</code>), or represents a group of other elements
              that have a mixture of checked and unchecked <span>values</span> (<code>mixed</code>). Most inputs only support values of <code>true</code> and <code>false</code>, but the
              <code>mixed</code> value is supported by certain tri-state inputs such as a <rref>checkbox</rref> or <rref>menuitemcheckbox</rref>.
            </p>
            <p>
              The <code>mixed</code> value is <em>not</em> supported on <rref>radio</rref>, <rref>menuitemradio</rref>, <rref>switch</rref> or any element that inherits from these, and [=user agents=]
              MUST treat a <code>mixed</code> value as equivalent to <code>false</code> for those <a>roles</a>.
            </p>
            <p>
              Examples using the <code>mixed</code> value of tri-state inputs are covered in the
              <cite
                ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite
              >.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="state-related-head" scope="row">Related Concepts:</th>
                <td class="state-related"> </td>
              </tr>
              <tr>
                <th class="state-applicability-head" scope="row">Used in Roles:</th>
                <td class="state-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="state-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="state-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="state-value-head" scope="row">Value:</th>
                <td class="state-value"><a href="#valuetype_tristate">tristate</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row">false</th>
                <td class="value-description">The element supports being checked but is not currently checked.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">mixed</th>
                <!-- make sure this value remains synced with its counterpart in #aria-pressed -->
                <td class="value-description">Indicates a mixed mode value for a tri-state checkbox or menuitemcheckbox.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">The element is checked.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row"><strong class="default">undefined</strong> (default)</th>
                <td class="value-description">The element does not support being checked.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-colcount">
          <pdef>aria-colcount</pdef>
          <div class="property-description">
            <p><a>Defines</a> the total number of columns in a <rref>table</rref>, <rref>grid</rref>, or <rref>treegrid</rref>. See related <pref>aria-colindex</pref>.</p>
            <p>
              If all of the columns are present in the <abbr title="Document Object Model">DOM</abbr>, it is not necessary to set this [=attribute=] as the <a>user agent</a> can automatically
              calculate the total number of columns. However, if only a portion of the columns is present in the <abbr title="Document Object Model">DOM</abbr> at a given moment, this attribute is
              needed to provide an explicit indication of the number of columns in the full table.
            </p>
            <p>
              Authors MUST set the value of <pref>aria-colcount</pref> to an integer equal to the number of columns in the full table. If the total number of columns is unknown, authors MUST set the
              value of <pref>aria-colcount</pref> to <code>-1</code> to indicate that the value should not be calculated by the user agent.
            </p>
            <p>The following example shows a grid with 16 columns, of which columns 2, 3, 4, and 9 are displayed to the user.</p>
            <pre class="example highlight">
&lt;div role="grid" <strong>aria-colcount="16"</strong>&gt;
  &lt;div role="rowgroup"&gt;
    &lt;div role="row"&gt;
      &lt;span role="columnheader" aria-colindex="2"&gt;First Name&lt;/span&gt;
      &lt;span role="columnheader" aria-colindex="3"&gt;Last Name&lt;/span&gt;
      &lt;span role="columnheader" aria-colindex="4"&gt;Company&lt;/span&gt;
      &lt;span role="columnheader" aria-colindex="9"&gt;Phone&lt;/span&gt;
    &lt;/div&gt;
  &lt;/div&gt;
  &lt;div role="rowgroup"&gt;
    &lt;div role="row"&gt;
      &lt;span role="gridcell" aria-colindex="2"&gt;Fred&lt;/span&gt;
      &lt;span role="gridcell" aria-colindex="3"&gt;Jackson&lt;/span&gt;
      &lt;span role="gridcell" aria-colindex="4"&gt;Acme, Inc.&lt;/span&gt;
      &lt;span role="gridcell" aria-colindex="9"&gt;555-1234&lt;/span&gt;
    &lt;/div&gt;
    &lt;div role="row"&gt;
      &lt;span role="gridcell" aria-colindex="2"&gt;Sara&lt;/span&gt;
      &lt;span role="gridcell" aria-colindex="3"&gt;James&lt;/span&gt;
      &lt;span role="gridcell" aria-colindex="4"&gt;Acme, Inc.&lt;/span&gt;
      &lt;span role="gridcell" aria-colindex="9"&gt;555-1235&lt;/span&gt;
    &lt;/div&gt;
   &#8230;
  &lt;/div&gt;
&lt;/div&gt;</pre
            >
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_integer">integer</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-colindex">
          <pdef>aria-colindex</pdef>
          <div class="property-description">
            <p>
              <a>Defines</a> an [=element|element's=] column index or position with respect to the total number of columns within a <rref>table</rref>, <rref>grid</rref>, or <rref>treegrid</rref>. See
              related <pref>aria-colindextext</pref>, <pref>aria-colcount</pref>, and <pref>aria-colspan</pref>.
            </p>
            <p>
              If all of the columns are present in the <abbr title="Document Object Model">DOM</abbr>, it is not necessary to set this <a>attribute</a> as the <a>user agent</a> can automatically
              calculate the column index of each cell or <rref>gridcell</rref>. However, if only a portion of the columns is present in the <abbr title="Document Object Model">DOM</abbr> at a given
              moment, this attribute is needed to provide an explicit indication of the column of each cell or gridcell with respect to the full table.
            </p>
            <p>
              Authors MUST set the <span>value</span> for <pref>aria-colindex</pref> to an integer greater than or equal to 1, greater than the <pref>aria-colindex</pref> value of any previous
              elements within the same row, and less than or equal to the number of columns in the full table. For a cell or gridcell which spans multiple columns, authors MUST set the value of
              <pref>aria-colindex</pref> to the start of the span.
            </p>
            <p>
              If the set of columns which is present in the <abbr title="Document Object Model">DOM</abbr> is contiguous, and if there are no cells which span more than one row or column in that set,
              then authors MAY place <pref>aria-colindex</pref> on each row, setting the value to the index of the first column of the set. Otherwise, authors SHOULD place
              <pref>aria-colindex</pref> on all of the <a>accessibility children</a> of each row.
            </p>
            <p>
              The following example shows a grid with 16 columns, of which columns 2 through 5 are displayed to the user. Because the set of columns is contiguous, <pref>aria-colindex</pref> can be
              placed on each row.
            </p>
            <pre class="example highlight">
&lt;div role="grid" aria-colcount="16"&gt;
  &lt;div role="rowgroup"&gt;
    &lt;div role="row" <strong>aria-colindex="2"</strong>&gt;
      &lt;span role="columnheader"&gt;First Name&lt;/span&gt;
      &lt;span role="columnheader"&gt;Last Name&lt;/span&gt;
      &lt;span role="columnheader"&gt;Company&lt;/span&gt;
      &lt;span role="columnheader"&gt;Address&lt;/span&gt;
    &lt;/div&gt;
  &lt;/div&gt;
  &lt;div role="rowgroup"&gt;
    &lt;div role="row" <strong>aria-colindex="2"</strong>&gt;
      &lt;span role="gridcell"&gt;Fred&lt;/span&gt;
      &lt;span role="gridcell"&gt;Jackson&lt;/span&gt;
      &lt;span role="gridcell"&gt;Acme, Inc.&lt;/span&gt;
      &lt;span role="gridcell"&gt;123 Broad St.&lt;/span&gt;
    &lt;/div&gt;
    &lt;div role="row" <strong>aria-colindex="2"</strong>&gt;
      &lt;span role="gridcell"&gt;Sara&lt;/span&gt;
      &lt;span role="gridcell"&gt;James&lt;/span&gt;
      &lt;span role="gridcell"&gt;Acme, Inc.&lt;/span&gt;
      &lt;span role="gridcell"&gt;123 Broad St.&lt;/span&gt;
    &lt;/div&gt;
   &#8230;
  &lt;/div&gt;
&lt;/div&gt;</pre
            >
            <p>
              The following example shows a grid with 16 columns, of which columns 2 through 5 are displayed to the user. While the set of columns is contiguous, some of the cells span multiple rows.
              As a result, <pref>aria-colindex</pref> needs to be placed on all of the <a>accessibility children</a> of each row.
            </p>
            <pre class="example highlight">
&lt;div role="grid" aria-colcount="16"&gt;
  &lt;div role="rowgroup"&gt;
    &lt;div role="row"&gt;
      &lt;span role="columnheader" <strong>aria-colindex="2"</strong>&gt;First Name&lt;/span&gt;
      &lt;span role="columnheader" <strong>aria-colindex="3"</strong>&gt;Last Name&lt;/span&gt;
      &lt;span role="columnheader" <strong>aria-colindex="4"</strong>&gt;Company&lt;/span&gt;
      &lt;span role="columnheader" <strong>aria-colindex="5"</strong>&gt;Address&lt;/span&gt;
    &lt;/div&gt;
  &lt;/div&gt;
  &lt;div role="rowgroup"&gt;
    &lt;div role="row"&gt;
      &lt;span role="gridcell" <strong>aria-colindex="2"</strong>&gt;Fred&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-colindex="3"</strong>&gt;Jackson&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-colindex="4"</strong> aria-rowspan="2"&gt;Acme, Inc.&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-colindex="5"</strong> aria-rowspan="2"&gt;123 Broad St.&lt;/span&gt;
    &lt;/div&gt;
    &lt;div role="row"&gt;
      &lt;span role="gridcell" <strong>aria-colindex="2"</strong>&gt;Sara&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-colindex="3"</strong>&gt;James&lt;/span&gt;
    &lt;/div&gt;
   &#8230;
  &lt;/div&gt;
&lt;/div&gt;</pre
            >
            <p>
              The following example shows a grid with 16 columns, of which columns 2, 3, 4, and 9 are displayed to the user. Because the set of columns is non-contiguous,
              <pref>aria-colindex</pref> needs to be placed on all of the <a>accessibility children</a> of each row.
            </p>
            <pre class="example highlight">
&lt;div role="grid" aria-colcount="16"&gt;
  &lt;div role="rowgroup"&gt;
    &lt;div role="row"&gt;
      &lt;span role="columnheader" <strong>aria-colindex="2"</strong>&gt;First Name&lt;/span&gt;
      &lt;span role="columnheader" <strong>aria-colindex="3"</strong>&gt;Last Name&lt;/span&gt;
      &lt;span role="columnheader" <strong>aria-colindex="4"</strong>&gt;Company&lt;/span&gt;
      &lt;span role="columnheader" <strong>aria-colindex="9"</strong>&gt;Phone&lt;/span&gt;
    &lt;/div&gt;
  &lt;/div&gt;
  &lt;div role="rowgroup"&gt;
    &lt;div role="row"&gt;
      &lt;span role="gridcell" <strong>aria-colindex="2"</strong>&gt;Fred&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-colindex="3"</strong>&gt;Jackson&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-colindex="4"</strong>&gt;Acme, Inc.&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-colindex="9"</strong>&gt;555-1234&lt;/span&gt;
    &lt;/div&gt;
    &lt;div role="row"&gt;
      &lt;span role="gridcell" <strong>aria-colindex="2"</strong>&gt;Sara&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-colindex="3"</strong>&gt;James&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-colindex="4"</strong>&gt;Acme, Inc.&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-colindex="9"</strong>&gt;555-1235&lt;/span&gt;
    &lt;/div&gt;
   &#8230;
  &lt;/div&gt;
&lt;/div&gt;</pre
            >
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_integer">integer</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-colindextext">
          <pdef>aria-colindextext</pdef>
          <div class="property-description">
            <p><a>Defines</a> a human readable text alternative of <pref>aria-colindex</pref>. See related <pref>aria-rowindextext</pref>.</p>
            <p>
              Authors SHOULD only use <code>aria-colindextext</code> when the provided or calculated value of <pref>aria-colindex</pref> is not meaningful or does not reflect the displayed index, as
              is the case with spreadsheets and chess boards.
            </p>
            <p>
              Authors SHOULD NOT use <code>aria-colindextext</code> as a replacement for <pref>aria-colindex</pref> because some assistive technologies rely upon the numeric column index for the
              purpose of keeping track of the user's position or providing alternative table navigation.
            </p>
            <p class="note">
              Unlike <pref>aria-colindex</pref>, <code>aria-colindextext</code> is not a supported property of <rref>row</rref> because user agents have no way to reliably calculate
              <code>aria-colindextext</code> for the purpose of exposing its value on the <rref>cell</rref> or <rref>gridcell</rref>.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_integer">string</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-colspan">
          <pdef>aria-colspan</pdef>
          <div class="property-description">
            <p>
              <a>Defines</a> the number of columns spanned by a cell or gridcell within a <rref>table</rref>, <rref>grid</rref>, or <rref>treegrid</rref>. See related <pref>aria-colindex</pref> and
              <pref>aria-rowspan</pref>.
            </p>
            <p>
              This <a>attribute</a> is intended for cells and gridcells which are not contained in a native table. When defining the column span of cells or gridcells in a native table, authors SHOULD
              use the host language's attribute instead of <pref>aria-colspan</pref>. If <pref>aria-colspan</pref> is used on an element for which the host language provides an equivalent attribute,
              [=user agents=] MUST ignore the value of <pref>aria-colspan</pref> and instead expose the value of the host language's attribute to <a>assistive technologies</a>.
            </p>
            <p>
              Authors MUST set the <span>value</span> of <pref>aria-colspan</pref> to an integer greater than or equal to 1 and less than the value which would cause the cell or gridcell to overlap
              the next cell or gridcell in the same row.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_integer">integer</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-controls">
          <pdef>aria-controls</pdef>
          <div class="property-description">
            <p><a>Identifies</a> the <a>element</a> (or elements) whose contents or presence are controlled by the current element. See related <pref>aria-owns</pref>.</p>
            <p>For example:</p>
            <ul>
              <li>A table of contents tree view can control the content of a neighboring document pane.</li>
              <li>A group of checkboxes can control what commodity prices are tracked live in a table or graph.</li>
              <li>A tab controls the display of its associated tab panel.</li>
            </ul>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <!--
					<tr>
						<th class="property-related-head" scope="row">Related Concepts:</th>
						<td class="property-related"><cite><a href="https://www.w3.org/TR/2007/WD-xml-events-20070216/"><abbr title="Extensible Markup Language">XML</abbr> Events</a></cite> [[XML-EVENTS]] object hyperlink target in <cite><a href="https://www.w3.org/TR/2002/REC-xhtml1-20020801/">HTML</a></cite> [[XHTML11]]</td>
					</tr>
					-->
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">All elements of the base markup</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_idref_list">ID reference list</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="state" id="aria-current">
          <sdef>aria-current</sdef>
          <div class="state-description">
            <p><a>Indicates</a> the <a>element</a> that represents the current item within a container or set of related elements.</p>
            <p>
              The <sref>aria-current</sref> <a>attribute</a> is a token type. Any value not included in the list of allowed values SHOULD be treated by <a>assistive technologies</a> as if the value
              <code>true</code> had been provided. If the attribute is not present or its value is the empty string or <code>undefined</code>, the default value of <code>false</code> applies and the
              <sref>aria-current</sref> <a>state</a> MUST NOT be exposed by user agents or assistive technologies.
            </p>
            <p>The <sref>aria-current</sref> attribute is used when an element within a set of related elements is visually styled to indicate it is the current item in the set. For example:</p>
            <ul>
              <li>A <code>page</code> token used to indicate a page within a set of pages, where the element is visually styled to represent the current page.</li>
              <li>A <code>step</code> token used to indicate a step within a step-based process, where the element is visually styled to represent the current step.</li>
              <li>A <code>location</code> token used to indicate the element that is visually styled as the current component, such as within a flow chart.</li>
              <li>A <code>date</code> token used to indicate the current date within a calendar or other date collection.</li>
              <li>A <code>time</code> token used to indicate the current time within a timetable or other time collection.</li>
            </ul>
            <p>Authors SHOULD only mark one element in a set of elements as current with <sref>aria-current</sref>.</p>
            <p>
              Authors SHOULD NOT use the <sref>aria-current</sref> attribute as a substitute for <sref>aria-selected</sref> in widgets where <sref>aria-selected</sref> has the same meaning. For
              example, in a <rref>tablist</rref>, <sref>aria-selected</sref> is used on a <rref>tab</rref> to indicate the currently-displayed <rref>tabpanel</rref>.
            </p>
            <p class="note">
              In some use cases for widgets that support <sref>aria-selected</sref>, current and selected can have different meanings and can both be used within the same set of elements. For example,
              <code>aria-current="page"</code> can be used in a navigation <rref>tree</rref> to indicate which page is currently displayed, while <code>aria-selected="true"</code> indicates which page
              will be displayed if the user activates the <rref>treeitem</rref>. Furthermore, the same tree can support operating on one or more selected pages (treeitems) by way of a context menu
              containing options such as "delete" and "move."
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="state-related-head" scope="row">Related Concepts:</th>
                <td class="state-related"> </td>
              </tr>
              <tr>
                <th class="state-applicability-head" scope="row">Used in Roles:</th>
                <td class="state-applicability">All elements of the base markup</td>
              </tr>
              <tr>
                <th class="state-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="state-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="state-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_token">token</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row">page</th>
                <td class="value-description">Represents the current page within a set of pages.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">step</th>
                <td class="value-description">Represents the current step within a process.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">location</th>
                <td class="value-description">Represents the current location within an environment or context.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">date</th>
                <td class="value-description">Represents the current date within a collection of dates.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">time</th>
                <td class="value-description">Represents the current time within a set of times.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">Represents the current item within a set.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row"><strong class="default">false (default)</strong></th>
                <td class="value-description">Does not represent the current item within a set.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-describedby">
          <pdef>aria-describedby</pdef>
          <div class="property-description">
            <p><a>Identifies</a> the <a>element</a> (or elements) that describes the <a>object</a>. See related <pref>aria-labelledby</pref> and <pref>aria-description</pref>.</p>
            <p>
              The <pref>aria-labelledby</pref> attribute is similar to <pref>aria-describedby</pref> in that both reference other elements to calculate a text alternative (an accessible name, and
              description, respectively). While a concise accessible name is preferable, a description can either be concise, or provide more verbose information.
            </p>
            <!-- keep previous sentence synced with the associated description in #aria-labelledby -->
            <p>
              The element or elements referenced by the aria-describedby comprise the entire description. Include ID references to multiple elements if necessary, or enclose a set of elements (e.g.,
              paragraphs) with the element referenced by the ID.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related">
                  <ul>
                    <li><code>&lt;[^label^]&gt;</code> in HTML</li>
                    <li>online help</li>
                    <li>HTML table cell headers</li>
                  </ul>
                </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">All elements of the base markup</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_idref_list">ID reference list</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-description">
          <pdef>aria-description</pdef>
          <div class="property-description">
            <p><a>Defines</a> a string value that describes or annotates the current element. See related <pref>aria-describedby</pref>.</p>
            <p>
              The <pref>aria-description</pref> attribute is similar to <pref>aria-label</pref> in that both provide a flat string to associate with the element (an accessible description, and name,
              respectively). Unlike an accessible name, which is generally preferred to be concise, a description can provide more verbose information, as necessary.
            </p>
            <p>
              The purpose of <pref>aria-description</pref> is the same as that of <pref>aria-describedby</pref>. It provides the user with additional descriptive text for the object. The most common
              <a>accessibility <abbr title="Application Programing Interfaces">API</abbr></a> mapping for a description is the <a class="informative">accessible description</a> property. User agents
              MUST give precedence to <pref>aria-describedby</pref> over <pref>aria-description</pref> when computing the accessible description property.
            </p>
            <p>
              In cases where providing a visible description is not the desired user experience, authors MAY set the accessible description of the element using <pref>aria-description</pref>. However,
              if the description text is available in the DOM, authors SHOULD NOT use <pref>aria-description</pref>, but should use one of the following instead:
            </p>
            <ul>
              <li>
                Authors SHOULD use <pref>aria-describedby</pref> when the related description or annotation elements contain a simple, small description that is best experienced as a flat string,
                rather than by having the user navigate to them.
              </li>
              <li>
                Authors SHOULD use <pref>aria-details</pref> when the related description or annotation elements contain useful semantics or structure, or there is a lot of content within them, making
                it difficult to experience as a flat string. Using <pref>aria-details</pref> will allow assistive technology users to visit the structured content and provide additional navigation
                commands, making it easier to understand the structure, or to experience the information in smaller pieces.
              </li>
            </ul>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"><code>[^html-global/title^]</code> attribute in HTML</td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">All elements of the base markup</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_string">string</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-details">
          <pdef>aria-details</pdef>
          <div class="property-description">
            <p><a>Identifies</a> the <a>element</a> (or elements) that provide additional information related to the <a>object</a>. See related <pref>aria-describedby</pref>.</p>
            <p>
              The <code>aria-details</code> property is for referencing elements that provide more detailed information than would normally be provided via <pref>aria-describedby</pref>. The presence
              of <code>aria-details</code> enables <a>assistive technologies</a> to make users aware of the availability of extended information and navigate to it. Authors SHOULD ensure that elements
              referenced by <code>aria-details</code> are visible to all users.
            </p>
            <p>
              Assistive technologies can use the role of elements referenced by the <code>aria-details</code> property to help users understand the types of information associated with the element.
              Authors MAY convey the type of details associated with an element as follows:
            </p>
            <ul>
              <li>Comment: <code>aria-details</code> refers to an element with role <rref>comment</rref>.</li>
              <li>Definition: <code>aria-details</code> is applied to an element with role <rref>term</rref> and refers to an element with role <rref>definition</rref>.</li>
              <li>
                Caption: <code>aria-details</code> is applied to an element with role <rref>figure</rref> and refers to an element with role <rref>caption</rref>, or an element within a
                <code>caption</code>.
              </li>
              <li>Footnote: <code>aria-details</code> refers to an element with role <code>doc-footnote</code>. This role is defined in [[DPUB-ARIA-1.0]].</li>
              <li>Endnote: <code>aria-details</code> refers to an element with role <code>doc-endnote</code>. This role is defined in [[DPUB-ARIA-1.0]].</li>
              <li>Description or general annotation: <code>aria-details</code> refers to an element with any other role.</li>
            </ul>

            <p>
              Unlike elements referenced by <code>aria-describedby</code>, elements referenced by <code>aria-details</code> are not used in the Accessible
              <a href="#mapping_additional_nd_description" class="accname">Description Computation</a> as defined in the Accessible Name and Description specification. Thus, the content of elements
              referenced by <code>aria-details</code> are not flattened to a string when presented to assistive technology users. This makes <code>aria-details</code> particularly useful when
              converting the information to a string would cause a loss of information or make the extended information more difficult to understand.
            </p>
            <p>
              The <code>aria-details</code> property supports referring to multiple elements. For example, a paragraph in a document editor might reference multiple comments that are not related to
              each other. If a user agent relies on an accessibility API that does not support exposing multiple descriptive relations, the user agent SHOULD expose the relationship to the first
              element referenced by <code>aria-details</code>.
            </p>
            <p>
              It is valid for an element to have both <code>aria-details</code> and a description specified with either <code>aria-describedby</code> or <code>aria-description</code>. If a user agent
              relies on an accessibility API that does not support exposing multiple descriptive relations, and if an element has both <code>aria-details</code> and <rref>aria-describedby</rref>, the
              user agent SHOULD expose the <code>aria-details</code> relation and the description string computed from the <rref>aria-describedby</rref> relationship.
            </p>
            <p>
              A common use for <code>aria-details</code> is in digital publishing where an extended description needs to be conveyed in a book that requires structural markup or the embedding of other
              technology to provide illustrative content. The following example demonstrates this scenario.
            </p>
            <pre class="example highlight">
                                &lt;!-- Provision of an extended description --&gt;
                                &lt;img src="pythagorean.jpg" alt="Pythagorean Theorem" aria-details="det"&gt;
                                &lt;details id="det"&gt;
                                  &lt;summary&gt;Example&lt;/summary&gt;
                                  &lt;p&gt;
                                    The Pythagorean Theorem is a relationship in Euclidean Geometry between the three sides of
                                    a right triangle, where the square of the hypotenuse is the sum of the squares of the two
                                    opposing sides.
                                  &lt;/p&gt;
                                  &lt;p&gt;
                                    The following drawing illustrates an application of the Pythagorean Theorem when used to
                                    construct a skateboard ramp.
                                  &lt;/p&gt;
                                  &lt;object data="skatebd-ramp.svg"  type="image/svg+xml"&gt;&lt;/object&gt;
                                  &lt;p&gt;
                                    In this example you will notice a skateboard ramp with a base and vertical board whose width
                                    is the width of the ramp. To compute how long the ramp must be, simply calculate the
                                    base length, square it, sum it with the square of the height of the ramp, and take the
                                    square root of the sum.
                                  &lt;/p&gt;
                                &lt;/details&gt;
				</pre
            >
            <p>Alternatively, <code>aria-details</code> can refer to a link to a web page having the extended description, as shown in the following example.</p>
            <pre class="example highlight">
                                &lt;!-- Provision of an extended description --&gt;
                                &lt;img src="pythagorean.jpg" alt="Pythagorean Theorem" aria-details="det"&gt;
                                &lt;p&gt;
                                  See an &lt;a href="http://foo.com/pt.html" id="det"&gt;Application of the Pythagorean Theorem&lt;/a&gt;.
                                &lt;/p&gt;
				</pre
            >
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">All elements of the base markup</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_idref_list">ID reference list</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="state" id="aria-disabled">
          <sdef>aria-disabled</sdef>
          <div class="state-description">
            <p>
              <a>Indicates</a> that the <a>element</a> is <a>perceivable</a> but disabled, so it is not editable or otherwise <a>operable</a>. See related <sref>aria-hidden</sref> and
              <pref>aria-readonly</pref>.
            </p>
            <p>
              For example, irrelevant options in a radio group can be disabled. Disabled elements might not receive focus from the tab order. For some disabled elements, applications might choose not
              to support navigation to descendants. In addition to setting the <sref>aria-disabled</sref> attribute, authors SHOULD change the appearance (grayed out, etc.) to indicate that the item
              has been disabled.
            </p>
            <p>
              The <a>state</a> of being disabled applies to the element with aria-disabled and all focusable descendant elements of the element on which the <sref>aria-disabled</sref>
              <a>attribute</a> is applied.
            </p>
            <p class="note">
              While <sref>aria-disabled</sref> and proper scripting can successfully disable an element with role <rref>link</rref>, fully disabling a host language equivalent can be problematic.
              Authors are advised not to use <sref>aria-disabled</sref> on elements that cannot be disabled through features of the host language alone.
            </p>
            <p class="note" title="Usage on columnheader, rowheader and row">
              While <sref>aria-disabled</sref> is currently supported on <rref>columnheader</rref>, <rref>rowheader</rref>, and <rref>row</rref>, in a future version the working group plans to
              prohibit its use on elements with any of those three roles except when they are in the context of a <rref>grid</rref> or <rref>treegrid</rref>.
            </p>
            <p class="note">This state is being deprecated as a global state in ARIA 1.2. In future versions it will only be allowed on roles where it is specifically supported.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="state-related-head" scope="row">Related Concepts:</th>
                <td class="state-related"> </td>
              </tr>
              <tr>
                <th class="state-applicability-head" scope="row">Used in Roles:</th>
                <td class="state-applicability">Use as a global deprecated in ARIA 1.2</td>
              </tr>
              <tr>
                <th class="state-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="state-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="state-value-head" scope="row">Value:</th>
                <td class="state-value"><a href="#valuetype_true-false">true/false</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row"><strong class="default">false (default)</strong></th>
                <td class="value-description">The element is enabled.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">The element and all focusable descendants are disabled and its value cannot be changed by the user.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property deprecated" id="aria-dropeffect">
          <pdef>aria-dropeffect</pdef>
          <div class="property-description">
            <p>[Deprecated in ARIA 1.1] Indicates what functions can be performed when a dragged object is released on the drop target.</p>
            <p class="note">
              The <code>aria-dropeffect</code> property is expected to be replaced by a new feature in a future version of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>. Authors
              are therefore advised to treat <code>aria-dropeffect</code> as <a>deprecated</a>.
            </p>
            <p>
              This [=ARIA/property=] allows assistive technologies to convey the possible drag options available to users, including whether a pop-up menu of choices is provided by the application.
              Typically, drop effect functions can only be provided once an object has been grabbed for a drag operation as the drop effect functions available are dependent on the object being
              dragged.
            </p>
            <p>
              More than one drop effect can be supported for a given <a>element</a>. Therefore, the value of this <a>attribute</a> is a space-separated set of tokens indicating the possible effects,
              or <code>none</code> if there is no supported operation. In addition to setting the <pref>aria-dropeffect</pref> attribute, authors SHOULD show a visual indication of potential drop
              targets.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">All elements of the base markup</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_token_list">token list</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row">copy</th>
                <td class="value-description">A duplicate of the source object will be dropped into the target.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">execute</th>
                <td class="value-description">A function supported by the drop target is executed, using the drag source as an input.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">link</th>
                <td class="value-description">A reference or shortcut to the dragged object will be created in the target object.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">move</th>
                <td class="value-description">The source object will be removed from its current location and dropped into the target.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row"><strong class="default">none (default)</strong></th>
                <td class="value-description">
                  No operation can be performed; effectively cancels the drag operation if an attempt is made to drop on this object. Ignored if combined with any other token value. e.g., 'none copy'
                  is equivalent to a 'copy' value.
                </td>
              </tr>
              <tr>
                <th class="value-name" scope="row">popup</th>
                <td class="value-description">
                  There is a popup menu or dialog that allows the user to choose one of the drag operations (copy, move, link, execute) and any other drag functionality, such as cancel.
                </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-errormessage">
          <pdef>aria-errormessage</pdef>
          <div class="property-description">
            <p><a>Identifies</a> the <a>element</a> (or elements) that provides an error message for an <a>object</a>. See related <sref>aria-invalid</sref> and <pref>aria-describedby</pref>.</p>
            <p>
              The <code>aria-errormessage</code> attribute references other elements that contain error message text. Authors MUST use <sref>aria-invalid</sref> in conjunction with
              <code>aria-errormessage</code>.
            </p>
            <p>
              When the value of an object is not valid, <sref>aria-invalid</sref> is set to <code>true</code>, which indicates that the message contained by elements referenced by
              <code>aria-errormessage</code> is pertinent.
            </p>
            <p>
              When an object is in a valid state, it has either <sref>aria-invalid</sref> set to <code>false</code> or it does not have the <sref>aria-invalid</sref> attribute. Authors MAY use
              <code>aria-errormessage</code> on an object that is currently valid, but only if the elements referenced by <code>aria-errormessage</code> are [=element/hidden from all users=], because
              the message they contain is not pertinent.
            </p>
            <p>
              When <code>aria-errormessage</code> is pertinent, authors MUST ensure the content is not [=element/hidden from all users=] so users can navigate to and examine the error message.
              Similarly, when <code>aria-errormessage</code> is not pertinent, authors MUST either ensure the content is [=element/hidden from all users=] or remove the
              <code>aria-errormessage</code> attribute or its value.
            </p>
            <p>User agents MUST NOT expose <code>aria-errormessage</code> for an object with an <sref>aria-invalid</sref> value of <code>false</code>.</p>
            <p>
              Authors MAY call attention to a newly rendered error message with a live region by either applying an <pref>aria-live</pref> property or using one of the
              <a href="#live_region_roles">live region roles</a>, such as <rref>alert</rref>. A live region is appropriate when an error message is displayed to users after they have provided an
              invalid value.
            </p>
            <p>
              A typical message describes what is wrong and informs users what is required. For example, an error message might be,
              <q>Invalid time: the time must be between 9:00 AM and 5:00 PM.</q> The following example code shows markup for an initial valid state and for a subsequent invalid state. Note the changes
              to <sref>aria-invalid</sref> on the text input <a>object</a>, and to <pref>aria-live</pref> on the <a>element</a> containing the text of the error message:
            </p>
            <pre class="example highlight">
				&lt;!-- Initial valid state --&gt;
				&lt;label for="startTime"&gt; Please enter a start time for the meeting: &lt;/label&gt;
				&lt;input id="startTime" type="text" aria-errormessage="msgID" value="" aria-invalid="false"&gt;
				&lt;span id="msgID" aria-live="assertive"&gt;&lt;span style="visibility:hidden"&gt;Invalid time: the time must be between 9:00 AM and 5:00 PM&lt;/span&gt;&lt;/span&gt;

				&lt;!-- User has input an invalid value --&gt;
				&lt;label for="startTime"&gt; Please enter a start time for the meeting: &lt;/label&gt;
				&lt;input id="startTime" type="text" aria-errormessage="msgID" aria-invalid="true" value="11:30 PM" &gt;
				&lt;span id="msgID" aria-live="assertive"&gt;&lt;span style="visibility:visible"&gt;Invalid time: the time must be between 9:00 AM and 5:00 PM&lt;/span&gt;&lt;/span&gt;
				</pre
            >
            <p class="note">
              This example uses <code>aria-live="assertive"</code> to indicate that assistive technologies should immediately announce the error message rather than completing other queued
              announcements first. This increases the likelihood that users are aware of the error message before they move focus out of the input.
            </p>
            <p class="note">This state is being deprecated as a global state in ARIA 1.2. In future versions it will only be allowed on roles where it is specifically supported.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Use as a global deprecated in ARIA 1.2</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_idref_list">ID reference list</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="state" id="aria-expanded">
          <sdef>aria-expanded</sdef>
          <div class="state-description">
            <p><a>Indicates</a> whether a grouping element that is the <a>accessibility child</a> of or is controlled by this element is expanded or collapsed.</p>
            <p>
              The <sref>aria-expanded</sref> attribute is applied to a focusable, interactive element that toggles visibility of content in another element. For example, it is applied to a parent
              <rref>treeitem</rref> to indicate whether its child branch of the tree is shown. Similarly, it can be applied to a <rref>button</rref> that controls visibility of a section of page
              content.
            </p>
            <p>
              If a grouping container that can be expanded or collapsed is not the <a>accessibility child</a> of the element that has the <sref>aria-expanded</sref> attribute, the author SHOULD
              identify the controlling relationship by referencing the container from the element that has <sref>aria-expanded</sref> with the <pref>aria-controls</pref> property.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="state-related-head" scope="row">Related Concepts:</th>
                <td class="state-related"></td>
              </tr>
              <tr>
                <th class="state-applicability-head" scope="row">Used in Roles:</th>
                <td class="state-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="state-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="state-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="state-value-head" scope="row">Value:</th>
                <td class="state-value"><a href="#valuetype_true-false-undefined">true/false/undefined</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row">false</th>
                <td class="value-description">The grouping element this element controls or is the accessibility parent of is collapsed.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">The grouping element this element controls or is the accessibility parent of is expanded.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row"><strong class="default">undefined (default)</strong></th>
                <td class="value-description">The element does not own or control a grouping element that is expandable.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-flowto">
          <pdef>aria-flowto</pdef>
          <div class="property-description">
            <p>
              <a>Identifies</a> the next <a>element</a> (or elements) in an alternate reading order of content which, at the user's discretion, allows assistive technology to override the general
              default of reading in document source order.
            </p>
            <p>
              When <pref>aria-flowto</pref> has a single ID reference, it allows <a>assistive technologies</a> to, at the user's request, forego normal document reading order and go to the targeted
              <a>object</a>.
              <!-- [No longer ref XHTML2] <pref>aria-flowto</pref> in subsequent elements would follow a process similar to <cite><a href="https://www.w3.org/TR/2006/WD-xhtml2-20060726/mod-hyperAttributes.html#adef_hyperAttributes_nextfocus">next focus in <abbr title="Extensible Hypertext Markup Language">XHTML</abbr>2</a></cite> ([[XHTML2]]). -->
              However, when <pref>aria-flowto</pref> is provided with multiple ID references, assistive technologies SHOULD present the referenced elements as path choices.
            </p>
            <p>
              In the case of one or more ID references, [=user agents=] or assistive technologies SHOULD give the user the option of navigating to any of the targeted elements. The name of the path
              can be determined by the name of the target element of the <pref>aria-flowto</pref> <a>attribute</a>. <a>Accessibility <abbr title="Application Programing Interfaces">APIs</abbr></a> can
              provide named path <a>relationships</a>.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <!--
					<tr>
						<th class="property-related-head" scope="row">Related Concepts:</th>
						<td class="property-related"><cite><a href="https://www.w3.org/TR/2006/WD-xhtml2-20060726/"><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 2</a></cite> [[XHTML2]] :nextfocus :prevfocus</td>
					</tr>
					-->
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">All elements of the base markup</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_idref_list">ID reference list</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="state deprecated" id="aria-grabbed">
          <sdef>aria-grabbed</sdef>
          <div class="state-description">
            <p>[Deprecated in ARIA 1.1] Indicates an element's "grabbed" <a>state</a> in a drag-and-drop operation.</p>
            <p class="note">
              The <code>aria-grabbed</code> state is expected to be replaced by a new feature in a future version of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>. Authors are
              therefore advised to treat <code>aria-grabbed</code> as <a>deprecated</a>.
            </p>
            <p>
              Setting <code>aria-grabbed</code> to <code>true</code> indicates that the <a>element</a> has been selected for dragging. Setting <code>aria-grabbed</code> to <code>false</code> indicates
              that the element can be grabbed for a drag-and-drop operation, but is not currently grabbed. If <code>aria-grabbed</code> is unspecified or set to <code>undefined</code> (default), the
              element cannot be grabbed.
            </p>
            <p>
              When <sref>aria-grabbed</sref> is set to <code>true</code>, authors SHOULD update the <pref>aria-dropeffect</pref> <a>attribute</a> of all potential drop targets. When an element is not
              grabbed (the value is set to <code>false</code> or <code>undefined</code>, or the attribute is removed), authors SHOULD revert the <pref>aria-dropeffect</pref> attributes of the
              associated drop targets to <code>none</code>.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="state-related-head" scope="row">Related Concepts:</th>
                <td class="state-related"> </td>
              </tr>
              <tr>
                <th class="state-applicability-head" scope="row">Used in Roles:</th>
                <td class="state-applicability">All elements of the base markup</td>
              </tr>
              <tr>
                <th class="state-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="state-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="state-value-head" scope="row">Value:</th>
                <td class="state-value"><a href="#valuetype_true-false-undefined">true/false/undefined</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row">false</th>
                <td class="value-description">Indicates that the element supports being dragged.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">Indicates that the element has been "grabbed" for dragging.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row"><strong class="default">undefined (default)</strong></th>
                <td class="value-description">Indicates that the element does not support being dragged.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-haspopup">
          <pdef>aria-haspopup</pdef>
          <div class="property-description">
            <p><a>Indicates</a> the availability and type of interactive popup element, such as menu or dialog, that can be triggered by an <a>element</a>.</p>
            <p>
              A popup element usually appears as a block of content that is on top of other content. Authors MUST ensure that the role of the element that serves as the container for the popup content
              is <rref>menu</rref>, <rref>listbox</rref>, <rref>tree</rref>, <rref>grid</rref>, or <rref>dialog</rref>, and that the value of <code>aria-haspopup</code> matches the role of the popup
              container.
            </p>
            <p>
              For the popup element to be keyboard accessible, authors SHOULD ensure that the element that can trigger the popup is focusable, that there is a keyboard mechanism for opening the popup,
              and that the popup element manages focus of all its descendants as described in <a href="#managingfocus">Managing Focus</a>.
            </p>
            <p>
              The <code>aria-haspopup</code> property is a token type. [=User agents=] MUST treat any value of <code>aria-haspopup</code> that is not included in the list of allowed values, including
              the empty string, as if the value <code>false</code> had been provided. To provide backward compatibility with ARIA 1.0 content, user agents MUST treat an
              <code>aria-haspopup</code> value of <code>true</code> as equivalent to a value of <code>menu</code>.
            </p>
            <p><a>Assistive technologies</a> and user agents SHOULD NOT expose the <code>aria-haspopup</code> property if it has a value of <code>false</code>.</p>
            <p class="note">A <rref>tooltip</rref> is not considered to be a popup in this context.</p>
            <p class="note">
              <code>aria-haspopup</code> is most relevant to use when there is a visual indicator in the element that triggers the popup. For example, many controls styled with a downward pointing
              triangle, chevron, or ellipsis (three consecutive dots) have become standard visual indicators that a popup will display when the control is activated. If some functional difference is
              relevant to display to a sighted user by means of a different visual style, that functional difference is usually relevant to convey to users of assistive technology. If there is no
              visual indication that an element will trigger a popup, authors are advised to consider whether use of <code>aria-haspopup</code> is necessary, and avoid using it when it's not.
            </p>
            <p class="note">This property is being deprecated as a global property in ARIA 1.2. In future versions it will only be allowed on roles where it is specifically supported.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related">
                  <pref>aria-controls</pref>
                </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Use as a global deprecated in ARIA 1.2</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_token">token</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row"><strong class="default">false (default)</strong></th>
                <td class="value-description">Indicates the element does not have a popup.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">Indicates the popup is a <rref>menu</rref>.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">menu</th>
                <td class="value-description">Indicates the popup is a <rref>menu</rref>.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">listbox</th>
                <td class="value-description">Indicates the popup is a <rref>listbox</rref>.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">tree</th>
                <td class="value-description">Indicates the popup is a <rref>tree</rref>.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">grid</th>
                <td class="value-description">Indicates the popup is a <rref>grid</rref>.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">dialog</th>
                <td class="value-description">Indicates the popup is a <rref>dialog</rref>.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="state" id="aria-hidden">
          <sdef>aria-hidden</sdef>
          <div class="state-description">
            <p><a>Indicates</a>, when set to <code>true</code>, that an <a>element</a> and its entire subtree are hidden from assistive technology, regardless of whether it is visibly rendered.</p>
            <p>
              User agents determine an element's [=element/hidden=] status based on whether it is rendered, and the rendering is usually controlled by CSS. For example, an element whose
              <code>display</code> property is set to <code>none</code> is not rendered. An element is considered [=element/hidden=] if it, or any of its ancestors are not rendered or have their
              <code>aria-hidden</code> attribute value set to <code>true</code>.
            </p>
            <p>
              Authors MUST NOT use <code>aria-hidden</code> to hide the root element or the host language element that <a data-cite="html/dom.html#represents">represents</a> the contents of the
              primary document in view. For instance, the <code>html</code> or <code>body</code> elements in an HTML document. Authors MAY, with caution, use <code>aria-hidden</code> to hide visibly
              rendered content from assistive technologies <em>only</em> if the act of hiding this content is intended to improve the experience for users of assistive technologies by removing
              redundant or extraneous content. Authors using <code>aria-hidden</code> to hide visible content from screen readers MUST ensure that identical or equivalent meaning and functionality is
              exposed to assistive technologies.
            </p>
            <p class="note">
              Authors are advised to use extreme caution and consider a wide range of disabilities when hiding visibly rendered content from assistive technologies. For example, a sighted,
              dexterity-impaired individual might use voice-controlled assistive technologies to access a visual interface. If an author hides visible link text "Go to checkout" and exposes similar,
              yet non-identical link text "Check out now" to the accessibility API, the user might be unable to access the interface they perceive using voice control software. Similar problems can
              also arise for screen reader users. For example, a sighted telephone support technician might attempt to have the blind screen reader user click the "Go to checkout" link, which they
              might be unable to find using a type-ahead item search ("Go to…"), since that text would have been hidden by the use of the attribute.
            </p>
            <p class="note">
              As of ARIA 1.3, <code><sref>aria-hidden</sref>="false"</code> is now synonymous with <code>aria-hidden="undefined"</code>.
            </p>
            <p class="note">
              The original intent for <code>aria-hidden="false"</code> was to allow user agents to expose content that was otherwise hidden from the accessibility tree. However, due to ambiguity in
              the specification and inconsistent browser support for the <code>false</code> value, the original intent is no longer supported.
            </p>
            <p>
              To prevent authors erroneously hiding entire window-rendered documents only to those using assistive technology, user agents MUST NOT expose the hidden state to assistive technologies if
              it is specified on the root element or the host language element that <a data-cite="html/dom.html#represents">represents</a> the contents of the primary document in view. For instance,
              the <code>html</code> or <code>body</code> elements in an HTML document, or the root <code>svg</code> element if it is rendered as its own primary document in the browser window. If
              authors were to specify <code>aria-hidden="true"</code> on the opening tag for an embedded document, for instance on a <code>math</code> or <code>svg</code> embedded within an HTML
              document, user agents would still be expected to hide these elements from assistive technologies.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="state-related-head" scope="row">Related Concepts:</th>
                <td class="state-related"> </td>
              </tr>
              <tr>
                <th class="state-applicability-head" scope="row">Used in Roles:</th>
                <td class="state-applicability">All elements of the base markup</td>
              </tr>
              <tr>
                <th class="state-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="state-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="state-value-head" scope="row">Value:</th>
                <td class="state-value"><a href="#valuetype_true-false-undefined">true/false/undefined</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row">false</th>
                <td class="value-description">The element's [=element/hidden=] state is determined by the user agent based on whether it is rendered. Synonym of <code>undefined</code>.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">The element is [=element/hidden=] from the accessibility API.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row"><strong class="default">undefined (default)</strong></th>
                <td class="value-description">The element's [=element/hidden=] state is determined by the user agent based on whether it is rendered.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="state" id="aria-invalid">
          <sdef>aria-invalid</sdef>
          <div class="state-description">
            <p><a>Indicates</a> the entered value does not conform to the format expected by the application. See related <pref>aria-errormessage</pref>.</p>
            <p>
              If the value is computed to be invalid or out-of-range, the author SHOULD set this <a>attribute</a> to <code>true</code>. [=user agents=] SHOULD inform the user of the error. Authors
              SHOULD provide suggestions for corrections if they are known.
            </p>
            <p>
              When the user attempts to submit data involving a field for which <pref>aria-required</pref> is <code>true</code>, authors MAY use the <sref>aria-invalid</sref> attribute to signal there
              is an error. However, if the user has not attempted to submit the form, authors SHOULD NOT set the <sref>aria-invalid</sref> attribute on required <a>widgets</a> simply because the user
              has not yet entered data.
            </p>
            <p>
              For future expansion, the <sref>aria-invalid</sref> attribute is a token type. Any value not recognized in the list of allowed <span>values</span> MUST be treated by user agents as if
              the value <code>true</code> had been provided. If the attribute is not present, or its value is <code>false</code>, or its value is the empty string, the default value of
              <code>false</code> applies.
            </p>
            <p class="note">This state is being deprecated as a global state in ARIA 1.2. In future versions it will only be allowed on roles where it is specifically supported.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="state-related-head" scope="row">Related Concepts:</th>
                <td class="state-related"></td>
              </tr>
              <tr>
                <th class="state-applicability-head" scope="row">Used in Roles:</th>
                <td class="state-applicability">Use as a global deprecated in ARIA 1.2</td>
              </tr>
              <tr>
                <th class="state-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="state-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="state-value-head" scope="row">Value:</th>
                <td class="state-value"><a href="#valuetype_token">token</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row">grammar</th>
                <td class="value-description">A grammatical error was detected.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row"><strong class="default">false (default)</strong></th>
                <td class="value-description">There are no detected errors in the value.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">spelling</th>
                <td class="value-description">A spelling error was detected.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">The value entered by the user has failed validation.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-keyshortcuts">
          <pdef>aria-keyshortcuts</pdef>
          <div class="property-description">
            <p><a>Defines</a> keyboard shortcuts that an author has implemented to activate or give focus to an element.</p>
            <p>
              The value of the <code>aria-keyshortcuts</code> attribute is a space-separated list of keyboard shortcuts that can be pressed to activate a command or textbox widget. The keys defined in
              the shortcuts represent the physical keys pressed and not the actual characters generated. Each keyboard shortcut consists of one or more tokens delimited by the plus sign ("+")
              representing zero or more modifier keys and exactly one non-modifier key that must be pressed simultaneously to activate the given shortcut.
            </p>
            <p>
              Authors MUST specify modifier keys exactly according to the <a href="https://www.w3.org/TR/uievents-key/">UI Events KeyboardEvent key Values</a> spec [[!uievents-key]] - for example,
              "Alt", "Control", "Shift", "Meta", or "AltGraph". Note that Meta corresponds to the Command key, and Alt to the Option key, on Apple computers.
            </p>
            <p>
              The valid names for non-modifier keys are any printable character such as "A", "B", "1", "2", "$", "Plus" for a plus sign, "Space" for the spacebar, or the names of any other
              non-modifier key specified in the <a href="https://www.w3.org/TR/uievents-key/">UI Events KeyboardEvent key Values</a> spec [[!uievents-key]] - for example, "Enter", "Tab", "ArrowRight",
              "PageDown", "Escape", or "F1". The use of "Space" for the spacebar is an exception to the <a href="https://www.w3.org/TR/uievents-key/">UI Events KeyboardEvent key Values</a> spec
              [[!uievents-key]] as the space or spacebar key is encoded as <code>'&#160;'</code> and would be treated as a whitespace character.
            </p>
            <p>
              Authors MUST ensure modifier keys come first when they are part of a keyboard shortcut. Authors MUST ensure that required non-modifier keys come last when they are part of a shortcut.
              The order of the modifier keys is not otherwise significant, so "Alt+Shift+T" and "Shift+Alt+T" are equivalent, but "T+Shift+Alt" is not valid because all of the modifier keys don't come
              first, and "Alt" is not valid because it doesn't include at least one non-modifier key.
            </p>
            <p>When specifying an alphabetic key, both the uppercase and lowercase variants are considered equivalent: "a" and "A" are the same.</p>
            <p>
              When implementing keyboard shortcuts authors should consider the keyboards they intend to support to avoid unintended results. Keyboard designs vary significantly based on the device
              used and the languages supported. For example, many modifier keys are used in conjunction with other keys to create common punctuation symbols, create number characters, swap keyboard
              sides on bilingual keyboards to switch languages, and perform a number of other functions.
            </p>
            <p>
              For many supported keyboards, authors can prevent conflicts by avoiding keys other than ASCII letters, as number characters and common punctuation often require modifiers. Here, the
              keyboard shortcut entered does not equate to the key generated. For example, in French keyboard layouts, the number characters are not available until you press the Control key, so a
              keyboard shortcut defined as "Control+2" would be ambiguous as this is how one would type the "2" character on a French keyboard.
            </p>
            <p>
              If the character used is determined by a modifier key, the author MUST specify the actual key used to generate the character, that is generated by the key, and not the resulting
              character. This convention enables the assistive technology to accurately convey what keys must be used to generate the shortcut. For example, on most U.S. English keyboards, the percent
              sign "%" can be input by pressing Shift+5. The correct way to specify this shortcut is "Shift+5". It is incorrect to specify "%" or "Shift+%". However, note that on some international
              keyboards the percent sign might be an unmodified key, in which case "%" and "Shift+%" could be correct on those keyboards.
            </p>
            <p>
              If the key that needs to be specified is illegal in the host language or would cause a string to be terminated, authors MUST use the string escaping sequence of the host language to
              specify it. For example, the single-quote character can be encoded as "&amp;#39;" in HTML.
            </p>
            <p>Examples of valid keyboard shortcuts include:</p>
            <ul>
              <li>"A"</li>
              <li>"Shift+Space"</li>
              <li>"Control+Alt+."</li>
              <li>"Control+Shift+&amp;#39;"</li>
              <li>"Alt+Shift+P Control+F"</li>
              <li>"Meta+C Meta+Shift+C"</li>
            </ul>
            <p>
              User agents MUST NOT change keyboard behavior in response to the <code>aria-keyshortcuts</code> attribute. Authors MUST handle scripted keyboard events to process
              <code>aria-keyshortcuts</code>. The <code>aria-keyshortcuts</code> attribute exposes the existence of these shortcuts so that assistive technologies can communicate this information to
              users.
            </p>
            <p>
              Authors SHOULD provide a way to expose keyboard shortcuts so that all users can discover them, such as through the use of a tooltip. Authors MUST ensure that
              <code>aria-keyshortcuts</code> applied to disabled elements are unavailable.
            </p>
            <p>
              Authors SHOULD avoid implementing shortcut keys that inhibit operating system, user agent, or assistive technology functionality. This requires the author to carefully consider both
              which keys to assign and the contexts and conditions in which the keys are available to the user. For guidance, see the keyboard shortcuts section of the
              <cite
                ><a href="" class="practices"><abbr title="Accessible Rich Internet Applications">ARIA</abbr> Authoring Practices Guide</a></cite
              >.
            </p>
            <p>
              Authors SHOULD consider whether the keyboard shortcut will be valid in each language and physical keyboard layout, and consider localizing the shortcut in languages, locales, and common
              hardware keyboard configurations.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"><a href="https://en.wikipedia.org/wiki/Keyboard_shortcut">Keyboard shortcut</a></td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">All elements of the base markup</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_string">string</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-label">
          <pdef>aria-label</pdef>
          <div class="property-description">
            <p><a>Defines</a> a string value that labels the current element. See related <pref>aria-labelledby</pref>.</p>
            <p>
              The purpose of <pref>aria-label</pref> is the same as that of <pref>aria-labelledby</pref>. It provides the user with a recognizable name of the object. The most common
              <a>accessibility <abbr title="Application Programing Interfaces">API</abbr></a> mapping for a label is the <a class="informative">accessible name</a> property.
            </p>
            <p>
              Most host languages provide an attribute that could be used to name the element (e.g., the <code>[^html-global/title^]</code> attribute in HTML), yet this could present a browser
              tooltip. In the cases where DOM content or a tooltip is undesirable, authors MAY set the accessible name of the element using <pref>aria-label</pref>, if the element does not
              <a href="#prohibitedattributes">prohibit</a> use of the attribute. If the label text is available in the DOM (i.e. typically visible text content), authors SHOULD use
              <pref>aria-labelledby</pref> and SHOULD NOT use <pref>aria-label</pref>. There might be instances where the name of an element cannot be determined programmatically from the DOM, and
              there are cases where referencing DOM content is not the desired user experience. Authors MUST NOT specify <code>aria-label</code> on an element which has an explicit or implicit
              WAI-ARIA role where <code>aria-label</code> is <a href="#prohibitedattributes">prohibited</a>. As required by the
              <a href="#textalternativecomputation">accessible name and description computation</a>, user agents give precedence to <pref>aria-labelledby</pref> over <pref>aria-label</pref> when
              computing the accessible name property.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"></td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">All elements of the base markup except for some roles or elements that prohibit its use</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_string">string</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-labelledby">
          <pdef>aria-labelledby</pdef>
          <div class="property-description">
            <p><a>Identifies</a> the <a>element</a> (or elements) that labels the current element. See related <pref>aria-label</pref> and <pref>aria-describedby</pref>.</p>
            <p>
              The purpose of <pref>aria-labelledby</pref> is the same as that of <pref>aria-label</pref>. It provides the user with a recognizable name of the object. The most common
              <a>accessibility <abbr title="Application Programing Interfaces">API</abbr></a> mapping for a label is the <a class="informative">accessible name</a> property.
            </p>
            <p>
              If the interface is such that it is not possible to have a visible label on the screen, authors SHOULD use <pref>aria-label</pref> and SHOULD NOT use <pref>aria-labelledby</pref>.
              Authors MUST NOT specify <code>aria-labelledby</code> on an element which has an explicit or implicit WAI-ARIA role where <code>aria-labelledby</code> is
              <a href="#prohibitedattributes">prohibited</a>. As required by the <a href="#textalternativecomputation">accessible name and description computation</a>, user agents give precedence to
              <pref>aria-labelledby</pref> over <pref>aria-label</pref> when computing the accessible name property.
            </p>
            <p>
              The <pref>aria-labelledby</pref> attribute is similar to <pref>aria-describedby</pref> in that both reference other elements to calculate a text alternative (an accessible name, and
              description, respectively). While a concise accessible name is preferable, a description can either be concise, or provide more verbose information.
            </p>
            <!-- keep previous sentence synced with the associated description in #aria-describedby -->
            <p class="note">
              The expected spelling of this property in <abbr title="United States">U.S.</abbr> English is "labeledby." However, the
              <a>accessibility <abbr title="Application Programing Interfaces">API</abbr></a> features to which this property is mapped have established the "labelledby" spelling. This property is
              spelled that way to match the convention and minimize the difficulty for developers.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"><code>&lt;[^label^]&gt;</code> in HTML</td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">All elements of the base markup except for some roles or elements that prohibit its use</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_idref_list">ID reference list</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-level">
          <pdef>aria-level</pdef>
          <div class="property-description">
            <p><a>Defines</a> the hierarchical level of an <a>element</a> within a structure.</p>
            <p>
              This can be applied inside trees to tree items, to headings inside a document, to nested grids, nested tablists and to other structural items that might appear inside a container or
              participate in an ownership hierarchy. The value for <pref>aria-level</pref> is an integer greater than or equal to 1.
            </p>
            <p>
              Levels increase with depth. If the <abbr title="Document Object Model">DOM</abbr> ancestry does not accurately represent the level, authors SHOULD explicitly define the
              <pref>aria-level</pref> <a>attribute</a>.
            </p>
            <p>
              This attribute is applied to elements that act as leaf nodes within the orientation of the set, for example, on elements with role <rref>treeitem</rref> rather than elements with role
              <rref>group</rref>. This means that multiple elements in a set can have the same value for this attribute. Although it would be less repetitive to provide a single value on the
              container, restricting this to leaf nodes ensures that there is a single way for <a>assistive technologies</a> to use the attribute.
            </p>
            <p>
              If the <abbr title="Document Object Model">DOM</abbr> ancestry accurately represents the level, the <a>user agent</a> can calculate the level of an item from the document structure. This
              attribute can be used to provide an explicit indication of the level when that is not possible to calculate from the document structure or the <pref>aria-owns</pref> attribute. User
              agent support for automatic calculation of level might vary; authors SHOULD test with [=user agents=] and assistive technologies to determine whether this attribute is needed. If the
              author intends for the user agent to calculate the level, the author SHOULD omit this attribute.
            </p>
            <p class="note">
              In the case of a <rref>treegrid</rref>, <pref>aria-level</pref> is supported on elements with the role <rref>row</rref>, not elements with role <rref>gridcell</rref>. At first glance,
              this might seem inconsistent with the application of <pref>aria-level</pref> on <rref>treeitem</rref> elements, but it is consistent in that the <rref>row</rref> acts as the leaf node
              within the vertical orientation of the <rref>grid</rref>, whereas the <rref>gridcell</rref> is a leaf node within the horizontal orientation of each <rref>row</rref>. Level is not
              supported on sets of cells within rows, so the <pref>aria-level</pref> attribute is applied to the element with the role <rref>row</rref>.
            </p>
            <p class="note">
              On elements with role <pref>heading</pref>, values for <pref>aria-level</pref> above 6 can create difficulties for users. Also, at the time of this writing, most combinations of user
              agents and assistive technologies only support <pref>aria-level</pref> integers 1-9 on headings.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_integer">integer</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-live">
          <pdef>aria-live</pdef>
          <div class="property-description">
            <p>
              <a>Indicates</a> that an <a>element</a> will be updated, and describes the types of updates the [=user agents=], <a>assistive technologies</a>, and user can expect from the
              <a>live region</a>.
            </p>
            <p>
              The <span>values</span> of this <a>attribute</a> are expressed in degrees of importance. When regions are specified as <code>polite</code>, assistive technologies will notify users of
              updates but generally do not interrupt the current task, and updates take low priority. When regions are specified as <code>assertive</code>, assistive technologies will immediately
              notify the user, and could potentially clear the speech queue of previous updates.
            </p>
            <p>
              Politeness levels are essentially an ordering mechanism for updates and serve as a strong suggestion to user agents or assistive technologies. The value can be overridden by user agents,
              assistive technologies, or the user. For example, if assistive technologies can determine that a change occurred in response to a key press or a mouse click, the assistive technologies
              might present that change immediately even if the value of the <pref>aria-live</pref> attribute states otherwise.
            </p>
            <p>
              Since different users have different needs, it is up to the user to tweak his or her assistive technologies' response to a live region with a certain politeness level from the commonly
              defined baseline. Assistive technologies might choose to implement increasing and decreasing levels of granularity so that the user can exercise control over queues and interruptions.
            </p>
            <p>
              When the [=ARIA/property=] is not set on an <a>object</a> that needs to send updates, the politeness level is the value of the nearest ancestor that sets the
              <pref>aria-live</pref> attribute.
            </p>
            <p>
              The <pref>aria-live</pref> attribute is the primary determination for the order of presentation of changes to live regions. Implementations will also consider the default level of
              politeness in a <a>role</a> when the <pref>aria-live</pref> attribute is not set in the ancestor chain (e.g., <rref>log</rref> changes are <code>polite</code> by default). Items which
              are <code>assertive</code> will be presented immediately, followed by <code>polite</code> items. User agents or assistive technologies can choose to clear queued changes when an
              assertive change occurs. (e.g., changes in an assertive region can remove all currently queued changes)
            </p>
            <p>
              When live regions are marked as <code>polite</code>, assistive technologies SHOULD announce updates at the next graceful opportunity, such as at the end of speaking the current sentence
              or when the user pauses typing. When live regions are marked as <code>assertive</code>, assistive technologies SHOULD notify the user immediately. Because an interruption might disorient
              users or cause them to not complete their current task, authors SHOULD NOT use the assertive value unless the interruption is imperative.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">All elements of the base markup</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_token">token</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row">assertive</th>
                <td class="value-description">Indicates that updates to the region have the highest priority and should be presented the user immediately.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row"><strong class="default">off (default)</strong></th>
                <td class="value-description">Indicates that updates to the region should not be presented to the user unless the user is currently focused on that region.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">polite</th>
                <td class="value-description">
                  Indicates that updates to the region should be presented at the next graceful opportunity, such as at the end of speaking the current sentence or when the user pauses typing.
                </td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-modal">
          <pdef>aria-modal</pdef>
          <div class="property-description">
            <p><a>Indicates</a> whether an <a>element</a> is modal when displayed.</p>
            <p>
              The <pref>aria-modal</pref> <a>attribute</a> is used to indicate that the presence of a "modal" element precludes usage of other content on the page. For example, when a modal dialog is
              displayed, it is expected that the user's interaction is limited to the contents of the dialog, until the modal dialog loses focus or is no longer displayed.
            </p>
            <p>
              When a modal element is displayed, assistive technologies SHOULD navigate to the element unless focus has explicitly been set elsewhere. Some assistive technologies limit navigation to
              the modal element's contents. If focus moves to an element outside the modal element, assistive technologies SHOULD NOT limit navigation to the modal element.
            </p>
            <p>
              When a modal element is displayed, authors MUST ensure the interface can be controlled using only descendants of the modal element. In other words, if a modal dialog has a close button,
              the button should be a descendant of the dialog. When a modal element is displayed, authors SHOULD mark all other contents as inert (such as "inert subtrees" in HTML) if the ability to
              do so exists in the host language.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_true-false">true/false</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row"><strong class="default">false (default)</strong></th>
                <td class="value-description">Element is not modal.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">Element is modal.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-multiline">
          <pdef>aria-multiline</pdef>
          <div class="property-description">
            <p><a>Indicates</a> whether a text box accepts multiple lines of input or only a single line.</p>
            <!-- keep the following para synced with its equivalent in #textbox -->
            <p class="note">
              In most user agent implementations, the default behavior of the <kbd>ENTER</kbd> or <kbd>RETURN</kbd> key is different between the single-line and multi-line text fields in HTML. When
              user has focus in a single-line <code>&lt;input type="text"&gt;</code> element, the keystroke usually submits the form. When user has focus in a multi-line
              <code>&lt;textarea&gt;</code> element, the keystroke inserts a line break. The <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <code>textbox</code> role
              differentiates these types of boxes with the <pref>aria-multiline</pref> attribute, so authors are advised to be aware of this distinction when designing the field.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_true-false">true/false</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row"><strong class="default">false (default)</strong></th>
                <td class="value-description">This is a single-line text box.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">This is a multi-line text box.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-multiselectable">
          <pdef>aria-multiselectable</pdef>
          <div class="property-description">
            <p><a>Indicates</a> that the user can select more than one item from the current selectable descendants.</p>
            <p>
              Authors SHOULD ensure that selected descendants have the <sref>aria-selected</sref> <a>attribute</a> set to <code>true</code>, and selectable descendants that are not selected have the
              <sref>aria-selected</sref> attribute set to <code>false</code>. Authors SHOULD NOT use the <sref>aria-selected</sref> attribute on descendants that are not selectable.
            </p>
            <p class="note">Lists and trees are examples of roles that might allow users to select more than one item at a time.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_true-false">true/false</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row"><strong class="default">false (default)</strong></th>
                <td class="value-description">Only one item can be selected.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">More than one item in the widget can be selected at a time.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-orientation">
          <pdef>aria-orientation</pdef>
          <div class="property-description">
            <p><a>Indicates</a> whether the element's orientation is horizontal, vertical, or unknown/ambiguous.</p>
            <p class="note">
              In ARIA 1.1, the default value for <pref>aria-orientation</pref> changed from <code>horizontal</code> to <code>undefined</code>. Implicit defaults are defined on some roles (e.g.,
              <rref>slider</rref> defaults to horizontal; <rref>scrollbar</rref> defaults to vertical) but remain undefined on roles where an expected default orientation is ambiguous (e.g.,
              <rref>radiogroup</rref>).
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_token">token</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row">horizontal</th>
                <td class="value-description">The element is oriented horizontally.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row"><strong class="default">undefined (default)</strong></th>
                <td class="value-description">The element's orientation is unknown/ambiguous.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">vertical</th>
                <td class="value-description">The element is oriented vertically.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-owns">
          <pdef>aria-owns</pdef>
          <div class="property-description">
            <p>
              <a>Identifies</a> an <a>element</a> (or elements) in order to define a visual, functional, or contextual parent/child <a>relationship</a> between
              <abbr title="Document Object Model">DOM</abbr> elements where the DOM hierarchy cannot be used to represent the relationship. See related <pref>aria-controls</pref>.
            </p>
            <p>
              The value of the <pref>aria-owns</pref> <a>attribute</a> is a space-separated ID reference list that references one or more elements in the document by ID. The reason for adding
              <pref>aria-owns</pref> is to expose a parent/child contextual relationship to <a>assistive technologies</a> that is otherwise impossible to infer from the
              <abbr title="Document Object Model">DOM</abbr>.
            </p>
            <p>
              If an element has both <pref>aria-owns</pref> and <abbr title="Document Object Model">DOM</abbr> children then the order of the child elements with respect to the parent/child
              relationship is the <abbr title="Document Object Model">DOM</abbr> children first, then the elements referenced in <pref>aria-owns</pref>. If the author intends that the
              <abbr title="Document Object Model">DOM</abbr> children are not first, then list the DOM children in <pref>aria-owns</pref> in the desired order. Authors SHOULD NOT use
              <pref>aria-owns</pref> as a replacement for the <abbr title="Document Object Model">DOM</abbr> hierarchy. If the relationship is represented in the DOM, do not use
              <pref>aria-owns</pref>.
            </p>
            <p>
              Authors MUST ensure that an element's ID is not specified in more than one other element's <pref>aria-owns</pref> attribute at any time. In other words, an element can have only one
              explicit owner. Authors MUST NOT create circular references with <pref>aria-owns</pref>. In the case of authoring error with <pref>aria-owns</pref>, the user agent MAY ignore some
              <pref>aria-owns</pref> element references in order to build a consistent model of the content.
            </p>
            <p>Authors MUST NOT specify <pref>aria-owns</pref> on an element which has <a href="#childrenArePresentational">Presentational Children</a>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">All elements of the base markup</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_idref_list">ID reference list</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-placeholder">
          <pdef>aria-placeholder</pdef>
          <div class="property-description">
            <p>
              <a>Defines</a> a short hint (a word or short phrase) intended to aid the user with data entry when the control has no value. A hint could be a sample value or a brief description of the
              expected format.
            </p>
            <p>
              Authors SHOULD NOT use <pref>aria-placeholder</pref> instead of a label as their purposes are different: The label indicates what kind of information is expected. The placeholder text is
              a hint about the expected value. See related <pref>aria-labelledby</pref> and <pref>aria-label</pref>.
            </p>
            <p>
              Authors SHOULD present this hint to the user by displaying the hint text at any time the control's <span>value</span> is the empty string. This includes cases where the control first
              receives focus, and when users remove a previously-entered value.
            </p>
            <p class="note">
              As is the case with the related <code>[^input/placeholder^]</code> attribute in HTML, use of placeholder text as a replacement for a displayed label can reduce the accessibility and
              usability of the control for a range of users including older users and users with cognitive, mobility, fine motor skill or vision impairments. While the hint given by the control's
              label is shown at all times, the short hint given in the placeholder attribute is only shown before the user enters a value. Furthermore, placeholder text might be mistaken for a
              pre-filled value, and as commonly implemented the default color of the placeholder text provides insufficient contrast and the lack of a separate visible label reduces the size of the
              hit region available for setting focus on the control.
            </p>
            <p class="note">The following examples do not use the HTML <code>label</code> element as it cannot be used to label HTML elements with <code>contenteditable</code>.</p>
            <p>The following example shows a <rref>searchbox</rref> in which the user has entered a value:</p>
            <pre class="example highlight">
&lt;span id="label"&gt;Birthday:&lt;/span&gt;
&lt;div contenteditable role="searchbox" aria-labelledby="label" <strong>aria-placeholder="MM-DD-YYYY"</strong>&gt;03-14-1879&lt;/div&gt;
				</pre
            >
            <p>The following example shows the same <rref>searchbox</rref> in which the user has not yet entered a value or has removed a previously-entered value:</p>
            <pre class="example highlight">
&lt;span id="label"&gt;Birthday:&lt;/span&gt;
&lt;div contenteditable role="searchbox" aria-labelledby="label" <strong>aria-placeholder="MM-DD-YYYY"</strong>&gt;MM-DD-YYYY&lt;/div&gt;
				</pre
            >
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"><code>[^input/placeholder^]</code> attribute in HTML</td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_string">string</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-posinset">
          <pdef>aria-posinset</pdef>
          <div class="property-description">
            <p>
              <a>Defines</a> an <a>element</a>'s number or position in the current set of listitems or treeitems. Not required if all elements in the set are present in the
              <abbr title="Document Object Model">DOM</abbr>. See related <pref>aria-setsize</pref>.
            </p>
            <p>
              If all items in a set are present in the document structure, it is not necessary to set this <a>attribute</a>, as the <a>user agent</a> can automatically calculate the set size and
              position for each item. However, if only a portion of the set is present in the document structure at a given moment, this [=ARIA/property=] is needed to provide an explicit indication
              of an element's position.
            </p>
            <p>The following example shows items 5 through 8 in a set of 16.</p>
            <pre class="example highlight">
&lt;h2 id="label_fruit"&gt; Available Fruit &lt;/h2&gt;
&lt;ul role="listbox" aria-labelledby="label_fruit"&gt;
  &lt;li role="option" aria-setsize="16" <strong>aria-posinset="5"</strong>&gt; apples &lt;/li&gt;
  &lt;li role="option" aria-setsize="16" <strong>aria-posinset="6"</strong>&gt; bananas &lt;/li&gt;
  &lt;li role="option" aria-setsize="16" <strong>aria-posinset="7"</strong>&gt; cantaloupes &lt;/li&gt;
  &lt;li role="option" aria-setsize="16" <strong>aria-posinset="8"</strong>&gt; dates &lt;/li&gt;
&lt;/ul&gt;</pre
            >
            <p>
              When specifying <pref>aria-posinset</pref>, authors MUST specify a value that is an integer greater than or equal to 1, and less than or equal to the size of the set when that size is
              known. If authors specify <pref>aria-posinset</pref>, authors MUST also specify a value for <pref>aria-setsize</pref>.
            </p>
            <p>
              When specifying <code>aria-posinset</code> on a <rref>menuitem</rref>, <rref>menuitemcheckbox</rref>, or <rref>menuitemradio</rref>, authors SHOULD set the value of
              <code>aria-posinset</code> with respect to the total number of items in the <rref>menu</rref>, excluding any separators.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_integer">integer</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="state" id="aria-pressed">
          <sdef>aria-pressed</sdef>
          <div class="state-description">
            <p><a>Indicates</a> the current "pressed" <a>state</a> of toggle buttons. See related <sref>aria-checked</sref> and <sref>aria-selected</sref>.</p>
            <p>
              Toggle buttons require a full press-and-release cycle to change their value. Activating it once changes the value to <code>true</code>, and activating it another time changes the value
              back to <code>false</code>. A value of <code>mixed</code> means that the values of more than one item controlled by the button do not all share the same value. If the <a>attribute</a> is
              not present, the button is not a toggle button.
            </p>
            <p>
              The <sref>aria-pressed</sref> attribute is similar but not identical to the <sref>aria-checked</sref> attribute. Operating systems support <code>pressed</code> on buttons and
              <code>checked</code> on checkboxes.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="state-related-head" scope="row">Related Concepts:</th>
                <td class="state-related"> </td>
              </tr>
              <tr>
                <th class="state-applicability-head" scope="row">Used in Roles:</th>
                <td class="state-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="state-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="state-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="state-value-head" scope="row">Value:</th>
                <td class="state-value"><a href="#valuetype_tristate">tristate</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row">false</th>
                <td class="value-description">The element supports being pressed but is not currently pressed.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">mixed</th>
                <!-- make sure this value remains synced with its counterpart in #aria-checked -->
                <td class="value-description">Indicates a mixed mode value for a tri-state toggle button.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">The element is pressed.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row"><strong class="default">undefined (default)</strong></th>
                <td class="value-description">The element does not support being pressed.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-readonly">
          <pdef>aria-readonly</pdef>
          <div class="property-description">
            <p>Indicates that the <a>element</a> is not editable, but is otherwise <a>operable</a>. See related <sref>aria-disabled</sref>.</p>
            <p>
              This means the user can read but not set the value of the <a>widget</a>. Readonly elements are relevant to the user, and authors SHOULD NOT restrict navigation to the element or its
              focusable descendants. Other actions such as copying the value of the element are also supported. This is in contrast to disabled elements, to which applications might not allow user
              navigation to descendants.
            </p>
            <p>Examples include:</p>
            <ul>
              <li>A form element which represents a constant.</li>
              <li>Row or column headers in a spreadsheet grid.</li>
              <li>The result of a calculation such as a shopping cart total.</li>
            </ul>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"><code>[^input/readonly^]</code> attribute in HTML</td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_true-false">true/false</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row"><strong class="default">false (default)</strong></th>
                <td class="value-description">The user can set the value of the element.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">The user cannot change the value of the element.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-relevant">
          <pdef>aria-relevant</pdef>
          <div class="property-description">
            <p><a>Indicates</a> what notifications the user agent will trigger when the <a>accessibility tree</a> within a live region is modified. See related <pref>aria-atomic</pref>.</p>
            <p>
              The <a>attribute</a> is represented as a space-separated list of the following <span>values</span>: <code>additions</code>, <code>removals</code>, <code>text</code>; or a single
              catch-all value <code>all</code>.
            </p>
            <p>
              This is used to describe <a>semantically</a> meaningful changes, as opposed to merely presentational ones. For example, nodes that are removed from the top of a log are merely removed
              for purposes of creating room for other entries, and the removal of them does not have meaning. However, in the case of a buddy list, removal of a buddy name indicates that they are no
              longer online, and this is a meaningful <a>event</a>. In that case <pref>aria-relevant</pref> will be set to <code>all</code>. When the <pref>aria-relevant</pref> attribute is not
              provided, the default value, <code>additions text</code>, indicates that text modifications and node additions are relevant, but that node removals are irrelevant.
            </p>
            <p class="note">
              <pref>aria-relevant</pref> values of removals or all are to be used sparingly. Assistive technologies only need to be informed of content removal when its removal represents an important
              change, such as a buddy leaving a chat room.
            </p>
            <p class="note">
              Text removals should only be considered relevant if one of the specified values is 'removals' or 'all'. For example, for a text change from 'foo' to 'bar' in a live region with a default
              <pref>aria-relevant</pref> value, the text addition ('bar') would be spoken, but the text removal ('foo') would not.
            </p>
            <p>
              <pref>aria-relevant</pref> is an optional attribute of live regions. This is a suggestion to <a>assistive technologies</a>, but assistive technologies are not required to present changes
              of all the relevant types.
            </p>
            <p>
              When <pref>aria-relevant</pref> is not defined, an element's value is inherited from the nearest ancestor with a defined value. Although the value is a
              <a href="#valuetype_token_list">token list</a>, inherited values are not additive; the value provided on a descendant element completely overrides any inherited value from an ancestor
              element.
            </p>
            <p>
              When text changes are denoted as relevant, user agents MUST monitor any descendant node change that affects the
              <a href="#textalternativecomputation">accessible name and description computation</a> of the live region as if the accessible name were determined from contents (<a
                href="#namecalculation"
                >nameFrom: contents</a
              >). For example, a text change would be triggered if the HTML <code>alt</code> attribute of a contained image changed. However, no change would be triggered if there was a text change to
              a node outside the live region, even if that node was referenced (via <pref>aria-labelledby</pref>) by an element contained in the live region.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">All elements of the base markup</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_token_list">token list</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row">additions</th>
                <td class="value-description">Element nodes are added to the <a>accessibility tree</a> within the live region.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row"><strong class="default">additions text (default)</strong></th>
                <td class="value-description">Equivalent to the combination of values, "additions text".</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">all</th>
                <td class="value-description">Equivalent to the combination of all values, "additions removals text".</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">removals</th>
                <td class="value-description">Text content, a text alternative, or an element node within the live region is removed from the <a>accessibility tree</a>.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">text</th>
                <td class="value-description">Text content or a text alternative is added to any descendant in the <a>accessibility tree</a> of the live region.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-required">
          <pdef>aria-required</pdef>
          <div class="property-description">
            <p><a>Indicates</a> that user input is required on the <a>element</a> before a form can be submitted.</p>
            <p>For example, if the user needs to fill in an address field, the author will need to set the field's <pref>aria-required</pref> attribute to <code>true</code>.</p>
            <p class="note">
              The fact that the element is required is often presented visually (such as a sign or symbol after the <a>widget</a>). Using the <pref>aria-required</pref> <a>attribute</a> allows the
              author to explicitly convey to <a>assistive technologies</a> that an element is required.
            </p>
            <p>
              Unless an exactly equivalent native attribute is available, host languages SHOULD allow authors to use the <pref>aria-required</pref> attribute on host language form elements that
              require input or selection by the user.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"><code>[^input/required^]</code> attribute in HTML</td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_true-false">true/false</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row"><strong class="default">false (default)</strong></th>
                <td class="value-description">User input is not necessary to submit the form.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">Users need to provide input on an element before a form is submitted.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-roledescription">
          <pdef>aria-roledescription</pdef>
          <div class="property-description">
            <p><a>Defines</a> a human-readable, author-localized description for the <a>role</a> of an <a>element</a>.</p>
            <p>
              Some <a>assistive technologies</a>, such as screen readers, present the role of an element as part of the user experience. Such assistive technologies typically localize the name of the
              role, and they might customize it as well. Users of these assistive technologies depend on the presentation of the role name, such as "region," "button," or "slider," for an
              understanding of the purpose of the element and, if it is a widget, how to interact with it.
            </p>
            <p>
              The <code>aria-roledescription</code> property gives authors the ability to override how assistive technologies localize and express the name of a role. Thus inappropriately using
              <code>aria-roledescription</code> might inhibit users' ability to understand or interact with an element. Authors SHOULD limit use of <code>aria-roledescription</code> to clarifying the
              purpose of non-interactive container roles like <rref>group</rref> or <rref>region</rref>, or to providing a <em>more specific</em> description of a <rref>widget</rref>.
            </p>
            <p>When using <code>aria-roledescription</code>, authors SHOULD also ensure that:</p>
            <ol>
              <li>
                The element to which <code>aria-roledescription</code> is applied has a valid <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role or has an implicit WAI-ARIA role
                semantic.
              </li>
              <li>The value of <code>aria-roledescription</code> is not empty or does not contain only [=ascii whitespace|whitespace=] characters.</li>
            </ol>
            <p class="note">
              Depending on the assistive technology, user verbosity settings, or other factors, certain elements' role descriptions might not be conveyed. If specifying
              <code>aria-roledescription</code> on such elements, then the custom role descriptions might also not be conveyed by these assistive technologies.
            </p>
            <p>
              Additionally, authors MUST NOT specify <code>aria-roledescription</code> on an element which has an explicit or implicit WAI-ARIA role where <code>aria-roledescription</code> is
              <a href="#prohibitedattributes">prohibited</a>.
            </p>
            <p>User agents MUST NOT expose the <code>aria-roledescription</code> property if any of the following conditions exist:</p>
            <ol>
              <li>
                The element to which <code>aria-roledescription</code> is applied has an explicit or implicit WAI-ARIA role where <code>aria-roledescription</code> is
                <a href="#prohibitedattributes">prohibited</a>.
              </li>
              <li>The value of <code>aria-roledescription</code> is undefined or the empty string.</li>
            </ol>
            <p>
              <a>Assistive technologies</a> SHOULD use the value of <code>aria-roledescription</code> when presenting the role of an element, but SHOULD NOT change other functionality based on the
              role of an element that has a value for <code>aria-roledescription</code>. For example, an assistive technology that provides functions for navigating to the next <rref>region</rref> or
              <rref>button</rref> SHOULD allow those functions to navigate to regions and buttons that have an <code>aria-roledescription</code>.
            </p>
            <p>The following two examples show the use of <code>aria-roledescription</code> to indicate that a non-interactive container is a "slide" in a web-based presentation application.</p>
            <pre class="example highlight">
&lt;div role="article" aria-roledescription="slide" id="slide" aria-labelledby="slideheading"&gt;
&lt;h1 id="slideheading">Quarterly Report&lt;/h1&gt;
&lt;!-- remaining slide contents --&gt;
&lt;/div&gt;</pre
            >
            <pre class="example highlight">
&lt;article aria-roledescription="slide" id="slide" aria-labelledby="slideheading"&gt;
&lt;h1 id="slideheading">Quarterly Report&lt;/h1&gt;
&lt;!-- remaining slide contents --&gt;
&lt;/article&gt;</pre
            >
            <p>In the previous examples, a screen reader user might hear "Quarterly Report, slide" rather than the more vague "Quarterly Report, article" or "Quarterly Report, group."</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">All elements of the base markup except for some roles or elements that prohibit its use</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_string">string</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-rowcount">
          <pdef>aria-rowcount</pdef>
          <div class="property-description">
            <p><a>Defines</a> the total number of rows in a <rref>table</rref>, <rref>grid</rref>, or <rref>treegrid</rref>. See related <pref>aria-rowindex</pref>.</p>
            <p>
              If all of the rows are present in the <abbr title="Document Object Model">DOM</abbr>, it is not necessary to set this <a>attribute</a> as the <a>user agent</a> can automatically
              calculate the total number of rows. However, if only a portion of the rows is present in the <abbr title="Document Object Model">DOM</abbr> at a given moment, this attribute is needed to
              provide an explicit indication of the number of rows in the full table.
            </p>
            <p>
              Authors MUST set the value of <pref>aria-rowcount</pref> to an integer equal to the number of rows in the full table. If the total number of rows is unknown, authors MUST set the value
              of <pref>aria-rowcount</pref> to <code>-1</code> to indicate that the value should not be calculated by the user agent.
            </p>
            <p>The following example shows a grid with 2000 rows, of which the first row and rows 100 through 102 are displayed to the user.</p>
            <pre class="example highlight">
&lt;div role="grid" <strong>aria-rowcount="2000"</strong>&gt;
  &lt;div role="rowgroup"&gt;
    &lt;div role="row" aria-rowindex="1"&gt;
      &lt;span role="columnheader"&gt;First Name&lt;/span&gt;
      &lt;span role="columnheader"&gt;Last Name&lt;/span&gt;
      &lt;span role="columnheader"&gt;Company&lt;/span&gt;
      &lt;span role="columnheader"&gt;Phone&lt;/span&gt;
    &lt;/div&gt;
  &lt;/div&gt;
  &lt;div role="rowgroup"&gt;
    &lt;div role="row" aria-rowindex="100"&gt;
      &lt;span role="gridcell"&gt;Fred&lt;/span&gt;
      &lt;span role="gridcell"&gt;Jackson&lt;/span&gt;
      &lt;span role="gridcell"&gt;Acme, Inc.&lt;/span&gt;
      &lt;span role="gridcell"&gt;555-1234&lt;/span&gt;
    &lt;/div&gt;
    &lt;div role="row" aria-rowindex="101"&gt;
      &lt;span role="gridcell"&gt;Sara&lt;/span&gt;
      &lt;span role="gridcell"&gt;James&lt;/span&gt;
      &lt;span role="gridcell"&gt;Acme, Inc.&lt;/span&gt;
      &lt;span role="gridcell"&gt;555-1235&lt;/span&gt;
    &lt;/div&gt;
    &lt;div role="row" aria-rowindex="102"&gt;
      &lt;span role="gridcell"&gt;Taylor&lt;/span&gt;
      &lt;span role="gridcell"&gt;Johnson&lt;/span&gt;
      &lt;span role="gridcell"&gt;Acme, Inc.&lt;/span&gt;
      &lt;span role="gridcell"&gt;555-1236&lt;/span&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;</pre
            >
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_integer">integer</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-rowindex">
          <pdef>aria-rowindex</pdef>
          <div class="property-description">
            <p>
              <a>Defines</a> an [=element|element's=] row index or position with respect to the total number of rows within a <rref>table</rref>, <rref>grid</rref>, or <rref>treegrid</rref>. See
              related <pref>aria-rowindextext</pref>, <pref>aria-rowcount</pref>, and <pref>aria-rowspan</pref>.
            </p>
            <p>
              If all of the rows are present in the <abbr title="Document Object Model">DOM</abbr>, it is not necessary to set this <a>attribute</a> as the <a>user agent</a> can automatically
              calculate the index of each row. However, if only a portion of the rows is present in the <abbr title="Document Object Model">DOM</abbr> at a given moment, this attribute is needed to
              provide an explicit indication of each row's position with respect to the full table.
            </p>
            <p>
              Authors MUST set the <span>value</span> for <pref>aria-rowindex</pref> to an integer greater than or equal to 1, greater than the <pref>aria-rowindex</pref> value of any previous rows,
              and less than or equal to the number of rows in the full table. For a cell or gridcell which spans multiple rows, authors MUST set the value of <pref>aria-rowindex</pref> to the start of
              the span.
            </p>
            <p>Authors SHOULD place <pref>aria-rowindex</pref> on each row. Authors MAY also place <pref>aria-rowindex</pref> on all of the <a>accessibility children</a> of each row.</p>
            <p>The following example shows a grid with 2000 rows, of which the first row and rows 100 through 102 are displayed to the user.</p>
            <pre class="example highlight">
&lt;div role="grid" aria-rowcount="2000"&gt;
  &lt;div role="rowgroup"&gt;
    &lt;div role="row" <strong>aria-rowindex="1"</strong>&gt;
      &lt;span role="columnheader"&gt;First Name&lt;/span&gt;
      &lt;span role="columnheader"&gt;Last Name&lt;/span&gt;
      &lt;span role="columnheader"&gt;Company&lt;/span&gt;
      &lt;span role="columnheader"&gt;Phone&lt;/span&gt;
    &lt;/div&gt;
  &lt;/div&gt;
  &lt;div role="rowgroup"&gt;
    &lt;div role="row" <strong>aria-rowindex="100"</strong>&gt;
      &lt;span role="gridcell"&gt;Fred&lt;/span&gt;
      &lt;span role="gridcell"&gt;Jackson&lt;/span&gt;
      &lt;span role="gridcell"&gt;Acme, Inc.&lt;/span&gt;
      &lt;span role="gridcell"&gt;555-1234&lt;/span&gt;
    &lt;/div&gt;
    &lt;div role="row" <strong>aria-rowindex="101"</strong>&gt;
      &lt;span role="gridcell"&gt;Sara&lt;/span&gt;
      &lt;span role="gridcell"&gt;James&lt;/span&gt;
      &lt;span role="gridcell"&gt;Acme, Inc.&lt;/span&gt;
      &lt;span role="gridcell"&gt;555-1235&lt;/span&gt;
    &lt;/div&gt;
    &lt;div role="row" <strong>aria-rowindex="102"</strong>&gt;
      &lt;span role="gridcell"&gt;Taylor&lt;/span&gt;
      &lt;span role="gridcell"&gt;Johnson&lt;/span&gt;
      &lt;span role="gridcell"&gt;Acme, Inc.&lt;/span&gt;
      &lt;span role="gridcell"&gt;555-1236&lt;/span&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;</pre
            >
            <p>The following example shows the grid from the previous example with <pref>aria-rowindex</pref> also placed on all of the <a>accessibility children</a> of each row.</p>
            <pre class="example highlight">
&lt;div role="grid" aria-rowcount="2000"&gt;
  &lt;div role="rowgroup"&gt;
    &lt;div role="row" <strong>aria-rowindex="1"</strong>&gt;
      &lt;span role="columnheader" <strong>aria-rowindex="1"</strong>&gt;First Name&lt;/span&gt;
      &lt;span role="columnheader" <strong>aria-rowindex="1"</strong>&gt;Last Name&lt;/span&gt;
      &lt;span role="columnheader" <strong>aria-rowindex="1"</strong>&gt;Company&lt;/span&gt;
      &lt;span role="columnheader" <strong>aria-rowindex="1"</strong>&gt;Phone&lt;/span&gt;
    &lt;/div&gt;
  &lt;/div&gt;
  &lt;div role="rowgroup"&gt;
    &lt;div role="row" <strong>aria-rowindex="100"</strong>&gt;
      &lt;span role="gridcell" <strong>aria-rowindex="100"</strong>&gt;Fred&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-rowindex="100"</strong>&gt;Jackson&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-rowindex="100"</strong>&gt;Acme, Inc.&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-rowindex="100"</strong>&gt;555-1234&lt;/span&gt;
    &lt;/div&gt;
    &lt;div role="row" <strong>aria-rowindex="101"</strong>&gt;
      &lt;span role="gridcell" <strong>aria-rowindex="101"</strong>&gt;Sara&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-rowindex="101"</strong>&gt;James&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-rowindex="101"</strong>&gt;Acme, Inc.&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-rowindex="101"</strong>&gt;555-1235&lt;/span&gt;
    &lt;/div&gt;
    &lt;div role="row" <strong>aria-rowindex="102"</strong>&gt;
      &lt;span role="gridcell" <strong>aria-rowindex="102"</strong>&gt;Taylor&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-rowindex="102"</strong>&gt;Johnson&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-rowindex="102"</strong>&gt;Acme, Inc.&lt;/span&gt;
      &lt;span role="gridcell" <strong>aria-rowindex="102"</strong>&gt;555-1236&lt;/span&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;</pre
            >
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_integer">integer</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-rowindextext">
          <pdef>aria-rowindextext</pdef>
          <div class="property-description">
            <p><a>Defines</a> a human readable text alternative of <pref>aria-rowindex</pref>. See related <pref>aria-colindextext</pref>.</p>
            <p>
              Authors SHOULD only use <code>aria-rowindextext</code> when the provided or calculated value of <pref>aria-rowindex</pref> is not meaningful or does not reflect the displayed index, as
              can be seen in the game Battleship.
            </p>
            <p>
              Authors SHOULD NOT use <code>aria-rowindextext</code> as a replacement for <pref>aria-rowindex</pref> because some assistive technologies rely upon the numeric row index for the purpose
              of keeping track of the user's position or providing alternative table navigation.
            </p>
            <p>Authors SHOULD place <code>aria-rowindextext</code> on each row. Authors MAY also place <code>aria-rowindextext</code> on all of the <a>accessibility children</a> of each row.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_integer">string</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-rowspan">
          <pdef>aria-rowspan</pdef>
          <div class="property-description">
            <p>
              <a>Defines</a> the number of rows spanned by a cell or gridcell within a <rref>table</rref>, <rref>grid</rref>, or <rref>treegrid</rref>. See related <pref>aria-rowindex</pref> and
              <pref>aria-colspan</pref>.
            </p>
            <p>
              This <a>attribute</a> is intended for cells and gridcells which are not contained in a native table. When defining the row span of cells or gridcells in a native table, authors SHOULD
              use the host language's attribute instead of <pref>aria-rowspan</pref>. If <pref>aria-rowspan</pref> is used on an element for which the host language provides an equivalent attribute,
              [=user agents=] MUST ignore the value of <pref>aria-rowspan</pref> and instead expose the value of the host language's attribute to <a>assistive technologies</a>.
            </p>
            <p>
              Authors MUST set the <span>value</span> of <pref>aria-rowspan</pref> to an integer greater than or equal to 0 and less than the value which would cause the cell or gridcell to overlap
              the next cell or gridcell in the same column. Setting the value to 0 indicates that the cell or gridcell is to span all the remaining rows in the row group.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_integer">integer</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="state" id="aria-selected">
          <sdef>aria-selected</sdef>
          <div class="state-description">
            <p><a>Indicates</a> the current "selected" <a>state</a> of various <a>widgets</a>. See related <sref>aria-checked</sref> and <sref>aria-pressed</sref>.</p>
            <p>This <a>attribute</a> is used to indicate which elements within single-selection and multiple-selection <rref>composite</rref> widgets are selected.</p>
            <p>
              The <rref>option</rref>, <rref>tab</rref>, and <rref>treeitem</rref> roles permit user agents to provide an implicit value for <sref>aria-selected</sref> when specified conditions are
              met. User agents MUST NOT provide an implicit value for aria-selected in any other circumstance.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="state-related-head" scope="row">Related Concepts:</th>
                <td class="state-related"> </td>
              </tr>
              <tr>
                <th class="state-applicability-head" scope="row">Used in Roles:</th>
                <td class="state-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="state-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="state-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="state-value-head" scope="row">Value:</th>
                <td class="state-value"><a href="#valuetype_true-false-undefined">true/false/undefined</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row">false</th>
                <td class="value-description">The selectable element is not selected.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">true</th>
                <td class="value-description">The selectable element is selected.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row"><strong class="default">undefined (default)</strong></th>
                <td class="value-description">The element is not selectable.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-setsize">
          <pdef>aria-setsize</pdef>
          <div class="property-description">
            <p>
              <a>Defines</a> the number of items in the current set of listitems or treeitems. Not required if all elements in the set are present in the
              <abbr title="Document Object Model">DOM</abbr>. See related <pref>aria-posinset</pref>.
            </p>
            <p>
              This [=ARIA/property=] is marked on the members of a set, not the container element that collects the members of the set. To orient the user by saying an element is "item X out of Y,"
              the <a>assistive technologies</a> would use X equal to the <pref>aria-posinset</pref> <a>attribute</a> and Y equal to the <code>aria-setsize</code> attribute.
            </p>
            <p>
              If all items up to the current item in a set are present in the document structure, it is not necessary to set this <a>attribute</a>, as the <a>user agent</a> can automatically calculate
              the position for these items. However, if all previous items in the set are not present in the document structure at a given moment, the author MUST set this <a>attribute</a>to provide
              an explicit indication of an element's position.
            </p>
            <p>
              When specifying <code>aria-setsize</code>, authors MUST set the value to an integer equal to the number of items in the set. If the total number of items is unknown, authors SHOULD set
              the value of <code>aria-setsize</code> to <code>-1</code>.
            </p>
            <p>
              When specifying <code>aria-setsize</code> on a <rref>menuitem</rref>, <rref>menuitemcheckbox</rref>, or <rref>menuitemradio</rref>, authors SHOULD set the value of
              <code>aria-setsize</code> based on the total number of items in the <rref>menu</rref>, excluding any separators.
            </p>
            <p>The following example shows items 5 through 8 in a set of 16.</p>
            <pre class="example highlight">
&lt;h2 id="label_fruit"&gt; Available Fruit &lt;/h2&gt;
&lt;ul role="listbox" aria-labelledby="label_fruit"&gt;
  &lt;li role="option" <strong>aria-setsize="16"</strong> aria-posinset="5"&gt; apples &lt;/li&gt;
  &lt;li role="option" <strong>aria-setsize="16"</strong> aria-posinset="6"&gt; bananas &lt;/li&gt;
  &lt;li role="option" <strong>aria-setsize="16"</strong> aria-posinset="7"&gt; cantaloupes &lt;/li&gt;
  &lt;li role="option" <strong>aria-setsize="16"</strong> aria-posinset="8"&gt; dates &lt;/li&gt;
&lt;/ul&gt;</pre
            >
            <p>The following example shows items 5 through 8 in a set whose total size is unknown.</p>
            <pre class="example highlight">
&lt;h2 id="label_fruit"&gt; Available Fruit &lt;/h2&gt;
&lt;ul role="listbox" aria-labelledby="label_fruit"&gt;
  &lt;li role="option" <strong>aria-setsize="-1"</strong> aria-posinset="5"&gt; apples &lt;/li&gt;
  &lt;li role="option" <strong>aria-setsize="-1"</strong> aria-posinset="6"&gt; bananas &lt;/li&gt;
  &lt;li role="option" <strong>aria-setsize="-1"</strong> aria-posinset="7"&gt; cantaloupes &lt;/li&gt;
  &lt;li role="option" <strong>aria-setsize="-1"</strong> aria-posinset="8"&gt; dates &lt;/li&gt;
&lt;/ul&gt;</pre
            >
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_integer">integer</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-sort">
          <pdef>aria-sort</pdef>
          <div class="property-description">
            <p><a>Indicates</a> if items in a table or grid are sorted in ascending or descending order.</p>
            <p>
              Authors SHOULD only apply this [=ARIA/property=] to table headers or grid headers. If the property is not provided, there is no defined sort order. For each table or grid, authors SHOULD
              apply <pref>aria-sort</pref> to only one header at a time.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"> </td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_token">token</a></td>
              </tr>
            </tbody>
          </table>
          <table class="def">
            <caption>
              Values:
            </caption>
            <thead>
              <tr>
                <th scope="col">Value</th>
                <th scope="col">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="value-name" scope="row">ascending</th>
                <td class="value-description">Items are sorted in ascending order.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">descending</th>
                <td class="value-description">Items are sorted in descending order.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row"><strong class="default">none (default)</strong></th>
                <td class="value-description">There is no defined sort applied.</td>
              </tr>
              <tr>
                <th class="value-name" scope="row">other</th>
                <td class="value-description">A sort algorithm other than ascending or descending has been applied.</td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-valuemax">
          <pdef>aria-valuemax</pdef>
          <div class="property-description">
            <p><a>Defines</a> the maximum allowed value for a range <a>widget</a>.</p>
            <p>
              Authors MUST ensure the value of <pref>aria-valuemax</pref> is greater than or equal to the value of <pref>aria-valuemin</pref>. If the <pref>aria-valuenow</pref> has a known maximum and
              minimum, the author SHOULD provide properties for <pref>aria-valuemax</pref> and <pref>aria-valuemin</pref>.
            </p>
            <p class="note">
              A range widget starts with a given value, which can be increased until reaching the maximum value, defined by this [=ARIA/property=]. Declaring the minimum and maximum
              <span>values</span> allows assistive technology to convey the size of the range to users.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"><code>&lt;input type="[^input/type/range^]"&gt;</code> element <code>[^input/max^]</code> attribute in HTML</td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_number">number</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-valuemin">
          <pdef>aria-valuemin</pdef>
          <div class="property-description">
            <p><a>Defines</a> the minimum allowed value for a range <a>widget</a>.</p>
            <p>
              Authors MUST ensure the value of <pref>aria-valuemin</pref> is less than or equal to the value of <pref>aria-valuemax</pref>. If the <pref>aria-valuenow</pref> has a known maximum and
              minimum, the author SHOULD provide properties for <pref>aria-valuemax</pref> and <pref>aria-valuemin</pref>.
            </p>
            <p class="note">
              A range widget starts with a given value, which can be decreased until reaching the minimum value, defined by this [=ARIA/property=]. Declaring the minimum and maximum
              <span>values</span> allows assistive technology to convey the size of the range to users.
            </p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"><code>&lt;input type="[^input/type/range^]"&gt;</code> element <code>[^input/min^]</code> attribute in HTML</td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_number">number</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-valuenow">
          <pdef>aria-valuenow</pdef>
          <div class="property-description">
            <p><a>Defines</a> the current value for a range <a>widget</a>. See related <pref>aria-valuetext</pref>.</p>
            <p>This property is used, for example, on a range widget such as a slider or progress bar.</p>
            <p>
              If the current value is not known (for example, an indeterminate progress bar), the author SHOULD NOT set the <pref>aria-valuenow</pref> <a>attribute</a>. If the
              <pref>aria-valuenow</pref> attribute is absent, no information is implied about the current value. If the <pref>aria-valuenow</pref> has a known maximum and minimum, the author SHOULD
              provide properties for <pref>aria-valuemax</pref> and <pref>aria-valuemin</pref>.
            </p>
            <p>
              The value of <pref>aria-valuenow</pref> is a decimal number. If the range is a set of numeric values, then <pref>aria-valuenow</pref> is one of those values. For example, if the range is
              [0, 1], a valid <pref>aria-valuenow</pref> is 0.5. A value outside the range, such as -2.5 or 1.1, is invalid.
            </p>
            <p>
              For <rref>progressbar</rref> elements and <rref>scrollbar</rref> elements, assistive technologies SHOULD render the value to users as a percent, calculated as a position on the range
              from <pref>aria-valuemin</pref> to <pref>aria-valuemax</pref> if both are defined, otherwise the actual value with a percent indicator. For elements with role <rref>slider</rref> and
              <rref>spinbutton</rref>, assistive technologies SHOULD render the actual value to users.
            </p>
            <p>
              When the rendered value cannot be accurately represented as a number, authors SHOULD use the <pref>aria-valuetext</pref> attribute in conjunction with <pref>aria-valuenow</pref> to
              provide a user-friendly representation of the range's current value. For example, a slider might have rendered values of <code>small</code>, <code>medium</code>, and <code>large</code>.
              In this case, the values of <pref>aria-valuetext</pref> would be one of the strings: <code>small</code>, <code>medium</code>, or <code>large</code>.
            </p>
            <p class="note">If <pref>aria-valuetext</pref> is specified, assistive technologies render that instead of the value of <pref>aria-valuenow</pref>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"><code>&lt;input type="[^input/type/range^]"&gt;</code> element <code>[^input/value^]</code> attribute in HTML</td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_number">number</a></td>
              </tr>
            </tbody>
          </table>
        </div>
        <div class="property" id="aria-valuetext">
          <pdef>aria-valuetext</pdef>
          <div class="property-description">
            <p><a>Defines</a> the human readable text alternative of <pref>aria-valuenow</pref> for a range <a>widget</a>.</p>
            <p>This property is used, for example, on a range widget such as a slider or progress bar.</p>
            <p>
              If the <pref>aria-valuetext</pref> attribute is set, authors SHOULD also set the <pref>aria-valuenow</pref> attribute, unless that value is unknown (for example, on an indeterminate
              <rref>progressbar</rref>).
            </p>
            <p>
              Authors SHOULD only set the <pref>aria-valuetext</pref> attribute when the rendered value cannot be meaningfully represented as a number. For example, a slider might have rendered values
              of <code>small</code>, <code>medium</code>, and <code>large</code>. In this case, the values of <pref>aria-valuenow</pref> could range from 1 through 3, which indicate the position of
              each value in the value space, but the <pref>aria-valuetext</pref> would be one of the strings: <code>small</code>, <code>medium</code>, or <code>large</code>. If the
              <pref>aria-valuetext</pref> attribute is absent, the <a>assistive technologies</a> will rely solely on the <pref>aria-valuenow</pref> attribute for the current value.
            </p>
            <p>If <pref>aria-valuetext</pref> is specified, assistive technologies SHOULD render that value instead of the value of <pref>aria-valuenow</pref>.</p>
          </div>
          <table class="def">
            <caption>
              Characteristics:
            </caption>
            <thead>
              <tr>
                <th scope="col">Characteristic</th>
                <th scope="col">Value</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <th class="property-related-head" scope="row">Related Concepts:</th>
                <td class="property-related"></td>
              </tr>
              <tr>
                <th class="property-applicability-head" scope="row">Used in Roles:</th>
                <td class="property-applicability">Placeholder</td>
              </tr>
              <tr>
                <th class="property-descendants-head" scope="row">Inherits into Roles:</th>
                <td class="property-descendants">Placeholder</td>
              </tr>
              <tr>
                <th class="property-value-head" scope="row">Value:</th>
                <td class="property-value"><a href="#valuetype_string">string</a></td>
              </tr>
            </tbody>
          </table>
        </div>
      </section>
    </section>
    <section class="normative" id="accessibility_tree">
      <h1><dfn class="export">Accessibility Tree</dfn></h1>
      <p>
        The <a class="termref">accessibility tree</a> and the DOM tree are parallel structures. The <a class="termref">accessibility tree</a> includes the user interface objects of the
        <a>user agent</a> and the objects of the document. <a>Accessible objects</a> are created in the accessibility tree for every DOM element that should be exposed to an
        <a>assistive technology</a>, either because it might fire an accessibility <a>event</a> or because it has a [=ARIA/property=], <a>relationship</a> or feature which needs to be exposed.
      </p>
      <section id="tree_exclusion">
        <h2>Excluding Elements from the Accessibility Tree</h2>
        <p>
          The following [=elements=] are not exposed via the <a>accessibility <abbr title="Application Programing Interfaces">API</abbr></a> and user agents MUST NOT include them in the
          <a class="termref">accessibility tree</a>:
        </p>
        <ul>
          <li>
            Elements, including their descendent elements, that have host language semantics specifying that the element is not displayed, such as CSS <code>display:none</code>,
            <code>visibility:hidden</code>, or the HTML <code>hidden</code> attribute.
          </li>
          <li>
            Elements with <rref>none</rref> or <rref>presentation</rref> as the first role in the role attribute. However, their exclusion is conditional. In addition, the element's descendants and
            text content are generally included. These exceptions and conditions are documented in the <a href="#presentation">presentation (role)</a> section.
          </li>
        </ul>
        <p>If not already excluded from the accessibility tree per the above rules, user agents SHOULD NOT include the following elements in the accessibility tree:</p>
        <ul>
          <li>
            Elements, including their descendants, that have <sref>aria-hidden</sref> set to <code>true</code>. In other words, <code>aria-hidden=&quot;true&quot;</code> on a parent overrides
            <code>aria-hidden=&quot;false&quot;</code> on descendants.
          </li>
          <li>
            <p>
              Any descendants of elements that have the characteristic &quot;<a href="#childrenArePresentational">Children Presentational: True</a>&quot; unless the descendant is not allowed to be
              presentational because it meets one of the conditions for exception described in <a href="#conflict_resolution_presentation_none">Presentational Roles Conflict Resolution</a>. However,
              the text content of any excluded descendants is included.
            </p>
            <p>Elements with the following roles have the characteristic &quot;Children Presentational: True&quot;:</p>
            <ul>
              <li><rref>button</rref></li>
              <li><rref>checkbox</rref></li>
              <li><rref>img</rref></li>
              <li><rref>menuitemcheckbox</rref></li>
              <li><rref>menuitemradio</rref></li>
              <li><rref>meter</rref></li>
              <li><rref>option</rref></li>
              <li><rref>progressbar</rref></li>
              <li><rref>radio</rref></li>
              <li><rref>scrollbar</rref></li>
              <li><rref>separator</rref></li>
              <li><rref>slider</rref></li>
              <li><rref>switch</rref></li>
              <li><rref>tab</rref></li>
            </ul>
          </li>
        </ul>
      </section>
      <section id="tree_inclusion">
        <h2>Including Elements in the Accessibility Tree</h2>
        <p>
          If not excluded from the accessibility tree per the rules above in <a href="#tree_exclusion">Excluding Elements in the Accessibility Tree</a>, user agents MUST provide an
          <a>accessible object</a> in the <a class="termref">accessibility tree</a> for <abbr title="Document Object Model">DOM</abbr> [=elements=] that meet any of the following criteria:
        </p>
        <ul>
          <li>
            Elements that are not [=element/hidden=] and can fire an <a>accessibility <abbr title="Application Program Interface">API</abbr></a> <a>event</a>, including:
            <ul>
              <li>Elements that are currently focused, even if the element or one of its ancestor elements has its <sref>aria-hidden</sref> attribute set to <code>true</code>.</li>
              <li>Elements that are a valid target of an <pref>aria-activedescendant</pref> attribute.</li>
            </ul>
          </li>
          <li>
            Elements that have an explicit role or a global <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> attribute and do not have <sref>aria-hidden</sref> set to
            <code>true</code>. (See <a href="#tree_exclusion">Excluding Elements in the Accessibility Tree</a> for additional guidance on <sref>aria-hidden</sref>.)
          </li>
          <li>
            Elements that are not [=element/hidden=] and have an ID that is referenced by another element via a <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> property.
            <p class="note">
              Text equivalents for [=element/hidden=] referenced objects can still be used in the <a href="#mapping_additional_nd" class="accname">name and description computation</a> even when not
              included in the accessibility tree.
            </p>
          </li>
        </ul>
      </section>
      <section id="tree_relationships">
        <h2>Relationships in the Accessibility Tree</h2>
        <p>The following terms are used to describe relationships between <abbr title="Document Object Model">DOM</abbr> elements.</p>
        <p>
          The <dfn data-export="" data-lt="accessibility child|owned child|child element|child|children|child elements">accessibility children</dfn> of a DOM element are all of the children of that
          element's corresponding <a>accessible object</a> in the <a>accessibility tree</a>. In terms of the DOM, that includes the following (with exclusions listed blow):
        </p>
        <ul>
          <li>The <abbr title="Document Object Model">DOM</abbr> children of the <a>element</a>.</li>
          <li>All DOM descendants of the <a>element</a> with only elements of role <rref>generic</rref> or <rref>none</rref> intervening.</li>
          <li>All DOM elements specified via an <pref>aria-owns</pref> relationship to the element.</li>
          <li>
            All DOM descendants of an element with role <rref>generic</rref> or <rref>none</rref> specified via <pref>aria-owns</pref> with only elements of role <rref>generic</rref> or
            <rref>none</rref> intervening.
          </li>
        </ul>
        <p>And excludes the following:</p>
        <ul>
          <li>All DOM elements that have no corresponding <a>accessible object</a> because they have been <a href="#tree_exclusion">excluded from the accessibility tree</a>.</li>
          <li>All DOM elements whose corresponding <a>accessible object</a> have been reparented in the <a>accessibility tree</a> via <pref>aria-owns</pref>.</li>
        </ul>
        <p>In the following example, the <rref>list</rref> element has four accessibility children:</p>
        <pre class="example highlight">
&lt;div role="list" aria-owns="child3 child4"&gt;
  &lt;div role="listitem"&gt;Accessibility Child 1&lt;/div&gt;
  &lt;div&gt;
    &lt;div role="listitem"&gt;Accessibility Child 2&lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;
&lt;div id="child3" role="listitem"&gt;Accessibility Child 3&lt;/div&gt;
&lt;div id="child4"&gt;
  &lt;div role="listitem"&gt;Accessibility Child 4&lt;/div&gt;
&lt;/div&gt;
          </pre
        >
        <p>
          In the following example, the first <rref>list</rref> element has no accessibility children, where as the second <rref>list</rref> element has one accessibility child, specifically the
          <rref>listitem</rref> with ID value "reparented".
        </p>
        <pre class="example highlight">
&lt;div role="list"&gt;
  &lt;div role="listitem" aria-hidden="true"&gt;Excluded element&lt;/div&gt;
  &lt;div role="listitem" id="reparented"&gt;Reparented element&lt;/div&gt;
&lt;/div&gt;
&lt;div role="list" aria-owns="reparented"&gt;&lt;/div&gt;
          </pre
        >
        <p>
          The <dfn data-export="" data-lt="accessibility descendant|accessibility descendants">accessibility descendants</dfn> of a DOM element are all DOM elements which correspond to descendants of
          the corresponding <a>accessible object</a> in the <a class="termref">accessibility tree</a>.
        </p>
        <p>
          The <dfn data-export="" data-lt="accessibility parent|parent element|parent">accessibility parent</dfn> of a DOM element is the parent of the corresponding <a>accessible object</a> in the
          <a>accessibility tree</a>. In terms of the DOM, the accessibility parent is one of the following:
        </p>
        <ul>
          <li>The <abbr title="Document Object Model">DOM</abbr> parent of the <a>element</a>.</li>
          <li>The DOM ancestor of the <a>element</a> with only elements of role <rref>generic</rref> or <rref>none</rref> intervening.</li>
          <li>A DOM element with <pref>aria-owns</pref> set to the DOM ID of the DOM element in question.</li>
          <li>
            A DOM element with <pref>aria-owns</pref> set to the DOM ID of an ancestor of the DOM element in question, with only elements of role <rref>generic</rref> or <rref>none</rref> intervening.
          </li>
        </ul>
        <p>The following four examples all contain a <rref>listitem</rref> element with an accessibility parent of role <rref>list</rref>:</p>
        <pre class="example highlight">
&lt;div role="list"&gt;
  &lt;div role="listitem"&gt;The "list" is my accessibility parent.&lt;/div&gt;
&lt;/div&gt;
          </pre
        >
        <pre class="example highlight">
&lt;div role="list"&gt;
  &lt;div&gt;
    &lt;div role="listitem"&gt;The "list" is my accessibility parent.&lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;
          </pre
        >
        <pre class="example highlight">
&lt;div role="list" aria-owns="child"&gt;&lt;/div&gt;
&lt;div id="child" role="listitem"&gt;The "list" is my accessibility parent.&lt;/div&gt;
          </pre
        >
        <pre class="example highlight">
&lt;div role="list" aria-owns="child"&gt;&lt;/div&gt;
&lt;div id="child"&gt;
  &lt;div role="listitem"&gt;The "list" is my accessibility parent.&lt;/div&gt;
&lt;/div&gt;
          </pre
        >
      </section>
    </section>
    <section class="normative" id="host_languages">
      <h1>Implementation in Host Languages</h1>
      <p>
        The <a>roles</a>, <a>state</a>, and [=ARIA/properties=] defined in this specification do not form a complete web language or format. They are intended to be used in the context of a host
        language. This section discusses how host languages are to implement <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>, to ensure that the markup specified here will
        integrate smoothly and effectively with the host language markup.
      </p>
      <p>
        Although markup languages look alike superficially, they do not share language definition infrastructure. To accommodate differences in language-building approaches, the requirements are both
        general and modularization-specific. While allowing for differences in how the specifications are written, the intent is to maintain consistency in how the
        <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> information looks to authors and how it is manipulated in the <abbr title="Document Object Model">DOM</abbr> by scripts.
      </p>
      <p>
        <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> roles, states, and properties are implemented as [=attributes=] of [=elements=]. Roles are applied by placing their names
        among the tokens appearing in the value of a host-language-provided <code>role</code> attribute. States and properties each get their own attribute, with values as defined for each particular
        state or property in this specification. The name of the attribute is the aria-prefixed name of the state or property.
      </p>
      <section id="host_general_role">
        <h2>Role Attribute</h2>
        <p>
          An implementing host language will provide a <code><a>role</a></code> <a>attribute</a> with the following characteristics:
        </p>
        <ul>
          <li>The attribute value MUST allow a [=token list=] as the value;</li>
          <li>
            The appearance of the name literal of any concrete <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a>role</a> as one of these tokens MUST NOT in and of itself make the
            attribute value illegal in the host-language syntax; and
          </li>
          <li>
            The first name literal of a non-abstract <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role in the list of tokens in the role attribute defines the role according to
            which the user agent MUST process the element. User Agent processing for roles is defined in the
            <cite><a href="" class="core-mapping">Core Accessibility API Mappings</a></cite> [[CORE-AAM-1.2]].
          </li>
        </ul>
      </section>
      <section id="host_general_attrs">
        <h3>State and Property Attributes</h3>
        <p>An implementing host language MUST allow [=attributes=] with the following characteristics:</p>
        <ul>
          <li>
            The attribute name is the name of any state or property identified in the <a href="#states_and_properties">Supported States and Properties</a> section, such as <sref>aria-busy</sref>,
            <sref>aria-selected</sref>, <pref>aria-activedescendant</pref>, <pref>aria-valuetext</pref>;
          </li>
          <li>The syntax does <strong>NOT</strong> prevent the attribute from appearing anywhere that it is applicable, as specified in this specification;</li>
          <li>When these attributes appear in a document instance, the attributes will be processed as defined in this specification.</li>
        </ul>
        <p>
          Host languages that support <cite><a href="https://www.w3.org/TR/2006/REC-xml-names-20060816/">XML Namespaces</a></cite> [[XML-NAMES]] <strong>MAY</strong> require that
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> attributes be used with a namespace. In this case, the namespace for
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> state and property attributes <strong>MUST</strong> be <code>http://www.w3.org/ns/wai-aria/</code>. To use
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> in host languages that do not explicitly describe support for it, authors <strong>SHOULD</strong> use this namespace as
          well, if the host language supports namespaces and there is expectation that user agents will recognize the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> namespace. The
          namespace prefix is not defined by this specification but generally is expected to be &quot;<code>aria</code>&quot;.
        </p>
        <p class="note">
          The <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> state and property attributes have a naming convention such that they all begin with the string
          &quot;<code>aria-</code>&quot;. This is <em>not</em> a namespace prefix, it is a part of the state or property name. Therefore, when using
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> states and properties with namespace prefixes, the complete attribute name will be like
          &quot;<code>aria:aria-foo</code>&quot;.
        </p>
        <p>
          Some host languages do not use namespaces with <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> state and property attributes, either because the host language does not
          support namespaces or because the designers wish to incorporate <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> into the core feature set. In these host languages, the
          namespace name for these attributes has no value. The names of these attributes do not have a prefix offset by a colon; in the terms of namespaces they are unprefixed attribute names. The
          ECMAScript binding of the <abbr title="Document Object Model">DOM</abbr> interface <code>getAttributeNS</code> for example, treats the empty string (<code>&quot;&quot;</code>) as
          representing this condition, so that both <code>getAttribute(&quot;aria-busy&quot;)</code> and <code>getAttributeNS(&quot;&quot;, &quot;aria-busy&quot;)</code> access the same
          <sref>aria-busy</sref> attribute in the <abbr title="Document Object Model">DOM</abbr>.
        </p>
        <p class="note">
          According to the requirements of this section, some user agents recognize <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> state and property attributes
          <em>with</em> namespaces, some <em>without</em> namespaces, and some might recognize both. Authors are advised to be aware of which form is supported for the host language they are using.
          Unless the host language and supporting user agents explicitly indicate that the namespace is required, authors are advised to use the attribute without namespaces. Even user agents that
          support namespaces generally do not publish namespaced <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> states and properties to accessibility APIs. In particular, current
          implementations of HTML, including XHTML, do not support this namespace.
        </p>
      </section>
      <section id="host_general_focus">
        <h2>Focus Navigation</h2>
        <p>
          An implementing host language MUST provide support for the author to make all interactive elements focusable, that is, any renderable or event-receiving elements. An implementing host
          language MUST provide a facility to allow authors to define whether these focusable, interactive elements appear in the default tab navigation order. The <code>tabindex</code>
          <a>attribute</a> in HTML is an example of one implementation.
        </p>
      </section>
      <section id="implicit_semantics">
        <h2>Implicit <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Semantics</h2>
        <p>
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> is designed to provide <a>semantic</a> information about objects when host languages lack native semantics for the object.
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> is designed, however, to provide additional semantics for many host languages. Furthermore, host languages over time can
          evolve and provide new native features that correspond to WAI-ARIA features. Therefore, there are many situations in which
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics are redundant with host language semantics.
        </p>
        <p>
          These host language features can be viewed as having &quot;implicit <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics&quot;. User agent processing of features
          with implicit <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics would be similar to the processing for the
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> feature. The processing might not be identical because of lexical differences between the host language feature and the
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> feature, but generally the user agent would expose the same information to the accessibility API. Features with implicit
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics satisfy <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> structural requirements such as
          Required Accessibility Parent Roles, Allowed Accessibility Child Roles, required states and properties, etc. and do not require explicit
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics to be provided. On elements with implicit WAI-ARIA roles, authors can also use WAI-ARIA states and properties
          supported by those roles <em>without</em> requiring explicit indication of the WAI-ARIA role.
        </p>
        <p>
          For example, if an element with the functionality already exists, such as a checkbox or radio button, use the native semantics of the host language.
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> markup is only intended to be used to enhance the native semantics (e.g., indicating that the element is required with
          <pref>aria-required</pref>), or to change the semantics to a different purpose from the standard functionality of the element.
        </p>
        <p>
          Implicit <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics affect the conflict resolution procedures in the following section, Conflicts with Host Language
          Semantics. Therefore, implicit <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics need to be defined in a normative specification, such as the host language
          specification or the <cite><a href="" class="core-mapping">Core Accessibility API Mappings</a></cite
          >.
        </p>
      </section>
      <section id="host_general_conflict">
        <h2>Conflicts with Host Language Semantics</h2>
        <p>
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> roles, states, and properties are intended to add <a>semantic</a> information when native host language elements with
          these semantics are not available, and are generally used on elements that have no native semantics of their own. They can also be used on elements that have similar but non-identical
          semantics (for example, a nested list could be used to represent a tree structure). This method can be part of a fallback strategy for older browsers that have no
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> implementation, or because native presentation of the repurposed element reduces the amount of style and/or script needed.
          Except for the cases outlined below, user agents MUST always use the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics to define how it exposes the element to
          accessibility APIs, rather than using the host language semantics.
        </p>
        <p>
          In addition to these normal situations in which <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> is expected to override native semantics, there are elements that are
          inappropriate to override with <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>. This could be because identical host language semantics exist, so
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> is not needed, or because semantics from <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> directly
          conflict with host language semantics. When a feature in the host language with identical role semantics and values is available, and the author has no compelling reason to avoid using the
          host language feature, authors SHOULD use the host language features rather than repurpose other elements with <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>.
        </p>
        <p>
          Host languages can have features that have implicit <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics corresponding to roles. When a
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role is provided, user agents MUST use the semantic of the
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role for processing, not the native semantic, unless the role requires
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> states and properties whose attributes are explicitly forbidden on the native element by the host language. Values for
          roles do not conflict in the same way as values for states and properties (for example, the HTML 'checked' attribute and the 'aria-checked' attribute could have conflicting values), and
          authors are expected to have valid reason to provide a <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role even on elements that would not normally be repurposed.
        </p>
        <p>
          When <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> states and properties correspond to host language features that have the same
          <a href="#implicit_semantics">implicit <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantic</a>, it can be particularly problematic to use the
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> feature. If the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> feature and the host language feature
          are both provided but their values are not kept in sync, user agents and assistive technologies cannot know which value to use. Therefore, to prevent providing conflicting states and
          properties to assistive technologies, host languages MUST explicitly declare where the use of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> attributes on each host
          language element conflicts with native features for that element. When a host language declares a <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> attribute to be in
          direct semantic conflict with a native feature for a given element, user agents MUST ignore the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> attribute and instead use
          the host language feature with the same implicit semantic.
        </p>
        <p>
          Host languages MAY document features that cannot be overridden with <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> (these are called "strong native semantics"). These
          can be features that have implicit <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics, as well as features where the processing would be uncertain if the semantics
          were changed with <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>. Conformance checkers MAY signal an error or warning when a
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role is used on elements with strong native semantics, but as described above, user agents MUST still use the value of the
          semantic of the WAI-ARIA role when exposing the element to accessibility APIs unless the native host language semantic is permanently presentational.
        </p>
        <p>
          The opportunity for host languages to create exceptions to the WAI-ARIA override of native features is meant to avoid potential author errors or problems with intrinsic processing of host
          language features. Author errors could happen when a host language and WAI-ARIA provide similar but not identical features, where it might not be clear how changing one but not the other
          affects the accessibility API. Intrinsic processing refers to the way a feature is processed, beyond simple rendering and exposure to the Accessibility API, that cannot reasonably be changed
          in response to an ARIA feature, and would lead to unpredictable results were ARIA allowed. In these situations, there is good reason for host languages to limit the scope of WAI-ARIA.
          However, this provision does not give blanket permission for host languages to forbid the use of WAI-ARIA simply by documenting, feature by feature, that it cannot be used. Host languages
          should create restrictions on the use of ARIA only when it is critical to effective processing of content.
        </p>
        <p>
          Certain ARIA features are critical to building a complete model in the accessibility API. Such features are not expected to conflict with native host language semantics (though they can
          complement them). Therefore, host languages MUST NOT declare strong native semantics that prevent use of the following ARIA features:
        </p>
        <ul>
          <li><pref>aria-describedby</pref></li>
          <li><pref>aria-description</pref></li>
          <li><pref>aria-label</pref></li>
          <li><pref>aria-labelledby</pref></li>
        </ul>

        <!-- previous 'Conflicts with Host Language Semantics' section -->
        <!--
		<p><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> is intended to add <a>semantic</a> information to objects when native host language elements are not available with these semantics. It is generally used on elements that have no native semantics of their own with respect to user interface objects. At times, however, it is used on elements that have similar but not identical semantics to the intended object (for instance, nested list elements might be used to represent a tree structure). This is usually done as part of a fallback strategy, or because native presentation of the repurposed element reduces the amount of style and script the author needs to use. In these cases, the user agent MUST use the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics to define how it exposes the element to accessibility APIs, not the native semantics.</p>
		<p>Notwithstanding these normal situations in which <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> is expected to override native semantics, there are elements that are inappropriate to override with <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>. This might be because native semantics already exist so <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> is not needed, or because semantics from <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> directly conflict with host language semantics. When features in the host language are available for a given type of object, authors SHOULD use those features rather than repurpose other elements with <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>. </p>
		<p>When <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> states and properties correspond to host language features that have the same <a href="#implicit_semantics">implicit <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantic</a>, it can be particularly problematic to use the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> feature. If the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> feature and the host language feature are both provided but their values are not kept in sync, it is uncertain which one is correct. Therefore, user agents MUST ignore <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> states and properties when a host language feature with the same implicit <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantic is provided on the same object. </p>
		<p>Although host languages can also have features that have implicit <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics corresponding to roles, the above rule does not apply to roles. When a <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role is provided, user agents MUST use the semantic of the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role for processing, not the native semantic. This is because values for roles do not conflict in the same way as values for states and properties, and because authors are expected to have good reason to provide a <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role even on elements that would not normally be repurposed.</p>
		<p>Host languages MAY document features that should not be overridden with <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> (these are called &quot;strong native semantics&quot;). These can be features that have implicit <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics, as well as features where the processing would be uncertain if the semantics were changed with <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>. Conformance checkers might signal an error or warning when a <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role is used on elements with strong native semantics, even though user agents process the feature as described above. </p>
		-->
      </section>
      <section id="state_property_processing">
        <h2>State and Property Attribute Processing</h2>
        <p>
          State and property attributes are included in host languages, and therefore syntax for representation of their value types is governed by the host language. For each of the value types
          defined in <a href="#propcharacteristic_value">Value</a>, an appropriate value type from the host language is used. Recommended correspondences between
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> value types and various host language value types are listed in
          <a href="#typemapping">Mapping <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Value types to languages</a>. This is a non-normative mapping in order to accommodate new
          host languages supporting <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>.
        </p>
        <p>
          The list value types&#8212;ID reference list and token list&#8212;allow more than one value of the given type to be provided. The values are separated by delimiter characters recognized by
          the host language for list attributes, such as space characters, commas, etc. Some languages might require a specific, single delimiter, while others might allow various delimiters.
        </p>
        <p>
          Global states and properties are supported on any element in the host language. However, authors MUST only use non-global states and properties on elements with a role supporting the state
          or property; either defined as an explicit <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role, or as defined by the host language implicit WAI-ARIA semantic matching an
          appropriate WAI-ARIA role. When a role attribute is added to an element, the <a>semantics</a> and behavior of the element, including support for
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> states and properties, are augmented or overridden by the role behavior. User agents <strong>MUST</strong> ignore
          non-global states and properties used on an element without a role supporting the state or property; either defined as an explicit WAI-ARIA role, or as defined by the host language WAI-ARIA
          semantic matching an appropriate <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role. For example, the <pref>aria-valuetext</pref> attribute can be used on a
          <rref>progressbar</rref>.
        </p>
        <p>
          <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> roles have associated states and properties that are qualified as "supported" or "required". An example of a property
          <em>supported</em> by the <a class="role-reference" href="#combobox">combobox</a> role is <a class="property-reference" href="#aria-autocomplete">aria-autocomplete</a>. The property is
          designated "supported" in this case because a given <code>combobox</code> might or might not implement auto completion. In contrast, the <code>combobox</code> role <em>requires</em> the
          <a class="state-reference" href="#aria-expanded">aria-expanded</a> state in order to indicate that it is expandable. Comboboxes have a controlled popup element, such as a
          <code>listbox</code>, that is either open or closed. If the <code>listbox</code> is open, the <code>combobox</code> is in its expanded state; otherwise it is collapsed.
        </p>
        <p>
          When <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> roles are used, <em>supported</em> states and properties that are not present in the DOM are treated according to
          their default value. Keeping with the <code>combobox</code> example, a missing <code>aria-autocomplete</code> attribute is equivalent to <code>aria-autocomplete=&quot;none&quot;</code>,
          meaning the <code>combobox</code> does not offer auto completion.
        </p>
        <p>
          However, <em>required</em> states and properties that are absent are an author error. Missing required states and properties are processed as detailed at
          <a href="#document-handling_author-errors">Handling Author Errors</a>.
        </p>
        <p>
          Elements that have implicit WAI-ARIA semantics support the full set of WAI-ARIA states and properties supported by the corresponding role. Therefore, authors MAY omit the role when setting
          states and properties. The role is only needed when the implicit WAI-ARIA role of the element needs to be changed.
        </p>
        <p>
          Sometimes states and properties are present in the DOM but have a zero-length string ("") as their value. Authors MAY specify a zero-length string ("") for any supported (but not required)
          state or property. User agents SHOULD treat state and property attributes with a value of "" the same as they treat an absent attribute. For supported states and properties, this corresponds
          to the default value, but if it is a required attribute, it signals an author error and is processed as detailed at <a href="#document-handling_author-errors">Handling Author Errors</a>.
        </p>
        <section id="mapping_additional_relations_error_processing">
          <h3>ID Reference Error Processing</h3>
          <p>[=user agents=] SHOULD ignore ID references that do not match the ID of another <a>element</a> in the same document.</p>
          <p>
            It is the author's responsibility to ensure that IDs are unique. If more than one element has the same ID, the user agent SHOULD use the first element found with the given ID. The behavior
            will be the same as <code>getElementById</code>.
          </p>
          <p>
            If the same element is specified multiple times in a single <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> relation, user agents SHOULD return multiple pointers to the
            same <a>element</a>.
          </p>
          <p>
            <pref>aria-activedescendant</pref> is defined as referencing only a single ID reference. Any <code>aria-activedescendant</code> value that does not match an existing ID reference exactly
            is an author error and will not match any element in the <abbr title="Document Object Model">DOM</abbr>.
          </p>
        </section>
      </section>
      <section id="document-handling_css-selectors">
        <h3>CSS Selectors</h3>
        <p class="note">This section might be removed in a future version.</p>
        <p>
          Support for <a class="termref">attribute</a> selectors MUST include <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> attributes. For example,
          <samp>.fooMenuItem[aria-haspopup=&quot;true&quot;]</samp> would select all [=elements=] with class <code>fooMenuItem</code>, and
          <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> property <pref>aria-haspopup</pref> with value of <code>true</code>. The presentation MUST be updated for dynamic changes
          to <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> attributes. This allows authors to match styling with
          <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> <a>semantics</a>.
        </p>
      </section>
    </section>
    <section id="document-handling_author-errors">
      <h2>Handling Author Errors</h2>
      <section id="document-handling_author-errors_roles">
        <h3>Roles</h3>
        <p>User agents are expected to perform validation of <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> <a>roles</a>.</p>
        <p>
          As stated in the <a href="#role_definitions">Definition of Roles</a> section, it is considered an authoring error to use <a href="#abstract_roles">abstract roles</a> in content. User agents
          MUST NOT map abstract roles via the standard role mechanism of the accessibility <abbr title="application programming interface">API</abbr>.
        </p>
        <p>
          If the <code>role</code> attribute contains no tokens matching the name of a non-abstract <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> role, the user agent MUST treat
          the element as if no <a>role</a> had been provided. For example, <code>&lt;table&nbsp;role=&quot;foo&quot;&gt;</code> should be exposed in the same way as <code>&lt;table&gt;</code> and
          <code>&lt;input&nbsp;type=&quot;text&quot;&nbsp;role=&quot;structure&quot;&gt;</code> in the same way as <code>&lt;input&nbsp;type=&quot;text&quot;&gt;</code>.
        </p>
        <p>
          Certain landmark roles require names from authors. In situations where an author has not specified names for these landmarks, it is considered an authoring error. The user agent MUST treat
          such elements as if no <a>role</a> had been provided. If a valid fallback role had been specified, or if the element had an implicit ARIA role, then user agents would continue to expose that
          role, instead. Instances of such roles are as follows:
        </p>
        <ul>
          <li><rref>form</rref></li>
          <li><rref>region</rref></li>
        </ul>
      </section>
      <section id="document-handling_author-errors_states-properties">
        <h3>States and Properties</h3>
        <p>
          In general, [=user agents=] do not do much validation of <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> [=ARIA/properties=]. User agents MAY do some minor validation on
          request and enforce things like <pref>aria-posinset</pref> being within 1 and <pref>aria-setsize</pref>, inclusive. User agents are not responsible for logical validation, such as the
          following:
        </p>
        <ol>
          <li>Circular references created by relations, such as specifying that two [=elements=] own each other.</li>
          <li>Correct usage with regard to <abbr title="Document Object Model">DOM</abbr> tree structure, such as an <a>element</a> being owned by more than one other element.</li>
          <li>
            Elements with <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> <a>roles</a> correctly implement the behavior of the specified role. For example, user agents do not verify
            that an element with a role of <rref>checkbox</rref> actually behaves like a checkbox.
          </li>
          <li>Elements that do not correctly observe required child / parent role relationships or that appear elsewhere than in their required parent.</li>
          <li>Determining whether <pref>aria-activedescendant</pref> actually points to an <a>accessibility descendant</a> of the container widget.</li>
          <li>Determining implicit values of <pref>aria-setsize</pref> and <pref>aria-posinset</pref> when they are specified on some but not all the elements of the set.</li>
        </ol>
        <p>If the author specifies a non-numeric value for a decimal or integer value type, the user agent SHOULD do the following:</p>
        <ul>
          <li>When asked for the string version of the property, return the string if specified by the author.</li>
          <li>
            When asked for the numeric version:
            <ul>
              <li>Follow the guidance in the <a href="#authorErrorDefaultValuesTable">Fallback values for missing required attributes</a> table below, if applicable.</li>
              <li>Otherwise, return a fallback value of 0.0 for decimal value types and 0 for integer value types.</li>
            </ul>
          </li>
        </ul>
        <p>
          If a <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> property contains an unknown or disallowed value, the user agent SHOULD expose to platform
          <a>accessibility APIs</a> as follows:
        </p>
        <ul>
          <li>When exposing as a platform accessibility API attribute, expose the unknown value &#8212; do not vet it against possible values.</li>
          <li>
            When exposing as a platform <abbr title="application programming interface">API</abbr> Boolean state:
            <ul>
              <li>
                For values of &quot;&quot; (empty string), &quot;undefined&quot; or no [=attribute=] present:
                <ul>
                  <li>Follow the guidance in the <a href="#authorErrorDefaultValuesTable">Fallback values for missing required attributes</a> table below, if applicable.</li>
                  <li>Otherwise, treat as false.</li>
                </ul>
              </li>
              <li>Treat any other value as true.</li>
            </ul>
          </li>
          <li>Otherwise, ignore the value and treat the property as not present.</li>
        </ul>
        <p class="note">In <abbr title="User Interface Automation">UIA</abbr>, the user agent might leave the corresponding property set to &quot;unsupported.&quot;</p>
        <p>User agents MUST NOT expose <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> attributes that reference unresolved IDs. For example:</p>
        <ul>
          <li>When the state or property has only one ID reference that cannot be resolved, treat as if the state or property is not present.</li>
          <li>When the state or property has a list of ID references, ignore any that can't be resolved. If none in the list can be resolved, treat as if the state or property is not present.</li>
        </ul>
        <p>
          If a required <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> attribute for a given role is missing, user agents SHOULD process the attribute as if the values given in the
          following table were provided.
        </p>
        <table id="authorErrorDefaultValuesTable" class="data">
          <caption>
            Fallback values for missing required attributes
          </caption>
          <thead>
            <tr>
              <th><abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> role</th>
              <th>Required Attribute</th>
              <th>Fallback value</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td><rref>checkbox</rref></td>
              <td><sref>aria-checked</sref></td>
              <td><code>false</code></td>
            </tr>
            <tr>
              <td><rref>combobox</rref></td>
              <td><sref>aria-controls</sref></td>
              <td>no mapping</td>
            </tr>
            <tr>
              <td><rref>combobox</rref></td>
              <td><sref>aria-expanded</sref></td>
              <td><code>false</code></td>
            </tr>
            <tr>
              <td><rref>heading</rref></td>
              <td><pref>aria-level</pref></td>
              <td><code>2</code></td>
            </tr>
            <tr>
              <td><rref>menuitemcheckbox</rref></td>
              <td><sref>aria-checked</sref></td>
              <td><code>false</code></td>
            </tr>
            <tr>
              <td><rref>menuitemradio</rref></td>
              <td><sref>aria-checked</sref></td>
              <td><code>false</code></td>
            </tr>
            <tr>
              <td><rref>radio</rref></td>
              <td><sref>aria-checked</sref></td>
              <td><code>false</code></td>
            </tr>
            <tr>
              <td><rref>scrollbar</rref></td>
              <td><pref>aria-controls</pref></td>
              <td>no mapping</td>
            </tr>
            <tr>
              <td><rref>scrollbar</rref></td>
              <td><pref>aria-valuenow</pref></td>
              <td>
                If missing or not a <a href="#valuetype_number">number</a>,<code>(aria-valuemax - aria-valuemin) / 2</code>. If present but less than <code>aria-valuemin</code>, the value of
                <code>aria-valuemin</code>. If present but greater than <code>aria-valuemax</code>, the value of <code>aria-valuemax</code>.
              </td>
            </tr>
            <tr>
              <td><rref>separator</rref> (if focusable)</td>
              <td><pref>aria-valuenow</pref></td>
              <td>
                If missing or not a <a href="#valuetype_number">number</a>,<code>(aria-valuemax - aria-valuemin) / 2</code>. If present but less than <code>aria-valuemin</code>, the value of
                <code>aria-valuemin</code>. If present but greater than <code>aria-valuemax</code>, the value of <code>aria-valuemax</code>.
              </td>
            </tr>
            <tr>
              <td><rref>slider</rref></td>
              <td><pref>aria-valuenow</pref></td>
              <td>
                If missing or not a <a href="#valuetype_number">number</a>,<code>(aria-valuemax - aria-valuemin) / 2</code>. If present but less than <code>aria-valuemin</code>, the value of
                <code>aria-valuemin</code>. If present but greater than <code>aria-valuemax</code>, the value of <code>aria-valuemax</code>.
              </td>
            </tr>
            <tr>
              <td><rref>switch</rref></td>
              <td><sref>aria-checked</sref></td>
              <td><code>false</code></td>
            </tr>
            <tr>
              <td><rref>meter</rref></td>
              <td><pref>aria-valuenow</pref></td>
              <td>A value matching the implicit or explicitly set <code>aria-valuemin</code>.</td>
            </tr>
          </tbody>
        </table>
        <p class="note">Implicit values for non-required states and properties appear in the characteristics table for each role. These are not considered fallback values so are not included here.</p>
      </section>
      <section id="conflict_resolution_presentation_none">
        <h3>Presentational Roles Conflict Resolution</h3>
        <p>There are a number of ways presentational role conflicts are resolved.</p>
        <p>User agents MUST NOT expose [=elements=] having explicit or inherited presentational role in the accessibility tree, with these exceptions:</p>
        <ul>
          <li>
            If an element is focusable, user agents MUST ignore the <rref>none</rref>/<rref>presentation</rref> role and expose the element with its implicit role, in order to ensure that the element
            is <a>operable</a>.
          </li>
          <li>
            If an <a href="#mustContain">allowed child element</a> has an explicit non-presentational role, user agents MUST ignore an inherited presentational role and expose the element with its
            explicit role. If the action of exposing the explicit role causes the accessibility tree to be malformed, the expected results are undefined.
          </li>
          <li>
            If an element has <a>global</a> WAI-ARIA states or properties, user agents MUST ignore the <rref>none</rref>/<rref>presentation</rref> role and instead expose the element's implicit role.
            However, if an element has only non-global, role-specific WAI-ARIA states or properties, the element MUST NOT be exposed unless the presentational role is inherited and an explicit
            non-presentational role is applied.
          </li>
        </ul>
        <p class="note">
          Some <a>global</a> WAI-ARIA states and properties are <a>prohibited</a> on certain roles. These states and properties are still considered global for the purposes of Presentational Role
          Conflict resolution.
        </p>
        <p>
          For example, <pref>aria-describedby</pref> is a global attribute and would always be applied; <pref>aria-level</pref> is not a global attribute and would therefore only apply if the element
          was not in a presentational state.
        </p>
        <pre class="example highlight">
<span class="comment">&lt;!-- 1. [role="none"] is ignored due to the global aria-describedby property. --&gt;</span>
&lt;h1 role="none" aria-describedby="comment-1"&gt; Sample Content &lt;/h1&gt;
<span class="comment">&lt;!-- 2. [role="none"] negates both the implicit 'heading' and the non-global aria-level. --&gt;</span>
&lt;h1 role="none" aria-level="2"&gt; Sample Content &lt;/h1&gt;
		</pre>
        <p>Authors MUST NOT use <rref>presentation</rref> and <rref>none</rref> on elements where user agents will ignore that role because it conflicts with one of the above items.</p>
      </section>
    </section>
    <section id="idl-interface" class="normative">
      <h2>IDL Interface</h2>
      <p>Conforming user agents MUST implement the following IDL interface.</p>
      <section id="ARIAMixin" class="normative" data-dfn-for="ARIAMixin" data-link-for="ARIAMixin">
        <h2>Interface Mixin <dfn>ARIAMixin</dfn></h2>
        <pre class="idl" data-cite="webidl">
			interface mixin ARIAMixin {
				[CEReactions] attribute DOMString? role;
				[CEReactions] attribute Element? ariaActiveDescendantElement;
				[CEReactions] attribute DOMString? ariaAtomic;
				[CEReactions] attribute DOMString? ariaAutoComplete;
				[CEReactions] attribute DOMString? ariaBrailleLabel;
				[CEReactions] attribute DOMString? ariaBrailleRoleDescription;
				[CEReactions] attribute DOMString? ariaBusy;
				[CEReactions] attribute DOMString? ariaChecked;
				[CEReactions] attribute DOMString? ariaColCount;
				[CEReactions] attribute DOMString? ariaColIndex;
				[CEReactions] attribute DOMString? ariaColIndexText;
				[CEReactions] attribute DOMString? ariaColSpan;
				[CEReactions] attribute FrozenArray&lt;Element&gt;? ariaControlsElements;
				[CEReactions] attribute DOMString? ariaCurrent;
				[CEReactions] attribute FrozenArray&lt;Element&gt;? ariaDescribedByElements;
				[CEReactions] attribute DOMString? ariaDescription;
				[CEReactions] attribute FrozenArray&lt;Element&gt;? ariaDetailsElements;
				[CEReactions] attribute DOMString? ariaDisabled;
				[CEReactions] attribute FrozenArray&lt;Element&gt;? ariaErrorMessageElements;
				[CEReactions] attribute DOMString? ariaExpanded;
				[CEReactions] attribute FrozenArray&lt;Element&gt;? ariaFlowToElements;
				[CEReactions] attribute DOMString? ariaHasPopup;
				[CEReactions] attribute DOMString? ariaHidden;
				[CEReactions] attribute DOMString? ariaInvalid;
				[CEReactions] attribute DOMString? ariaKeyShortcuts;
				[CEReactions] attribute DOMString? ariaLabel;
				[CEReactions] attribute FrozenArray&lt;Element&gt;? ariaLabelledByElements;
				[CEReactions] attribute DOMString? ariaLevel;
				[CEReactions] attribute DOMString? ariaLive;
				[CEReactions] attribute DOMString? ariaModal;
				[CEReactions] attribute DOMString? ariaMultiLine;
				[CEReactions] attribute DOMString? ariaMultiSelectable;
				[CEReactions] attribute DOMString? ariaOrientation;
				[CEReactions] attribute FrozenArray&lt;Element&gt;? ariaOwnsElements;
				[CEReactions] attribute DOMString? ariaPlaceholder;
				[CEReactions] attribute DOMString? ariaPosInSet;
				[CEReactions] attribute DOMString? ariaPressed;
				[CEReactions] attribute DOMString? ariaReadOnly;
				[CEReactions] attribute DOMString? ariaRelevant;
				[CEReactions] attribute DOMString? ariaRequired;
				[CEReactions] attribute DOMString? ariaRoleDescription;
				[CEReactions] attribute DOMString? ariaRowCount;
				[CEReactions] attribute DOMString? ariaRowIndex;
				[CEReactions] attribute DOMString? ariaRowIndexText;
				[CEReactions] attribute DOMString? ariaRowSpan;
				[CEReactions] attribute DOMString? ariaSelected;
				[CEReactions] attribute DOMString? ariaSetSize;
				[CEReactions] attribute DOMString? ariaSort;
				[CEReactions] attribute DOMString? ariaValueMax;
				[CEReactions] attribute DOMString? ariaValueMin;
				[CEReactions] attribute DOMString? ariaValueNow;
				[CEReactions] attribute DOMString? ariaValueText;
			};
			Element includes ARIAMixin;
		</pre
        >

        <p>For every IDL attribute <var>idlAttribute</var> defined in <code>ARIAMixin</code> when included on an element:</p>

        <ol>
          <li>
            <p>Let <var>contentAttributeName</var> be the local name of the ARIA content attribute determined by looking up <var>idlAttribute</var> in the ARIA Attribute Correspondence table.</p>
          </li>

          <li>
            <p><var>idlAttribute</var> must [=reflect=] <var>contentAttributeName</var> and support {{ElementInternals}}.</p>
          </li>
        </ol>

        <p class="note">
          In practice, this means that, e.g., the <code>role</code> IDL attribute on <code>Element</code> reflects the <code>role</code> content attribute; the <code>ariaValueMin</code> IDL attribute
          reflects the <pref>aria-valuemin</pref> content attribute; etc. Ambiguity clarifications (such as <code>ariaPosInSet</code>) are listed in
          <a href="#idl_attr_exceptions">IDL Attribute Name Notes or Exceptions</a>.
        </p>
      </section>

      <section id="accessibilityroleandproperties-correspondence" class="normative" data-dfn-for="ARIAMixin" data-link-for="ARIAMixin">
        <h2>ARIA Attribute Correspondence</h2>
        <p>The following table provides a correspondence between IDL attribute names and content attribute names, for use by <code>ARIAMixin</code>.</p>

        <table class="def">
          <tr>
            <th>IDL Attribute</th>
            <th>Reflected ARIA Content Attribute</th>
          </tr>
          <tr>
            <td>role</td>
            <td><a href="#introroles">role</a></td>
          </tr>
          <tr>
            <td><dfn>ariaActiveDescendantElement</dfn></td>
            <td><pref>aria-activedescendant</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaAtomic</dfn></td>
            <td><pref>aria-atomic</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaAutoComplete</dfn></td>
            <td><pref>aria-autocomplete</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaBrailleLabel</dfn></td>
            <td><pref>aria-braillelabel</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaBrailleRoleDescription</dfn></td>
            <td><pref>aria-brailleroledescription</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaBusy</dfn></td>
            <td><sref>aria-busy</sref></td>
          </tr>
          <tr>
            <td><dfn>ariaChecked</dfn></td>
            <td><sref>aria-checked</sref></td>
          </tr>
          <tr>
            <td><dfn>ariaColCount</dfn></td>
            <td><pref>aria-colcount</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaColIndex</dfn></td>
            <td><pref>aria-colindex</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaColIndexText</dfn></td>
            <td><pref>aria-colindextext</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaColSpan</dfn></td>
            <td><pref>aria-colspan</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaControlsElements</dfn></td>
            <td><pref>aria-controls</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaCurrent</dfn></td>
            <td><sref>aria-current</sref></td>
          </tr>
          <tr>
            <td><dfn>ariaDescribedByElements</dfn></td>
            <td><pref>aria-describedby</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaDescription</dfn></td>
            <td><pref>aria-description</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaDetailsElements</dfn></td>
            <td><pref>aria-details</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaDisabled</dfn></td>
            <td><sref>aria-disabled</sref></td>
          </tr>
          <tr>
            <td><dfn>ariaErrorMessageElements</dfn></td>
            <td><pref>aria-errormessage</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaExpanded</dfn></td>
            <td><sref>aria-expanded</sref></td>
          </tr>
          <tr>
            <td><dfn>ariaFlowToElements</dfn></td>
            <td><pref>aria-flowto</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaHasPopup</dfn></td>
            <td><pref>aria-haspopup</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaHidden</dfn></td>
            <td><sref>aria-hidden</sref></td>
          </tr>
          <tr>
            <td><dfn>ariaInvalid</dfn></td>
            <td><sref>aria-invalid</sref></td>
          </tr>
          <tr>
            <td><dfn>ariaKeyShortcuts</dfn></td>
            <td><pref>aria-keyshortcuts</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaLabel</dfn></td>
            <td><pref>aria-label</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaLabelledByElements</dfn></td>
            <td><pref>aria-labelledby</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaLevel</dfn></td>
            <td><pref>aria-level</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaLive</dfn></td>
            <td><pref>aria-live</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaModal</dfn></td>
            <td><pref>aria-modal</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaMultiLine</dfn></td>
            <td><pref>aria-multiline</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaMultiSelectable</dfn></td>
            <td><pref>aria-multiselectable</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaOrientation</dfn></td>
            <td><pref>aria-orientation</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaOwnsElements</dfn></td>
            <td><pref>aria-owns</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaPlaceholder</dfn></td>
            <td><pref>aria-placeholder</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaPosInSet</dfn></td>
            <td><pref>aria-posinset</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaPressed</dfn></td>
            <td><sref>aria-pressed</sref></td>
          </tr>
          <tr>
            <td><dfn>ariaReadOnly</dfn></td>
            <td><pref>aria-readonly</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaRelevant</dfn></td>
            <td><pref>aria-relevant</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaRequired</dfn></td>
            <td><pref>aria-required</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaRoleDescription</dfn></td>
            <td><pref>aria-roledescription</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaRowCount</dfn></td>
            <td><pref>aria-rowcount</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaRowIndex</dfn></td>
            <td><pref>aria-rowindex</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaRowIndexText</dfn></td>
            <td><pref>aria-rowindextext</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaRowSpan</dfn></td>
            <td><pref>aria-rowspan</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaSelected</dfn></td>
            <td><sref>aria-selected</sref></td>
          </tr>
          <tr>
            <td><dfn>ariaSetSize</dfn></td>
            <td><pref>aria-setsize</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaSort</dfn></td>
            <td><pref>aria-sort</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaValueMax</dfn></td>
            <td><pref>aria-valuemax</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaValueMin</dfn></td>
            <td><pref>aria-valuemin</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaValueNow</dfn></td>
            <td><pref>aria-valuenow</pref></td>
          </tr>
          <tr>
            <td><dfn>ariaValueText</dfn></td>
            <td><pref>aria-valuetext</pref></td>
          </tr>
        </table>
        <p class="note">Note: Attributes <pref>aria-dropeffect</pref> and <sref>aria-grabbed</sref> were deprecated in ARIA 1.1 and do not have corresponding IDL attributes.</p>

        <section class="informative" id="idl_attr_disambiguation">
          <h3>Disambiguation Pattern</h3>
          <p>Though specification authors can make exceptions to this pattern, the following rules were used to disambiguate names and case of the IDL attributes listed above.</p>
          <ul>
            <li>
              Any attribute name referencing concepts that are combinations of two or more words (such as "value text") becomes a camel-cased IDL attribute capitalizing each word boundary. For
              example, <pref>aria-valuetext</pref> becomes <code>ariaValueText</code> with both the V and T capitalized.
            </li>
            <li>
              Likewise, any attribute name referencing concepts that can be hyphenated (such as "multi-selectable") becomes a camel-cased IDL attribute capitalizing each hyphenation boundary. For
              example, the only valid spelling for "multi-selectable" is hyphenated, so <pref>aria-multiselectable</pref> becomes <code>ariaMultiSelectable</code> with both the M and S capitalized.
            </li>
            <li>
              When trusted dictionary sources list both hyphenated or non-hyphenated spellings (e.g. "multi-line" and "multiline" are both valid spellings) use the hyphenated version and apply the
              hyphenation rule above. For example, <pref>aria-multiline</pref> becomes <code>ariaMultiLine</code> with both the M and L capitalized.
            </li>
            <li>
              If all trusted dictionary sources list a single spelling of a compound word with no spaces or hyphens, only the first letter of the term is capitalized. For example, neither
              “place-holder” nor “place holder” are considered valid spellings of the term “placeholder,” so <pref>aria-placeholder</pref> becomes <code>ariaPlaceholder</code> with only the P
              capitalized.
            </li>
            <li>There are currently no acronym-based ARIA attributes, but if future attributes include acronym usage, attempt to match existing DOM conventions (e.g. ID becomes Id).</li>
          </ul>
        </section>
        <section class="informative" id="idl_attr_exceptions">
          <h3>IDL Attribute Name Notes or Exceptions</h3>
          <p>Any notes or exceptions for specific attribute names will be listed here.</p>
          <ul>
            <li>
              <code>ariaPosInSet</code>: The <pref>aria-posinset</pref> attribute refers to an item's position in a set (two words: "in set") rather than the "inset" of an item from the beginning of
              the collection. Therefore the IDL attribute name is <code>ariaPosInSet</code> with the P, I, and second S capitalized, <em>not</em> <code>ariaPosInset</code>.
            </li>
          </ul>
        </section>
      </section>

      <section class="informative" id="idl_example_usage">
        <h2>Example IDL Attribute Usage</h2>
        <p>The primary purpose of ARIA IDL attribute reflection is to ease JavaScript-based manipulation of values. The following examples demonstrate its usage.</p>
        <aside class="example">
          <!-- ReSpec needs these examples to be unindented. -->
          <pre>
&lt;div id="inaccessibleButton"&gt;
    &lt;!-- Use semantic markup instead. This is just a retrofit example. --&gt;
&lt;/div&gt;</pre
          >
          <pre>
// Get a reference to the element.
let el = document.getElementById('inaccessibleButton');
el.tabIndex = 0; // Make it focusable.

// Set the role and label.
el.role = "button";
el.ariaLabel = "Edit";

// Get the role and label.
el.role; // Returns "button"
el.ariaLabel; // Returns "Edit"

// These are interchangeable with the more verbose setAttribute and getAttribute methods.
el.setAttribute("role", "button");
el.setAttribute("aria-label", "Edit");
el.getAttribute("role"); // Returns "button"
el.getAttribute("aria-label"); // Returns "Edit"

// Changes via either interface are reflected by the other.
el.setAttribute("aria-label", "Delete");
el.ariaLabel; // Returns "Delete"
el.ariaLabel = "Publish";
el.getAttribute("aria-label"); // Returns "Publish"</pre
          >
        </aside>
      </section>
    </section>
    <section class="informative">
      <h2>Security Considerations</h2>
      <p>This specification introduces no new security considerations.</p>
    </section>
    <section class="informative">
      <h2>Privacy Considerations</h2>
      <p>
        In accordance with <a data-cite="design-principles#do-not-expose-use-of-assistive-tech">Web Platform Design Principles</a>, this specification provides no programmatic interface to determine
        if information is being used by Assistive Technologies. However, this specification does allow an author to present different information to users of Assistive Technologies from the
        information available to users who do not use Assistive Technologies. This is possible using many features of the ARIA specification, just as this is possible using many other parts of the web
        technology stack. This content disparity could be abused to perform <a data-cite="fingerprinting-guidance#active-0">active fingerprinting</a> of users of Assistive Technologies.
      </p>
    </section>
    <section class="informative appendix" id="typemapping">
      <h2>Mapping WAI-ARIA Value types to languages</h2>
      <p class="note">
        The HTML column of the table below is advisory. Guidance on use of WAI-ARIA state and properties in HTML is provided in
        <a data-cite="html-aria/#docconformance">Document conformance requirements for use of ARIA attributes in HTML</a> ([[HTML-ARIA]]).
      </p>
      <p class="note">
        The suggested mappings for true/false values in HTML use <a data-cite="html/common-microsyntaxes.html#keywords-and-enumerated-attributes">Keyword and enumerated attributes</a> with allowed
        values of <code>true</code> and <code>false</code>, instead of using the HTML boolean value type.
        <!--@@ can't rely on attribute absence because of default value in true/false/undefined case.-->
      </p>
      <p>The table below provides recommended mappings between WAI-ARIA state and property types and attribute types from [[[HTML]]] and [[[XMLSCHEMA11-2]]].</p>
      <p>
        Languages not listed below might have appropriate value types defined in the language. If they do not, we recommend XML Schema Datatypes for general purpose XML languages. Documents using DTDs
        instead of schemas will not be able to validate automatically and require additional processing on WAI-ARIA attributes.
      </p>
      <table class="data">
        <tr>
          <th scope="col">WAI-ARIA type</th>
          <th scope="col">HTML</th>
          <th scope="col">XML Schema</th>
        </tr>
        <tr>
          <td>true/false</td>
          <td><a data-cite="html/common-microsyntaxes.html#keywords-and-enumerated-attributes">Keyword and enumerated attributes</a> with allowed values of &quot;true&quot; and &quot;false&quot;</td>
          <td><a data-cite="xmlschema11-2/#boolean">boolean</a></td>
        </tr>
        <tr>
          <td>true/false/undefined</td>
          <td>
            <a data-cite="html/common-microsyntaxes.html#keywords-and-enumerated-attributes">Keyword and enumerated attributes</a> with allowed values of <code>true</code>, <code>false</code>, and
            <code>undefined</code>
          </td>
          <td>
            <a data-cite="xmlschema11-2/#NMTOKEN">NMTOKEN</a> with an <a href="https://www.w3.org/TR/xmlschema11-2/#NMTOKEN">enumeration constraint</a> allowing values of <code>true</code>,
            <code>false</code>, and <code>undefined</code>
          </td>
        </tr>
        <tr>
          <td>tristate</td>
          <td>
            <a data-cite="html/common-microsyntaxes.html#keywords-and-enumerated-attributes">Keyword and enumerated attributes</a> with allowed values of &quot;true&quot;, &quot;false&quot;, and
            &quot;mixed&quot;
          </td>
          <td>
            <a data-cite="xmlschema11-2/#NMTOKEN">NMTOKEN</a> with an <a href="https://www.w3.org/TR/xmlschema11-2/#NMTOKEN">enumeration constraint</a> allowing values of &quot;true&quot;,
            &quot;false&quot;, and &quot;mixed&quot;
          </td>
        </tr>
        <tr>
          <td>number</td>
          <td><a data-cite="html/common-microsyntaxes.html#floating-point-numbers">Floating-point numbers</a></td>
          <td><a data-cite="xmlschema11-2/#decimal">decimal</a></td>
        </tr>
        <tr>
          <td>integer</td>
          <td><a data-cite="html/common-microsyntaxes.html#floating-point-numbers">Non-negative integer</a></td>
          <td><a data-cite="xmlschema11-2/#integer">integer</a></td>
        </tr>
        <tr>
          <td>token</td>
          <td><a data-cite="html/common-microsyntaxes.html#keywords-and-enumerated-attributes">Keyword and enumerated attributes</a></td>
          <td>
            <a data-cite="xmlschema11-2/#NMTOKEN">NMTOKEN</a> with an <a data-cite="xmlschema11-2/#dt-enumeration">enumeration constraint</a> allowing values listed in the state or property definition
          </td>
        </tr>
        <tr>
          <td>token list</td>
          <td><a data-cite="html/common-microsyntaxes.html#space-separated-tokens">Space-separated tokens</a></td>
          <td>
            <a data-cite="xmlschema11-2/#NMTOKENS">NMTOKENS</a> with an <a data-cite="xmlschema11-2/#dt-enumeration">enumeration constraint</a> allowing values listed in the state or property
            definition
          </td>
        </tr>
        <tr>
          <td>ID reference</td>
          <td>The value of a defined <a data-cite="html/dom.html#the-id-attribute">id attribute</a> on another element</td>
          <td><a data-cite="xmlschema11-2/#IDREF">IDREF</a></td>
        </tr>
        <tr>
          <td>ID reference list</td>
          <td>
            The value of one or more defined <a data-cite="html/dom.html#the-id-attribute">id attributes</a> on other element(s), represented as
            <a data-cite="html/common-microsyntaxes.html#space-separated-tokens">Space-separated tokens</a>
          </td>
          <td><a data-cite="xmlschema11-2/#IDREFS">IDREFS</a></td>
        </tr>
        <tr>
          <td>string</td>
          <td>No value constraints</td>
          <td><a data-cite="xmlschema11-2/#string">string</a></td>
        </tr>
      </table>
    </section>
    <section class="appendix" id="changelog">
      <h2>Change Log</h2>
      <section>
        <h2>Major feature in this release</h2>
        <ul>
          <li>11-Mar-2020: Add <pref>aria-braillelabel</pref></li>
          <li>13-Feb-2020: Role <rref>suggestion</rref> added</li>
          <li>11-Feb-2020: Update <pref>aria-details</pref> to allow multiple IDrefs</li>
          <li>11-Feb-2020: Role <rref>comment</rref> added</li>
          <li>16-Jan-2020: Add <pref>aria-description</pref></li>
          <li>15-Jan-2020: Role <rref>mark</rref>: Added</li>
          <li>14-Oct-2019: Add <pref>aria-brailleroledescription</pref></li>
        </ul>
      </section>
      <section>
        <h2>Substantive changes since ARIA 1.2</h2>
        <!-- <rs-changelog from="3a3edfb" filter="respecChangelogFilter"></rs-changelog> -->
        <ul>
          <li><a href="https://github.com/w3c/aria/commit/4d3fefe">Fix link to definition of accessibility child</a></li>
          <li><a href="https://github.com/w3c/aria/commit/5bd87f4">interop-accessibilty repo rename</a> (<a href="https://github.com/w3c/aria/pull/2077">#2077</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/0486a98">Add statemment about translating in keyshortcuts</a> (<a href="https://github.com/w3c/aria/pull/2041">#2041</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/9b2a146">Clarify that user agents should not expose aria-haspopup=false</a> (<a href="https://github.com/w3c/aria/pull/2030">#2030</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/ff9b9c3">Add accessibility web stack and tests diagrams</a> (<a href="https://github.com/w3c/aria/pull/2009">#2009</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/ef1ad85">Makes aria-braillelabel prohibited whereever aria-label is prohibited…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/122fad6">"cell" and "treegrid" roles are the only ones without any reference t…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/411bd50">Updated the characteristics table of "caption" role</a> (<a href="https://github.com/w3c/aria/pull/1975">#1975</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/dc19188">Clarification for exposure of generic elements</a> (<a href="https://github.com/w3c/aria/pull/1949">#1949</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/051ed84">Distinction between none and generic</a> (<a href="https://github.com/w3c/aria/pull/1959">#1959</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/cd6b483">fix/1939 swap presentation/none roles</a> (<a href="https://github.com/w3c/aria/pull/1945">#1945</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/7205d35">aria-atomic has no default</a> (<a href="https://github.com/w3c/aria/pull/1894">#1894</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/232ae78">Update required owned elements and required context role</a> (<a href="https://github.com/w3c/aria/pull/1454">#1454</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/11902fc">aria-errormessage is hidden or removed when not pertinent</a> (<a href="https://github.com/w3c/aria/pull/1588">#1588</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/c77c2c4">Add search role’s base concept pointing to HTML spec. Fix #1898</a> (<a href="https://github.com/w3c/aria/pull/1900">#1900</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/abbef89">role=note fleshed out a little.</a> (<a href="https://github.com/w3c/aria/pull/1639">#1639</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/af84654">fix(aria-level): update to specify only level 1-6</a> (<a href="https://github.com/w3c/aria/pull/1873">#1873</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/11c8909">Change aria-errormessage to ID reference list</a> (<a href="https://github.com/w3c/aria/pull/1802">#1802</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/a31260e">fix: Permit UA to ignore user-triggered changes inside live regions (…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/7314996">Are all constraints inherited?</a> (<a href="https://github.com/w3c/aria/pull/1815">#1815</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/bcf44d1">Allude to other widgets that allow group in group role definition (#1…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/c625cb7">update figure role</a> (<a href="https://github.com/w3c/aria/pull/1705">#1705</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/2617046">Add accessibility tree definition</a> (<a href="https://github.com/w3c/aria/pull/1784">#1784</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/72063a0">remove overly prescriptive distinctions from aria-current values. (#1…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/8ef7dde">proposed rewording for the complementary landmark</a> (<a href="https://github.com/w3c/aria/pull/1698">#1698</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/d925596">fix(reword): use 'on a page' instead of 'within any document or appli…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/483334d">add [CEReactions] to IDL.</a> (<a href="https://github.com/w3c/aria/pull/1766">#1766</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/82bd83f">Resolving user agent must not statement and whitespace defs</a> (<a href="https://github.com/w3c/aria/pull/1778">#1778</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/ece14a1">Revised complementary definition re: DOM hierarchy</a> (<a href="https://github.com/w3c/aria/pull/1779">#1779</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/7a56f40">Fix for "name required" for tab at 5.2.8.4 and 5.2.8.5</a> (<a href="https://github.com/w3c/aria/pull/1771">#1771</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/6d46a9a">Clarify description for aria-keyshortcuts</a> (<a href="https://github.com/w3c/aria/pull/1713">#1713</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/060b878">Resolves #978, add back ARIA element reflection IDL</a> (<a href="https://github.com/w3c/aria/pull/1755">#1755</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/9cb71e9">add note to aria-roledescription</a> (<a href="https://github.com/w3c/aria/pull/1666">#1666</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/2ece5c5">include mention of figure/caption</a> (<a href="https://github.com/w3c/aria/pull/1704">#1704</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/f215561">Replace irrelevant ariaDescribedBy example with ariaValueText</a> (<a href="https://github.com/w3c/aria/pull/1729">#1729</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/2d2d341">revise caption definition</a> (<a href="https://github.com/w3c/aria/pull/1703">#1703</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/43b6a45">added a label to the combobox listbox example</a> (<a href="https://github.com/w3c/aria/pull/1728">#1728</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/51e0073">Update authoring requirement for aria-selected on options</a> (<a href="https://github.com/w3c/aria/pull/1719">#1719</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/47db8e8">Handling Author Errors: form &amp; region roles</a> (<a href="https://github.com/w3c/aria/pull/1683">#1683</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/e138d5c">add lang clarification to translatable attributes section.</a> (<a href="https://github.com/w3c/aria/pull/1690">#1690</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/157d711">abstract roles remove 'name from'</a> (<a href="https://github.com/w3c/aria/pull/1667">#1667</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/3aed0e2">Fix: add aria-level as supported on treeitem</a> (<a href="https://github.com/w3c/aria/pull/1676">#1676</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/e1d9d12">progressbar: clarify described-by</a> (<a href="https://github.com/w3c/aria/pull/1671">#1671</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/b710565">Update aria sort value descriptions to include "row" fixes #1614</a> (<a href="https://github.com/w3c/aria/pull/1616">#1616</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/028bbbb">Change aria-keyshortcuts initial keyword from Indicates to Defines. R…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/9653692">Add note to checkbox def</a> (<a href="https://github.com/w3c/aria/pull/1657">#1657</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/1e0383a">removed references to &lt;range&gt;</a> (<a href="https://github.com/w3c/aria/pull/1652">#1652</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/bd03476">updates to IDL section per discussion in #1598</a> (<a href="https://github.com/w3c/aria/pull/1633">#1633</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/0d06a71">Update IDL and enumerated attribute section</a> (<a href="https://github.com/w3c/aria/pull/1611">#1611</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/b41a010">Revisions to accessible name required</a> (<a href="https://github.com/w3c/aria/pull/1477">#1477</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/7f72832">Remove aria-level attribute from listitem</a> (<a href="https://github.com/w3c/aria/pull/1484">#1484</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/912ff77">rewording of how a _name_ (not necessarily a “label” - so changed tha…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/627b3a6">Change containing to owning in Required Owned Elements.</a> (<a href="https://github.com/w3c/aria/pull/1438">#1438</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/103dec9">Revert new labeling mechanisms</a> (<a href="https://github.com/w3c/aria/pull/1491">#1491</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/f4c6669">Add and link attribute terms: Defines, Identifies, and Indicates. (#1…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/d75a248">Add role=image as synonym for role=img</a> (<a href="https://github.com/w3c/aria/pull/1370">#1370</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/3ebb415">add local abstract role usage warnings. fixes #1428</a> (<a href="https://github.com/w3c/aria/pull/1445">#1445</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/e482b6f">clarify "current element"</a> (<a href="https://github.com/w3c/aria/pull/1460">#1460</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/8c597bf">prohibit name from time role</a> (<a href="https://github.com/w3c/aria/pull/1464">#1464</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/e68a7ff">update bullet 3 of name calc</a> (<a href="https://github.com/w3c/aria/pull/1475">#1475</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/c908c7f">Updated aria-setsize and aria-posinset to clarify usage for authors (…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/8fa8068">Assistive tech SHOULD provide landmark navigation... user agents MAY …</a></li>
          <li><a href="https://github.com/w3c/aria/commit/327a22f">Adds sentence about group role</a> (<a href="https://github.com/w3c/aria/pull/1422">#1422</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/ce5d37d">Use "containing/contained by" wording instead of arrow abbreviations …</a></li>
          <li><a href="https://github.com/w3c/aria/commit/c38c9af">resolves #1407 by changing example in aria-brailleroledescription (#1…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/3dc85aa">resolves #1394, remove misleading note about AT modifying attrs direc…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/4c3484b">Fix remaining instance of confusing role="none presentation" note (#1…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/4f387e3">Move section on presentation role conflicts to “Handling Author Error…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/b35ecf9">Implicit values for required properties section needs revising</a> (<a href="https://github.com/w3c/aria/pull/1414">#1414</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/0218c25">aria-expanded requirement needs to be the same for tab and tablist (#…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/fc6b7fb">Listbox and tree: clarify requirements for selected and checked</a> (<a href="https://github.com/w3c/aria/pull/1340">#1340</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/c803925">Tighten up Required Context Role: group</a> (<a href="https://github.com/w3c/aria/pull/1359">#1359</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/e496a4d">term/definition should use aria-details instead of aria-labelledby (#…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/48ad8d4">Add a conditional on when aria-controls is needed</a> (<a href="https://github.com/w3c/aria/pull/1335">#1335</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/257b0e1">make menuitemradio subclass menuitem, require aria-checked</a> (<a href="https://github.com/w3c/aria/pull/1354">#1354</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/78ab6b6">Stricter language for authors using aria-owns</a> (<a href="https://github.com/w3c/aria/pull/1351">#1351</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/42417ce">improve wording for braille patterns</a> (<a href="https://github.com/w3c/aria/pull/1287">#1287</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/fc91e55">aria-braille properties: improve authoring note</a> (<a href="https://github.com/w3c/aria/pull/1291">#1291</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/586af31">remove name required from marquee</a> (<a href="https://github.com/w3c/aria/pull/1342">#1342</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/02fee23">Generalize AccessibilityRole/AriaAttributes IDL</a> (<a href="https://github.com/w3c/aria/pull/984">#984</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/d781656">Add editor note for label role</a></li>
          <li><a href="https://github.com/w3c/aria/commit/26cb23d">Issue 1151: updated document to use the terms owned and container for…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/48282a0">Fix list structure for required owners in `suggestion`</a> (<a href="https://github.com/w3c/aria/pull/1293">#1293</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/37ca124">Clarify wording in "Including Elements in the Accessibility Tree" sec…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/9c73b5b">Make fallback value for separator aria-valuenow consistent with scrol…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/99763b0">feat: aria-braillelabel</a> (<a href="https://github.com/w3c/aria/pull/923">#923</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/db5a8c5">brailleroledescription update</a> (<a href="https://github.com/w3c/aria/pull/1097">#1097</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/76474e5">Remove superfluous authoring requirement to specify aria-multiline (#…</a></li>
          <li><a href="https://github.com/w3c/aria/commit/2a047fd">Add suggestion role</a> (<a href="https://github.com/w3c/aria/pull/1134">#1134</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/dfe62bf">clarify that modal requires an accessible name</a> (<a href="https://github.com/w3c/aria/pull/1180">#1180</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/8420961">Correct mistake in aria-description pointed out in issue 1186.</a> (<a href="https://github.com/w3c/aria/pull/1193">#1193</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/e8b2274">Update aria-details</a> (<a href="https://github.com/w3c/aria/pull/1136">#1136</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/eed0ef0">Add comment role</a> (<a href="https://github.com/w3c/aria/pull/1135">#1135</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/f262087">Add aria-description</a> (<a href="https://github.com/w3c/aria/pull/1137">#1137</a>)</li>
          <li><a href="https://github.com/w3c/aria/commit/b3017b3">Add mark role</a> (<a href="https://github.com/w3c/aria/pull/1133">#1133</a>)</li>
        </ul>
      </section>
    </section>
    <!--
<section class="informative appendix" id="quickref">
	<h2>WAI-ARIA Role, State, and Property Quick Reference</h2>
	<p>The following table provides a quick reference to the supported states and properties for all WAI-ARIA roles that may be used in markup.</p>
	<div id="quickref_global_states">
		<p>In addition to the states and properties shown in the table, the following global states and properties are supported on all roles.</p>
		<p class="placeholder">Placeholder for global states and properties</p>
	</div>
	<p class="placeholder">Placeholder for quick reference table</p>
</section>
-->
    <section class="appendix informative section" id="acknowledgements">
      <h3>Acknowledgments</h3>
      <p>The following people contributed to the development of this document.</p>
      <ul id="gh-contributors">
        <!-- list of contributors will appear here,
					 along with link to their GitHub profiles -->
      </ul>
      <section class="section" id="ack_group">
        <h4>ARIA WG participants at the time of publication</h4>
        <ul>
          <!-- List of participants is injected here -->
        </ul>
      </section>
      <div data-include="common/acknowledgements/funders.html" data-include-replace="true"></div>
    </section>
  </body>
</html>