Movatterモバイル変換

5.The Roles Model

This section definesWAI-ARIA roles and describes their characteristics and properties.

The roles, their characteristics, the states and properties they support, and specification of how they can be used in markup, shall be considered normative.

In order to reflect the content in theDOM, user agentsSHOULD map the role attribute to the appropriate value in the implemented accessibility API, and user agentsSHOULD update the mapping when the role attribute changes.

5.1Relationships Between Concepts

The Roles Model uses the following relationships to relateWAI-ARIA roles to each other and to concepts from other specifications, such as HTML.

5.1.1Superclass Role

Therole 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.

5.1.2Subclass Roles

Informative list ofroles for which this role is the superclass. This is provided to facilitate reading of the specification but adds no new information.

5.1.3Related Concepts

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.

For example, a progress bar is like a status indicator. Therefore, theprogressbarwidget has a related concept which includesstatus. However, if the definition ofstatus is modified, the definition of aprogressbar is not affected.

5.1.4Base Concept

Informative data aboutobjects that are considered prototypes for therole. 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 arelated concept except that the base concept is almost identical to the role definition.

For example, thecheckbox defined in this document has similar functionality and anticipated behavior to a<input type="checkbox"> defined inHTML. Therefore, a checkbox has an [HTML]checkbox as abaseConcept. However, if the original [HTML] checkbox baseConcept definition is modified, the definition of acheckbox in this document will not be affected, because there is no actual inheritance of the respective type.

5.2Characteristics of Roles

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 ofwidgets this also includes how it interacts with theuser agent based on mapping toHTML forms. States and properties from WAI-ARIA that are supported by the role are also indicated.

Roles define the following characteristics.

5.2.1Abstract Roles

Abstractroles are the foundation upon which all otherWAI-ARIA roles are built. AuthorsMUST NOT use abstract roles because they are not implemented in the API binding. User agentsMUST NOT map abstract roles to the standard role mechanism of the accessibility API. Abstract roles are provided to help with the following:

Organize the Roles Model and provide roles with a meaning in the context of known concepts.
Streamline the addition of roles that include necessary features.

5.2.2Required States and Properties

States andproperties specifically required for therole and subclass roles. AuthorsMUST provide a non-emptyvalue for required states and properties. AuthorsMUST NOT use the valueundefined for required states and properties, unlessundefined is an explicitly-supported value of that state or property.

When anobject 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.

Note

A host language attribute with the appropriateimplicit WAI-ARIA semantic fulfills this requirement.

5.2.3Supported States and Properties

States andproperties specifically applicable to therole and child roles. AuthorsMAY providevalues for supported states and properties, but need not in cases where default values are sufficient.user agentsMUST map all supported states and properties for the role to an accessibilityAPI. If the state or property is undefined and it has a default value for the role,user agentsSHOULD expose the default value.

Note

A host language attribute with the appropriateimplicit WAI-ARIA semantic fulfills this requirement.

5.2.4Inherited States and Properties

Informative list of properties that are inherited by arole from superclass roles.States andproperties are inherited from superclass roles in the Roles Model, not from ancestorelements in theDOM 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.

5.2.5Prohibited States and Properties

List of states and properties that are prohibited on arole. AuthorsMUST NOT specify a prohibited state or property.

Note

A host language attribute with the appropriateimplicit WAI-ARIA semantic would also prohibit a state or property in this section.

5.2.6Allowed Accessibility Child Roles

A list of roles which are allowed on anaccessibility child (simplified as "child") of the element with thisrole. AuthorsMUST only add child element with allowed roles. For example, an element with the rolelist can own child elements with the rolelistitem, but cannot own elements with the roleoption.

To determine whether an element is thechild of an element,user agentsMUST ignore any intervening elements with the rolegeneric ornone.

Descendants which are not children of an element ancestor are not constrained byallowed accessibility child roles. For example, animage is not an allowed child of alist, but it is a valid descendant if it is also a descendant of thelist's allowed childlistitem.

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. Seerequired accessibility parent roles for requirements about the context where elements of a given role will be contained.

Note

An element with asubclass role of the 'allowed accessibility child role' does not fulfill this requirement. For example, thelistbox role allows a child element using theoption orgroup role. Although thegroup role is the superclass ofrow, adding a child element with a role ofrow will not fulfill the requirement thatlistbox allows children withoption orgroup roles.

Note

An element with the appropriateimplicit WAI-ARIA semantic fulfills this requirement.

Note

Examples of valid ways to mark up allowed accessibility child roles include:

DirectDOM child:

Example 5

<divrole="listbox"><divrole="option">option text</div></div>

DOM child with generics intervening:

Example 6

<divrole="listbox"><div><divrole="option">option text</div></div></div>

Directaria-owns relationship:

Example 7

<divrole="listbox"aria-owns="id1"></div><divrole="option"id="id1">option text</div>

aria-owns relationship with generics intervening:

Example 8

<divrole="listbox"aria-owns="id1"></div><divid="id1"><div><divrole="option">option text</div></div></div>

5.2.7Required Accessibility Parent Role

The requiredaccessibility parent (simplified as "parent") role defines the container where thisrole is allowed. If a role has a required accessibility parent, authorsMUST ensure that an element with the role is anaccessibility child of an element with the required accessibility parent role. For example, an element with rolelistitem is only meaningful when it is a child of an element with rolelist.

To determine whether an element has a parent with the required role,user agentsMUST ignore any elements with the rolegeneric ornone.

Also,user agentsSHOULD ignore the role if it occurs outside the context of a required accessibility parent role.

Note

An element with the appropriateimplicit WAI-ARIA semantic fulfills this requirement.

5.2.8Name From

Determines which content contributes to theAccessible Name and Description Computation [ACCNAME-1.2].

One of the following values:

author: name comes from values provided by the author in explicit markup features such as thearia-label attribute, thearia-labelledby attribute, or the host language labeling mechanism, such as thealt ortitle attributes inHTML, with HTMLtitle attribute having the lowest precedence for specifying a text alternative.
contents: name comes from the text value of the element node. Although this might be allowed in addition to "author" in someroles, this is used in content only if higher priority "author" features are not provided. Priority is defined by theAccessible Name and Description Computation [ACCNAME-1.2].
prohibited: the element does not support name from author. AuthorsMUST NOT use thearia-label oraria-labelledby attributes to name the element.

5.2.8.1Roles Supporting Name from Author

alert
alertdialog
application (name required)
article
banner
blockquote
button (name required)
cell
checkbox (name required)
columnheader (name required)
combobox (name required)
comment
complementary
contentinfo
dialog
directory
document
feed
figure
form
grid
gridcell
group
heading (name required)
image (name required)
link (name required)
list
listbox (name required)
listitem
log
main
marquee
math
menu
menubar
menuitem (name required)
menuitemcheckbox (name required)
menuitemradio (name required)
meter (name required)
navigation
note
option (name required)
progressbar (name required)
radio (name required)
radiogroup
region (name required)
row
rowgroup
rowheader (name required)
scrollbar
search
searchbox (name required)
sectionfooter
sectionheader
separator
slider (name required)
spinbutton (name required)
status
switch (name required)
tab (name required)
table
tablist
tabpanel (name required)
textbox (name required)
timer
toolbar
tooltip
tree (name required)
treegrid (name required)
treeitem (name required)

5.2.8.2Roles Supporting Name from Content

button (name required)
cell
checkbox (name required)
columnheader (name required)
comment
gridcell
heading (name required)
link (name required)
menuitem (name required)
menuitemcheckbox (name required)
menuitemradio (name required)
option (name required)
radio (name required)
row
rowheader (name required)
switch (name required)
tab (name required)
tooltip
treeitem (name required)

5.2.8.3Roles which cannot be named (Name prohibited)

5.2.9Children Presentational

Indicates whetherDOM descendants are presentational.user agentsSHOULD NOT expose descendants of thiselement through the platformaccessibility API. Ifuser agents do not hide the descendant nodes, some information might be read twice.

AuthorsMUST NOT specifyaria-owns on an element which has Presentational Children.

5.2.10Implicit Value for Role

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 forstate or property name isnew default value". Roles that define this have the new default value for the state or property if the author does not provide an explicit value.

5.3Categorization of Roles

To support the current user scenario, this specification categorizesroles that define user interfacewidgets (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 roleapplication ordocument.

A visual description of the relationships among roles is available in the ARIA 1.2 Class Diagram.

Roles are categorized as follows:

5.3.1Abstract Roles

The followingroles are used to support theWAI-ARIA Roles Model for the purpose of defining general role concepts.

Abstract roles are used for the ontology. AuthorsMUST NOT use abstract roles in content.

5.3.2Widget Roles

The following roles act as standalone user interface widgets or as part of larger, composite widgets.

The following roles act as composite user interface widgets. These roles typically act as containers that manage other, contained widgets.

5.3.3Document Structure Roles

The followingroles describe structures that organize content in a page. Document structures are not usually interactive.

5.3.4Landmark Roles

The followingroles are regions of the page intended as navigationallandmarks. All of these roles inherit from thelandmark base type and all are imported from theRole Attribute [ROLE-ATTRIBUTE]. The roles are included here in order to make them clearly part of theWAI-ARIA Roles Model.

5.3.5Live Region Roles

The followingroles arelive regions and can be modified bylive region attributes.

Typically, assistive technology will only conveychanges to a live region, not the initial contents of a live region. To ensure content in a live region is announced, authorsSHOULD create a rendered but empty live region as early as possible (such as on page load), and then modify the content of the live region when the author expects changes to be spoken or brailled. The exception to this live region convention isalert, due to system accessibility notifications events required for the role. While analert is a live region, its content is announced by assistive technology when the alert is rendered on the page and when the content changes.

5.3.6Window Roles

The followingroles act as windows within the browser or application.

5.4Definition of Roles

Below is an alphabetical list ofWAI-ARIA roles.

Abstract roles are used for the ontology. AuthorsMUST NOT use abstract roles in content.

alert: A type oflive region with important, and usually time-sensitive, information. See relatedalertdialog andstatus.
alertdialog: A type of dialog that contains an alert message, where initial focus goes to anelement within the dialog. See relatedalert anddialog.
application: Astructure containing one or morefocusable elements requiring user input, such as keyboard or gesture events, that do not follow a standard interaction pattern supported by awidget role.
article: A section of a page that consists of a composition that forms an independent part of a document, page, or site.
banner: Alandmark that contains mostly site-oriented content, rather than page-specific content.
blockquote: A section of content that is quoted from another source.
button: An input that allows for user-triggered actions when clicked or pressed. See relatedlink.
caption: Visible content that names, or describes afigure,grid,group,radiogroup,table ortreegrid.
cell: A cell in a tabular container. See relatedgridcell.
checkbox: A checkable input that has three possiblevalues:true,false, ormixed.
code: A section whose content represents a fragment of computer code.
columnheader: A cell containing header information for a column.
combobox: Aninput that controls another element, such as alistbox orgrid, that can dynamically pop up to help the user set the value of theinput.
command (abstract role): A form of widget that performs an action but does not receive input data.
comment: A comment contains content expressing reaction to other content.
complementary: Alandmark 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.
composite (abstract role): Awidget that can contain navigableaccessibility descendants.
contentinfo: Alandmark that contains information about the parent document.
definition: A definition of a term or concept. See relatedterm.
deletion: 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 relatedinsertion.
dialog: A dialog is a descendant window of the primary window of a web application. ForHTML pages, the primary application window is the entire web document.
directory: [Deprecated inARIA 1.2] A list of references to members of a group, such as a static table of contents.
document: Anelement containing content thatassistive technology users might want to browse in a reading mode.
emphasis: One or more emphasized characters. See relatedstrong.
feed: A scrollablelist ofarticles where scrolling might causearticles to be added to or removed from either end of the list.
figure: A perceivablesection of content that typically contains agraphical document, images, media player, code snippets, or example text. The parts of afigureMAY be user-navigable.
form: Alandmark region that contains a collection of items and objects that, as a whole, combine to create a form. See relatedsearch.
generic: A nameless containerelement that has no semantic meaning on its own.
grid: A compositewidget containing a collection of one or more rows with one or more cells where some or all cells in the grid arefocusable by using methods of two-dimensional navigation, such as directional arrow keys.
gridcell: Acell in agrid ortreegrid.
group: A set of user interfaceobjects that is not intended to be included in a page summary or table of contents byassistive technologies.
heading: A heading for a section of the page.
image: A container for a collection ofelements that form an image. See synonymimg.
img: A container for a collection ofelements that form an image. See synonymimage.
input (abstract role): A generic type ofwidget that allows user input.
insertion: An insertion contains content that is marked as added or content that is being suggested for addition. See relateddeletion.
landmark (abstract role): A perceivablesection 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.
link: An interactive reference to an internal or external resource that, when activated, causes the user agent to navigate to that resource. See relatedbutton.
list: Asection containinglistitem elements. See relatedlistbox.
listbox: Awidget that allows the user to select one or more items from a list of choices. See relatedcombobox andlist.
listitem: A single item in a list or directory.
log: A type oflive region where new information is added in meaningful order and old information can disappear. See relatedmarquee.
main: Alandmark containing the main content of a document.
mark: Content which is marked or highlighted for reference or notation purposes, due to the content's relevance in the enclosing context.
marquee: A type oflive region where non-essential information changes frequently. See relatedlog.
math: Content that represents a mathematical expression.
menu: A type ofwidget that offers a list of choices to the user.
menubar: A presentation ofmenu that usually remains visible and is usually presented horizontally.
menuitem: An option in a set of choices contained by amenu ormenubar.
menuitemcheckbox: Amenuitem with a checkable state whose possiblevalues aretrue,false, ormixed.
menuitemradio: A checkablemenuitem in a set of elements with the same role, only one of which can be checked at a time.
meter: Anelement that represents a scalar measurement within a known range, or a fractional value. See relatedprogressbar.
navigation: Alandmark containing a collection of navigationalelements (usually links) for navigating the document or related documents.
none: Anelement whose implicit native role semantics will not be mapped to theaccessibility API. See synonympresentation.
note: Asection whose content represents additional information or parenthetical context to the primary content it supplements.
option: An item in alistbox.
paragraph: A paragraph of content.
presentation: Anelement whose implicit native role semantics will not be mapped to theaccessibility API. See synonymnone.
progressbar: Anelement that displays the progress status for tasks that take a long time.
radio: A checkable input in a group of elements with the same role, only one of which can be checked at a time.
radiogroup: A group ofradio buttons.
range (abstract role): An element representing a range of values.
region: Alandmark 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.
roletype (abstract role): The baserole from which all other roles inherit.
row: A row of cells in a tabular container.
rowgroup: A structure containing one or more row elements in a tabular container.
rowheader: A cell containing header information for a row.
scrollbar: 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.
search: Alandmark region that contains a collection of items and objects that, as a whole, combine to create a search facility. See relatedform andsearchbox.
searchbox: A type of textbox intended for specifying search criteria. See relatedtextbox andsearch.
section (abstract role): A renderable structural containment unit on a page.
sectionfooter: A set of user interface objects and information representing information about its closest ancestral content group. For instance, asectionfooter can include information about who wrote the specific section of content, such as anarticle. It can contain links to related documents, copyright information or other indices and colophon specific to the current section of the page.
sectionhead (abstract role): A structure that labels or summarizes the topic of its related section.
sectionheader: 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, asectionheader can include the heading, introductory statement and related meta data for a section of content, for instance aregion orarticle, within a web page.
select (abstract role): A form widget that allows the user to make selections from a set of choices.
separator: A divider that separates and distinguishes sections of content or groups of menuitems.
slider: An input where the user selects a value from within a given range.
spinbutton: A form ofrange that expects the user to select from among discrete choices.
status: A type oflive region whose content is advisory information for the user but is not important enough to justify analert, often but not necessarily presented as a status bar.
strong: Content that is important, serious, or urgent. See relatedemphasis.
structure (abstract role): A document structuralelement.
subscript: One or more subscripted characters. See relatedsuperscript.
suggestion: A single proposed change to content.
superscript: One or more superscripted characters. See relatedsubscript.
switch: A type of checkbox that represents on/off values, as opposed to checked/unchecked values. See relatedcheckbox.
tab: A grouping label providing a mechanism for selecting the tab content that is to be rendered to the user.
table: Asection containing data arranged in rows and columns. See relatedgrid.
tablist: A list oftabelements, which are references totabpanel elements.
tabpanel: A container for the resources associated with atab, where eachtab is contained in atablist.
term: A word or phrase with an optional corresponding definition. See relateddefinition.
textbox: A type of input that allows free-form text as its value.
time: An element that represents a specific point in time.
timer: A type oflive region containing a numerical counter which indicates an amount of elapsed time from a start point, or the time remaining until an end point.
toolbar: A collection of commonly used function buttons or controls represented in compact visual form.
tooltip: A contextual popup that displays a description for an element.
tree: Awidget that allows the user to select one or more items from a hierarchically organized collection.
treegrid: Agrid whose rows can be expanded and collapsed in the same manner as for atree.
treeitem: An item in atree.
widget (abstract role): An interactive component of a graphical user interface (GUI).
window (abstract role): A browser or application window.

`alert`role

A type oflive region with important, and usually time-sensitive, information. See relatedalertdialog andstatus.

Alerts are used to convey messages that will be immediately important to users. In the case of audio warnings, visibly displayed alerts provide an accessible alternative to audible alerts for Deaf or hard-of-hearing users. Likewise, alerts can provide an accessible alternative to the visible alerts for blind, deaf-blind, or low-vision users, and others with certain developmental disabilities. Thealertrole is applied to the element containing the alert message.

Alert is a special type of assertive live region that is intended to cause immediate notification for assistive technology users. If the operating system allows, theuser agentSHOULD fire a system alertevent through the accessibilityAPI when the alert is rendered.

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, authorsSHOULD NOT require users to close an alert. If an author desires focus to move to a message when it is conveyed, the authorSHOULD use alertdialog instead ofalert.

Elements with the rolealert have an implicitaria-live value ofassertive, and an implicitaria-atomic value oftrue.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Subclass Roles:	`alertdialog`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Implicit Value for Role:	Default for`aria-live` is`assertive`. Default for`aria-atomic` is`true`.

`alertdialog`role

A type of dialog that contains an alert message, where initial focus goes to anelement within the dialog. See relatedalert anddialog.

Alert dialogs are used to convey messages to alert the user. Thealertdialogrole goes on thenode containing both the alert message and the rest of the dialog. AuthorsSHOULD make alert dialogs modal by ensuring that, while thealertdialog is shown, keyboard and mouse interactions only operate within the dialog. Seearia-modal.

Alertdialog is a special type of dialog that is intended to cause an immediate, alert-level notification for assistive technology users. If the operating system allows, theuser agentSHOULD fire a system alertevent through the accessibilityAPI when the alert dialog is rendered.

Unlike alert,alertdialog 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, authorsSHOULD set focus to an active element within the alert dialog, such as a form control or confirmation button. Theuser agentSHOULD fire a system alertevent through the accessibilityAPI when the alert is created, provided one is specified by the intended accessibility API.

AuthorsSHOULD provide an accessible name for analertdialog, which can be done with thearia-label oraria-labelledby attribute.

AuthorsSHOULD usearia-describedby on analertdialog to reference the alert message element in the dialog. If they do not, anassistive technology can resort to its internal recovery mechanism to determine the contents of the alert message.

Characteristics:
Characteristic	Value
Superclass Role:	`alert` `dialog`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-modal` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`application`role

Astructure containing one or morefocusable elements requiring user input, such as keyboard or gesture events, that do not follow a standard interaction pattern supported by awidget role.

Someuser agents andassistive technologies 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 awidget role from receiving and using such keyboard and gesture events to provide interactive functionality.

When there is a need to create an element with an interaction model that is not supported by any of theWAI-ARIA widget roles, authorsMAY give that element roleapplication. And, when a user navigates into an element with roleapplication,assistive technologies that intercept standard input eventsSHOULD switch to a mode that passes most or all standard input events through to the web application.

For example, a presentation slide editor uses arrow keys to change the positions of textbox and image elements on the slide. There are not anyWAI-ARIA widget roles that correspond to such an interaction model so an author could give the slide container roleapplication, anaria-roledescription of "Slide Editor", and usearia-describedby to provide instructions.

Because only the focusable elements contained in anapplication element are accessible to users of some assistive technologies, authorsMUST use one of the following techniques to ensure all non-decorative static text or image content inside an application is accessible:

Associate the content with a focusable element usingaria-labelledby oraria-describedby.
Place the content in a focusable element that has roledocument orarticle.
Manage focus ofaccessibility descendants as described inManaging Focus, updating the value ofaria-activedescendant to reference theelement containing the focused content.

Characteristics:
Characteristic	Value
Superclass Role:	`structure`
Supported States and Properties:	`aria-activedescendant` `aria-disabled` `aria-errormessage` `aria-expanded` `aria-haspopup` `aria-invalid`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-dropeffect` `aria-flowto` `aria-grabbed` (state) `aria-hidden` (state) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Accessible Name Required:	True

`article`role

A section of a page that consists of a composition that forms an independent part of a document, page, or site.

An article is not a navigationallandmark, 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 isindependent in that its contents could stand alone, for example in syndication. However, theelement 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.

When the user navigates to an element assigned the role ofarticle,assistive technologies that typically intercept standard keyboard eventsSHOULD 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 nestedarticle elements.

When anarticle is in the context of afeed, the authorMAY specify values foraria-posinset andaria-setsize.

Characteristics:
Characteristic	Value
Superclass Role:	`document`
Subclass Roles:	`comment`
Related Concepts:	`<article>` inHTML
Supported States and Properties:	`aria-posinset` `aria-setsize`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`banner`role

Alandmark that contains mostly site-oriented content, rather than page-specific content.

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.

Assistive technologiesSHOULD enable users to quickly navigate to elements with rolebanner.user agentsSHOULD treat elements with rolebanner as navigationallandmarks.user agentsMAY enable users to quickly navigate to elements with rolebanner.

The authorSHOULD mark no more than oneelement on a page with thebannerrole.

Note

Becausedocument andapplication elements can be nested in theDOM, they can have multiplebanner elements as DOM descendants, assuming each of those is associated with different document nodes, either by a DOM nesting (e.g.,document withindocument) or by use of thearia-ownsattribute.

Characteristics:
Characteristic	Value
Superclass Role:	`landmark`
Related Concepts:	`<header>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`blockquote`role

A section of content that is quoted from another source.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Related Concepts:	`<blockquote>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`button`role

An input that allows for user-triggered actions when clicked or pressed. See relatedlink.

Buttons are mostly used for discrete actions. Standardizing the appearance of buttons enhances the user's recognition of thewidgets as buttons and allows for a more compact display in toolbars.

Buttons support the optionalattribute aria-pressed. Buttons with a non-emptyaria-pressed attribute are toggle buttons. Whenaria-pressed istrue the button is in a "pressed"state, whenaria-pressed isfalse it is not pressed. If the attribute is not present, the button is a simple command button.

Characteristics:
Characteristic	Value
Superclass Role:	`command`
Base Concept:	`<button>` inHTML
Related Concepts:	`link`
Supported States and Properties:	`aria-disabled` `aria-haspopup` `aria-expanded` `aria-pressed`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	contents author
Accessible Name Required:	True
Children Presentational:	True

`caption`role

Visible content that names, or describes afigure,grid,group,radiogroup,table ortreegrid.

When usingcaption authorsSHOULD ensure:

Thecaption is a descendant of afigure,grid,group,radiogroup,table, ortreegrid.
Thecaption is the first non-generic descendant of agrid,group,radiogroup,table ortreegrid.
Thecaption is the first or last non-generic descendant of afigure.

If thecaption represents an accessible name for its containing element, authorsSHOULD specifyaria-labelledby on the containing element to reference the element with rolecaption.

Example 9

<divrole="radiogroup"aria-labelledby="cap"><divrole="caption"id="cap">     Choose your favorite fruit</div><!-- ... -->

If acaption contains content that serves as both a name and description for its containing element, authorsMAY instead specifyaria-labelledby to reference an element within thecaption that represents the "name" of the containing element, and specifyaria-describedby to reference an element within thecaption that represents the descriptive content.

Example 10

<divrole="table"aria-labelledby="name"aria-describedby="desc"><divrole="caption"><divid="name">Contest Entrants</div><divid="desc">       This table shows the total number of entrants (500) the       contest accepted over the past four weeks.</div></div><!-- ... -->

If thecaption represents a long-form description, or if the description contains semantic elements which are important in understanding the description, authorsMAY instead specifyaria-labelledby to reference an element within thecaption that represents the "name" of the containing element, and specifyaria-details to reference an element within thecaption that represents the descriptive content.

Example 11

<divrole="figure"aria-labelledby="name"aria-details="details"><!-- figure content here, such as a complex data viz SVG --><divrole="caption"><divid="name">Sales information for 20XX</div><divid="details">       This barchart represents the total amount of sales over the course       of five years.<ahref="...">Sales information for last year</a> can       be reviewed, or you can overlay<buttonaria-pressed="false">previous year</button>       information in this graphic.</div></div><!-- ... -->

If acaption contains only a description, without a suitable text string to serve as the accessible name for its containing element, thenaria-label oraria-labelledbyMAY be used to provide an accessible name, and thecaptionMAY be treated solely as descriptive content, referenced viaaria-details.

Example 12

<divrole="figure"aria-label="Sales information"aria-details="details"><!-- figure content here, such as a complex data viz SVG --><divrole="caption"id="details">     This barchart represents the total amount of sales over the course     of five years.<ahref="...">Sales information for last year</a> can     be reviewed, or you can overlay<buttonaria-pressed="false">previous year</button>     information in this graphic.</div><!-- ... -->

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Related Concepts:	`<caption>` inHTML `<figcaption>` inHTML `<legend>` inHTML
Required Accessibility Parent Roles:	`figure` `grid` `group` `radiogroup` `table` `treegrid`
Inherited States and Properties:	`aria-atomic` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Prohibited States and Properties:	`aria-braillelabel` `aria-label` `aria-labelledby`
Name From:	prohibited

`cell`role

A cell in a tabular container. See relatedgridcell.

AuthorsMUST ensureelements withrole cell are theaccessibility children of an element with therole row.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Subclass Roles:	`columnheader` `gridcell` `rowheader`
Base Concept:	`<td>` inHTML
Required Accessibility Parent Roles:	`row`
Supported States and Properties:	`aria-colindex` `aria-colindextext` `aria-colspan` `aria-rowindex` `aria-rowindextext` `aria-rowspan`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	contents author

`checkbox`role

A checkable input that has three possiblevalues:true,false, ormixed.

Thearia-checkedattribute of acheckbox indicates whether the input is checked (true), unchecked (false), or represents a group ofelements that have a mixture of checked and unchecked values (mixed). Many checkboxes do not use themixed value, and thus are effectively boolean checkboxes.

Note

Due to the strong native semantics ofHTML's native checkbox, authors are advised against usingaria-checked on aninput type=checkbox. Rather, use the nativechecked attribute or theindeterminate IDL attribute to specify the checkbox's "checked" or "mixed" state, respectively.

Characteristics:
Characteristic	Value
Superclass Role:	`input`
Subclass Roles:	`switch`
Related Concepts:	`<input type="checkbox">` inHTML `option`
Required States and Properties:	`aria-checked`
Supported States and Properties:	`aria-errormessage` `aria-expanded` `aria-invalid` `aria-readonly` `aria-required`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	contents author
Accessible Name Required:	True
Children Presentational:	True

`code`role

A section whose content represents a fragment of computer code.

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 contentSHOULD prefer full punctuation verbosity to ensure common symbols (e.g., "-") are spoken.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Related Concepts:	`<code>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Prohibited States and Properties:	`aria-braillelabel` `aria-label` `aria-labelledby`
Name From:	prohibited

`columnheader`role

A cell containing header information for a column.

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

Thecolumnheader establishes a relationship between it and all cells in the corresponding column. It is the structural equivalent to anHTMLthelement with a column scope.

AuthorsMUST ensureelements withrolecolumnheader are theaccessibility children of an element with the rolerow.

Applying thearia-selected state on a columnheaderMUST not cause the user agent to automatically propagate thearia-selected state to all the cells in the corresponding column. An authorMAY choose to propagate selection in this manner depending on the specific application.

While thecolumnheader role can be used in both interactive grids and non-interactive tables, the use ofaria-readonly andaria-required is only applicable to interactive elements. Therefore, authorsSHOULD NOT usearia-required oraria-readonly in acolumnheader that descends from atable, and user agentsSHOULD NOT expose either property toassistive technologies unless thecolumnheader descends from agrid.

Note

Because cells are organized into rows, there is not a single container element for the column. The column is the set ofgridcell elements in a particular position within their respectiverow containers.

Note: Usage of aria-disabled

Whilearia-disabled is currently supported oncolumnheader, in a future version the working group plans to prohibit its use on elements with rolecolumnheader except when the element is in the context of agrid ortreegrid.

Characteristics:
Characteristic	Value
Superclass Role:	`cell` `gridcell` `sectionhead`
Base Concept:	`<th scope="col">` inHTML
Required Accessibility Parent Roles:	`row`
Supported States and Properties:	`aria-sort`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-colindex` `aria-colindextext` `aria-colspan` `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage` `aria-expanded` (state) `aria-flowto` `aria-grabbed` (state) `aria-haspopup` `aria-hidden` (state) `aria-invalid` (state) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-readonly` `aria-relevant` `aria-required` `aria-roledescription` `aria-rowindex` `aria-rowindextext` `aria-rowspan` `aria-selected` (state)
Name From:	contents author
Accessible Name Required:	True

`combobox`role

Aninput that controls another element, such as alistbox orgrid, that can dynamically pop up to help the user set the value of theinput.

Editor's note: Major Changes to combobox role in ARIA 1.2

The Guidance forcombobox has changed significantly inARIA 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 ARIA repository wiki.

Acombobox functionally combines a named input field with the ability to assist value selection via a supplementary popup element. Acombobox inputMAY be either a single-line text field that supports editing and typing or an element that only displays the current value of thecombobox. If thecombobox supports text input and provides autocompletion behavior as described inaria-autocomplete, authorsMUST setaria-autocomplete on thecombobox element to the value that corresponds to the provided behavior.

Typically, the initial state of acombobox is collapsed. In the collapsed state, only thecombobox element and a separate, optional popup controlbutton are visible. Acombobox is said to be expanded when both thecombobox element showing its current value and its associated popup element are visible. AuthorsMUST setaria-expanded totrue on an element with rolecombobox when it is expanded andfalse when it is collapsed.

Elements with the rolecombobox have an implicitaria-haspopup value oflistbox. If thecombobox popup element has a role other thanlistbox, authorsMUST specify anaria-haspopup value oftree,grid, ordialog that corresponds to the role of its popup.

If the user interface includes an additional icon that allows the visibility of the popup to be controlled via pointer and touch events, authorsSHOULD ensure that element has rolebutton, that it isfocusable but not included in the pageTab sequence, and that it is not a descendant of the element with rolecombobox. In addition, to be keyboard accessible, authorsSHOULD provide keyboard mechanisms for moving focus between thecombobox element and elements contained in the popup. For example, one common convention is thatDown Arrow moves focus from the input to the first focusable descendant of the popup element. If the popup element supportsaria-activedescendant, in lieu of moving focus, such keyboard mechanisms can control the value ofaria-activedescendant on thecombobox element. When a descendant of the popup element is active, authorsMAY setaria-activedescendant on thecombobox to a value that refers to the active element within the popup while focus remains on thecombobox element.

User agentsMUST expose the value of elements with rolecombobox toassistive technologies. The value of acombobox is represented by one of the following:

If thecombobox element is a host language element that provides a value, such as anHTMLinput element, the value of the combobox is the value of that element.
Otherwise, the value of thecombobox is represented by its descendant elements and can be determined using the same method used to compute the name of a button from its descendant content.

Example 13

<labelid="tag_label"for="tag_combo">Tag</label><inputtype="text"id="tag_combo"role="combobox"aria-autocomplete="list"aria-haspopup="listbox"aria-expanded="true"aria-controls="popup_listbox"aria-activedescendant="selected_option"><ulrole="listbox"id="popup_listbox"aria-labelledby="tag_label"><lirole="option">Zebra</li><lirole="option"id="selected_option">Zoom</li></ul>

Editor's note: Validity changes combobox for ARIA 1.2

Please review the following carefully. As a result of these changes a combobox following theARIA 1.1 combobox specification will no longer conform with the ARIA specification.

Note

The structural requirements forcombobox defined by this version of the specification are different from the requirements defined by ARIA 1.0 and ARIA 1.1:

The ARIA 1.0 specification required the input element with thecombobox role to be a single-line text field and reference the popup element with aria-owns instead ofaria-controls.
TheARIA 1.1 specification, which was not broadly supported by assistive technologies, required thecombobox to be a non-focusable element with two required accessibility children -- a focusabletextbox and a popup element controlled by thetextbox.
The changes introduced inARIA 1.2 improve interoperability with assistive technologies and enable authors to create presentations of combobox that more closely imitate a native HTMLselect element.

The features and behaviors of combobox implementations vary widely. Consequently, there are many important authoring considerations. See the ARIA Authoring Practices Guide for additional details on implementing combobox design patterns.

Characteristics:
Characteristic	Value
Superclass Role:	`input`
Related Concepts:	`<select>` inHTML
Required States and Properties:	`aria-expanded`
Supported States and Properties:	`aria-activedescendant` `aria-autocomplete` `aria-controls` `aria-errormessage` `aria-haspopup` `aria-invalid` `aria-readonly` `aria-required`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-flowto` `aria-grabbed` (state) `aria-hidden` (state) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Accessible Name Required:	True
Implicit Value for Role:	Default for`aria-haspopup` is`listbox`.

`command`abstract role

A form of widget that performs an action but does not receive input data.

command is anabstract role used for the ontology. AuthorsMUST NOT usecommand role in content.

Characteristics:
Characteristic	Value
Is Abstract:	True
Superclass Role:	`widget`
Subclass Roles:	`button` `link` `menuitem`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`

`comment`role

A comment contains content expressing reaction to other content.

Comments can annotate any visible content, from small spans of text, to other comments, to entire articles. AuthorsSHOULD identify the relationships between comments and the commented content, as follows:

If the comment is a reply to anothercomment:
- If all ancestor comments are available in theDOM, make each replycomment a semantic descendant of thecomment to which it is replying, either by making it a DOM descendant element or by using aria-owns.
- Alternatively, if all ancestor comments are not in theDOM, such as when comments are paginated, the hierarchical levelMAY be indicated via aria-level. Additional group positional informationMAY be indicated viaaria-posinset andaria-setsize.
Otherwise, if the comment relates to other content in the page:
- Providearia-details on the element containing the commented content with a value refering to the element with rolecomment.
- If there are multiple comments related to the same commented content, either provide a value foraria-details on the commented content that refers to each individual comment, or usearia-details to refer to a parent container of the comments. Ifaria-details refers to an element containing comments rather thancomment elements, authorsSHOULD assign a role ofgroup orregion to the referenced container.

If the author has not explicitly declaredaria-level,aria-posinset, oraria-setsize for acomment element, user agentsMUST automatically compute the missing values and expose them to assistive technologies.

Characteristics:
Characteristic	Value
Superclass Role:	`article`
Supported States and Properties:	`aria-level` `aria-posinset` `aria-setsize`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	contents author

`complementary`role

Alandmark 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.

There are various types of content that would appropriately have thisrole. 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.

Assistive technologiesSHOULD enable users to quickly navigate to elements with rolecomplementary.user agentsSHOULD treat elements with rolecomplementary as navigationallandmarks.user agentsMAY enable users to quickly navigate to elements with rolecomplementary.

Characteristics:
Characteristic	Value
Superclass Role:	`landmark`
Related Concepts:	`<aside>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`composite`abstract role

Awidget that can contain navigableaccessibility descendants.

AuthorsSHOULD 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, authorsSHOULD provide a separate navigation mechanism for users to navigate toelements that areaccessibility descendants of the composite element.

composite is anabstract role used for the ontology. AuthorsMUST NOT usecomposite role in content.

Characteristics:
Characteristic	Value
Is Abstract:	True
Superclass Role:	`widget`
Subclass Roles:	`grid` `select` `spinbutton` `tablist`
Supported States and Properties:	`aria-activedescendant` `aria-disabled`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`

`contentinfo`role

Alandmark that contains information about the parent document.

Examples of information included in this region of the page are copyrights and links to privacy statements.

Assistive technologiesSHOULD enable users to quickly navigate to elements with rolecontentinfo.user agentsSHOULD treat elements with rolecontentinfo as navigationallandmarks.user agentsMAY enable users to quickly navigate to elements with rolecontentinfo.

The authorSHOULD mark no more than oneelement on a page with thecontentinfo role.

Note

Becausedocument andapplication elements can be nested in theDOM, they can have multiplecontentinfo elements as DOM descendants, assuming each of those is associated with different document nodes, either by a DOM nesting (e.g.,document withindocument) or by use of thearia-owns attribute.

Characteristics:
Characteristic	Value
Superclass Role:	`landmark`
Related Concepts:	`<footer>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`definition`role

A definition of a term or concept. See relatedterm.

AuthorsMUST identify theelement being defined and assign that element a role ofterm.

AuthorsSHOULD NOT use thedefinition role on interactive elements such as form controls because doing so could prevent users of assistive technologies from interacting with those elements.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Inherited States and Properties:	`aria-atomic` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Prohibited States and Properties:	`aria-braillelabel` `aria-label` `aria-labelledby`
Name From:	prohibited

`deletion`role

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 relatedinsertion.

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.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Related Concepts:	`<del>` inHTML `<s>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Prohibited States and Properties:	`aria-braillelabel` `aria-label` `aria-labelledby`
Name From:	prohibited

`dialog`role

A dialog is a descendant window of the primary window of a web application. ForHTML pages, the primary application window is the entire web document.

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 alertdialog. 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 asinert, authorsSHOULD use thearia-modal attribute, and constrain focus to dialogs. See the WAI-ARIA Authoring Practices: Dialog (modal) pattern for additional details on implementing modal dialog design patterns.

AuthorsSHOULD provide an accessible name for a dialog, which can be done with thearia-label oraria-labelledby attribute.

AuthorsSHOULD ensure that all dialogs (both modal and non-modal) have at least onefocusable descendant element. AuthorsSHOULD focus an element in the modal dialog when it is displayed, and authorsSHOULD constrain keyboard focus to focusable elements within a modal dialog, until dismissed.

AuthorsSHOULD provide a dialog an accessible description, with thearia-describedby attribute, for instances where authors have set initial keyboard focus on an element that follows content that outlines the purpose of the dialog. Assistive technologySHOULD 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.

Note

Authors are strongly encouraged to usearia-describedby, rather thanaria-description, to provide descriptions to dialogs. Whilearia-description 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.

Example 14

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, anaria-describedby attribute is used to expose this content as a description for thedialog.

Example

<divrole="dialog"aria-labelledby="h"aria-describedby="d"aria-modal="true"...><h2id="h">Add Shipping Address</h2><pid="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!</p><label>    Street:<inputautofocus...></label>  ...</div>

Note

In the description of this role, the term "web application" does not refer to theapplication role, which specifies specific assistive technology behaviors.

Characteristics:
Characteristic	Value
Superclass Role:	`window`
Subclass Roles:	`alertdialog`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-modal` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`directory`role

[Deprecated inARIA 1.2] A list of references to members of a group, such as a static table of contents.

Note

As exposed by accessibility APIs, thedirectoryrole is essentially equivalent to thelistrole. So, usingdirectory does not provide any additional benefits to assistive technology users. Authors are advised to treatdirectory as deprecated and to uselist, or a host language's equivalent semantics instead.

Adirectory 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 atree role instead.

Characteristics:
Characteristic	Value
Superclass Role:	`list`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`document`role

Anelement containing content thatassistive technology users might want to browse in a reading mode.

Whenuser agent focus moves to an element assigned the role ofdocument,assistive technologies having a reading mode for browsing static contentMAY switch to that reading mode and intercept standard input events, such as Up or Down arrow keyboard events, to control the reading cursor.

Becauseassistive technologies that have a reading mode default to that mode for all elements except for those with either awidget orapplication role, the only circumstance where thedocument role is useful for changing assistive technology behavior is when the element with roledocument is afocusable child element of awidget orapplication. For example, given anapplication element which contains some static rich text, the author can apply roledocument to the element containing the text and give it atabindex of0. When a screen reader user presses the Tab key and places focus on thedocument element, the user will be able to read the text with the screen reader's reading cursor.

Characteristics:
Characteristic	Value
Superclass Role:	`structure`
Subclass Roles:	`article`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`emphasis`role

One or more emphasized characters. See relatedstrong.

The purpose of theemphasis 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. AuthorsSHOULD use theemphasis role only if its absence would change the meaning of the content.

Theemphasis role is not intended to convey importance; for that purpose, thestrong role is more appropriate.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Related Concepts:	`<em>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Prohibited States and Properties:	`aria-braillelabel` `aria-label` `aria-labelledby`
Name From:	prohibited

`feed`role

A scrollablelist ofarticles where scrolling might causearticles to be added to or removed from either end of the list.

Afeed enables users ofassistive technologies 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 afeed,assistive technologies provide a web application with signals of the user's reading cursor movement by movinguser agent focus, enabling the application to both add new content and visually position content as the user browses the page. Thefeed 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.

For example, afeed could be used to present a stream of news stories where eacharticle 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.

Afeed is a container element whose children have rolearticle. Whenarticles are added or removed from either or both ends of afeed, authorsSHOULD setaria-busy totrue on thefeed element before the changes are made and set it tofalse after the changes are complete. AuthorsSHOULD avoid inserting or removingarticles in the middle of afeed. These requirements helpassistive technologies gracefully respond to changes in thefeed content that occur simultaneously with user commands to move the reading cursor within thefeed.

AuthorsSHOULD make eacharticle in afeedfocusable and ensure that the application scrolls anarticle into view whenuser agent focus is set on thearticle or one of its descendant elements. For example, inHTML, each article element should have atabindex value of either-1 or0.

When anassistive technology reading cursor moves from onearticle to another,assistive technologiesSHOULD set user agent focus on thearticle that contains the reading cursor. If the reading cursor lands on a focusable element inside thearticle, the assistive technologyMAY set focus on that element in lieu of setting focus on the containingarticle.

Because the ability to scroll to anotherarticle with anassistive technology reading cursor depends on the presence of anotherarticle in the page, authorsSHOULD attempt to load additionalarticles beforeuser agent focus reaches anarticle at either end of the set ofarticles that has been loaded. Alternatively, authorsMAY include anarticle at either or both ends of the loaded set ofarticles that includes an element, such as abutton, that lets the user request morearticles to be loaded.

In addition to providing a brief label, authorsMAY applyaria-describedby toarticle elements in afeed to suggest to screen readers which elements to speak after the label when users navigate byarticle. Screen readersMAY provide users with a way to quickly scanfeed content by speaking both the label andaccessible description when navigating byarticle, enabling the user to ignore repetitive or less important elements, such as embedded interaction widgets, that the author has left out of the description.

AuthorsSHOULD provide keyboard commands for moving focus amongarticles in afeed so users who do not utilize an assistive technology that providesarticle navigation features can use the keyboard to navigate thefeed.

If the number of articles available in afeed supply is static, authorsMAY specifyaria-setsize onarticle elements in thatfeed. However, if the total number is extremely large, indefinite, or changes often, authorsMAY setaria-setsize to-1 to communicate the unknown size of the set.

See the ARIA Authoring Practices Guide for additional details on implementing a feed design pattern.

Characteristics:
Characteristic	Value
Superclass Role:	`list`
Allowed Accessibility Child Roles:	`article`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`figure`role

A perceivablesection of content that typically contains agraphical document, images, media player, code snippets, or example text. The parts of afigureMAY be user-navigable.

AuthorsSHOULD provide a reference to thefigure from the main text, but thefigure need not be displayed at the same location as the referencing element. AuthorsMAY provide afigure acaption which can include its name, descriptive text, or both. If acaption is provided, and it serves as a description to the contents of thefigure, authorsSHOULD associate it to thefigure element usingaria-details.

AuthorsMAY provide afigure an accessible name usingaria-label or usearia-labelledby to reference other text in the page to serve as the element's label and accessible name.

Please refer to thecaption role for more information on how to associate afigure with itscaption.

Assistive technologiesSHOULD enable users to quickly navigate to figures.User agentsMAY enable users to quickly navigate to figures.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Related Concepts:	`<figure>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`form`role

Alandmark region that contains a collection of items and objects that, as a whole, combine to create a form. See relatedsearch.

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, authorsSHOULD use thesearch role instead of the genericform role.

AuthorsSHOULD give each element with roleform a brief label that describes the purpose of the form. AuthorsSHOULD reference a visible label witharia-labelledby if a visible label is present. AuthorsSHOULD include the label inside of a heading whenever possible. The headingMAY be an instance of the standard host language heading element or an instance of an element with roleheading.

If an author uses a script to submit a form based on a user action that would otherwise not trigger anonsubmit event (for example, a form submission triggered by the user changing a form element's value), the authorSHOULD provide the user with advance notification of the behavior.

Assistive technologiesSHOULD enable users to quickly navigate to elements with roleform.User agentsSHOULD treat elements with roleform and an accessible name as navigationallandmarks.User agentsMAY enable users to quickly navigate to elements with roleform.

Characteristics:
Characteristic	Value
Superclass Role:	`landmark`
Base Concept:	`<form>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`generic`role

A nameless containerelement that has no semantic meaning on its own.

Thegeneric role is intended for use as the implicit role of generic elements in host languages (such asHTMLdiv orspan), so is primarily for implementors of user agents. AuthorsSHOULD NOT use this role in content. AuthorsMAY use presentation ornone to remove implicit accessibility semantics, or a semantic container role such asgroup to semantically group descendants in a named container.

Like an element with rolepresentation, an element with rolegeneric can provide a limited number of accessible states and properties for its descendants, such asaria-live attributes.

However, unlike elements with rolepresentation, user agents exposegeneric elements inaccessibility APIs when permitted accessibility attributes have been specified. User agentsMAY otherwise ignoregeneric elements if such permitted attributes have not been specified.

Characteristics:
Characteristic	Value
Superclass Role:	`structure`
Related Concepts:	HTML`div`,HTML`span`
Inherited States and Properties:	`aria-atomic` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-live` `aria-owns` `aria-relevant`
Prohibited States and Properties:	`aria-braillelabel` `aria-brailleroledescription` `aria-label` `aria-labelledby` `aria-roledescription`
Name From:	prohibited

`grid`role

A compositewidget containing a collection of one or more rows with one or more cells where some or all cells in the grid arefocusable by using methods of two-dimensional navigation, such as directional arrow keys.

Thegrid role does not imply a specific visual, e.g., tabular, presentation. It describesrelationships amongelements. 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.

The cell elements of agrid have rolegridcell. AuthorsMAY designate a cell as a row or column header by using either therowheader orcolumnheaderrole in lieu of thegridcell role. AuthorsMUST ensure elements with rolegridcell,columnheader, orrowheader areaccessibility children of elements with rolerow, which are in turn areaccessibility children of an element with rolerowgroup, orgrid.

To bekeyboard accessible, authorsSHOULD manage focus of descendants of agrid as described inManaging Focus. When a user is navigating thegrid content with a keyboard, authorsSHOULD set focus as follows:

If agridcell contains a single interactivewidget that will not consume arrow key presses when it receives focus, such as acheckbox,button, orlink, authorsMAY set focus on the interactive element contained in that cell. This allows the contained widget to be directly operable.
Otherwise, authorsSHOULD ensure the element that receives focus is agridcell,rowheader, orcolumnheader element.

AuthorsSHOULD 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:

a widget that requires arrow keys to operate, e.g., acombobox orradiogroup
multiple interactive elements
editable content

For example, if a cell in a spreadsheet contains acombobox or editable text, theEnter 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 containedcombobox ortextbox. Depending on the implementation, pressingEnter again,Tab,Escape, or another key might switch the application back to the grid navigation mode.

AuthorsMAY use agridcell to display the result of a formula, which could be editable by the user. In a spreadsheet application, for example, agridcell might show a value calculated from a formula until the user activates thegridcell for editing when atextbox appears in thegridcell containing the formula in an editable state.

Ifaria-readonly is set on an element with rolegrid,user agentsMUST propagate the value to allgridcell elements that areaccessibility descendants of thatgrid and expose the value in the accessibilityAPI. An authorMAY override the propagated value of aria-readonly for an individualgridcell element.

In agrid that provides cell content editing functions, if the content of a focusablegridcell element is not editable, authorsMAY setaria-readonly totrue on thegridcell element. However, the value ofaria-readonly, whether specified for agrid or individual cells, only indicates whether the content contained in cells is editable. It does not represent availability of functions for navigating or manipulating thegrid itself.

An unspecified value foraria-readonly does not imply that agrid or agridcell contains editable content. For example, if agrid presents a collection of elements that are not editable, such as a collection oflink elements representing dates in a datepicker, it is not necessary for the author to specify a value foraria-readonly.

AuthorsMAY indicate that a focusablegridcell is selectable as the object of an action with thearia-selected attribute. If thegrid allows multiplegridcells to be selected, the authorSHOULD setaria-multiselectable totrue on the element with rolegrid.

SinceWAI-ARIA can augment an element of the host language, agrid can reuse the elements and attributes of a native table, such as an HTMLtable element. For example, if an author applies thegrid role to an HTMLtable element, the author does not need to apply the row andgridcell roles to the descendantHTMLtr andtd elements because the user agent will automatically make the appropriate translations. When the author is reusing a native host language table element and needs agridcell element to span multiple rows or columns, the authorSHOULD apply the appropriate host language attributes instead ofWAI-ARIA aria-rowspan oraria-colspan properties.

AuthorsSHOULD provide an accessible name for agrid, which can be done with thearia-label oraria-labelledby attribute. AuthorsSHOULD reference a visible label witharia-labelledby if a visible label is present for thegrid.

See the ARIA Authoring Practices Guide for additional details on implementing grid design patterns.

Characteristics:
Characteristic	Value
Superclass Role:	`composite` `table`
Subclass Roles:	`treegrid`
Base Concept:	`<table>` inHTML
Allowed Accessibility Child Roles:	`caption` `row` `rowgroup` withaccessibility child `row`
Supported States and Properties:	`aria-multiselectable` `aria-readonly`
Inherited States and Properties:	`aria-activedescendant` `aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-colcount` `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription` `aria-rowcount`
Name From:	author

`gridcell`role

Acell in agrid ortreegrid.

Agridcell can befocusable, editable, and selectable. Agridcell can haverelationships such asaria-controls to address the application of functional relationships.

If an author intends agridcell to have a row header, column header, or both, and if the relevant headers cannot be determined from theDOM structure, authorsSHOULD explicitly indicate which header cells are relevant to thegridcell by applying aria-describedby on thegridcell and referencingelements withrole rowheader orcolumnheader.

In atreegrid, authorsMAY define agridcell as expandable by using thearia-expanded attribute. If thearia-expanded attribute is provided, it applies only to the individual cell. It is not a proxy for the containerrow, which also can be expanded. The main use case for providing this attribute on agridcell is pivot table behavior.

AuthorsMUST ensureelements withrole gridcell areaccessibility children of an element with therole row.

Characteristics:
Characteristic	Value
Superclass Role:	`cell` `widget`
Subclass Roles:	`columnheader` `rowheader`
Base Concept:	`<td>` inHTML
Required Accessibility Parent Roles:	`row`
Supported States and Properties:	`aria-disabled` `aria-errormessage` `aria-expanded` `aria-haspopup` `aria-invalid` `aria-readonly` `aria-required` `aria-selected`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-colindex` `aria-colindextext` `aria-colspan` `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-dropeffect` `aria-flowto` `aria-grabbed` (state) `aria-hidden` (state) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription` `aria-rowindex` `aria-rowindextext` `aria-rowspan`
Name From:	contents author

`group`role

A set of user interfaceobjects that is not intended to be included in a page summary or table of contents byassistive technologies.

Contrast withregion, which is a grouping of user interface objects that will be included in a page summary or table of contents.

AuthorsSHOULD use agroup to form a logical collection of items in awidget, such as children in a tree widget forming a collection of siblings in a hierarchy. However, when agroup is used in the context of alistbox, for example, authorsMUST limit its children tooption elements. Therefore, proper handling ofgroup by authors and assistive technologies is determined by the context in which it is provided.

AuthorsMAY nestgroup elements. If a section is significant enough to warrant inclusion in the web page's table of contents, the authorSHOULD assign it arole ofregion or astandard landmark role.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Subclass Roles:	`row` `select` `toolbar`
Related Concepts:	`<fieldset>` inHTML
Supported States and Properties:	`aria-activedescendant` `aria-disabled`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`heading`role

A heading for a section of the page.

To ensure elements with a role ofheading are organized into a logical outline, authorsMUST use thearia-level attribute to indicate the proper nesting level.

Characteristics:
Characteristic	Value
Superclass Role:	`sectionhead`
Related Concepts:	`<h1>`,`<h2>`,`<h3>`,`<h4>`,`<h5>`, and`<h6>` inHTML
Required States and Properties:	`aria-level`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	contents author
Accessible Name Required:	True

`image`role

A container for a collection ofelements that form an image. See synonymimg.

Animg can contain captions and descriptive text, as well as multiple image files that when viewed together give the impression of a single image. Animg represents a single graphic within a document, whether or not it is formed by a collection of drawingobjects. In order for an element with arole ofimg to beperceivable, authorsMUST provide the element with anaccessible name. This can be done using thearia-label oraria-labelledby attribute.

Note

Note regarding theARIA 1.3image role.

Theimage role was added to ARIA in version 1.3 as a synonym of the ARIA 1.0 img role. Theimage role improves syntactic consistency with the names of other roles, which are complete words or concatenations of complete words.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Related Concepts:	`<img>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Accessible Name Required:	True
Children Presentational:	True

`img`role

A container for a collection ofelements that form an image. See synonymimage.

`input`abstract role

A generic type ofwidget that allows user input.

input is anabstract role used for the ontology. AuthorsMUST NOT useinput role in content.

Characteristics:
Characteristic	Value
Is Abstract:	True
Superclass Role:	`widget`
Subclass Roles:	`checkbox` `combobox` `option` `radio` `slider` `spinbutton` `textbox`
Supported States and Properties:	`aria-disabled`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`

`insertion`role

An insertion contains content that is marked as added or content that is being suggested for addition. See relateddeletion.

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.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Related Concepts:	`<ins>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Prohibited States and Properties:	`aria-braillelabel` `aria-label` `aria-labelledby`
Name From:	prohibited

`landmark`abstract role

A perceivablesection 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.

landmark is an abstract role used for the ontology. AuthorsMUST NOT uselandmark role in content.

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.

Elements with a role that is a subclass of the landmark role are known aslandmark regions or navigational landmark regions.

Assistive technologiesSHOULD enable users to quickly navigate to landmark regions.user agentsMAY enable users to quickly navigate to landmark regions.

Characteristics:
Characteristic	Value
Is Abstract:	True
Superclass Role:	`section`
Subclass Roles:	`banner` `complementary` `contentinfo` `form` `main` `navigation` `region` `search`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`

`link`role

An interactive reference to an internal or external resource that, when activated, causes the user agent to navigate to that resource. See relatedbutton.

If this is a native link in the host language (such as anHTML anchor with anhref value), activating the link causes the user agent to navigate to that resource. If this is a simulated link, the author is responsible for managing navigation.

Note

If pressing the link triggers an action but does not change browser focus or page location, authors are advised to consider using thebutton role instead of thelink role.

Characteristics:
Characteristic	Value
Superclass Role:	`command`
Related Concepts:	`<a>` inHTML `<link>` inHTML
Supported States and Properties:	`aria-disabled` `aria-expanded` `aria-haspopup`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	contents author
Accessible Name Required:	True

`list`role

Asection containinglistitem elements. See relatedlistbox.

Lists contain children whoserole islistitem.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Subclass Roles:	`directory` `feed`
Base Concept:	`<ol>` inHTML `<ul>` inHTML
Allowed Accessibility Child Roles:	`listitem`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`listbox`role

Awidget that allows the user to select one or more items from a list of choices. See relatedcombobox andlist.

Items within the list are static and, unlike standardHTMLselectelements, can contain images. List boxes contain children whoserole isoption or elements whoserole isgroup which in turn contain children whoserole isoption.

To bekeyboard accessible, authorsSHOULD manage focus ofoption descendants for all instances of thisrole, as described inManaging Focus.

Elements with the rolelistbox have an implicitaria-orientation value ofvertical.

Characteristics:
Characteristic	Value
Superclass Role:	`select`
Related Concepts:	`list` `<select>` inHTML
Allowed Accessibility Child Roles:	`group` withaccessibility child `option` `option`
Supported States and Properties:	`aria-errormessage` `aria-invalid` `aria-multiselectable` `aria-readonly` `aria-required`
Inherited States and Properties:	`aria-activedescendant` `aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-orientation` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Accessible Name Required:	True
Implicit Value for Role:	Default for`aria-orientation` is`vertical`.

`listitem`role

A single item in a list or directory.

AuthorsMUST ensureelements whoserole islistitem areaccessibility children of anelement whoserole islist.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Subclass Roles:	`treeitem`
Base Concept:	`<li>` inHTML
Required Accessibility Parent Roles:	`directory` `list`
Supported States and Properties:	`aria-posinset` `aria-setsize`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`log`role

A type oflive region where new information is added in meaningful order and old information can disappear. See relatedmarquee.

Examples include chat logs, messaging history, game log, or an error log. In contrast to other live regions, in thisrole there is arelationship 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.

Elements with the rolelog have an implicitaria-live value ofpolite.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Implicit Value for Role:	Default for`aria-live` is`polite`.

`main`role

Alandmark containing the main content of a document.

This marks the content that is directly related to or expands upon the central topic of the document. Themainrole is a non-obtrusive alternative for "skip to main content" links, where the navigation option to go to the main content (or otherlandmarks) is provided byassistive technologies, or by auser agent or browser extension, through a keyboard shortcut orUI feature such as a side panel or dialog.

Assistive technologiesSHOULD enable users to quickly navigate to elements with rolemain.user agentsSHOULD treat elements with rolemain as navigationallandmarks.user agentsMAY enable users to quickly navigate to elements with rolemain.

The authorSHOULD mark no more than oneelement on a page with themain role.

Note

Becausedocument andapplication elements can be nested in theDOM, they can have multiplemain elements as DOM descendants, assuming each of those is associated with different document nodes, either by a DOM nesting (e.g.,document withindocument) or by use of thearia-owns attribute.

Characteristics:
Characteristic	Value
Superclass Role:	`landmark`
Related Concepts:	`<main>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`mark`role

Content which is marked or highlighted for reference or notation purposes, due to the content's relevance in the enclosing context.

Example uses formark include:

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.
Indicating portions of the content that are relevant to the user's current activity, such as highlighting text matches found by a search feature.

AuthorsSHOULD NOT usemark for purely decorative styling such as syntax highlighting.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Related Concepts:	`<mark>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Prohibited States and Properties:	`aria-braillelabel` `aria-label` `aria-labelledby`
Name From:	prohibited

`marquee`role

A type oflive region where non-essential information changes frequently. See relatedlog.

Common usages ofmarquee include stock tickers and ad banners. The primary difference between amarquee and alog is that logs usually have a meaningful order or sequence of important content changes.

Elements with the rolemarquee have an implicitaria-live value ofoff.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`math`role

Content that represents a mathematical expression.

Content with the rolemath is intended to be marked up in an accessible format such as MathML [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.

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. AuthorsSHOULD ensure that images of math are labeled by text that describes the mathematical expression as it might be spoken.

Note

Browsers that support native implementations ofMathML 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 Nemeth Braille format. This level of integration is not supported with images of mathematical formulas, even if the author provides a plain text approximation.

At the time of this writing, some mainstream browsers do not supportMathML 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.

MathML Example with Embedded TeX Annotation

Example 15

<!--Note: Use a JavaScript polyfill library to ensure     this renders in user agents that do not support MathML. --><!-- The math element has an implicit role="math". --><mathxmlns="http://www.w3.org/1998/Math/MathML"><mrow><mi>x</mi><mo>=</mo><mfrac><mrow><moform="prefix">−</mo><mi>b</mi><mo>±</mo><msqrt><msup><mi>b</mi><mn>2</mn></msup><mo>−</mo><mn>4</mn><mo>&#x2062;<!-- &InvisibleTimes; --></mo><mi>a</mi><mo>&#x2062;<!-- &InvisibleTimes; --></mo><mi>c</mi></msqrt></mrow><mrow><mn>2</mn><mo>&#x2062;<!-- &InvisibleTimes; --></mo><mi>a</mi></mrow></mfrac></mrow><annotationencoding="TeX">    x=\frac{-b\pm\sqrt{b^2-4ac}}{2a}</annotation></math>

PlainHTML or Polyfill DOM Result of the MathML Quadratic Formula

If a rendering engine does not support a native math format such asMathML, authorsMAY 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.

Example 16

<imgrole="math"src="..."alt="x=⟮−b±√⟮b²−4ac⟯⟯÷2a">

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`menu`role

A type ofwidget that offers a list of choices to the user.

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.

Themenurole 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 amenubar or anothermenu popup.

To bekeyboard accessible, authorsSHOULD manage focus of descendants for all instances of thisrole, as described inManaging Focus.

Elements with the rolemenu have an implicitaria-orientation value ofvertical.

Characteristics:
Characteristic	Value
Superclass Role:	`select`
Subclass Roles:	`menubar`
Related Concepts:	`list`
Allowed Accessibility Child Roles:	`group` withaccessibility child `menuitem` `group` withaccessibility child `menuitemradio` `group` withaccessibility child `menuitemcheckbox` `menuitem` `menuitemcheckbox` `menuitemradio` `separator`
Inherited States and Properties:	`aria-activedescendant` `aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-orientation` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Implicit Value for Role:	Default for`aria-orientation` is`vertical`.

`menubar`role

A presentation ofmenu that usually remains visible and is usually presented horizontally.

Themenubarrole 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. AuthorsSHOULD ensure thatmenubar interaction is similar to the typical menu bar interaction in a desktop graphical user interface.

To bekeyboard accessible, authorsSHOULD manage focus of descendants for all instances of thisrole, as described inManaging Focus.

Elements with the rolemenubar have an implicitaria-orientation value ofhorizontal.

Characteristics:
Characteristic	Value
Superclass Role:	`menu`
Related Concepts:	`toolbar`
Allowed Accessibility Child Roles:	`group` withaccessibility child `menuitem` `group` withaccessibility child `menuitemradio` `group` withaccessibility child `menuitemcheckbox` `menuitem` `menuitemcheckbox` `menuitemradio` `separator`
Inherited States and Properties:	`aria-activedescendant` `aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-orientation` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Implicit Value for Role:	Default for`aria-orientation` is`horizontal`.

`menuitem`role

An option in a set of choices contained by amenu ormenubar.

AuthorsMUST ensureelements withrolemenuitem areaccessibility children of an element with rolemenu,menubar, or an element with rolegroup that is anaccessibility child of an element with rolemenu ormenubar.

AuthorsMAY disable a menu item with thearia-disabled attribute. If the menu item has itsaria-haspopup attribute set totrue, it indicates that the menu item can be used to launch a sub-level menu, and authorsSHOULD display a new sub-level menu when the menu item is activated.

In order to identify that they are relatedwidgets, authorsMUST ensure that menu items areaccessibility descendants of an element with rolemenu ormenubar. AuthorsMAY separate menu items into sets by use of aseparator or an element with an equivalent role from the native markup language.

Characteristics:
Characteristic	Value
Superclass Role:	`command`
Subclass Roles:	`menuitemcheckbox` `menuitemradio`
Related Concepts:	`listitem` `option`
Required Accessibility Parent Roles:	`menu` `menubar` `group` withaccessibility parent `menu` `group` withaccessibility parent `menubar`
Supported States and Properties:	`aria-disabled` `aria-expanded` `aria-haspopup` `aria-posinset` `aria-setsize`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	contents author
Accessible Name Required:	True

`menuitemcheckbox`role

Amenuitem with a checkable state whose possiblevalues aretrue,false, ormixed.

AuthorsMUST ensureelements withrolemenuitemcheckbox areaccessibility children of an element with rolemenu,menubar, or an element with rolegroup that is anaccessibility child of an element with rolemenu ormenubar.

Thearia-checkedattribute of amenuitemcheckbox indicates whether the menu item is checked (true), unchecked (false), or represents a sub-level menu of other menu items that have a mixture of checked and unchecked values (mixed).

In order to identify that they are relatedwidgets, authorsMUST ensure that menu item checkboxes are theaccessibility descendants of an element with rolemenu ormenubar. AuthorsMAY separate menu items into sets by use of aseparator or an element with an equivalent role from the native markup language.

Characteristics:
Characteristic	Value
Superclass Role:	`menuitem`
Related Concepts:	`menuitemradio`
Required Accessibility Parent Roles:	`menu` `menubar` `group` withaccessibility parent `menu` `group` withaccessibility parent `menubar`
Required States and Properties:	`aria-checked`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-expanded` (state) `aria-flowto` `aria-grabbed` (state) `aria-haspopup` `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-posinset` `aria-relevant` `aria-roledescription` `aria-setsize`
Name From:	contents author
Accessible Name Required:	True
Children Presentational:	True

`menuitemradio`role

A checkablemenuitem in a set of elements with the same role, only one of which can be checked at a time.

AuthorsMUST ensureelements withrolemenuitemradio areaccessibility children of an element with rolemenu,menubar, or an element with rolegroup that is anaccessibility child of an element with rolemenu ormenubar.

AuthorsSHOULD enforce that only onemenuitemradio in a group can be checked at the same time. When one item in the group is checked, the previously checked item becomes unchecked (itsaria-checkedattribute becomesfalse).

In order to identify that they are relatedwidgets, authorsMUST ensure that menu item radios areaccessibility descendants of an element with rolemenu ormenubar.

If amenu ormenubar contains more than one group ofmenuitemradio elements, or if the menu contains one group and other, unrelated menu items, authorsSHOULD contain each set of relatedmenuitemradio elements in an element using thegroup role. AuthorsMAY also delimit the group from other menu items with an element using theseparator role, or an element with an equivalent role from the native markup language.

Characteristics:
Characteristic	Value
Superclass Role:	`menuitem`
Related Concepts:	`menuitemcheckbox`
Required Accessibility Parent Roles:	`menu` `menubar` `group` withaccessibility parent `menu` `group` withaccessibility parent `menubar`
Required States and Properties:	`aria-checked`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-expanded` (state) `aria-flowto` `aria-grabbed` (state) `aria-haspopup` `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-posinset` `aria-relevant` `aria-roledescription` `aria-setsize`
Name From:	contents author
Accessible Name Required:	True
Children Presentational:	True

`meter`role

Anelement that represents a scalar measurement within a known range, or a fractional value. See relatedprogressbar.

AuthorsMAY setaria-valuemin andaria-valuemax to indicate the minimum and maximum values for themeter. Otherwise, their implicit values follow the same rules as<input type="range"> inHTML:

Ifaria-valuemin is missing or not a number, it defaults to 0 (zero).
Ifaria-valuemax is missing or not anumber, it defaults to 100.

The value ofaria-valuenowMUST NOT fall below or exceed the computed values ofaria-valuemin andaria-valuemax, respectively.

AuthorsSHOULD NOT use themeter role to indicate progress; theprogressbar role exists to address that need.

Note

Presently, there are noWAI-ARIA properties corresponding to thelow,optimum, andhigh attributes supported on the<meter> element inHTML. The addition of these properties will be considered for ARIA version 1.3.

Characteristics:
Characteristic	Value
Superclass Role:	`range`
Related Concepts:	`<meter>` inHTML
Required States and Properties:	`aria-valuenow`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription` `aria-valuemax` `aria-valuemin` `aria-valuetext`
Name From:	author
Accessible Name Required:	True
Children Presentational:	True
Implicit Value for Role:	Default for`aria-valuemin` is`0`. Default for`aria-valuemax` is`100`.

`navigation`role

A landmark containing a collection of navigationalelements (usually links) for navigating the document or related documents.

Assistive technologiesSHOULD enable users to quickly navigate to elements with rolenavigation.user agentsSHOULD treat elements with rolenavigation as navigationallandmarks.user agentsMAY enable users to quickly navigate to elements with rolenavigation.

Characteristics:
Characteristic	Value
Superclass Role:	`landmark`
Related Concepts:	`<nav>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`none`role

Anelement whose implicit native role semantics will not be mapped to theaccessibility API. See synonympresentation.

Note

Note regarding theARIA 1.1 none role.

InARIA 1.1, the working group introduced none as a synonym to thepresentation role, due to author confusion surrounding the intended meaning of the word "presentation" or "presentational." Many individuals erroneously considerrole="presentation" to be synonymous witharia-hidden="true", and we believerole="none" conveys the actual meaning more unambiguously.

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 supportWAI-ARIA.

Example use cases:

An element whose content is completely presentational (like a spacer image, decorative graphic, or clearing element);
An image that is in a container with the imgrole and where the full text alternative is available and is marked up witharia-labelledby and (if needed)aria-describedby;
An element used as an additional markup "hook" forCSS; or
A layout table and/or any of its associated rows, cells, etc.

For any element with a role of none/presentation and which is notfocusable, the user agentMUST NOT expose the implicit native semantics of the element (the role and its states and properties) to accessibilityAPIs. However, the user agentMUST expose content and descendant elements that do not have an explicit or inherited role of none/presentation. Thus, thenone/presentation role causes a given element to be treated as having no role or to be removed from theaccessibility tree, but does not cause the content contained within the element to be removed from the accessibility tree.

For example, the following two markup snippets will be exposed similarly to an accessibilityAPI.

Example 17

<!-- 1. role="none" negates the implicit 'heading' role semantics but does not affect the contents, including the nested hyperlink. --><h1role="none"> Sample Content<ahref="...">let's go!</a></h1><!-- 2. A span has an implicit 'generic' role and no other attributes important to accessibility, so only its content is exposed, including the hyperlink. --><span> Sample Content<ahref="...">let's go!</a></span>

InHTML, the<img>element is treated as a single entity regardless of the type of image file. Consequently, usingrole="none" orrole="presentation" on anHTMLimg is equivalent to usingaria-hidden="true". In order to make the image contents accessible, authors can embed the object using an<object> or<iframe>element, or use inlineSVG code, and follow the accessibility guidelines for the image content.

AuthorsSHOULD NOT provide a non-empty text alternative when thenone/presentation role is applied to an image.

In the following code sample, the containing img and is appropriately labeled by the caption paragraph. In this example theimg element can be marked asnone/presentation because the role and the text alternatives are provided by the containing element.

Example 18

<divrole="img"aria-labelledby="caption"><imgsrc="example.png"role="none"alt=""><pid="caption">A visible text caption labeling the image.</p></div>

In the following code sample, because the anchor (HTMLa element) is acting as the treeitem, the list item (HTMLli element) is assigned an explicit WAI-ARIA role of none/presentation to override the user agent's implicit native semantics for list items.

Example 19

<ulrole="tree"><lirole="none"><arole="treeitem"aria-expanded="true">An expanded tree node</a></li>  …</ul>

Presentational Role Inheritance

Thenone/presentation role is used on an element that has implicit native semantics, meaning that there is a default accessibilityAPI role for the element. Some elements are only complete when additional descendant elements are provided. For example, in HTML, table elements (matching the table role) requiretr descendants (which have an implicitrowrole), which in turn requireth ortd children (thecolumnheader orrowheader andcell roles, respectively). Similarly, lists require list item children. The descendant elements that complete the semantics of an element are described inWAI-ARIA as Allowed Accessibility Child Roles.

When an explicit or inherited role ofnone/presentation is applied to an element with the implicit semantic of aWAI-ARIA role that has Allowed Accessibility Child Roles, in addition to the element with the explicit role ofnone/presentation, the user agentMUST apply an inherited role ofnone to anyaccessibility descendants that do not have an explicit role defined. Also, when an explicit or inherited role ofnone/presentation 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 ofnone/presentation, the user agentMUST apply an inherited role ofnone to any specifically allowed children that do not have an explicit role defined.

For any element with an explicit or inherited role ofnone/presentation and which is not focusable, user agentsMUST ignore role-specificWAI-ARIA states and properties for that element. For example, in HTML, aul orol element with a role of none/presentation will have the implicit native semantics of itsli elements removed because thelist role to which theul orol corresponds has anAllowed Accessibility Child Role oflistitem. Likewise, the implicit native semantics of anHTMLtable element'sthead/tbody/tfoot/tr/th/td descendants will also be removed, because the HTML specification indicates that these are required structural descendants of thetable element.

Note

Only the implicit native semantics of elements that correspond to WAI-ARIA Allowed Accessibility Child Roles are removed. All other content remains intact, including nested tables or lists, unless those elements also have an explicit role ofnone/presentation specified.

For example, according to an accessibilityAPI, the following markup elements might have identical or very similar role semantics (generic or none role) and identical content.

Example 20

<!-- 1. [role="none"] negates the implicit 'list' and 'listitem' role semantics but does not affect the contents. --><ulrole="none"><li> Sample Content</li><li> More Sample Content</li></ul><!-- 2. There is no implicit role for "foo", so only the contents are exposed. --><foo><foo> Sample Content</foo><foo> More Sample Content</foo></foo>

Note

There are otherWAI-ARIA 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.

For any element with an explicit or inherited role of none/presentation, user agentsMUST apply an inherited role ofnone to all host-language-specific labeling elements for the presentational element. For example, atable element with a role ofnone/presentation will have the implicit native semantics of itscaption element removed, because the caption is merely a label for the presentational table.

Editor's note

Information aboutresolving conflicts in the none/presentation role has been moved toHandling Author Errors

Characteristics:
Characteristic	Value
Superclass Role:	`structure`
Inherited States and Properties:	`aria-atomic` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Prohibited States and Properties:	`aria-braillelabel` `aria-label` `aria-labelledby`
Name From:	prohibited

`note`role

Asection whose content represents additional information or parenthetical context to the primary content it supplements.

Anote 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 reviewcomment andsuggestion.

When used within the normal flow of a page's content, anote has an implicit association with the content that it supplements. The following example demonstrates using anote to call out additional information in the natural reading order of a page:

Example 21

<p>... the following results outline support for the tested features.</p><divrole="note"><p>Please keep in mind that at the time of publishing this page all results were accurate.</p><p>If you find any variations in results, please let us know!</p></div><p>...</p>

In cases where an element with rolenote 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:

If thenote contains structured or interactive content (for example, a link, button, list, table, etc.) usearia-details.
If thenote is brief and consists of static text, usearia-describedby.

Example 22

<!-- using aria-details to reference a note containing a link --> ...<buttonaria-details="info-note">Get Started</button>...<divrole="note"id="info-note"><p>Need more information before you get started?</p><p>Visit our<ahref="...">product description page</a> to get all the information you need.</p></div>

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`option`role

An item in alistbox.

AuthorsMUST ensureelements withroleoption areaccessibility children of an element withrole listbox or of an element withrole group that is theaccessibility child of an element withrolelistbox. Options not associated with alistbox might not be correctly mapped to anaccessibility API.

In certain conditions, a user agentMAY provide an implicit value foraria-selected for eachoption in alistbox, and if it does, the user agentMUST ensure the following conditions are met before providing an implicit value:

The value ofaria-multiselectable on thelistbox isfalse orundefined.
None of theoption elements in thelistbox have an explicitly declared value foraria-selected oraria-checked.

If a user agent provides an implicitaria-selected value for anoption, the valueSHOULD betrue if theoption hasDOM focus or the listbox hasDOM focus and the option is referenced byaria-activedescendant. Otherwise, if a user agent provides an implicitaria-selected value for anoption, the valueSHOULD befalse.

AuthorsSHOULD indicate selection foroption elements using one of the following:

Anaria-selected value oftrue on the selected option within a single-selectlistbox, and optionallyaria-selected values offalse on unselected options.
Eitheraria-selected oraria-checked on all options within a multi-selectlistbox, with a value oftrue on selected options, and a value offalse on unselected options.

AuthorsSHOULD NOT specify botharia-selected andaria-checked onoption elements contained by the samelistbox except in the extremely rare circumstances where all the following conditions are met:

The meaning and purpose ofaria-selected is different from the meaning and purpose ofaria-checked in the user interface.
The user interface makes the meaning and purpose of each state apparent.
The user interface provides a separate method for controlling each state.

Characteristics:
Characteristic	Value
Superclass Role:	`input`
Subclass Roles:	`treeitem`
Base Concept:	`<option>` inHTML
Related Concepts:	`listitem`
Required Accessibility Parent Roles:	`listbox` `group` with parent`listbox`
Supported States and Properties:	`aria-checked` `aria-posinset` `aria-selected` `aria-setsize`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	contents author
Accessible Name Required:	True
Children Presentational:	True

`paragraph`role

A paragraph of content.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Related Concepts:	`<p>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Prohibited States and Properties:	`aria-braillelabel` `aria-label` `aria-labelledby`
Name From:	prohibited

`presentation`role

Anelement whose implicit native role semantics will not be mapped to theaccessibility API. See synonymnone.

Note

Note regarding theARIA 1.1 none role.

InARIA 1.1, the working group introduced none as the preferred synonym to thepresentation role, due to author confusion surrounding the intended meaning of the word "presentation" or "presentational." Many individuals erroneously considerrole="presentation" to be synonymous witharia-hidden="true", and theARIA Working Group believesrole="none" conveys the actual meaning more unambiguously.

`progressbar`role

An element that displays the progress status for tasks that take a long time.

A progressbar indicates that the user's request has been received and the application is making progress toward completing the requested action.

AuthorsMAY setaria-valuemin andaria-valuemax to indicate the minimum and maximum progress indicator values. Otherwise, their implicit values follow the same rules as<input type="range"> inHTML:

Ifaria-valuemin is missing or not a number, it defaults to 0 (zero).
Ifaria-valuemax is missing or not anumber, it defaults to 100.

The authorSHOULD supply avalue foraria-valuenow unless the value is indeterminate, in which case the authorSHOULD omit thearia-valuenow attribute. AuthorsSHOULD update this value when the visual progress indicator is updated. If theprogressbar is describing the loading progress of a particular region of a page, authorsSHOULD both usearia-describedby to reference the progressbar status, and set thearia-busy attribute totrue on the region until it is finished loading. It is not possible for the user to alter the value of aprogressbar because it is always read-only.

Note

Assistive technologies generally will render the value ofaria-valuenow as a percent of a range between the value ofaria-valuemin andaria-valuemax, unlessaria-valuetext is specified.

Characteristics:
Characteristic	Value
Superclass Role:	`range` `widget`
Related Concepts:	`status`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription` `aria-valuemax` `aria-valuemin` `aria-valuenow` `aria-valuetext`
Name From:	author
Accessible Name Required:	True
Children Presentational:	True
Implicit Value for Role:	Default for`aria-valuemin` is`0`. Default for`aria-valuemax` is`100`.

`radio`role

A checkable input in a group of elements with the same role, only one of which can be checked at a time.

AuthorsSHOULD ensure thatelements with roleradio 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 roleradiogroup. If it is not possible to make the radio buttonsDOM children of the radiogroup, authorsSHOULD use thearia-ownsattribute on theradiogroup element to indicate therelationship to its children.

Characteristics:
Characteristic	Value
Superclass Role:	`input`
Related Concepts:	`<input type="radio">` inHTML
Required States and Properties:	`aria-checked`
Supported States and Properties:	`aria-posinset` `aria-setsize`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	contents author
Accessible Name Required:	True
Children Presentational:	True

`radiogroup`role

A group ofradio buttons.

Aradiogroup is a type ofselect list that can only have a single entry checked at any one time. AuthorsSHOULD 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 (itsaria-checkedattribute becomesfalse).

AuthorsSHOULD provide an accessible name for aradiogroup, which can be done with thearia-label oraria-labelledby attribute. AuthorsSHOULD reference a visible label witharia-labelledby if a visible label is present for theradiogroup.

Characteristics:
Characteristic	Value
Superclass Role:	`select`
Related Concepts:	`list`
Supported States and Properties:	`aria-errormessage` `aria-invalid` `aria-readonly` `aria-required`
Inherited States and Properties:	`aria-activedescendant` `aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-orientation` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`range`abstract role

An element representing a range of values.

range is anabstract role used for the ontology. AuthorsMUST NOT userange role in content.

Characteristics:
Characteristic	Value
Is Abstract:	True
Superclass Role:	`structure`
Subclass Roles:	`meter` `progressbar` `scrollbar` `slider` `spinbutton`
Supported States and Properties:	`aria-valuemax` `aria-valuemin` `aria-valuenow` `aria-valuetext`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`

`region`role

Alandmark 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.

AuthorsSHOULD limit use of the region role to sections containing content with a purpose that is not accurately described by one of the otherlandmark roles, such asmain,complementary, ornavigation.

AuthorsMUST give each element with role region a brief label that describes the purpose of the content in the region. AuthorsSHOULD reference a visible label witharia-labelledby if a visible label is present. AuthorsSHOULD include the label inside of a heading whenever possible. The headingMAY be an instance of the standard host language heading element or an instance of an element with roleheading.

Assistive technologiesSHOULD enable users to quickly navigate to elements with roleregion.User agentsSHOULD treat elements with roleregion and an accessible name as navigationallandmarks.User agentsMAY enable users to quickly navigate to elements with roleregion.

Characteristics:
Characteristic	Value
Superclass Role:	`landmark`
Related Concepts:	`<section>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Accessible Name Required:	True

`roletype`abstract role

The baserole from which all other roles inherit.

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

roletype is anabstract role used for the ontology. AuthorsMUST NOT useroletype role in content.

Characteristics:
Characteristic	Value
Is Abstract:	True
Subclass Roles:	`structure` `widget` `window`
Supported States and Properties:	`aria-atomic` `aria-braillelabel` (Except where prohibited) `aria-brailleroledescription` (Except where prohibited) `aria-busy (state)` `aria-controls` `aria-current (state)` `aria-describedby` `aria-description` `aria-details` `aria-disabled (state)` (Global use deprecated in ARIA 1.2) `aria-dropeffect` `aria-errormessage` (Global use deprecated in ARIA 1.2) `aria-flowto` `aria-grabbed (state)` `aria-haspopup` (Global use deprecated in ARIA 1.2) `aria-hidden (state)` `aria-invalid (state)` (Global use deprecated in ARIA 1.2) `aria-keyshortcuts` `aria-label` (Except where prohibited) `aria-labelledby` (Except where prohibited) `aria-live` `aria-owns` `aria-relevant` `aria-roledescription` (Except where prohibited)

`row`role

A row of cells in a tabular container.

Rows containcell orgridcellelements, and thus serve to organize atable,grid, ortreegrid.

While the row role can be used in atable,grid, ortreegrid, the semantics ofaria-expanded,aria-posinset,aria-setsize, andaria-level are only applicable to the hierarchical structure of an interactive tree grid. Therefore, authorsMUST NOT applyaria-expanded,aria-posinset,aria-setsize, andaria-level to arow that descends from atable orgrid, and user agentsSHOULD NOT expose any of these four properties to assistive technologies unless therow descends from atreegrid.

AuthorsMUST ensureelements withrolerow areaccessibility children of an element with the roletable,grid,rowgroup, ortreegrid.

Note: Usage of aria-disabled

Whilearia-disabled is currently supported onrow, in a future version the working group plans to prohibit its on elements with rolerow except when the element is in the context of agrid ortreegrid.

Characteristics:
Characteristic	Value
Superclass Role:	`group` `widget`
Base Concept:	`<tr>` inHTML
Required Accessibility Parent Roles:	`grid` `table` `treegrid` `rowgroup`
Allowed Accessibility Child Roles:	`cell` `columnheader` `gridcell` `rowheader`
Supported States and Properties:	`aria-colindex` `aria-expanded` `aria-level` `aria-posinset` `aria-rowindex` `aria-rowindextext` `aria-setsize` `aria-selected`
Inherited States and Properties:	`aria-activedescendant` `aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	contents author

`rowgroup`role

A structure containing one or more row elements in a tabular container.

Therowgroup role establishes arelationship with itsaccessibility children of rolerow. It is a structural equivalent to thethead,tfoot, andtbody elements in anHTMLtableelement.

AuthorsMUST ensureelements withrolerowgroup areaccessibility children of an element with the rolegrid,table, ortreegrid.

Note

Therowgroup role exists, in part, to support role symmetry inHTML, and allows for the propagation of presentation inheritance on HTMLtable elements with an explicitpresentation role applied.

Note

This role does not differentiate between types of row groups (e.g.,thead vs.tbody), but an issue has been raised for WAI-ARIA 2.0.

Characteristics:
Characteristic	Value
Superclass Role:	`structure`
Base Concept:	`<tbody>`,`<tfoot>` and`<thead>`inHTML
Required Accessibility Parent Roles:	`grid` `table` `treegrid`
Allowed Accessibility Child Roles:	`row`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`rowheader`role

A cell containing header information for a row.

The rowheader role can be used to identify a cell as a header for a row in atable,grid, ortreegrid. The rowheader establishes arelationship between it and all cells in the corresponding row. It is a structural equivalent to settingscope="row" on anHTMLthelement.

AuthorsMUST ensureelements withrolerowheader areaccessibility children of an element with the rolerow.

Applying thearia-selected state on a rowheaderMUST NOT cause the user agent to automatically propagate thearia-selected state to all the cells in the corresponding row. An authorMAY choose to propagate selection in this manner depending on the specific application.

While therowheader role can be used in both interactive grids and non-interactive tables, the use ofaria-expanded,aria-readonly, andaria-required is only applicable to interactive elements. Therefore, authorsSHOULD NOT usearia-expanded,aria-readonly, oraria-required in arowheader that descends from atable, and user agentsSHOULD NOT expose these properties toassistive technologies unless therowheader descends from agrid ortreegrid.

Note: Usage of aria-disabled

Whilearia-disabled is currently supported onrowheader, in a future version the working group plans to prohibit its use on elements with rolerowheader except when the element is in the context of agrid ortreegrid.

Characteristics:
Characteristic	Value
Superclass Role:	`cell` `gridcell` `sectionhead`
Base Concept:	`<th scope="row">` inHTML
Required Accessibility Parent Roles:	`row`
Supported States and Properties:	`aria-expanded` `aria-sort`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-colindex` `aria-colindextext` `aria-colspan` `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage` `aria-flowto` `aria-grabbed` (state) `aria-haspopup` `aria-hidden` (state) `aria-invalid` (state) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-readonly` `aria-relevant` `aria-required` `aria-roledescription` `aria-rowindex` `aria-rowindextext` `aria-rowspan` `aria-selected` (state)
Name From:	contents author
Accessible Name Required:	True

`scrollbar`role

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.

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.

AuthorsMAY set thearia-controls attribute on the scrollbar element to reference the scrollable area it controls.

AuthorsMAY setaria-valuemin andaria-valuemax to indicate the minimum and maximum thumb position. Otherwise, their implicit values follow the same rules as<input type="range"> inHTML:

Ifaria-valuemin is missing or not a number, it defaults to 0 (zero).
Ifaria-valuemax is missing or not anumber, it defaults to 100.

AuthorsMUST set thearia-valuenow attribute to indicate the current thumb position. If aria-valuenow is missing or has an unexpected value,user agentsMAY implement the repair techniques specified in thesection describing handling author errors in states and properties, which are equivalent to the repair techniques for<input type="range"> inHTML.

Elements with the rolescrollbar have an implicit aria-orientation value ofvertical.

Note

Assistive technologies generally will render the value ofaria-valuenow as a percent of a range between the value ofaria-valuemin andaria-valuemax, unlessaria-valuetext is specified. It is best to set the values foraria-valuemin,aria-valuemax, andaria-valuenow in a manner that is appropriate for this calculation.

Characteristics:
Characteristic	Value
Superclass Role:	`range` `widget`
Required States and Properties:	`aria-valuenow`
Supported States and Properties:	`aria-disabled` `aria-orientation` `aria-valuemax` `aria-valuemin`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription` `aria-valuetext`
Name From:	author
Children Presentational:	True
Implicit Value for Role:	Default for`aria-orientation` is`vertical`. Default for`aria-valuemin` is`0`. Default for`aria-valuemax` is`100`.

`search`role

Alandmark region that contains a collection of items and objects that, as a whole, combine to create a search facility. See relatedform andsearchbox.

A search region can be a mix of host language form controls, scripted controls, and hyperlinks.

Assistive technologiesSHOULD enable users to quickly navigate to elements with rolesearch.user agentsSHOULD treat elements with rolesearch as navigationallandmarks.user agentsMAY enable users to quickly navigate to elements with rolesearch.

Characteristics:
Characteristic	Value
Superclass Role:	`landmark`
Base Concept:	HTML`search`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`searchbox`role

A type of textbox intended for specifying search criteria. See relatedtextbox andsearch.

Characteristics:
Characteristic	Value
Superclass Role:	`textbox`
Base Concept:	`<input type="search">` inHTML
Inherited States and Properties:	`aria-activedescendant` `aria-atomic` `aria-autocomplete` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage` `aria-flowto` `aria-grabbed` (state) `aria-haspopup` `aria-hidden` (state) `aria-invalid` (state) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-multiline` `aria-owns` `aria-placeholder` `aria-readonly` `aria-relevant` `aria-required` `aria-roledescription`
Name From:	author
Accessible Name Required:	True

`section`abstract role

A renderable structural containment unit on a page.

section is anabstract role used for the ontology. AuthorsMUST NOT usesection role in content.

Characteristics:
Characteristic	Value
Is Abstract:	True
Superclass Role:	`structure`
Subclass Roles:	`alert` `blockquote` `caption` `cell` `code` `definition` `deletion` `emphasis` `figure` `group` `image` `insertion` `landmark` `list` `listitem` `log` `mark` `marquee` `math` `note` `paragraph` `sectionfooter` `sectionheader` `status` `strong` `subscript` `suggestion` `superscript` `table` `tabpanel` `term` `time` `tooltip`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`

`sectionfooter`role

A set of user interface objects and information representing information about its closest ancestral content group. For instance, asectionfooter can include information about who wrote the specific section of content, such as anarticle. It can contain links to related documents, copyright information or other indices and colophon specific to the current section of the page.

Asectionfooter does not represent information about the parent document, or globally repeating content found across multiple pages related to the website. For such content, thecontentinfo role would be more appropriate.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Base Concept:	`<footer>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`sectionhead`abstract role

A structure that labels or summarizes the topic of its related section.

sectionhead is anabstract role used for the ontology. AuthorsMUST NOT usesectionhead role in content.

Characteristics:
Characteristic	Value
Is Abstract:	True
Superclass Role:	`structure`
Subclass Roles:	`columnheader` `heading` `rowheader` `tab`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`

`sectionheader`role

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, asectionheader can include the heading, introductory statement and related meta data for a section of content, for instance aregion orarticle, within a web page.

Asectionheader does not represent site-oriented or globally repeating content found across multiple pages of a website. For such content, thebanner role would be more appropriate.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Base Concept:	`<header>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`select`abstract role

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

select is anabstract role used for the ontology. AuthorsMUST NOT useselect role in content.

Characteristics:
Characteristic	Value
Is Abstract:	True
Superclass Role:	`composite` `group`
Subclass Roles:	`listbox` `menu` `radiogroup` `tree`
Supported States and Properties:	`aria-orientation`
Inherited States and Properties:	`aria-activedescendant` `aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`

`separator`role

A divider that separates and distinguishes sections of content or groups of menuitems.

There are two types of separators: a staticstructure that provides only a visible boundary and afocusable, interactivewidget that is also moveable. If aseparator is not focusable, it is revealed toassistive technologies as a static structural element. For example, a staticseparator 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.

AuthorsMAY make aseparator focusable to create awidget 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 theseparator. A variableseparator widget can be moved continuously within a range, whereas a fixedseparator widget supports only two discrete positions. Typically, a fixedseparator widget is used to toggle one of the sections between expanded and collapsed states.

If theseparator is focusable, authorsMUST set the value ofaria-valuenow to anumber reflecting the current position of theseparator and update that value when it changes. AuthorsSHOULD also provide the value ofaria-valuemin if it is not0 and the value ofaria-valuemax if it is not100. If missing or not a number, the implicit values of these attributes are as follows:

The implicit value ofaria-valuemin is0.
The implicit value ofaria-valuemax is100.

In applications where there is more than one focusableseparator, authorsSHOULD provide an accessible name for each one.

Elements with the roleseparator have an implicitaria-orientation value ofhorizontal.

Characteristics:
Characteristic	Value
Superclass Role:	`structure` (if not focusable) `widget` (if focusable)
Related Concepts:	`<hr>` inHTML
Required States and Properties:	`aria-valuenow` (if focusable)
Supported States and Properties:	`aria-disabled` (if focusable) `aria-orientation` `aria-valuemax` (if focusable) `aria-valuemin` (if focusable) `aria-valuetext` (if focusable)
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Children Presentational:	True
Implicit Value for Role:	Default for`aria-orientation` is`horizontal`. Default for`aria-valuemin` is`0`. Default for`aria-valuemax` is`100`.

`slider`role

An input where the user selects a value from within a given range.

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.

AuthorsMAY set thearia-valuemin andaria-valuemax attributes. Otherwise, their implicit values follow the same rules as<input type="range"> inHTML:

Ifaria-valuemin is missing or not a number, it defaults to 0 (zero).
Ifaria-valuemax is missing or not anumber, it defaults to 100.

AuthorsMUST set thearia-valuenow attribute. If aria-valuenow is missing or has an unexpected value, browsersMAY implement the repair techniques specified in thesection describing handling author errors in states and properties, which are equivalent to the repair techniques for<input type="range"> inHTML.

Elements with the roleslider have an implicit aria-orientation value ofhorizontal.

Characteristics:
Characteristic	Value
Superclass Role:	`input` `range`
Required States and Properties:	`aria-valuenow`
Supported States and Properties:	`aria-errormessage` `aria-haspopup` `aria-invalid` `aria-orientation` `aria-readonly` `aria-valuemax` `aria-valuemin`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-flowto` `aria-grabbed` (state) `aria-hidden` (state) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription` `aria-valuetext`
Name From:	author
Accessible Name Required:	True
Children Presentational:	True
Implicit Value for Role:	Default for`aria-orientation` is`horizontal`. Default for`aria-valuemin` is`0`. Default for`aria-valuemax` is`100`.

`spinbutton`role

A form ofrange that expects the user to select from among discrete choices.

Aspinbutton 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.

Although aspinbutton is similar in appearance to many presentations ofselect, it is advisable to usespinbutton when working with known ranges (especially in the case of large ranges) as opposed to distinct options. For example, aspinbutton representing a range from 1 to 1,000,000 would provide much better performance than aselectwidget representing the same values.

AuthorsMAY create aspinbutton withaccessibility children, butMUST limit those elements to atextbox and/or twobuttons. Alternatively, authorsMAY apply thespinbutton role to a text input and create sibling buttons to support the increment and decrement functions.

To bekeyboard accessible, authorsSHOULD manage focus of descendants for all instances of thisrole, as described inManaging Focus. When aspinbutton receives focus, authorsSHOULD ensure focus is placed on thetextbox element if one is present, and on thespinbutton itself otherwise. AuthorsSHOULD also ensure theup anddown arrows on a keyboard perform the increment and decrement functions and that the increment and decrementbutton elements areNOT included in the primary navigation ring, e.g., the Tab ring inHTML.

AuthorsSHOULD set the aria-valuenow attribute when thespinbutton has a value. AuthorsSHOULD set thearia-valuemin attribute when there is a minimum value, and thearia-valuemax attribute when there is a maximum value.

Characteristics:
Characteristic	Value
Superclass Role:	`composite` `input` `range`
Supported States and Properties:	`aria-errormessage` `aria-invalid` `aria-readonly` `aria-required` `aria-valuemax` `aria-valuemin` `aria-valuenow` `aria-valuetext`
Inherited States and Properties:	`aria-activedescendant` `aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Accessible Name Required:	True
Implicit Value for Role:	Default for`aria-valuemin` is that there is no minimum value. Default for`aria-valuemax` is that there is no maximum value. Default for`aria-valuenow` is that there is no current value.

`status`role

A type oflive region whose content is advisory information for the user but is not important enough to justify analert, often but not necessarily presented as a status bar.

AuthorsSHOULD ensure an element with rolestatus does not receive focus as a result of change in status.

Status is a form oflive region. If another part of the page controls what appears in the status, authorsSHOULD make therelationship explicit with thearia-controlsattribute.

Assistive technologiesMAY reserve some cells of a Braille display to render the status.

Elements with the rolestatus have an implicitaria-live value ofpolite and an implicitaria-atomic value oftrue.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Subclass Roles:	`timer`
Related Concepts:	`<output>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Implicit Value for Role:	Default for`aria-live` is`polite`. Default for`aria-atomic` is`true`.

`strong`role

Content that is important, serious, or urgent. See relatedemphasis.

The purpose of thestrong 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. AuthorsSHOULD use thestrong role only if its absence would change the meaning of the content.

Thestrong role is not intended to convey stress or emphasis; for that purpose, theemphasis role is more appropriate.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Related Concepts:	`<strong>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Prohibited States and Properties:	`aria-braillelabel` `aria-label` `aria-labelledby`
Name From:	prohibited

`structure`abstract role

A document structuralelement.

Roles for document structure support the accessibility of dynamic web content by helpingassistive technologies determine active content versus static document content. Structural roles by themselves do not all map toaccessibility APIs, but are used to createwidget roles or assist content adaptation for assistive technologies.

structure is anabstract role used for the ontology. AuthorsMUST NOT usestructure role in content.

Characteristics:
Characteristic	Value
Is Abstract:	True
Superclass Role:	`roletype`
Subclass Roles:	`application` `document` `generic` `none` `range` `rowgroup` `section` `sectionhead` `separator`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`

`subscript`role

One or more subscripted characters. See relatedsuperscript.

Thesubscript 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, authorsSHOULD use this role only if the absence of the subscript would change the meaning of the content.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Related Concepts:	`<sub>` and`<sup>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Prohibited States and Properties:	`aria-braillelabel` `aria-label` `aria-labelledby`
Name From:	prohibited

`suggestion`role

A single proposed change to content.

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.

AuthorsMUST ensure that asuggestion contains either oneinsertion child or onedeletion child or ensure that it contains two children where one is aninsertion and the other is adeletion. AuthorsMUST ensure asuggestion does not contain any other children.

AuthorsMAY usearia-details oraria-description to associate thesuggestion with related information such as comments, authoring info, and time stamps.

Example 23

<p>  The best pet is a<spanrole="suggestion"><spanrole="deletion">cat</span><spanrole="insertion">dog</span></span></p>

When a suggestion is accepted, authorsSHOULD remove thesuggestion role, indicating that the proposed revision has been made. After thesuggestion role is removed, childinsertion anddeletion elements can either be retained to document the revision or replaced with the revised content.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Allowed Accessibility Child Roles:	`insertion` `deletion`
Inherited States and Properties:	`aria-atomic` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Prohibited States and Properties:	`aria-braillelabel` `aria-label` `aria-labelledby`
Name From:	prohibited

`superscript`role

One or more superscripted characters. See relatedsubscript.

Thesuperscript 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, authorsSHOULD use this role only if the absence of the superscript would change the meaning of the content.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Related Concepts:	`<sub>` and`<sup>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Prohibited States and Properties:	`aria-braillelabel` `aria-label` `aria-labelledby`
Name From:	prohibited

`switch`role

A type of checkbox that represents on/off values, as opposed to checked/unchecked values. See relatedcheckbox.

Thearia-checkedattribute of aswitch indicates whether the input is on (true) or off (false). Themixed value is invalid, and user agentsMUST treat amixed value as equivalent tofalse for this role.

Note

Aswitch provides approximately the same functionality as acheckbox and togglebutton, but makes it possible for assistive technologies to present the widget in a fashion consistent with its on-screen appearance.

Characteristics:
Characteristic	Value
Superclass Role:	`checkbox`
Related Concepts:	`button`
Required States and Properties:	`aria-checked`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage` `aria-expanded` (state) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-readonly` `aria-relevant` `aria-required` `aria-roledescription`
Name From:	contents author
Accessible Name Required:	True
Children Presentational:	True

`tab`role

A grouping label providing a mechanism for selecting the tab content that is to be rendered to the user.

If atabpanel or item in atabpanel has focus, the associatedtab is the currently active tab in thetablist, as defined inManaging Focus.tablist elements, which contain a set of associatedtab elements, are typically placed near a series oftabpanel elements, usually preceding it. See the ARIA Authoring Practices Guide for details on implementing a tab set design pattern.

AuthorsMUST ensureelements withrole tab areaccessibility children of an element with the roletablist.

AuthorsMUST ensure that if atab is active, a correspondingtabpanel that represents the activetab is rendered.

AuthorsSHOULD ensure thetabpanel associated with the currently active tab isperceivable to the user.

For a single-selectabletablist, authorsSHOULDhide from all users othertabpanelelements until the user selects the tab associated with that tabpanel. For a multi-selectabletablist, authorsSHOULD ensure that thetab for each visibletabpanel has thearia-expandedattribute set totrue, and that thetabs associated with the remaininghidden from all userstabpanel elements have theiraria-expanded attributes set tofalse.

AuthorsSHOULD ensure that a selected tab has itsaria-selected attribute set totrue, that inactive tab elements have theiraria-selected attribute set tofalse, and that the currently selected tab provides a visual indication that it is selected.

In certain conditions, a user agentMAY provide an implicit value foraria-selected for eachtab in atablist, and if it does, the user agentMUST ensure the following conditions are met before providing an implicit value:

The value ofaria-multiselectable on thetablist isfalse orundefined.
None of thetab elements in thetablist have an explicitly declared value foraria-selected oraria-expanded.

Characteristics:
Characteristic	Value
Superclass Role:	`sectionhead` `widget`
Required Accessibility Parent Roles:	`tablist`
Supported States and Properties:	`aria-disabled` `aria-expanded` `aria-haspopup` `aria-posinset` `aria-selected` `aria-setsize`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	contents author
Accessible Name Required:	True
Children Presentational:	True
Implicit Value for Role:	Default for`aria-selected` is`false`.

`table`role

Asection containing data arranged in rows and columns. See relatedgrid.

Thetable 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, authorsSHOULD usegrid ortreegrid instead.

AuthorsSHOULD provide an accessible name for atable, which can be done with thearia-label oraria-labelledby attribute. AuthorsSHOULD reference a visible label witharia-labelledby if a visible label is present for thetable.

AuthorsSHOULD prefer the use of the host language's semantics for table whenever possible, such as the<table> element inHTML.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Subclass Roles:	`grid`
Base Concept:	`<table>` inHTML
Allowed Accessibility Child Roles:	`caption` `row` `rowgroup` withaccessibility child `row`
Supported States and Properties:	`aria-colcount` `aria-rowcount`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author

`tablist`role

A list of tabelements, which are references totabpanel elements.

To bekeyboard accessible, authorsSHOULD manage focus of descendants for all instances of thisrole, as described inManaging Focus.

tablist elements are typically placed near, and usually preceding, a series oftabpanel elements. See the ARIA Authoring Practices Guide for details on implementing a tab set design pattern.

Elements with the roletablist have an implicitaria-orientation value ofhorizontal.

Characteristics:
Characteristic	Value
Superclass Role:	`composite`
Allowed Accessibility Child Roles:	`tab`
Supported States and Properties:	`aria-multiselectable` `aria-orientation`
Inherited States and Properties:	`aria-activedescendant` `aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Implicit Value for Role:	Default for`aria-orientation` is`horizontal`.

`tabpanel`role

A container for the resources associated with atab, where eachtab is contained in atablist.

AuthorsSHOULD associate atabpanelelement with itstab, by using thearia-controls attribute on the tab to reference the tab panel, and/or by using thearia-labelledby attribute on the tab panel to reference the tab.

tablist elements are typically placed near, and usually preceding, a series oftabpanel elements. See the ARIA Authoring Practices Guide for details on implementing a tab set design pattern.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Accessible Name Required:	True

`term`role

A word or phrase with an optional corresponding definition. See relateddefinition.

Theterm role is used to explicitly identify a word or phrase for which adefinition has been provided by the author or is expected to be provided by the user. If there is an existingdefinition, or a form or form control to enter a definition, authorsSHOULD setaria-details to point to the related element.

AuthorsSHOULD NOT use theterm role on interactive elements such as links because doing so could prevent users ofassistive technologies from interacting with those elements.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Related Concepts:	`<dfn>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Prohibited States and Properties:	`aria-braillelabel` `aria-label` `aria-labelledby`
Name From:	prohibited

`textbox`role

A type of input that allows free-form text as its value.

If thearia-multilineattribute istrue, thewidget accepts line breaks within the input, as in anHTMLtextarea. Otherwise, this is a simple text box. The intended use is for languages that do not have a text input element, or cases in which an element with differentsemantics is repurposed as a text field.

AuthorsMUST 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:

an error icon, where the containing textbox has been provided anaria-invalid,aria-errormessage, or both attributes;
an icon of a user silhouette, where the textbox is also visibly labeled or provided an accessible name of "name" or "username"; and
a graphical status indicator, such as a gauge to represent characters remaining, which represents dynamically updating text available outside of the textbox.

Note

In most user agent implementations, the default behavior of theENTER orRETURN key is different between the single-line and multi-line text fields inHTML. When user has focus in a single-line<input type="text"> element, the keystroke usually submits the form. When user has focus in a multi-line<textarea> element, the keystroke inserts a line break. The WAI-ARIAtextbox role differentiates these types of boxes with the aria-multiline attribute, so authors are advised to be aware of this distinction when designing the field.

Characteristics:
Characteristic	Value
Superclass Role:	`input`
Subclass Roles:	`searchbox`
Related Concepts:	`<textarea>` inHTML `<input type="text">` inHTML
Supported States and Properties:	`aria-activedescendant` `aria-autocomplete` `aria-errormessage` `aria-haspopup` `aria-invalid` `aria-multiline` `aria-placeholder` `aria-readonly` `aria-required`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-flowto` `aria-grabbed` (state) `aria-hidden` (state) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Accessible Name Required:	True

`time`role

An element that represents a specific point in time.

Note

At the present time, there are noWAI-ARIA properties corresponding to thedatetime attribute supported on<time> inHTML. The addition of this property will be considered for ARIA version 1.3.

AuthorsSHOULD limit text contents to a valid date- or time-related string, or apply this futuredatetime-equivalent property to the element which has roletime.

Example 24

Examples of valid date- or time-related strings as text contents of an element with thetime role:

A valid month string:<span role="time">2019-11</span>
A valid date string:<span role="time">2019-11-18</span>
A valid yearless date string:<span role="time">11-18</span>
A valid time string:<span role="time">09:54:39</span>
A valid floating date and time string:<span role="time">2019-11-18T14:54</span>
A valid time-zone offset string:<span role="time">-08:00</span>
A valid global date and time string:<span role="time">2019-11-18T14:54Z</span>
A valid week string:<span role="time">2019-W47</span>
Four or more ASCII digits, at least one of which is not U+0030 DIGIT ZERO (0):<span role="time">0001</span>
A valid duration string:<span role="time">4h 18m 3s</span>

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Related Concepts:	`<time>` inHTML
Inherited States and Properties:	`aria-atomic` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Prohibited States and Properties:	`aria-braillelabel` `aria-label` `aria-labelledby`
Name From:	prohibited

`timer`role

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

The text contents of the timerobject indicate the current time measurement, and are updated as that amount changes. The timer value is not necessarily machine parsable, but authorsSHOULD update the text contents at fixed intervals, except when the timer is paused or reaches an end-point.

Elements with the roletimer have an implicitaria-live value ofoff.

Characteristics:
Characteristic	Value
Superclass Role:	`status`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Implicit Value for Role:	Default for`aria-live` is`off`.

`toolbar`role

A collection of commonly used function buttons or controls represented in compact visual form.

The toolbar is often a subset of functions found in amenubar, designed to reduce user effort in using these functions. AuthorsMUST supply a label on each toolbar when the application contains more than one toolbar.

AuthorsMAY manage focus of descendants for all instances of thisrole, as described inManaging Focus.

Elements with the roletoolbar have an implicitaria-orientation value ofhorizontal.

Characteristics:
Characteristic	Value
Superclass Role:	`group`
Related Concepts:	`menubar`
Supported States and Properties:	`aria-orientation`
Inherited States and Properties:	`aria-activedescendant` `aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Implicit Value for Role:	Default for`aria-orientation` is`horizontal`.

`tooltip`role

A contextual popup that displays a description for an element.

Thetooltip typically becomes visible, after a short delay, in response to a mouse hover, or after theaccessibility parent receives keyboard focus. The use of aWAI-ARIA tooltip is a supplement to the normal tooltip behavior of the user agent.

Note

Typical tooltip delays last from one to five seconds.

AuthorsSHOULD ensure that elements with the roletooltip are referenced through the use ofaria-describedby before or at the time the tooltip is displayed.

Characteristics:
Characteristic	Value
Superclass Role:	`section`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	contents author

`tree`role

Awidget that allows the user to select one or more items from a hierarchically organized collection.

To bekeyboard accessible, authorsSHOULD manage focus of descendants for all instances of thisrole, as described inManaging Focus.

Elements with the roletree have an implicitaria-orientation value ofvertical.

Characteristics:
Characteristic	Value
Superclass Role:	`select`
Subclass Roles:	`treegrid`
Allowed Accessibility Child Roles:	`treeitem`
Supported States and Properties:	`aria-errormessage` `aria-invalid` `aria-multiselectable` `aria-required`
Inherited States and Properties:	`aria-activedescendant` `aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-orientation` `aria-owns` `aria-relevant` `aria-roledescription`
Name From:	author
Accessible Name Required:	True
Implicit Value for Role:	Default for`aria-orientation` is`vertical`.

`treegrid`role

Agrid whose rows can be expanded and collapsed in the same manner as for atree.

Ifaria-readonly is set on anelement withroletreegrid,user agentsMUST propagate the value to allgridcell elements that areaccessibility descendants of thetreegrid and expose the value in the accessibilityAPI. An authorMAY override the propagated value of aria-readonly for an individualgridcell element.

When thearia-readonly attribute is applied to afocusable gridcell, it indicates whether the content contained in thegridcell is editable. Thearia-readonly attribute does not represent availability of functions for navigating or manipulating thetreegrid itself.

In atreegrid that provides content editing functions, if the content of a focusablegridcell element is not editable, authorsMAY setaria-readonly totrue on thegridcell element. However, if atreegrid presents a collection of elements that do not supportaria-readonly, such as a collection oflink elements, it is not necessary for the author to specify a value foraria-readonly.

To bekeyboard accessible, authorsSHOULD manage focus of descendants for all instances of thisrole, as described inManaging Focus.

Characteristics:
Characteristic	Value
Superclass Role:	`grid` `tree`
Allowed Accessibility Child Roles:	`caption` `row` `rowgroup` withaccessibility child `row`
Inherited States and Properties:	`aria-activedescendant` `aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-colcount` `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage` `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-multiselectable` `aria-orientation` `aria-owns` `aria-readonly` `aria-relevant` `aria-required` `aria-roledescription` `aria-rowcount`
Name From:	author
Accessible Name Required:	True

`treeitem`role

An item in atree.

Atreeitemelement can contain a sub-level group of elements that can be expanded or collapsed. An expandable collection oftreeitem elements are enclosed in an element with thegrouprole.

AuthorsMUST ensureelements withroletreeitem areaccessibility children of an element with roletree or an element with rolegroup that is theaccessibility child of an element with roletreeitem.

In certain conditions, a user agentMAY provide an implicit value foraria-selected for eachtreeitem in atree, and if it does, the user agentMUST ensure the following conditions are met before providing an implicit value:

The value ofaria-multiselectable on thetree isfalse orundefined.
None of thetreeitem elements in thetree have an explicitly declared value foraria-selected oraria-checked.

If a user agent provides an implicitaria-selected value for atreeitem, the valueSHOULD betrue if thetreeitem hasDOM focus or the tree hasDOM focus and the treeitem is referenced byaria-activedescendant. Otherwise, if a user agent provides an implicitaria-selected value for atreeitem, the valueSHOULD befalse.

AuthorsMAY indicate selection fortreeitem elements using eitheraria-selected oraria-checked. Some user interfaces indicate selection witharia-selected in single-select trees and witharia-checked in multi-select trees. AuthorsSHOULD NOT specify botharia-selected andaria-checked ontreeitem elements contained by the sametree except in the extremely rare circumstances where all the following conditions are met:

The meaning and purpose ofaria-selected is different from the meaning and purpose ofaria-checked in the user interface.
The user interface makes the meaning and purpose of each state apparent.
The user interface provides a separate method for controlling each state.

Characteristics:
Characteristic	Value
Superclass Role:	`listitem` `option`
Required Accessibility Parent Roles:	`tree` `group` withaccessibility parent `treeitem`
Supported States and Properties:	`aria-expanded` `aria-haspopup` `aria-level`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-checked` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-posinset` `aria-relevant` `aria-roledescription` `aria-selected` (state) `aria-setsize`
Name From:	contents author
Accessible Name Required:	True

`widget`abstract role

An interactive component of a graphical user interface (GUI).

Widgets are discrete user interface objects with which the user can interact. Widget roles map to standard features inaccessibility APIs. When the user navigates an element assigned any of the non-abstract subclass roles ofwidget,assistive technologies that typically intercept standard keyboard eventsSHOULD switch to an application browsing mode, and pass keyboard events through to the web application. The intent is to hint to certainassistive technologies to switch from normal browsing mode into a mode more appropriate for interacting with a web application; someuser 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.

widget is anabstract role used for the ontology. AuthorsMUST NOT usewidget role in content.

Characteristics:
Characteristic	Value
Is Abstract:	True
Superclass Role:	`roletype`
Subclass Roles:	`command` `composite` `gridcell` `input` `progressbar` `row` `scrollbar` `separator` `tab`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`

`window`abstract role

A browser or application window.

Elements with thisrole have a window-like behavior in a graphical user interface (GUI) 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.

window is an abstract role used for the ontology. AuthorsMUST NOT usewindow role in content.

Note

In the description of this role, the term "application" does not refer to theapplication role, which specifies specific assistive technology behaviors.

Characteristics:
Characteristic	Value
Is Abstract:	True
Superclass Role:	`roletype`
Subclass Roles:	`dialog`
Supported States and Properties:	`aria-modal`
Inherited States and Properties:	`aria-atomic` `aria-braillelabel` `aria-brailleroledescription` `aria-busy` (state) `aria-controls` `aria-current` (state) `aria-describedby` `aria-description` `aria-details` `aria-disabled` (state)(deprecated on this role in ARIA 1.2) `aria-dropeffect` `aria-errormessage`(deprecated on this role in ARIA 1.2) `aria-flowto` `aria-grabbed` (state) `aria-haspopup`(deprecated on this role in ARIA 1.2) `aria-hidden` (state) `aria-invalid` (state)(deprecated on this role in ARIA 1.2) `aria-keyshortcuts` `aria-label` `aria-labelledby` `aria-live` `aria-owns` `aria-relevant` `aria-roledescription`

6.Supported States and Properties

6.1Clarification of States versus Properties

The terms "states" and "properties" refer to similar features. Both provide specific information about anobject, and both form part of the definition of the nature ofroles. In this document, states and properties are both treated as aria-prefixed markupattributes. However, they are maintained conceptually distinct to clarify subtle differences in their meaning. One major difference is that thevalues of properties (such asaria-labelledby) are often less likely to change throughout the application life-cycle than the values of states (such asaria-checked) which might change frequently due to user interaction. Note that the frequency of change difference is not a rule; a few properties, such asaria-valuetext 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 ofstate andproperty for more information.

6.2Characteristics of States and Properties

States and properties have the characteristics described in the following sections.

6.2.1Related Concepts

Advisory information about features from this or other languages that correspond to thisstate orproperty. While the correspondence might not be exact, it is useful to help understand the intent of the state or property.

6.2.2Used in Roles

Advisory information aboutroles that use thisstate orproperty. 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.

6.2.3Inherits into Roles

Advisory information aboutroles that inherit thestate orproperty from an ancestor role.

6.2.4Value

Value type of thestate orproperty. The value is one of the following types:

true/false: Value representing eithertrue orfalse. The default value for this value type isfalse unless otherwise specified.
tristate: Value representingtrue,false,mixed, orundefined values. The default value for this value type isundefined unless otherwise specified.
true/false/undefined: Value representingtrue,false, orundefined (not applicable). The default value for this value type isundefined unless otherwise specified. For example, an element witharia-expanded set tofalse is not currently expanded; an element witharia-expanded set toundefined is not expandable.
ID reference: Reference to the ID of anotherelement in the same document
ID reference list: A list of one or more ID references.
integer: A numerical value without a fractional component.
number: Any real numerical value.
string: Unconstrained value type.
token: One of a limited set of allowed values. The default value is defined in each attribute's Values table, as specified in theAttribute Values section.
token list: A list of one or more tokens.

These are generic types for states and properties, but do not define specific representation. SeeState and Property Attribute Processing for details on how these values are expressed and handled in host languages.

6.3ARIA Attributes

6.3.4ARIA nullable DOMString Attributes

As noted inA.Mapping WAI-ARIA Value types to languages, attributes are included in host languages, and the syntax for representation ofWAI-ARIA types is governed by the host language.

The following algorithm should be used for ARIA nullable DOMString attributes inHTML:

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.

Note

Note: As of ARIA 1.2, all ARIA attributes exposed via IDL are defined as nullable DOMStrings. 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, theARIA 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 enumerated attributes.

6.3.4.1Example Attribute Usage

This section is non-normative.

Example 25

Example

// 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

Example 26

Example

// aria-busy example// true/false ~ boolean-like nullable string; returns null unless setel.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"

Example 27

Example

// aria-pressed example// Tristate ~ true/false/mixed/undefined string; null if unspecified// no value has been definedbutton.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 valuebutton.removeAttribute("aria-pressed");button.ariaPressed;// null

6.4Translatable Attributes

TheHTML specification states that other specifications can define translatable attributes. The language and directionality of each attribute value is the same as thelanguage anddirectionality of the element.

To be understandable by assistive technology users, the values of the followingstates andproperties aretranslatable attributes and should be translated when a page is localized:

6.5Global States and Properties

Somestates andproperties are applicable to all host languageelements regardless of whether arole 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.

aria-atomic
aria-braillelabel (Except where prohibited)
aria-brailleroledescription (Except where prohibited)
aria-busy (state)
aria-controls
aria-current (state)
aria-describedby
aria-description
aria-details
aria-disabled (state) (Global use deprecated in ARIA 1.2)
aria-dropeffect
aria-errormessage (Global use deprecated in ARIA 1.2)
aria-flowto
aria-grabbed (state)
aria-haspopup (Global use deprecated in ARIA 1.2)
aria-hidden (state)
aria-invalid (state) (Global use deprecated in ARIA 1.2)
aria-keyshortcuts
aria-label (Except where prohibited)
aria-labelledby (Except where prohibited)
aria-live
aria-owns
aria-relevant
aria-roledescription (Except where prohibited)

6.6Taxonomy ofWAI-ARIA States and Properties

States and properties are categorized as follows:

6.6.1Widget Attributes

This section containsattributes specific to common user interfaceelements found onGUI systems or in rich internet applications which receive user input and process user actions. These attributes are used to support the widget roles.

Widget attributes might be mapped by auser agent to platformaccessibility API state, for access byassistive technologies, or they might be accessed directly from theDOM.

6.6.2Live Region Attributes

This section containsattributes specific tolive regions in rich internet applications. These attributesMAY be applied to anyelement. The purpose of these attributes is to indicate that content changes might occur without the element having focus, and to provideassistive technologies with information on how to process those content updates. Someroles specify a default value for thearia-live attribute specific to that role. An example of a live region is a ticker section that lists updating stock quotes. User agentsMAY ignore changes triggered by direct user action on anelement inside a live region (e.g., editing the value of a text field).

6.6.3Drag-and-Drop Attributes

This section listsattributes which indicate information about drag-and-drop interfaceelements, such as draggable elements and their drop targets. Drop target information will be rendered visually by the author and provided toassistive technologies through an alternate modality.

6.6.4Relationship Attributes

This section listsattributes that indicaterelationships or associations betweenelements which cannot be readily determined from the document structure.

6.7State change notification

User agentsMUST provide a way for assistive technologies to be notified when states change, either throughDOM attribute change events or platform accessibilityAPI events.

6.8Definitions of States and Properties (all aria-* attributes)

Below is an alphabetical list ofWAI-ARIA states andproperties to be used by authors. A detailed definition of eachWAI-ARIA state and property follows this compact list.

aria-activedescendant: Identifies the currently active element whenDOM focus is on a composite widget,combobox,textbox,group, orapplication.
aria-atomic: Indicates whetherassistive technologies will present all, or only parts of, the changed region based on the change notifications defined by thearia-relevant attribute.
aria-autocomplete: Indicates whether inputting text could trigger display of one or more predictions of the user's intended value for acombobox,searchbox, ortextbox and specifies how predictions would be presented if they were made.
aria-braillelabel: Defines a string value that labels the current element, which is intended to be converted into Braille. See relatedaria-label.
aria-brailleroledescription: Defines a human-readable, author-localized abbreviated description for therole of anelement, which is intended to be converted into Braille. See relatedaria-roledescription.
aria-busy: Indicates an element is being modified and that assistive technologies could wait until the modifications are complete before exposing them to the user.
aria-checked: Indicates the current "checked"state of checkboxes, radio buttons, and otherwidgets. See relatedaria-pressed andaria-selected.
aria-colcount: Defines the total number of columns in atable,grid, ortreegrid. See relatedaria-colindex.
aria-colindex: Defines anelement's column index or position with respect to the total number of columns within atable,grid, ortreegrid. See relatedaria-colindextext,aria-colcount, andaria-colspan.
aria-colindextext: Defines a human readable text alternative ofaria-colindex. See relatedaria-rowindextext.
aria-colspan: Defines the number of columns spanned by a cell or gridcell within atable,grid, ortreegrid. See relatedaria-colindex andaria-rowspan.
aria-controls: Identifies theelement (or elements) whose contents or presence are controlled by the focused element or composite widget. See relatedaria-details andaria-owns.
aria-current: Indicates theelement that represents the current item within a container or set of related elements.
aria-describedby: Identifies theelement (or elements) that describes theobject. See relatedaria-labelledby andaria-description.
aria-description: Defines a string value that describes or annotates the current element. See relatedaria-describedby.
aria-details: Identifies theelement (or elements) that provide additional information related to theobject. See relatedaria-describedby.
aria-disabled: Indicates that theelement isperceivable but disabled, so it is not editable or otherwiseoperable. See relatedaria-hidden andaria-readonly.
aria-dropeffect: [Deprecated inARIA 1.1] Indicates what functions can be performed when a dragged object is released on the drop target.
aria-errormessage: Identifies theelement (or elements) that provides an error message for anobject. See relatedaria-invalid andaria-describedby.
aria-expanded: Indicates whether a related element is expanded (shown) or collapsed (hidden).
aria-flowto: Identifies the nextelement (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.
aria-grabbed: [Deprecated inARIA 1.1] Indicates an element's "grabbed"state in a drag-and-drop operation.
aria-haspopup: Indicates the availability and type of interactive popup element, such as menu or dialog, that can be triggered by anelement.
aria-hidden: Indicates, when set totrue, that anelement and its entire subtree are hidden from assistive technology, regardless of whether it is visibly rendered.
aria-invalid: Indicates the entered value does not conform to the format expected by the application. See relatedaria-errormessage.
aria-keyshortcuts: Defines keyboard shortcuts that an author has implemented to activate or give focus to an element.
aria-label: Defines a string value that labels the current element. See relatedaria-labelledby.
aria-labelledby: Identifies theelement (or elements) that labels the current element. See relatedaria-label andaria-describedby.
aria-level: Defines the hierarchical level of anelement within a structure.
aria-live: Indicates that anelement will be updated or modified, and defines the priority of updates theuser agents,assistive technologies, and user can expect from thelive region.
aria-modal: Indicates whether anelement is modal when displayed.
aria-multiline: Indicates whether a text box accepts multiple lines of input or only a single line.
aria-multiselectable: Indicates that the user can select more than one item from the current selectable descendants.
aria-orientation: Indicates whether the element's orientation is horizontal, vertical, or unknown/ambiguous.
aria-owns: Identifies anelement (or elements) in order to define a visual, functional, or contextual parent/childrelationship betweenDOM elements where the DOM hierarchy cannot be used to represent the relationship. See related aria-controls.
aria-placeholder: Defines 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.
aria-posinset: Defines anelement's number or position in the current set of listitems or treeitems. Not required if all elements in the set are present in theDOM. See related aria-setsize.
aria-pressed: Indicates the current "pressed"state of toggle buttons. See relatedaria-checked andaria-selected.
aria-readonly: Indicates that theelement is not editable, but is otherwiseoperable. See relatedaria-disabled.
aria-relevant: Indicates what notifications the user agent will trigger when theaccessibility tree within a live region is modified. See relatedaria-atomic.
aria-required: Indicates that user input is required on theelement before a form can be submitted.
aria-roledescription: Defines a human-readable, author-localized description for therole of anelement.
aria-rowcount: Defines the total number of rows in atable,grid, ortreegrid. See relatedaria-rowindex.
aria-rowindex: Defines anelement's row index or position with respect to the total number of rows within atable,grid, ortreegrid. See relatedaria-rowindextext,aria-rowcount, andaria-rowspan.
aria-rowindextext: Defines a human readable text alternative ofaria-rowindex. See relatedaria-colindextext.
aria-rowspan: Defines the number of rows spanned by a cell or gridcell within atable,grid, ortreegrid. See relatedaria-rowindex andaria-colspan.
aria-selected: Indicates the current "selected"state of variouswidgets. See relatedaria-checked andaria-pressed.
aria-setsize: Defines the number of items in the current set of listitems or treeitems. Not required if all elements in the set are present in theDOM. See related aria-posinset.
aria-sort: Indicates if items in a table or grid are sorted in ascending or descending order.
aria-valuemax: Defines the maximum allowed value for a rangewidget.
aria-valuemin: Defines the minimum allowed value for a rangewidget.
aria-valuenow: Defines the current value for a rangewidget. See relatedaria-valuetext.
aria-valuetext: Defines the human readable text alternative ofaria-valuenow for a rangewidget.

`aria-activedescendant`property

Identifies the currently active element whenDOM focus is on a composite widget,combobox,textbox,group, orapplication.

Thearia-activedescendant property provides an alternative method of managing focus for interactive elements that might contain multiplefocusable descendants, such as menus, grids, and toolbars. Instead of movingDOM focus among accessibility descendants, authorsMAY setDOM focus on a container element that supportsaria-activedescendant and then usearia-activedescendant to refer to the element that is active.

AuthorsMUST ensure that one of the following two sets of conditions is met when setting the value ofaria-activedescendant on an element withDOM focus:

The value ofaria-activedescendant refers to an accessibility descendant.
The element withDOM focus is a combobox,textbox orsearchbox witharia-controls referring to an element that supportsaria-activedescendant, and the value ofaria-activedescendant refers to anaccessibility descendant of the controlled element. For example, in acombobox, focus can remain on thecombobox while the value ofaria-activedescendant on thecombobox element refers to a descendant of a popuplistbox that is controlled by thecombobox.

AuthorsSHOULD also ensure that the currently active descendant is visible and in view (or scrolls into view) when focused.

Characteristics:
Characteristic	Value
Related Concepts:	SVG [SVG2] and DOM [DOM] active
Used in Roles:	`application` `combobox` `composite` `group` `textbox`
Inherits into Roles:	`grid` `listbox` `menu` `menubar` `radiogroup` `row` `searchbox` `select` `spinbutton` `tablist` `toolbar` `tree` `treegrid`
Value:	ID reference

`aria-atomic`property

Indicates whetherassistive technologies will present all, or only parts of, the changed region based on the change notifications defined by thearia-relevant attribute.

Bothaccessibility APIs and theDocument Object Model [DOM] provide events to allow the assistive technologies to determine changed areas of the document.

When the content of alive region changes, user agentsSHOULD examine the changedelement and traverse the ancestors to find the first element witharia-atomic set, and apply the appropriate behavior for the cases below.

If none of the ancestors have explicitly setaria-atomic, the default is thataria-atomic isfalse, and assistive technologies will only present the changed node to the user.
Ifaria-atomic is explicitly set tofalse, assistive technologies will stop searching up the ancestor chain and present only the changed node to the user.
Ifaria-atomic is explicitly set totrue, assistive technologies will present the entire contents of the element, including the author-defined live region label if one exists.

Whenaria-atomic istrue, assistive technologies can choose to combine several changes and present the entire changed region at once.

Characteristics:
Characteristic	Value
Used in Roles:	All elements of the base markup
Value:	true/false

Values:
Value	Description
false	Assistive technologies will present only the changed node or nodes.
true	Assistive technologies will present the entire changed region as a whole, including the author-defined label if one exists.

`aria-autocomplete`property

Indicates whether inputting text could trigger display of one or more predictions of the user's intended value for acombobox,searchbox, ortextbox and specifies how predictions would be presented if they were made.

Thearia-autocomplete property describes the type of interaction model atextbox,searchbox, orcombobox employs when dynamically helping users complete text input. It distinguishes between two models: the inline model (aria-autocomplete="inline") that presents a value completion prediction inside the text input and the list model (aria-autocomplete="list") 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 (aria-autocomplete="both").

Thearia-autocomplete property is limited to describing predictive behaviors of an input element. AuthorsSHOULD either omit specifying a value foraria-autocomplete or setaria-autocomplete tonone 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 ofaria-autocomplete would benone 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 supportsaria-autocomplete have a default value foraria-autocomplete ofnone.

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 hasaria-autocomplete set toinline orboth, authorsSHOULD 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.

If an element hasaria-autocomplete set tolist orboth, authorsMUST ensure both of the following conditions are met:

The element has a value specified foraria-controls that refers to the element that contains the collection of suggested values.
The element has a value foraria-haspopup that matches the role of the element that contains the collection of suggested values.

Some implementations of the list model require the user to perform an action, such as moving focus to the suggestion with theDown Arrow or clicking on the suggestion, in order to choose the suggestion. In such implementations, authorsMAY manage focus by either usingaria-activedescendant if the collection container supports it or by movingDOM 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 theTab key or clicks on a different field. If an element hasaria-autocomplete set tolist orboth, and if a suggestion is automatically selected as the user provides input, authorsMUST ensure all the following conditions are met:

The collection of suggestions is presented in an element with a role that supports aria-activedescendant.
The value ofaria-activedescendant set on the input field is dynamically adjusted to refer to the element containing the selected suggestion as described in the definition ofaria-activedescendant.
DOM focus remains on the text input while the suggestions are displayed.

Thearia-autocomplete property is not intended to indicate the presence of a completion suggestion, and authorsSHOULD NOT dynamically change its value in order to communicate the presence of a suggestion. When an element hasaria-autocomplete set tolist orboth, authorsSHOULD use the aria-expanded state to communicate whether the element that presents the suggestion collection is displayed.

Characteristics:
Characteristic	Value
Used in Roles:	`combobox` `textbox`
Inherits into Roles:	`searchbox`
Value:	token

Values:
Value	Description
inline	When a user is providing input, text suggesting one way to complete the provided input might be dynamically inserted after the caret.
list	When a user is providing input, an element containing a collection of values that could complete the provided input might be displayed.
both	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.
none (default)	When a user is providing input, an automatic suggestion that attempts to predict how the user intends to complete the input is not displayed.

`aria-braillelabel`property

Defines a string value that labels the current element, which is intended to be converted into Braille. See relatedaria-label.

The purpose ofaria-braillelabel is similar to that ofaria-label. It provides the user with a recognizable name of the object in Braille.

Thearia-braillelabel property gives authors the ability to override how assistive technologies localize and express the accessible name of an element in Braille. Thus inappropriately usingaria-braillelabel might inhibit users' ability to understand an element on braille interfaces. AuthorsSHOULD limit use ofaria-braillelabel to instances where the name of an element when converted to Braille is not the desired user experience.

When usingaria-braillelabel, authorsSHOULD also ensure that:

The element to whicharia-braillelabel is applied has a valid accessible name.
The value ofaria-braillelabel is not empty or does not contain onlywhitespace characters.
The value ofaria-braillelabel does not contain any characters inUnicode Braille Patterns or consists of only characters inUnicode Braille Patterns; the value does not only contain Braille Pattern dots-0.
The value ofaria-braillelabel is not identical to the element's accessible name.

AuthorsMUST NOT specifyaria-braillelabel on an element which has an explicit or implicitWAI-ARIA role wherearia-braillelabel is prohibited.

Note

Note thatAssistive Technologies 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 viaaria-label isalmost always the better user experience and authors arestrongly discouraged from usingaria-braillelabel to replicatearia-label. Instead,aria-braillelabel 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 usingaria-braillelabel, 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 becauseAssistive Technologies will pass such content directly to the user without applying user specific braille translations; in general, authors arestrongly discouraged from using Unicode Braille Patterns inaria-braillelabel.

Assistive technologiesSHOULD use the value ofaria-braillelabel when presenting the accessible name of an element in Braille, butSHOULD NOT change other functionality. For example, an assistive technology that provides aural renderingSHOULD use the accessible name.

Assistive technologiesSHOULD expose thearia-braillelabel property as follows:

If the value ofaria-braillelabel does not contain characters inUnicode Braille Patterns, translate the value according to the user's preferred translation table.
Otherwise, pass the value to the user without translation.

The following example shows the use ofaria-braillelabel to customize a button's name in braille output.

Example 28

<buttonaria-braillelabel="****"><imgalt="4 stars"src="images/stars.jpg"></button>

In the previous example, a braille display would display "btn ****" in Braille rather than the verbose "btn gra 4 stars".

Characteristics:
Characteristic	Value
Used in Roles:	All elements of the base markup except for the following roles:`caption`,`code`,`definition`,`deletion`,`emphasis`,`generic`,`insertion`,`mark`,`none`,`paragraph`,`strong`,`subscript`,`suggestion`,`superscript`,`term`,`time`
Value:	string

`aria-brailleroledescription`property

Defines a human-readable, author-localized abbreviated description for therole of anelement, which is intended to be converted into Braille. See relatedaria-roledescription.

Someassistive technologies, 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.

Thearia-brailleroledescription property gives authors the ability to override howassistive technologies localize and express the name of a role in Braille. Thus inappropriately usingaria-brailleroledescription might inhibit users' ability to understand or interact with an element on braille interfaces. AuthorsSHOULD limit use ofaria-brailleroledescription to clarifying the purpose of non-interactive container roles likegroup orregion, or to providing amore specific description of awidget in a braille context.

AuthorsMUST NOT usearia-brailleroledescription without providingaria-roledescription. Additionally, as witharia-roledescription, authorsMUST NOT specifyaria-brailleroledescription on an element which has an explicit or implicitWAI-ARIA role wherearia-brailleroledescription is prohibited.

In general,aria-brailleroledescription is only meant to be used in rare cases when aaria-roledescription is excessively verbose when rendered in Braille.

When usingaria-brailleroledescription, authorsSHOULD also ensure that:

The element to whicharia-brailleroledescription is applied has a validWAI-ARIA role or has an implicit WAI-ARIA role semantic.
The value ofaria-brailleroledescription is not empty or does not contain only whitespace characters.
The value ofaria-brailleroledescription does not contain any characters inUnicode Braille Patterns or consists of only characters inUnicode Braille Patterns; the value does not only contain Braille Pattern dots-0.
The value ofaria-brailleroledescription should not be identical to the element'sWAI-ARIAaria-roledescription,WAI-ARIArole or implicit WAI-ARIA role semantic.

Note

Note that Assistive Technologies with braille support can convertaria-roledescription content to Braille. In addition, assistive technologies will be able to customize such braille output according to user preferences. Using onlyaria-roledescription isalmost always the better user experience and authors arestrongly discouraged from usingaria-brailleroledescription to replicatearia-roledescription. Instead,aria-brailleroledescription is meant to be used only whenaria-roledescription 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 usingaria-brailleroledescription, 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 becauseAssistive Technologies will pass such content directly to the user without applying user specific braille translations; in general, authors arestrongly discouraged from using Unicode Braille Patterns inaria-brailleroledescription.

User agentsMUST NOT expose thearia-brailleroledescription property if any of the following conditions exist:

The value ofaria-brailleroledescription is empty or contains only whitespace characters, which includes standardwhitespace and the empty Braille pattern: dots-0 (U+2800).
The element to whicharia-brailleroledescription is applied has an explicit or implicitWAI-ARIA role wherearia-brailleroledescription is prohibited.
The element to whicharia-brailleroledescription is applied does not have a validWAI-ARIAaria-roledescription.

Assistive technologiesSHOULD use the value ofaria-brailleroledescription when presenting the role of an element in Braille, butSHOULD NOT change other functionality based on the role of an element that has a value foraria-brailleroledescription. For example, an assistive technology that provides functions for navigating to the nextregion orbuttonSHOULD allow those functions to navigate to regions and buttons that have anaria-brailleroledescription.

Assistive technologiesSHOULD expose thearia-brailleroledescription property as follows:

If the value ofaria-brailleroledescription does not contain characters inUnicode Braille Patterns, translate the value according to the user's preferred translation table.
Otherwise, pass the value to the user without translation.

The following two examples show the use ofaria-brailleroledescription to abbreviate the role of a repeated non-interactive "slide" container in a web-based presentation application.

Example 29

<divrole="article"aria-roledescription="slide"aria-brailleroledescription="sld"id="slide"aria-labelledby="slideheading"><h1id="slideheading">Quarterly Report</h1><!-- remaining slide contents --></div>

Example 30

<articlearia-roledescription="slide"aria-brailleroledescription="sld"id="slide"aria-labelledby="slideheading"><h1id="slideheading">Quarterly Report</h1><!-- remaining slide contents --></div>

In the previous examples, a braille screen reader user would read "sld Quarterly Report" rather than the more verbose "slide Quarterly Report."

Characteristics:
Characteristic	Value
Used in Roles:	All elements of the base markup except for the following roles:`generic`
Value:	string

`aria-busy`state

Indicates an element is being modified and that assistive technologies could wait until the modifications are complete before exposing them to the user.

The default value ofaria-busy isfalse for all elements. Whenaria-busy istrue for an element, assistive technologies can ignore changes to content that is anaccessibility descendant that element and then process all changes made during the busy period as a single, atomic update whenaria-busy becomesfalse.

If it is necessary to make multiple additions, modifications, or removals within a container element that is already either partially or fully rendered, authorsMAY setaria-busy totrue on the container element before the first change, and then set it tofalse when the last change is complete. For example, if multiple changes to alive region should be spoken as a single unit of speech, authorsMAY setaria-busy totrue while the changes are being made and then set it tofalse when the changes are complete and ready to be spoken.

If an element with rolefeed is marked busy, assistive technologies might defer rendering changes that occur inside thefeed with the exception of user-initiated changes that occur inside thearticle that the user is reading during the busy period.

If changes to a renderedwidget would create a state where thewidget is modifyingAllowed Accessibility Child Roles during script execution, authorsMAY setaria-busy totrue on thewidget 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.

Characteristics:
Characteristic	Value
Used in Roles:	All elements of the base markup
Value:	true/false

Values:
Value	Description
false (default):	There are no expected updates for the element.
true	The element is being updated.

`aria-checked`state

Indicates the current "checked"state of checkboxes, radio buttons, and otherwidgets. See relatedaria-pressed andaria-selected.

Thearia-checkedattribute indicates whether theelement is checked (true), unchecked (false), or represents a group of other elements that have a mixture of checked and uncheckedvalues (mixed). Most inputs only support values oftrue andfalse, but themixed value is supported by certain tri-state inputs such as acheckbox ormenuitemcheckbox.

Themixed value isnot supported onradio,menuitemradio,switch or any element that inherits from these, anduser agentsMUST treat amixed value as equivalent tofalse for thoseroles.

Examples using themixed value of tri-state inputs are covered in the ARIA Authoring Practices Guide.

Characteristics:
Characteristic	Value
Used in Roles:	`checkbox` `menuitemcheckbox` `menuitemradio` `option` `radio` `switch`
Inherits into Roles:	`switch` `treeitem`
Value:	tristate

Values:
Value	Description
false	The element supports being checked but is not currently checked.
mixed	Indicates a mixed mode value for a tri-state checkbox or menuitemcheckbox.
true	The element is checked.
undefined (default)	The element does not support being checked.

`aria-colcount`property

Defines the total number of columns in atable,grid, ortreegrid. See relatedaria-colindex.

If all of the columns are present in theDOM, it is not necessary to set this attribute as theuser agent can automatically calculate the total number of columns. However, if only a portion of the columns is present in theDOM at a given moment, this attribute is needed to provide an explicit indication of the number of columns in the full table.

AuthorsMUST set the value of aria-colcount to an integer equal to the number of columns in the full table. If the total number of columns is unknown, authorsMUST set the value ofaria-colcount to-1 to indicate that the value should not be calculated by the user agent.

The following example shows a grid with 16 columns, of which columns 2, 3, 4, and 9 are displayed to the user.

Example 31

<divrole="grid"aria-colcount="16"><divrole="rowgroup"><divrole="row"><spanrole="columnheader"aria-colindex="2">First Name</span><spanrole="columnheader"aria-colindex="3">Last Name</span><spanrole="columnheader"aria-colindex="4">Company</span><spanrole="columnheader"aria-colindex="9">Phone</span></div></div><divrole="rowgroup"><divrole="row"><spanrole="gridcell"aria-colindex="2">Fred</span><spanrole="gridcell"aria-colindex="3">Jackson</span><spanrole="gridcell"aria-colindex="4">Acme, Inc.</span><spanrole="gridcell"aria-colindex="9">555-1234</span></div><divrole="row"><spanrole="gridcell"aria-colindex="2">Sara</span><spanrole="gridcell"aria-colindex="3">James</span><spanrole="gridcell"aria-colindex="4">Acme, Inc.</span><spanrole="gridcell"aria-colindex="9">555-1235</span></div>   …</div></div>

Characteristics:
Characteristic	Value
Used in Roles:	`table`
Inherits into Roles:	`grid` `treegrid`
Value:	integer

`aria-colindex`property

Defines anelement's column index or position with respect to the total number of columns within atable,grid, ortreegrid. See relatedaria-colindextext,aria-colcount, andaria-colspan.

If all of the columns are present in theDOM, it is not necessary to set this attribute as theuser agent can automatically calculate the column index of each cell orgridcell. However, if only a portion of the columns is present in theDOM 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.

AuthorsMUST set thevalue for aria-colindex to an integer greater than or equal to 1, greater than thearia-colindex 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, authorsMUST set the value ofaria-colindex to the start of the span.

If the set of columns which is present in theDOM is contiguous, and if there are no cells which span more than one row or column in that set, then authorsMAY place aria-colindex on each row, setting the value to the index of the first column of the set. Otherwise, authorsSHOULD placearia-colindex on all of theaccessibility children of each row.

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,aria-colindex can be placed on each row.

Example 32

<divrole="grid"aria-colcount="16"><divrole="rowgroup"><divrole="row"aria-colindex="2"><spanrole="columnheader">First Name</span><spanrole="columnheader">Last Name</span><spanrole="columnheader">Company</span><spanrole="columnheader">Address</span></div></div><divrole="rowgroup"><divrole="row"aria-colindex="2"><spanrole="gridcell">Fred</span><spanrole="gridcell">Jackson</span><spanrole="gridcell">Acme, Inc.</span><spanrole="gridcell">123 Broad St.</span></div><divrole="row"aria-colindex="2"><spanrole="gridcell">Sara</span><spanrole="gridcell">James</span><spanrole="gridcell">Acme, Inc.</span><spanrole="gridcell">123 Broad St.</span></div>   …</div></div>

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,aria-colindex needs to be placed on all of theaccessibility children of each row.

Example 33

<divrole="grid"aria-colcount="16"><divrole="rowgroup"><divrole="row"><spanrole="columnheader"aria-colindex="2">First Name</span><spanrole="columnheader"aria-colindex="3">Last Name</span><spanrole="columnheader"aria-colindex="4">Company</span><spanrole="columnheader"aria-colindex="5">Address</span></div></div><divrole="rowgroup"><divrole="row"><spanrole="gridcell"aria-colindex="2">Fred</span><spanrole="gridcell"aria-colindex="3">Jackson</span><spanrole="gridcell"aria-colindex="4"aria-rowspan="2">Acme, Inc.</span><spanrole="gridcell"aria-colindex="5"aria-rowspan="2">123 Broad St.</span></div><divrole="row"><spanrole="gridcell"aria-colindex="2">Sara</span><spanrole="gridcell"aria-colindex="3">James</span></div>   …</div></div>

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,aria-colindex needs to be placed on all of theaccessibility children of each row.

Example 34

<divrole="grid"aria-colcount="16"><divrole="rowgroup"><divrole="row"><spanrole="columnheader"aria-colindex="2">First Name</span><spanrole="columnheader"aria-colindex="3">Last Name</span><spanrole="columnheader"aria-colindex="4">Company</span><spanrole="columnheader"aria-colindex="9">Phone</span></div></div><divrole="rowgroup"><divrole="row"><spanrole="gridcell"aria-colindex="2">Fred</span><spanrole="gridcell"aria-colindex="3">Jackson</span><spanrole="gridcell"aria-colindex="4">Acme, Inc.</span><spanrole="gridcell"aria-colindex="9">555-1234</span></div><divrole="row"><spanrole="gridcell"aria-colindex="2">Sara</span><spanrole="gridcell"aria-colindex="3">James</span><spanrole="gridcell"aria-colindex="4">Acme, Inc.</span><spanrole="gridcell"aria-colindex="9">555-1235</span></div>   …</div></div>

Characteristics:
Characteristic	Value
Used in Roles:	`cell` `row`
Inherits into Roles:	`columnheader` `gridcell` `rowheader`
Value:	integer

`aria-colindextext`property

Defines a human readable text alternative ofaria-colindex. See relatedaria-rowindextext.

AuthorsSHOULD only usearia-colindextext when the provided or calculated value ofaria-colindex is not meaningful or does not reflect the displayed index, as is the case with spreadsheets and chess boards.

AuthorsSHOULD NOT usearia-colindextext as a replacement foraria-colindex 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.

Note

Unlikearia-colindex,aria-colindextext is not a supported property ofrow because user agents have no way to reliably calculatearia-colindextext for the purpose of exposing its value on thecell orgridcell.

Characteristics:
Characteristic	Value
Used in Roles:	`cell`
Inherits into Roles:	`columnheader` `rowheader`
Value:	string

`aria-colspan`property

Defines the number of columns spanned by a cell or gridcell within atable,grid, ortreegrid. See relatedaria-colindex andaria-rowspan.

Thisattribute 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, authorsSHOULD use the host language's attribute instead ofaria-colspan. Ifaria-colspan is used on an element for which the host language provides an equivalent attribute,user agentsMUST ignore the value ofaria-colspan and instead expose the value of the host language's attribute toassistive technologies.

AuthorsMUST set thevalue ofaria-colspan 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.

Characteristics:
Characteristic	Value
Used in Roles:	`cell`
Inherits into Roles:	`columnheader` `rowheader`
Value:	integer

`aria-controls`property

Identifies theelement (or elements) whose contents or presence are controlled by the focused element or composite widget. See relatedaria-details andaria-owns.

Thearia-controls property is for referencing elements that are modified by the user interacting with the currently focused element or composite widget. The presence ofaria-controls enablesassistive technologies to programmatically associate the currently focused element with the element or elements it controls. For instance, it can be used to inform users that by interacting with the controlling element they have revealed an element or elements that were previously in the hidden state. Or, by interacting with an element, they caused the selection or value of a controlled element to change.

Instance where anaria-controls association could be made:

Interacting with a text field or editable combobox results in the display of a listbox popup. Upon entering text, the associated listbox is filtered, or the selected option changes to match the text value entered by the user.
A tree view representing a table of contents where choosing a treeitem updates content of a neighboring document pane.
A series of checkboxes can each control what commodity prices are tracked live in a table or graph.
An interactive element reveals associated content when selected. For instance, selecting a tab control reveals its associated tab panel. Or checking a radio button reveals additional information or form controls related to the chosen radio button.
Radio buttons allow for filtering to a listing of search results.

Additionally, thearia-controls property supports multiple ID references. For example, a control can be used to highlight different instances of spelling errors. A user agentMAY convey to a user that there are a number of related controlled elements (the misspellings), allow the user to navigate to the controlled elements in sequence, or both.

Characteristics:
Characteristic	Value
Used in Roles:	All elements of the base markup
Value:	ID reference list

`aria-current`state

Indicates theelement that represents the current item within a container or set of related elements.

Thearia-currentattribute is a token type. Any value not included in the list of allowed valuesSHOULD be treated byassistive technologies as if the valuetrue had been provided. If the attribute is not present or its value is the empty string orundefined, the default value offalse applies and thearia-currentstateMUST NOT be exposed by user agents or assistive technologies.

Thearia-current 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:

Apage token used to indicate a page within a set of pages, where the element is visually styled to represent the current page.
Astep token used to indicate a step within a step-based process, where the element is visually styled to represent the current step.
Alocation token used to indicate the element that is visually styled as the current component, such as within a flow chart.
Adate token used to indicate the current date within a calendar or other date collection.
Atime token used to indicate the current time within a timetable or other time collection.

AuthorsSHOULD only mark one element in a set of elements as current witharia-current.

AuthorsSHOULD NOT use thearia-current attribute as a substitute foraria-selected in widgets wherearia-selected has the same meaning. For example, in atablist,aria-selected is used on atab to indicate the currently-displayedtabpanel.

Note

In some use cases for widgets that supportaria-selected, current and selected can have different meanings and can both be used within the same set of elements. For example,aria-current="page" can be used in a navigationtree to indicate which page is currently displayed, whilearia-selected="true" indicates which page will be displayed if the user activates thetreeitem. 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."

Characteristics:
Characteristic	Value
Used in Roles:	All elements of the base markup
Value:	token

Values:
Value	Description
page	Represents the current page within a set of pages.
step	Represents the current step within a process.
location	Represents the current location within an environment or context.
date	Represents the current date within a collection of dates.
time	Represents the current time within a set of times.
true	Represents the current item within a set.
false (default)	Does not represent the current item within a set.

`aria-describedby`property

Identifies theelement (or elements) that describes theobject. See relatedaria-labelledby andaria-description.

Thearia-labelledby attribute is similar toaria-describedby 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.

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.

Characteristics:
Characteristic	Value
Related Concepts:	`<label>` inHTML online help HTML table cell headers
Used in Roles:	All elements of the base markup
Value:	ID reference list

`aria-description`property

Defines a string value that describes or annotates the current element. See relatedaria-describedby.

Thearia-description attribute is similar toaria-label 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.

The purpose ofaria-description is the same as that ofaria-describedby. It provides the user with additional descriptive text for the object. The most commonaccessibility API mapping for a description is theaccessible description property. User agentsMUST give precedence toaria-describedby overaria-description when computing the accessible description property.

In cases where providing a visible description is not the desired user experience, authorsMAY set the accessible description of the element usingaria-description. However, if the description text is available in theDOM, authorsSHOULD NOT use aria-description, but should use one of the following instead:

AuthorsSHOULD usearia-describedby 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.
AuthorsSHOULD usearia-details 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. Usingaria-details 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.

Characteristics:
Characteristic	Value
Related Concepts:	`title` attribute inHTML
Used in Roles:	All elements of the base markup
Value:	string

`aria-details`property

Identifies theelement (or elements) that provide additional information related to theobject. See relatedaria-describedby.

Thearia-details property is for referencing elements that provide more detailed information than would normally be provided viaaria-describedby. The presence ofaria-details enablesassistive technologies to make users aware of the availability of extended information and navigate to it. AuthorsSHOULD ensure that elements referenced byaria-details are visible to all users.

Assistive technologies can use the role of elements referenced by thearia-details property to help users understand the types of information associated with the element. AuthorsMAY convey the type of details associated with an element as follows:

Comment:aria-details refers to an element with rolecomment.
Definition:aria-details is applied to an element with roleterm and refers to an element with roledefinition.
Caption:aria-details is applied to an element with rolefigure and refers to an element with rolecaption, or an element within acaption.
Footnote:aria-details refers to an element with roledoc-footnote. This role is defined in [DPUB-ARIA-1.0].
Endnote:aria-details refers to an element with roledoc-endnote. This role is defined in [DPUB-ARIA-1.0].
Description or general annotation:aria-details refers to an element with any other role.

Unlike elements referenced byaria-describedby, elements referenced byaria-details are not used in the Accessible Description Computation as defined in theAccessible Name and Description Computation [ACCNAME-1.2]. Thus, the content of elements referenced byaria-details are not flattened to a string when presented to assistive technology users. This makesaria-details particularly useful when converting the information to a string would cause a loss of information or make the extended information more difficult to understand.

Thearia-details 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 accessibilityAPI that does not support exposing multiple descriptive relations, the user agentSHOULD expose the relationship to the first element referenced byaria-details.

It is valid for an element to have botharia-details and a description specified with eitheraria-describedby oraria-description. If a user agent relies on an accessibility API that does not support exposing multiple descriptive relations, and if an element has botharia-details and aria-describedby, the user agentSHOULD expose thearia-details relation and the description string computed from thearia-describedby relationship.

A common use foraria-details 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.

Example 35

<!-- Provision of an extended description --><imgsrc="pythagorean.jpg"alt="Pythagorean Theorem"aria-details="det"><detailsid="det"><summary>Example</summary><p>    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.</p><p>    The following drawing illustrates an application of the Pythagorean Theorem when used to    construct a skateboard ramp.</p><objectdata="skatebd-ramp.svg"type="image/svg+xml"></object><p>    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.</p></details>

Alternatively,aria-details can refer to a link to a web page having the extended description, as shown in the following example.

Example 36

<!-- Provision of an extended description --><imgsrc="pythagorean.jpg"alt="Pythagorean Theorem"aria-details="det"><p>  See an<ahref="https://example.com/pt.html"id="det">Application of the Pythagorean Theorem</a>.</p>

Characteristics:
Characteristic	Value
Used in Roles:	All elements of the base markup
Value:	ID reference list

`aria-disabled`state

Indicates that theelement isperceivable but disabled, so it is not editable or otherwiseoperable. See relatedaria-hidden andaria-readonly.

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 thearia-disabled attribute, authorsSHOULD change the appearance (grayed out, etc.) to indicate that the item has been disabled.

Thestate of being disabled applies to the element with aria-disabled and allfocusable descendant elements of the element on which thearia-disabledattribute is applied.

Note

Whilearia-disabled and proper scripting can successfully disable an element with rolelink, fully disabling a host language equivalent can be problematic. Authors are advised not to usearia-disabled on elements that cannot be disabled through features of the host language alone.

Note: Usage on columnheader, rowheader and row

Whilearia-disabled is currently supported oncolumnheader,rowheader, androw, 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 agrid ortreegrid.

Note

This state is being deprecated as a global state inARIA 1.2. In future versions it will only be allowed on roles where it is specifically supported.

Characteristics:
Characteristic	Value
Used in Roles:	`application` `button` `composite` `gridcell` `group` `input` `link` `menuitem` `scrollbar` `separator` `tab`
Inherits into Roles:	`checkbox` `columnheader` `combobox` `grid` `listbox` `menu` `menubar` `menuitemcheckbox` `menuitemradio` `option` `radio` `radiogroup` `row` `rowheader` `searchbox` `select` `slider` `spinbutton` `switch` `tablist` `textbox` `toolbar` `tree` `treegrid` `treeitem`
Value:	true/false

Values:
Value	Description
false (default)	The element is enabled.
true	The element and all focusable descendants are disabled and its value cannot be changed by the user.

`aria-dropeffect`property

[Deprecated in ARIA 1.1] Indicates what functions can be performed when a dragged object is released on the drop target.

Note

Thearia-dropeffect property is expected to be replaced by a new feature in a future version of WAI-ARIA. Authors are therefore advised to treataria-dropeffect as deprecated.

Thisproperty 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.

More than one drop effect can be supported for a givenelement. Therefore, the value of thisattribute is a space-separated set of tokens indicating the possible effects, ornone if there is no supported operation. In addition to setting thearia-dropeffect attribute, authorsSHOULD show a visual indication of potential drop targets.

Characteristics:
Characteristic	Value
Used in Roles:	All elements of the base markup
Value:	token list

Values:
Value	Description
copy	A duplicate of the source object will be dropped into the target.
execute	A function supported by the drop target is executed, using the drag source as an input.
link	A reference or shortcut to the dragged object will be created in the target object.
move	The source object will be removed from its current location and dropped into the target.
none (default)	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.
popup	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.

`aria-errormessage`property

Identifies theelement (or elements) that provides an error message for anobject. See relatedaria-invalid andaria-describedby.

Thearia-errormessage attribute references other elements that contain error message text. AuthorsMUST usearia-invalid in conjunction witharia-errormessage.

When the value of an object is not valid,aria-invalid is set totrue, which indicates that the message contained by elements referenced byaria-errormessage is pertinent.

When an object is in a valid state, it has eitheraria-invalid set tofalse or it does not have thearia-invalid attribute. AuthorsMAY usearia-errormessage on an object that is currently valid, but only if the elements referenced byaria-errormessage arehidden from all users, because the message they contain is not pertinent.

Whenaria-errormessage is pertinent, authorsMUST ensure the content is nothidden from all users so users can navigate to and examine the error message. Similarly, whenaria-errormessage is not pertinent, authorsMUST either ensure the content ishidden from all users or remove thearia-errormessage attribute or its value.

User agentsMUST NOT exposearia-errormessage for an object with anaria-invalid value offalse.

AuthorsMAY call attention to a new error message with a live region by modifying inserting the error message into the contents of a existing, rendered element with alive region role, such asalert. A live region notification is appropriate when an error message is displayed to users after they have provided an invalid value.

A typical message describes what is wrong and informs users what is required. For example, an error message might be,Invalid time: the time must be between 9:00 AM and 5:00 PM. The following example code shows markup for an initial valid state and for a subsequent invalid state. Note the changes toaria-invalid on the text inputobject, and toaria-live on theelement containing the text of the error message:

Example 37

<!-- Initial valid state --><labelfor="startTime"> Please enter a start time for the meeting:</label><inputid="startTime"type="text"aria-errormessage="msgID"value=""aria-invalid="false"><spanid="msgID"role="alert"></span><!-- User has input an invalid value --><labelfor="startTime"> Please enter a start time for the meeting:</label><inputid="startTime"type="text"aria-errormessage="msgID"aria-invalid="true"value="11:30 PM" ><spanid="msgID"role="alert">Invalid time: the time must be between 9:00 AM and 5:00 PM</span>

Note

This example usesrole="alert" (which includes an implicit value ofaria-live="assertive") to indicate that assistive technologies will 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.

Note

This state has been deprecated as a global state inARIA 1.2. It is only supported on live region roles.

Characteristics:
Characteristic	Value
Used in Roles:	`application` `checkbox` `combobox` `gridcell` `listbox` `radiogroup` `slider` `spinbutton` `textbox` `tree`
Inherits into Roles:	`columnheader` `rowheader` `searchbox` `switch` `treegrid`
Value:	ID reference list

`aria-expanded`state

Indicates whether a related element is expanded (shown) or collapsed (hidden).

Thearia-expanded attribute is applied to afocusable, interactive element that toggles visibility of content of a different element. If the element witharia-expanded is also atreeitem in atree or arow in atreegrid, then the authorSHOULD ensure the element is also theaccessibility parent of the content it expands and collapses. Otherwise, the authorSHOULD ensure the element witharia-expanded is not theaccessibility parent of the content that is expanding or collapsing. Rather, identify that relationship between the interactive element and the element being controlled usingaria-controls.

For example,aria-expanded is applied to a parenttreeitem to indicate whether its child branch of the tree is shown.

Example 38

<ulrole="tree"><lirole="treeitem"aria-expanded="false"aria-selected="false"><span>Fruits</span><ulrole="group"hidden><lirole="treeitem"aria-selected="false">Apricot</li><lirole="treeitem"aria-selected="false">Mangosteen</li><lirole="treeitem"aria-selected="false">Yuzu</li></ul></li></ul>

Similarly, it can be applied to abutton to control the visibility of another element and its content on the current page.

Example 39

<button type="button" aria-controls="mangosteen" aria-expanded="false">Mangosteen</button><div id="mangosteen" hidden>  An edible fruit native to tropical lands surrounding the Indian Ocean.</div>

Characteristics:
Characteristic	Value
Used in Roles:	`application` `button` `checkbox` `combobox` `gridcell` `link` `menuitem` `row` `rowheader` `tab` `treeitem`
Inherits into Roles:	`columnheader` `menuitemcheckbox` `menuitemradio` `rowheader` `switch`
Value:	true/false/undefined

Values:
Value	Description
false	The grouping element this element controls or is the accessibility parent of is collapsed.
true	The grouping element this element controls or is the accessibility parent of is expanded.
undefined (default)	The element does not own or control a grouping element that is expandable.

`aria-flowto`property

Identifies the nextelement (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.

Whenaria-flowto has a single ID reference, it allowsassistive technologies to, at the user's request, forego normal document reading order and go to the targetedobject. However, whenaria-flowto is provided with multiple ID references, assistive technologiesSHOULD present the referenced elements as path choices.

In the case of one or more ID references,user agents or assistive technologiesSHOULD 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 thearia-flowtoattribute.Accessibility APIs can provide named pathrelationships.

Characteristics:
Characteristic	Value
Used in Roles:	All elements of the base markup
Value:	ID reference list

`aria-grabbed`state

[Deprecated inARIA 1.1] Indicates an element's "grabbed"state in a drag-and-drop operation.

Note

Thearia-grabbed state is expected to be replaced by a new feature in a future version ofWAI-ARIA. Authors are therefore advised to treataria-grabbed as deprecated.

Settingaria-grabbed totrue indicates that theelement has been selected for dragging. Settingaria-grabbed tofalse indicates that the element can be grabbed for a drag-and-drop operation, but is not currently grabbed. Ifaria-grabbed is unspecified or set toundefined (default), the element cannot be grabbed.

Whenaria-grabbed is set totrue, authorsSHOULD update thearia-dropeffectattribute of all potential drop targets. When an element is not grabbed (the value is set tofalse orundefined, or the attribute is removed), authorsSHOULD revert thearia-dropeffect attributes of the associated drop targets tonone.

Characteristics:
Characteristic	Value
Used in Roles:	All elements of the base markup
Value:	true/false/undefined

Values:
Value	Description
false	Indicates that the element supports being dragged.
true	Indicates that the element has been "grabbed" for dragging.
undefined (default)	Indicates that the element does not support being dragged.

`aria-haspopup`property

Indicates the availability and type of interactive popup element, such as menu or dialog, that can be triggered by anelement.

A popup element usually appears as a block of content that is on top of other content. AuthorsMUST ensure that the role of the element that serves as the container for the popup content ismenu,listbox,tree,grid, ordialog, and that the value ofaria-haspopup matches the role of the popup container.

For the popup element to be keyboard accessible, authorsSHOULD ensure that the element that can trigger the popup isfocusable, that there is a keyboard mechanism for opening the popup, and that the popup element manages focus of all its descendants as described inManaging Focus.

Thearia-haspopup property is a token type.User agentsMUST treat any value ofaria-haspopup that is not included in the list of allowed values, including the empty string, as if the valuefalse had been provided. To provide backward compatibility withARIA 1.0 content, user agentsMUST treat anaria-haspopup value oftrue as equivalent to a value ofmenu.

Assistive technologies and user agentsSHOULD NOT expose thearia-haspopup property if it has a value offalse.

Note

Atooltip is not considered to be a popup in this context.

Note

aria-haspopup 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 ofaria-haspopup is necessary, and avoid using it when it's not.

Note

This property is being deprecated as a global property inARIA 1.2. In future versions it will only be allowed on roles where it is specifically supported.

Characteristics:
Characteristic	Value
Related Concepts:	`aria-controls`
Used in Roles:	`application` `button` `combobox` `gridcell` `link` `menuitem` `slider` `tab` `textbox` `treeitem`
Inherits into Roles:	`columnheader` `menuitemcheckbox` `menuitemradio` `rowheader` `searchbox`
Value:	token

Values:
Value	Description
false (default)	Indicates the element does not have a popup.
true	Indicates the popup is a`menu`.
menu	Indicates the popup is a`menu`.
listbox	Indicates the popup is a`listbox`.
tree	Indicates the popup is a`tree`.
grid	Indicates the popup is a`grid`.
dialog	Indicates the popup is a`dialog`.

`aria-hidden`state

Indicates, when set totrue, that anelement and its entire subtree are hidden from assistive technology, regardless of whether it is visibly rendered.

User agents determine an element'shidden status based on whether it is rendered, and the rendering is usually controlled byCSS. For example, an element whosedisplay property is set tonone is not rendered. An element will be excluded from the accessibility tree if it or any of itsaccessibility ancestors arehidden or have theiraria-hidden attribute value set totrue.

AuthorsMUST NOT usearia-hidden to hide the root element or the host language element thatrepresents or contains the contents of the primary document in view. For instance, thehtml orbody elements in anHTML document. AuthorsMAY, with caution, usearia-hidden to hide visibly rendered content from assistive technologiesonly 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 usingaria-hidden to hide visible content from screen readersMUST ensure that identical or equivalent meaning and functionality is exposed to assistive technologies.

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.

Note

As of ARIA 1.3,aria-hidden="false" is now synonymous witharia-hidden="undefined".

Note

The original intent foraria-hidden="false" 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 thefalse value, the original intent is no longer supported.

To prevent authors erroneously hiding entire window-rendered documents only to those using assistive technology, user agentsMUST NOT expose the hidden state to assistive technologies if it is specified on the root element or the host language element thatrepresents or contains the contents of the primary document in view. For instance, thehtml orbody elements in anHTML document, or the rootsvg element if it is rendered as its own primary document in the browser window. If authors were to specifyaria-hidden="true" on the opening tag for an embedded document, for instance on amath orsvg embedded within an HTML document, user agents would still be expected to hide these elements from assistive technologies.

Characteristics:
Characteristic	Value
Used in Roles:	All elements of the base markup
Value:	true/false/undefined

Values:
Value	Description
false	The element'shidden state is determined by the user agent based on whether it is rendered. Synonym of`undefined`.
true	The element ishidden from the accessibilityAPI.
undefined (default)	The element'shidden state is determined by the user agent based on whether it is rendered.

`aria-invalid`state

Indicates the entered value does not conform to the format expected by the application. See relatedaria-errormessage.

If the value is computed to be invalid or out-of-range, the authorSHOULD set thisattribute totrue.user agentsSHOULD inform the user of the error. AuthorsSHOULD provide suggestions for corrections if they are known.

When the user attempts to submit data involving a field for whicharia-required istrue, authorsMAY use thearia-invalid attribute to signal there is an error. However, if the user has not attempted to submit the form, authorsSHOULD NOT set thearia-invalid attribute on requiredwidgets simply because the user has not yet entered data.

For future expansion, thearia-invalid attribute is a token type. Any value not recognized in the list of allowedvaluesMUST be treated by user agents as if the valuetrue had been provided. If the attribute is not present, or its value isfalse, or its value is the empty string, the default value offalse applies.

Note

This state is being deprecated as a global state inARIA 1.2. In future versions it will only be allowed on roles where it is specifically supported.

Characteristics:
Characteristic	Value
Used in Roles:	`application` `checkbox` `combobox` `gridcell` `listbox` `radiogroup` `slider` `spinbutton` `textbox` `tree`
Inherits into Roles:	`columnheader` `rowheader` `searchbox` `switch` `treegrid`
Value:	token

Values:
Value	Description
grammar	A grammatical error was detected.
false (default)	There are no detected errors in the value.
spelling	A spelling error was detected.
true	The value entered by the user has failed validation.

`aria-keyshortcuts`property

Defines keyboard shortcuts that an author has implemented to activate or give focus to an element.

The value of thearia-keyshortcuts 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.

AuthorsMUST specify modifier keys exactly according to the UI Events KeyboardEvent key Values 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.

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 UI Events KeyboardEvent key Values spec [uievents-key] - for example, "Enter", "Tab", "ArrowRight", "PageDown", "Escape", or "F1". The use of "Space" for the spacebar is an exception to the UI Events KeyboardEvent key Values spec [uievents-key] as the space or spacebar key is encoded as' ' and would be treated as a whitespace character.

AuthorsMUST ensure modifier keys come first when they are part of a keyboard shortcut. AuthorsMUST 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.

When specifying an alphabetic key, both the uppercase and lowercase variants are considered equivalent: "a" and "A" are the same.

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.

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 Shift key, so a keyboard shortcut defined as "Shift+2" would be ambiguous as this is how one would type the "2" character on a French keyboard.

If the character used is determined by a modifier key, the authorMUST 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.

If the key that needs to be specified is illegal in the host language or would cause a string to be terminated, authorsMUST use the string escaping sequence of the host language to specify it. For example, the single-quote character can be encoded as "'" inHTML.

Examples of valid keyboard shortcuts include:

"A"
"Shift+Space"
"Control+Alt+."
"Control+Shift+'"
"Alt+Shift+P Control+F"
"Meta+C Meta+Shift+C"

User agentsMUST NOT change keyboard behavior in response to thearia-keyshortcuts attribute. AuthorsMUST handle scripted keyboard events to processaria-keyshortcuts. Thearia-keyshortcuts attribute exposes the existence of these shortcuts so that assistive technologies can communicate this information to users.

AuthorsSHOULD provide a way to expose keyboard shortcuts so that all users can discover them, such as through the use of a tooltip. AuthorsMUST ensure thataria-keyshortcuts applied to disabled elements are unavailable.

AuthorsSHOULD 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 ARIA Authoring Practices Guide.

AuthorsSHOULD 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.

Characteristics:
Characteristic	Value
Related Concepts:	Keyboard shortcut
Used in Roles:	All elements of the base markup
Value:	string

`aria-label`property

Defines a string value that labels the current element. See relatedaria-labelledby.

The purpose ofaria-label is the same as that ofaria-labelledby. It provides the user with a recognizable name of the object. The most commonaccessibility API mapping for a label is theaccessible name property.

Most host languages provide an attribute that could be used to name the element (e.g., thetitle attribute inHTML), yet this could present a browser tooltip. In the cases where DOM content or a tooltip is undesirable, authorsMAY set the accessible name of the element using aria-label, if the element does notprohibit use of the attribute. If the label text is available in theDOM (i.e., typically visible text content), authorsSHOULD use aria-labelledby andSHOULD NOT usearia-label. There might be instances where the name of an element cannot be determined programmatically from theDOM, and there are cases where referencing DOM content is not the desired user experience. AuthorsMUST NOT specifyaria-label on an element which has an explicit or implicit WAI-ARIA role wherearia-label is prohibited. As required by theAccessible Name and Description Computation [ACCNAME-1.2], user agents give precedence toaria-labelledby overaria-label when computing the accessible name property.

Characteristics:
Characteristic	Value
Used in Roles:	All elements of the base markup except for the following roles:`caption`,`code`,`definition`,`deletion`,`emphasis`,`generic`,`insertion`,`mark`,`none`,`paragraph`,`strong`,`subscript`,`suggestion`,`superscript`,`term`,`time`
Value:	string

`aria-labelledby`property

Identifies theelement (or elements) that labels the current element. See relatedaria-label andaria-describedby.

The purpose ofaria-labelledby is the same as that ofaria-label. It provides the user with a recognizable name of the object. The most commonaccessibility API mapping for a label is theaccessible name property.

If the interface is such that it is not possible to have a visible label on the screen, authorsSHOULD usearia-label andSHOULD NOT usearia-labelledby. AuthorsMUST NOT specifyaria-labelledby on an element which has an explicit or implicitWAI-ARIA role wherearia-labelledby is prohibited. As required by theAccessible Name and Description Computation [ACCNAME-1.2], user agents give precedence toaria-labelledby overaria-label when computing the accessible name property.

Note

The expected spelling of this property inU.S. English is "labeledby." However, the accessibility API 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.

Characteristics:
Characteristic	Value
Related Concepts:	`<label>` inHTML
Used in Roles:	All elements of the base markup except for the following roles:`caption`,`code`,`definition`,`deletion`,`emphasis`,`generic`,`insertion`,`mark`,`none`,`paragraph`,`strong`,`subscript`,`suggestion`,`superscript`,`term`,`time`
Value:	ID reference list

`aria-level`property

Defines the hierarchical level of anelement within a structure.

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 foraria-level is an integer greater than or equal to 1.

Levels increase with depth. If theDOM ancestry does not accurately represent the level, authorsSHOULD explicitly define the aria-levelattribute.

This attribute is applied to elements that act as leaf nodes within the orientation of the set, for example, on elements with roletreeitem rather than elements with rolegroup. 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 forassistive technologies to use the attribute.

If theDOM ancestry accurately represents the level, the user agent 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 thearia-owns attribute. User agent support for automatic calculation of level might vary; authorsSHOULD test withuser agents and assistive technologies to determine whether this attribute is needed. If the author intends for the user agent to calculate the level, the authorSHOULD omit this attribute.

Note

In the case of atreegrid,aria-level is supported on elements with the rolerow, not elements with rolegridcell. At first glance, this might seem inconsistent with the application ofaria-level ontreeitem elements, but it is consistent in that therow acts as the leaf node within the vertical orientation of thegrid, whereas thegridcell is a leaf node within the horizontal orientation of eachrow. Level is not supported on sets of cells within rows, so thearia-level attribute is applied to the element with the rolerow.

Note

On elements with roleheading, values foraria-level above 6 can create difficulties for users. Also, at the time of this writing, most combinations of user agents and assistive technologies only supportaria-level integers 1-9 on headings.

Characteristics:
Characteristic	Value
Used in Roles:	`comment` `heading` `row` `treeitem`
Value:	integer

`aria-live`property

Indicates that anelement will be updated or modified, and defines the priority of updates theuser agents,assistive technologies, and user can expect from thelive region.

Thevalues of thisattribute are expressed in degrees of importance. When regions are specified aspolite, assistive technologies will notify users of updates but generally do not interrupt the current task, and updates take low priority. When regions are specified asassertive, assistive technologies will immediately notify the user of relevant modifications to the live region, and could potentially clear the speech queue of previous updates.

Priority levels (none,polite,assertive) act as an ordering mechanism for updates and serve as a recommendation 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 thearia-live attribute states otherwise.

Since different users have different needs, it is up to the user to tweak their assistive technologies' response to a live region. Assistive technologies might choose to implement increasing and decreasing levels of granularity so that the user can exercise control over queues and interruptions.

When theproperty is not set on anobject that needs to send updates, the priority level is the value of the nearest ancestor that sets thearia-live attribute.

Thearia-live attribute is the primary determination for the order of presentation of changes to live regions. Implementations will also consider the default level of priority in arole when thearia-live attribute is not set in the ancestor chain (e.g.,log changes arepolite by default). Modifications to live regions which areassertive will be presented immediately, followed bypolite 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)

When live regions are marked aspolite, assistive technologiesSHOULD 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 asassertive, assistive technologiesSHOULD immediately notify the user of modifications to the live region. Because an interruption might disorient users or cause them to not complete their current task, authorsSHOULD NOT use theassertive value unless the interruption is imperative.

Characteristics:
Characteristic	Value
Used in Roles:	All elements of the base markup
Value:	token

Values:
Value	Description
assertive	Indicates that updates to the region have the highest priority and should be presented the user immediately.
off (default)	Indicates that updates to the region should not be presented to the user unless the user is currently focused on that region.
polite	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.

`aria-modal`property

Indicates whether anelement is modal when displayed.

Thearia-modalattribute 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.

When a modal element is displayed, assistive technologiesSHOULD 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 technologiesSHOULD NOT limit navigation to the modal element.

When a modal element is displayed, authorsMUST 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, authorsSHOULD mark all other contents as inert (such as "inert subtrees" inHTML) if the ability to do so exists in the host language.

Characteristics:
Characteristic	Value
Used in Roles:	`window`
Inherits into Roles:	`alertdialog` `dialog`
Value:	true/false

Values:
Value	Description
false (default)	Element is not modal.
true	Element is modal.

`aria-multiline`property

Indicates whether a text box accepts multiple lines of input or only a single line.

Note

Characteristics:
Characteristic	Value
Used in Roles:	`textbox`
Inherits into Roles:	`searchbox`
Value:	true/false

Values:
Value	Description
false (default)	This is a single-line text box.
true	This is a multi-line text box.

`aria-multiselectable`property

Indicates that the user can select more than one item from the current selectable descendants.

AuthorsSHOULD ensure that selected descendants have thearia-selectedattribute set totrue, and selectable descendants that are not selected have thearia-selected attribute set tofalse. AuthorsSHOULD NOT use thearia-selected attribute on descendants that are not selectable.

Note

Lists and trees are examples of roles that might allow users to select more than one item at a time.

Characteristics:
Characteristic	Value
Used in Roles:	`grid` `listbox` `tablist` `tree`
Inherits into Roles:	`treegrid`
Value:	true/false

Values:
Value	Description
false (default)	Only one item can be selected.
true	More than one item in the widget can be selected at a time.

`aria-orientation`property

Indicates whether the element's orientation is horizontal, vertical, or unknown/ambiguous.

Note

InARIA 1.1, the default value for aria-orientation changed fromhorizontal toundefined. Implicit defaults are defined on some roles (e.g.,slider defaults to horizontal;scrollbar defaults to vertical) but remain undefined on roles where an expected default orientation is ambiguous (e.g.,radiogroup).

Characteristics:
Characteristic	Value
Used in Roles:	`scrollbar` `select` `separator` `slider` `tablist` `toolbar`
Inherits into Roles:	`listbox` `menu` `menubar` `radiogroup` `tree` `treegrid`
Value:	token

Values:
Value	Description
horizontal	The element is oriented horizontally.
undefined (default)	The element's orientation is unknown/ambiguous.
vertical	The element is oriented vertically.

`aria-owns`property

Identifies anelement (or elements) in order to define a visual, functional, or contextual parent/childrelationship betweenDOM elements where the DOM hierarchy cannot be used to represent the relationship. See related aria-controls.

The value of thearia-ownsattribute is a space-separated ID reference list that references one or more elements in the document by ID. The reason for addingaria-owns is to expose a parent/child contextual relationship toassistive technologies that is otherwise impossible to infer from theDOM.

If an element has both aria-owns andDOM children then the order of the child elements with respect to the parent/child relationship is the DOM children first, then the elements referenced in aria-owns. If the author intends that theDOM children are not first, then list the DOM children in aria-owns in the desired order. AuthorsSHOULD NOT usearia-owns as a replacement for theDOM hierarchy. If the relationship is represented in the DOM, do not use aria-owns.

AuthorsMUST ensure that an element's ID is not specified in more than one other element'saria-owns attribute at any time. In other words, an element can have only one explicit owner. AuthorsMUST NOT create circular references witharia-owns. In the case of authoring error witharia-owns, the user agentMAY ignore somearia-owns element references in order to build a consistent model of the content.

AuthorsMUST NOT specifyaria-owns on an element which hasPresentational Children.

aria-owns is resolved in the order it is encountered in theDOM. Every element referenced by aria-owns will determine itsexposure to the accessibility tree after its change in ownership is resolved. However:

User agentsMUST NOT resolvearia-owns when it is set on an element that has beenexcluded from the accessibility tree.
User agentsMUST NOT resolvearia-owns when it references an element that is, or has aDOM ancestor that is,hidden from all users.

In the following example, “(opens in a new window)” isincluded in the accessibility tree by virtue of its changed ownership.

Example 40

<ahref="https://www.w3.org/"target="_blank"aria-owns="new-window-warning">  World Wide Web Consortium</a><divaria-hidden="true"><spanid="new-window-warning"> (opens in a new window)</span></div>

In the following example, “(opens in a new window)” remainsexcluded from the accessibility tree since itsDOM ancestor is hidden from all users in host language terms.

Example 41

<ahref="https://www.w3.org/"aria-owns="new-window-warning">  World Wide Web Consortium</a><divhidden><spanid="new-window-warning"> (opens in a new window)</span></div>

In the following example,<div> and its text content remain exposed and unmovedin the accessibility tree since the would-be accessibility parent element witharia-owns ishidden from all users.

Example 42

<divhiddenaria-owns="instructions">  ...</div>...<divid="instructions">  Instructions go here...</div>

Characteristics:
Characteristic	Value
Used in Roles:	All elements of the base markup
Value:	ID reference list

`aria-placeholder`property

Defines 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.

AuthorsSHOULD NOT usearia-placeholder 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 relatedaria-labelledby andaria-label.

AuthorsSHOULD present this hint to the user by displaying the hint text at any time the control'svalue is the empty string. This includes cases where the control first receives focus, and when users remove a previously-entered value.

Note

As is the case with the relatedplaceholder attribute inHTML, 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.

Note

The following examples do not use the HTMLlabel element as it cannot be used to label HTML elements withcontenteditable.

The following example shows a searchbox in which the user has entered a value:

Example 43

<spanid="label">Birthday:</span><divcontenteditablerole="searchbox"aria-labelledby="label"aria-placeholder="MM-DD-YYYY">03-14-1879</div>

The following example shows the samesearchbox in which the user has not yet entered a value or has removed a previously-entered value:

Example 44

<spanid="label">Birthday:</span><divcontenteditablerole="searchbox"aria-labelledby="label"aria-placeholder="MM-DD-YYYY">MM-DD-YYYY</div>

Characteristics:
Characteristic	Value
Related Concepts:	`placeholder` attribute inHTML
Used in Roles:	`textbox`
Inherits into Roles:	`searchbox`
Value:	string

`aria-posinset`property

Defines anelement's number or position in the current set of listitems or treeitems. Not required if all elements in the set are present in theDOM. See related aria-setsize.

If all items in a set are present in the document structure, it is not necessary to set thisattribute, as theuser agent 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, thisproperty is needed to provide an explicit indication of an element's position.

The following example shows items 5 through 8 in a set of 16.

Example 45

<h2id="label_fruit"> Available Fruit</h2><ulrole="listbox"aria-labelledby="label_fruit"><lirole="option"aria-setsize="16"aria-posinset="5"> apples</li><lirole="option"aria-setsize="16"aria-posinset="6"> bananas</li><lirole="option"aria-setsize="16"aria-posinset="7"> cantaloupes</li><lirole="option"aria-setsize="16"aria-posinset="8"> dates</li></ul>

When specifyingaria-posinset, authorsMUST 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 specifyaria-posinset, authorsMUST also specify a value foraria-setsize.

When specifyingaria-posinset on amenuitem,menuitemcheckbox, ormenuitemradio, authorsSHOULD set the value ofaria-posinset with respect to the total number of items in themenu, excluding any separators.

Characteristics:
Characteristic	Value
Used in Roles:	`article` `comment` `listitem` `menuitem` `option` `radio` `row` `tab`
Inherits into Roles:	`comment` `menuitemcheckbox` `menuitemradio` `treeitem`
Value:	integer

`aria-pressed`state

Indicates the current "pressed"state of toggle buttons. See relatedaria-checked andaria-selected.

Toggle buttons require a full press-and-release cycle to change their value. Activating it once changes the value totrue, and activating it another time changes the value back tofalse. A value ofmixed means that the values of more than one item controlled by the button do not all share the same value. If theattribute is not present, the button is not a toggle button.

Thearia-pressed attribute is similar but not identical to thearia-checked attribute. Operating systems supportpressed on buttons andchecked on checkboxes.

Characteristics:
Characteristic	Value
Used in Roles:	`button`
Value:	tristate

Values:
Value	Description
false	The element supports being pressed but is not currently pressed.
mixed	Indicates a mixed mode value for a tri-state toggle button.
true	The element is pressed.
undefined (default)	The element does not support being pressed.

`aria-readonly`property

Indicates that theelement is not editable, but is otherwiseoperable. See relatedaria-disabled.

This means the user can read but not set the value of thewidget. Readonly elements are relevant to the user, and authorsSHOULD NOT restrict navigation to the element or itsfocusable 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.

Examples include:

A form element which represents a constant.
Row or column headers in a spreadsheet grid.
The result of a calculation such as a shopping cart total.

Characteristics:
Characteristic	Value
Related Concepts:	`readonly` attribute inHTML
Used in Roles:	`checkbox` `combobox` `grid` `gridcell` `listbox` `radiogroup` `slider` `spinbutton` `textbox`
Inherits into Roles:	`columnheader` `rowheader` `searchbox` `switch` `treegrid`
Value:	true/false

Values:
Value	Description
false (default)	The user can set the value of the element.
true	The user cannot change the value of the element.

`aria-relevant`property

Indicates what notifications the user agent will trigger when theaccessibility tree within a live region is modified. See relatedaria-atomic.

Theattribute is represented as a space-separated list of the followingvalues:additions,removals,text; or a single catch-all valueall.

This is used to describesemantically 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 meaningfulevent. In that casearia-relevant will be set toall. When thearia-relevant attribute is not provided, the default value,additions text, indicates that text modifications and node additions are relevant, but that node removals are irrelevant.

Note

aria-relevant 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.

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 defaultaria-relevant value, the text addition ('bar') would be spoken, but the text removal ('foo') would not.

aria-relevant is an optional attribute of live regions. This is a suggestion toassistive technologies, but assistive technologies are not required to present changes of all the relevant types.

Whenaria-relevant is not defined, an element's value is inherited from the nearest ancestor with a defined value. Although the value is atoken list, inherited values are not additive; the value provided on a descendant element completely overrides any inherited value from an ancestor element.

When text changes are denoted as relevant, user agentsMUST monitor any descendant node change that affects theAccessible Name and Description Computation [ACCNAME-1.2] of the live region as if the accessible name were determined from contents (nameFrom: contents). For example, a text change would be triggered if theHTMLalt 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 aria-labelledby) by an element contained in the live region.

Characteristics:
Characteristic	Value
Used in Roles:	All elements of the base markup
Value:	token list

Values:
Value	Description
additions	Element nodes are added to theaccessibility tree within the live region.
additions text (default)	Equivalent to the combination of values, "additions text".
all	Equivalent to the combination of all values, "additions removals text".
removals	Text content, a text alternative, or an element node within the live region is removed from theaccessibility tree.
text	Text content or a text alternative is added to any descendant in theaccessibility tree of the live region.

`aria-required`property

Indicates that user input is required on theelement before a form can be submitted.

For example, if the user needs to fill in an address field, the author will need to set the field'saria-required attribute totrue.

Note

The fact that the element is required is often presented visually (such as a sign or symbol after thewidget). Using thearia-requiredattribute allows the author to explicitly convey toassistive technologies that an element is required.

Unless an exactly equivalent native attribute is available, host languagesSHOULD allow authors to use thearia-required attribute on host language form elements that require input or selection by the user.

Characteristics:
Characteristic	Value
Related Concepts:	`required` attribute inHTML
Used in Roles:	`checkbox` `combobox` `gridcell` `listbox` `radiogroup` `spinbutton` `textbox` `tree`
Inherits into Roles:	`columnheader` `rowheader` `searchbox` `switch` `treegrid`
Value:	true/false

Values:
Value	Description
false (default)	User input is not necessary to submit the form.
true	Users need to provide input on an element before a form is submitted.

`aria-roledescription`property

Defines a human-readable, author-localized description for therole of anelement.

Thearia-roledescription property gives authors the ability to override how assistive technologies localize and express the name of a role. Thus inappropriately usingaria-roledescription might inhibit users' ability to understand or interact with an element. AuthorsSHOULD limit use ofaria-roledescription to clarifying the purpose of non-interactive container roles likegroup orregion, or to providing amore specific description of awidget.

When usingaria-roledescription, authorsSHOULD also ensure that:

The element to whicharia-roledescription is applied has a validWAI-ARIA role or has an implicit WAI-ARIA role semantic.
The value ofaria-roledescription is not empty or does not contain only whitespace characters.

Note

Depending on the assistive technology, user verbosity settings, or other factors, certain elements' role descriptions might not be conveyed. If specifyingaria-roledescription on such elements, then the custom role descriptions might also not be conveyed by these assistive technologies.

Additionally, authorsMUST NOT specifyaria-roledescription on an element which has an explicit or implicitWAI-ARIA role wherearia-roledescription is prohibited.

User agentsMUST NOT expose thearia-roledescription property if any of the following conditions exist:

The element to whicharia-roledescription is applied has an explicit or implicitWAI-ARIA role wherearia-roledescription is prohibited.
The value ofaria-roledescription is undefined or the empty string.

Assistive technologiesSHOULD use the value ofaria-roledescription when presenting the role of an element, butSHOULD NOT change other functionality based on the role of an element that has a value foraria-roledescription. For example, an assistive technology that provides functions for navigating to the nextregion orbuttonSHOULD allow those functions to navigate to regions and buttons that have anaria-roledescription.

The following two examples show the use ofaria-roledescription to indicate that a non-interactive container is a "slide" in a web-based presentation application.

Example 46

<divrole="article"aria-roledescription="slide"id="slide"aria-labelledby="slideheading"><h1id="slideheading">Quarterly Report</h1><!-- remaining slide contents --></div>

Example 47

<articlearia-roledescription="slide"id="slide"aria-labelledby="slideheading"><h1id="slideheading">Quarterly Report</h1><!-- remaining slide contents --></article>

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."

Characteristics:
Characteristic	Value
Used in Roles:	All elements of the base markup except for the following roles:`generic`
Value:	string

`aria-rowcount`property

Defines the total number of rows in atable,grid, ortreegrid. See relatedaria-rowindex.

If all of the rows are present in theDOM, it is not necessary to set this attribute as theuser agent can automatically calculate the total number of rows. However, if only a portion of the rows is present in theDOM at a given moment, this attribute is needed to provide an explicit indication of the number of rows in the full table.

AuthorsMUST set the value of aria-rowcount to an integer equal to the number of rows in the full table. If the total number of rows is unknown, authorsMUST set the value ofaria-rowcount to-1 to indicate that the value should not be calculated by the user agent.

The following example shows a grid with 2000 rows, of which the first row and rows 100 through 102 are displayed to the user.

Example 48

<divrole="grid"aria-rowcount="2000"><divrole="rowgroup"><divrole="row"aria-rowindex="1"><spanrole="columnheader">First Name</span><spanrole="columnheader">Last Name</span><spanrole="columnheader">Company</span><spanrole="columnheader">Phone</span></div></div><divrole="rowgroup"><divrole="row"aria-rowindex="100"><spanrole="gridcell">Fred</span><spanrole="gridcell">Jackson</span><spanrole="gridcell">Acme, Inc.</span><spanrole="gridcell">555-1234</span></div><divrole="row"aria-rowindex="101"><spanrole="gridcell">Sara</span><spanrole="gridcell">James</span><spanrole="gridcell">Acme, Inc.</span><spanrole="gridcell">555-1235</span></div><divrole="row"aria-rowindex="102"><spanrole="gridcell">Taylor</span><spanrole="gridcell">Johnson</span><spanrole="gridcell">Acme, Inc.</span><spanrole="gridcell">555-1236</span></div></div></div>

Characteristics:
Characteristic	Value
Used in Roles:	`table`
Inherits into Roles:	`grid` `treegrid`
Value:	integer

`aria-rowindex`property

Defines anelement's row index or position with respect to the total number of rows within atable,grid, ortreegrid. See relatedaria-rowindextext,aria-rowcount, andaria-rowspan.

If all of the rows are present in theDOM, it is not necessary to set this attribute as theuser agent can automatically calculate the index of each row. However, if only a portion of the rows is present in theDOM at a given moment, this attribute is needed to provide an explicit indication of each row's position with respect to the full table.

AuthorsMUST set thevalue for aria-rowindex to an integer greater than or equal to 1, greater than thearia-rowindex 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, authorsMUST set the value ofaria-rowindex to the start of the span.

AuthorsSHOULD placearia-rowindex on each row. AuthorsMAY also placearia-rowindex on all of theaccessibility children of each row.

The following example shows a grid with 2000 rows, of which the first row and rows 100 through 102 are displayed to the user.

Example 49

<divrole="grid"aria-rowcount="2000"><divrole="rowgroup"><divrole="row"aria-rowindex="1"><spanrole="columnheader">First Name</span><spanrole="columnheader">Last Name</span><spanrole="columnheader">Company</span><spanrole="columnheader">Phone</span></div></div><divrole="rowgroup"><divrole="row"aria-rowindex="100"><spanrole="gridcell">Fred</span><spanrole="gridcell">Jackson</span><spanrole="gridcell">Acme, Inc.</span><spanrole="gridcell">555-1234</span></div><divrole="row"aria-rowindex="101"><spanrole="gridcell">Sara</span><spanrole="gridcell">James</span><spanrole="gridcell">Acme, Inc.</span><spanrole="gridcell">555-1235</span></div><divrole="row"aria-rowindex="102"><spanrole="gridcell">Taylor</span><spanrole="gridcell">Johnson</span><spanrole="gridcell">Acme, Inc.</span><spanrole="gridcell">555-1236</span></div></div></div>

The following example shows the grid from the previous example witharia-rowindex also placed on all of theaccessibility children of each row.

Example 50

<divrole="grid"aria-rowcount="2000"><divrole="rowgroup"><divrole="row"aria-rowindex="1"><spanrole="columnheader"aria-rowindex="1">First Name</span><spanrole="columnheader"aria-rowindex="1">Last Name</span><spanrole="columnheader"aria-rowindex="1">Company</span><spanrole="columnheader"aria-rowindex="1">Phone</span></div></div><divrole="rowgroup"><divrole="row"aria-rowindex="100"><spanrole="gridcell"aria-rowindex="100">Fred</span><spanrole="gridcell"aria-rowindex="100">Jackson</span><spanrole="gridcell"aria-rowindex="100">Acme, Inc.</span><spanrole="gridcell"aria-rowindex="100">555-1234</span></div><divrole="row"aria-rowindex="101"><spanrole="gridcell"aria-rowindex="101">Sara</span><spanrole="gridcell"aria-rowindex="101">James</span><spanrole="gridcell"aria-rowindex="101">Acme, Inc.</span><spanrole="gridcell"aria-rowindex="101">555-1235</span></div><divrole="row"aria-rowindex="102"><spanrole="gridcell"aria-rowindex="102">Taylor</span><spanrole="gridcell"aria-rowindex="102">Johnson</span><spanrole="gridcell"aria-rowindex="102">Acme, Inc.</span><spanrole="gridcell"aria-rowindex="102">555-1236</span></div></div></div>

Characteristics:
Characteristic	Value
Used in Roles:	`cell` `row`
Inherits into Roles:	`columnheader` `gridcell` `rowheader`
Value:	integer

`aria-rowindextext`property

Defines a human readable text alternative ofaria-rowindex. See relatedaria-colindextext.

AuthorsSHOULD only usearia-rowindextext when the provided or calculated value ofaria-rowindex is not meaningful or does not reflect the displayed index, as can be seen in the game Battleship.

AuthorsSHOULD NOT usearia-rowindextext as a replacement foraria-rowindex 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.

AuthorsSHOULD placearia-rowindextext on each row. AuthorsMAY also placearia-rowindextext on all of theaccessibility children of each row.

Characteristics:
Characteristic	Value
Used in Roles:	`cell` `row`
Inherits into Roles:	`columnheader` `gridcell` `rowheader`
Value:	string

`aria-rowspan`property

Defines the number of rows spanned by a cell or gridcell within atable,grid, ortreegrid. See relatedaria-rowindex andaria-colspan.

Thisattribute 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, authorsSHOULD use the host language's attribute instead ofaria-rowspan. Ifaria-rowspan is used on an element for which the host language provides an equivalent attribute,user agentsMUST ignore the value ofaria-rowspan and instead expose the value of the host language's attribute toassistive technologies.

AuthorsMUST set thevalue ofaria-rowspan 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.

Characteristics:
Characteristic	Value
Used in Roles:	`cell`
Inherits into Roles:	`columnheader` `rowheader`
Value:	integer

`aria-selected`state

Indicates the current "selected"state of variouswidgets. See relatedaria-checked andaria-pressed.

Thisattribute is used to indicate which elements within single-selection and multiple-selectioncomposite widgets are selected.

Theoption,tab, andtreeitem roles permit user agents to provide an implicit value foraria-selected when specified conditions are met. User agentsMUST NOT provide an implicit value for aria-selected in any other circumstance.

Characteristics:
Characteristic	Value
Used in Roles:	`gridcell` `option` `row` `tab`
Inherits into Roles:	`columnheader` `rowheader` `treeitem`
Value:	true/false/undefined

Values:
Value	Description
false	The selectable element is not selected.
true	The selectable element is selected.
undefined (default)	The element is not selectable.

`aria-setsize`property

Defines the number of items in the current set of listitems or treeitems. Not required if all elements in the set are present in theDOM. See related aria-posinset.

Thisproperty 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," theassistive technologies would use X equal to thearia-posinsetattribute and Y equal to thearia-setsize attribute.

If all items up to the current item in a set are present in the document structure, it is not necessary to set thisattribute, as theuser agent 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 authorMUST set thisattributeto provide an explicit indication of an element's position.

When specifyingaria-setsize, authorsMUST set the value to an integer equal to the number of items in the set. If the total number of items is unknown, authorsSHOULD set the value ofaria-setsize to-1.

When specifyingaria-setsize on amenuitem,menuitemcheckbox, ormenuitemradio, authorsSHOULD set the value ofaria-setsize based on the total number of items in themenu, excluding any separators.

The following example shows items 5 through 8 in a set of 16.

Example 51

<h2id="label_fruit"> Available Fruit</h2><ulrole="listbox"aria-labelledby="label_fruit"><lirole="option"aria-setsize="16"aria-posinset="5"> apples</li><lirole="option"aria-setsize="16"aria-posinset="6"> bananas</li><lirole="option"aria-setsize="16"aria-posinset="7"> cantaloupes</li><lirole="option"aria-setsize="16"aria-posinset="8"> dates</li></ul>

The following example shows items 5 through 8 in a set whose total size is unknown.

Example 52

<h2id="label_fruit"> Available Fruit</h2><ulrole="listbox"aria-labelledby="label_fruit"><lirole="option"aria-setsize="-1"aria-posinset="5"> apples</li><lirole="option"aria-setsize="-1"aria-posinset="6"> bananas</li><lirole="option"aria-setsize="-1"aria-posinset="7"> cantaloupes</li><lirole="option"aria-setsize="-1"aria-posinset="8"> dates</li></ul>

Characteristics:
Characteristic	Value
Used in Roles:	`article` `comment` `listitem` `menuitem` `option` `radio` `row` `tab`
Inherits into Roles:	`comment` `menuitemcheckbox` `menuitemradio` `treeitem`
Value:	integer

`aria-sort`property

Indicates if items in a table or grid are sorted in ascending or descending order.

AuthorsSHOULD only apply thisproperty to table headers or grid headers. If the property is not provided, there is no defined sort order. For each table or grid, authorsSHOULD applyaria-sort to only one header at a time.

Characteristics:
Characteristic	Value
Used in Roles:	`columnheader` `rowheader`
Value:	token

Values:
Value	Description
ascending	Items are sorted in ascending order.
descending	Items are sorted in descending order.
none (default)	There is no defined sort applied.
other	A sort algorithm other than ascending or descending has been applied.

`aria-valuemax`property

Defines the maximum allowed value for a rangewidget.

AuthorsMUST ensure the value ofaria-valuemax is greater than or equal to the value ofaria-valuemin. If thearia-valuenow has a known maximum and minimum, the authorSHOULD provide properties foraria-valuemax andaria-valuemin.

Note

A range widget starts with a given value, which can be increased until reaching the maximum value, defined by thisproperty. Declaring the minimum and maximumvalues allows assistive technology to convey the size of the range to users.

Characteristics:
Characteristic	Value
Related Concepts:	`<input type="range">` element`max` attribute inHTML
Used in Roles:	`range` `scrollbar` `separator` `slider` `spinbutton`
Inherits into Roles:	`meter` `progressbar` `scrollbar` `slider` `spinbutton`
Value:	number

`aria-valuemin`property

Defines the minimum allowed value for a rangewidget.

AuthorsMUST ensure the value ofaria-valuemin is less than or equal to the value ofaria-valuemax. If thearia-valuenow has a known maximum and minimum, the authorSHOULD provide properties foraria-valuemax andaria-valuemin.

Note

A range widget starts with a given value, which can be decreased until reaching the minimum value, defined by thisproperty. Declaring the minimum and maximumvalues allows assistive technology to convey the size of the range to users.

Characteristics:
Characteristic	Value
Related Concepts:	`<input type="range">` element`min` attribute inHTML
Used in Roles:	`range` `scrollbar` `separator` `slider` `spinbutton`
Inherits into Roles:	`meter` `progressbar` `scrollbar` `slider` `spinbutton`
Value:	number

`aria-valuenow`property

Defines the current value for a rangewidget. See relatedaria-valuetext.

This property is used, for example, on a range widget such as a slider or progress bar.

If the current value is not known (for example, an indeterminate progress bar), the authorSHOULD NOT set thearia-valuenowattribute. If thearia-valuenow attribute is absent, no information is implied about the current value. If thearia-valuenow has a known maximum and minimum, the authorSHOULD provide properties foraria-valuemax andaria-valuemin.

The value ofaria-valuenow is a decimal number. If the range is a set of numeric values, thenaria-valuenow is one of those values. For example, if the range is [0, 1], a validaria-valuenow is 0.5. A value outside the range, such as -2.5 or 1.1, is invalid.

Forprogressbar elements andscrollbar elements, assistive technologiesSHOULD render the value to users as a percent, calculated as a position on the range fromaria-valuemin toaria-valuemax if both are defined, otherwise the actual value with a percent indicator. For elements with roleslider andspinbutton, assistive technologiesSHOULD render the actual value to users.

When the rendered value cannot be accurately represented as a number, authorsSHOULD use thearia-valuetext attribute in conjunction witharia-valuenow to provide a user-friendly representation of the range's current value. For example, a slider might have rendered values ofsmall,medium, andlarge. In this case, the values ofaria-valuetext would be one of the strings:small,medium, orlarge.

Note

Ifaria-valuetext is specified, assistive technologies render that instead of the value ofaria-valuenow.

Characteristics:
Characteristic	Value
Related Concepts:	`<input type="range">` element`value` attribute inHTML
Used in Roles:	`meter` `range` `scrollbar` `separator` `slider` `spinbutton`
Inherits into Roles:	`meter` `progressbar` `scrollbar` `slider` `spinbutton`
Value:	number

`aria-valuetext`property

Defines the human readable text alternative ofaria-valuenow for a rangewidget.

This property is used, for example, on a range widget such as a slider or progress bar.

If thearia-valuetext attribute is set, authorsSHOULD also set thearia-valuenow attribute, unless that value is unknown (for example, on an indeterminateprogressbar).

AuthorsSHOULD only set thearia-valuetext attribute when the rendered value cannot be meaningfully represented as a number. For example, a slider might have rendered values ofsmall,medium, andlarge. In this case, the values ofaria-valuenow could range from 1 through 3, which indicate the position of each value in the value space, but thearia-valuetext would be one of the strings:small,medium, orlarge. If thearia-valuetext attribute is absent, theassistive technologies will rely solely on thearia-valuenow attribute for the current value.

Ifaria-valuetext is specified, assistive technologiesSHOULD render that value instead of the value ofaria-valuenow.

Characteristics:
Characteristic	Value
Used in Roles:	`range` `separator` `spinbutton`
Inherits into Roles:	`meter` `progressbar` `scrollbar` `slider` `spinbutton`
Value:	string

WAI-ARIA role	Required Attribute	Fallback value
`checkbox`	`aria-checked`	`false`
`combobox`	`aria-expanded`	`false`
`heading`	`aria-level`	`2`
`menuitemcheckbox`	`aria-checked`	`false`
`menuitemradio`	`aria-checked`	`false`
`radio`	`aria-checked`	`false`
`scrollbar`	`aria-valuenow`	If missing or not anumber,`(aria-valuemax - aria-valuemin) / 2`. If present but less than`aria-valuemin`, the value of`aria-valuemin`. If present but greater than`aria-valuemax`, the value of`aria-valuemax`.
`separator` (if focusable)	`aria-valuenow`	If missing or not anumber,`(aria-valuemax - aria-valuemin) / 2`. If present but less than`aria-valuemin`, the value of`aria-valuemin`. If present but greater than`aria-valuemax`, the value of`aria-valuemax`.
`slider`	`aria-valuenow`	If missing or not anumber,`(aria-valuemax - aria-valuemin) / 2`. If present but less than`aria-valuemin`, the value of`aria-valuemin`. If present but greater than`aria-valuemax`, the value of`aria-valuemax`.
`switch`	`aria-checked`	`false`
`meter`	`aria-valuenow`	A value matching the implicit or explicitly set`aria-valuemin`.

IDL Attribute	ReflectedARIA Content Attribute	Value type (non-normative)
`role`	role	token list
`ariaActiveDescendantElement`	`aria-activedescendant`	ID reference list
`ariaAtomic`	`aria-atomic`	true/false
`ariaAutoComplete`	`aria-autocomplete`	token
`ariaBrailleLabel`	`aria-braillelabel`	string
`ariaBrailleRoleDescription`	`aria-brailleroledescription`	string
`ariaBusy`	`aria-busy`	true/false
`ariaChecked`	`aria-checked`	tristate
`ariaColCount`	`aria-colcount`	integer
`ariaColIndex`	`aria-colindex`	integer
`ariaColIndexText`	`aria-colindextext`	string
`ariaColSpan`	`aria-colspan`	integer
`ariaControlsElements`	`aria-controls`	ID reference list
`ariaCurrent`	`aria-current`	token
`ariaDescribedByElements`	`aria-describedby`	ID reference list
`ariaDescription`	`aria-description`	string
`ariaDetailsElements`	`aria-details`	ID reference list
`ariaDisabled`	`aria-disabled`	true/false
`ariaErrorMessageElements`	`aria-errormessage`	ID reference list
`ariaExpanded`	`aria-expanded`	true/false/undefined
`ariaFlowToElements`	`aria-flowto`	ID reference list
`ariaHasPopup`	`aria-haspopup`	token
`ariaHidden`	`aria-hidden`	true/false/undefined
`ariaInvalid`	`aria-invalid`	token
`ariaKeyShortcuts`	`aria-keyshortcuts`	string
`ariaLabel`	`aria-label`	string
`ariaLabelledByElements`	`aria-labelledby`	ID reference list
`ariaLevel`	`aria-level`	integer
`ariaLive`	`aria-live`	token
`ariaModal`	`aria-modal`	true/false
`ariaMultiLine`	`aria-multiline`	true/false
`ariaMultiSelectable`	`aria-multiselectable`	true/false
`ariaOrientation`	`aria-orientation`	token
`ariaOwnsElements`	`aria-owns`	ID reference list
`ariaPlaceholder`	`aria-placeholder`	string
`ariaPosInSet`	`aria-posinset`	integer
`ariaPressed`	`aria-pressed`	tristate
`ariaReadOnly`	`aria-readonly`	true/false
`ariaRelevant`	`aria-relevant`	token list
`ariaRequired`	`aria-required`	true/false
`ariaRoleDescription`	`aria-roledescription`	string
`ariaRowCount`	`aria-rowcount`	integer
`ariaRowIndex`	`aria-rowindex`	integer
`ariaRowIndexText`	`aria-rowindextext`	string
`ariaRowSpan`	`aria-rowspan`	integer
`ariaSelected`	`aria-selected`	true/false/undefined
`ariaSetSize`	`aria-setsize`	integer
`ariaSort`	`aria-sort`	token
`ariaValueMax`	`aria-valuemax`	number
`ariaValueMin`	`aria-valuemin`	number
`ariaValueNow`	`aria-valuenow`	number
`ariaValueText`	`aria-valuetext`	string

WAI-ARIA type	HTML	XML Schema
true/false	Keyword and enumerated attributes with allowed values of "true" and "false"	boolean
true/false/undefined	Keyword and enumerated attributes with allowed values of`true`,`false`, and`undefined`	NMTOKEN with anenumeration constraint allowing values of`true`,`false`, and`undefined`
tristate	Keyword and enumerated attributes with allowed values of "true", "false", and "mixed"	NMTOKEN with anenumeration constraint allowing values of "true", "false", and "mixed"
number	Floating-point numbers	decimal
integer	Non-negative integer	integer
token	Keyword and enumerated attributes	NMTOKEN with anenumeration constraint allowing values listed in the state or property definition
token list	Space-separated tokens	NMTOKENS with anenumeration constraint allowing values listed in the state or property definition
ID reference	The value of a definedid attribute on another element	IDREF
ID reference list	The value of one or more definedid attributes on other element(s), represented asSpace-separated tokens	IDREFS
string	No value constraints	string

Movatterモバイル変換

Accessible Rich Internet Applications (WAI-ARIA) 1.3

Abstract

Status of This Document

1.Introduction

1.1Rich Internet Application Accessibility

1.3User Agent Support

1.5.1Authoring Tools

1.5.2Testing Practices and Tools

3.Conformance

3.1Non-interference with the Host Language

3.5Deprecated Requirements

4.UsingWAI-ARIA

4.1WAI-ARIA Roles

4.2WAI-ARIA States and Properties

4.3Managing Focus and Supporting Keyboard Navigation

5.The Roles Model

5.1.2Subclass Roles

5.1.3Related Concepts

5.1.4Base Concept

5.2Characteristics of Roles

5.2.3Supported States and Properties

5.2.4Inherited States and Properties

5.2.6Allowed Accessibility Child Roles

5.2.7Required Accessibility Parent Role

5.2.8Name From

5.2.8.1Roles Supporting Name from Author

5.2.8.2Roles Supporting Name from Content

5.2.8.3Roles which cannot be named (Name prohibited)

5.2.9Children Presentational

5.2.10Implicit Value for Role

5.3Categorization of Roles

5.3.1Abstract Roles

5.3.2Widget Roles

5.3.3Document Structure Roles

5.3.4Landmark Roles

5.3.5Live Region Roles

5.3.6Window Roles

5.4Definition of Roles

alertrole

alertdialogrole

applicationrole

articlerole

bannerrole

blockquoterole

buttonrole

captionrole

cellrole

checkboxrole

comboboxrole

commandabstract role

commentrole

complementaryrole

compositeabstract role

contentinforole

definitionrole

deletionrole

dialogrole

directoryrole

documentrole

emphasisrole

feedrole

figurerole

formrole

genericrole

gridrole

gridcellrole

grouprole

headingrole

imagerole

imgrole

inputabstract role

insertionrole

landmarkabstract role

linkrole

listrole

listboxrole

listitemrole

logrole

mainrole

`alert`role

`alertdialog`role

`application`role

`article`role

`banner`role

`blockquote`role

`button`role

`caption`role

`cell`role

`checkbox`role

`combobox`role

`command`abstract role

`comment`role

`complementary`role

`composite`abstract role

`contentinfo`role

`definition`role

`deletion`role

`dialog`role

`directory`role

`document`role

`emphasis`role

`feed`role

`figure`role

`form`role

`generic`role

`grid`role

`gridcell`role

`group`role

`heading`role

`image`role

`img`role

`input`abstract role

`insertion`role

`landmark`abstract role

`link`role

`list`role

`listbox`role

`listitem`role

`log`role

`main`role

`mark`role

`marquee`role

`math`role

PlainHTML or Polyfill DOM Result of the MathML Quadratic Formula

`menu`role

`menubar`role

`menuitem`role

`menuitemcheckbox`role

`menuitemradio`role

`meter`role

`none`role

`note`role

`option`role

`paragraph`role

`presentation`role

`radio`role

`radiogroup`role

`range`abstract role

`region`role

`roletype`abstract role

`row`role

`rowgroup`role

`scrollbar`role

`search`role

`searchbox`role

`section`abstract role

`sectionfooter`role

`sectionhead`abstract role

`sectionheader`role

`select`abstract role

`separator`role

`slider`role

`spinbutton`role

`status`role

`strong`role

`structure`abstract role

`subscript`role

`suggestion`role

`superscript`role