Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://w3c.github.io/html-aam/ below:

HTML Accessibility API Mappings 1.0

HTML Accessibility API Mappings (HTML-AAM) defines how user agents map HTML [HTML] elements and attributes to platform accessibility application programming interfaces (APIs). It leverages and extends the Core Accessibility API Mappings 1.2 and the Accessible Name and Description Computation 1.2 for use with the HTML host language. Documenting these mappings promotes interoperable exposure of roles, states, properties, and events implemented by accessibility APIs and helps to ensure that this information appears in a manner consistent with author intent.

The HTML-AAM is part of the WAI-ARIA suite described in the WAI-ARIA Overview.

This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C standards and drafts index at https://www.w3.org/TR/.

Note

This document is subject to change without notice.

This document was initially developed by and with the approval of the HTML Accessibility Taskforce, a joint task force of the Protocols and Formats Working Group and the HTML Working Group. Work continued with the successor groups Accessible Rich Internet Applications Working Group and the Web Applications Working Group. This document is now maintained solely by the Accessible Rich Internet Applications Working Group.

This document was published by the Accessible Rich Internet Applications Working Group as an Editor's Draft.

Publication as an Editor's Draft does not imply endorsement by W3C and its Members.

This is a draft document and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

This document is governed by the 03 November 2023 W3C Process Document.

1. Abstract
2. Status of This Document
3. 1. Introduction
   1. 1.1 Accessibility APIs
4. 2. Conformance
   1. 2.1 Deprecated
5. 3. Mapping HTML to Accessibility APIs
   1. 3.1 General Rules for Exposing WAI-ARIA Semantics
   2. 3.2 Conflicts Between Native Markup Semantics and WAI-ARIA
   3. 3.3 Exposing HTML Features That Do Not Directly Map to Accessibility APIs
   4. 3.4 Exposing HTML Features That Require a Minimum Role
   5. 3.5 HTML Element Role Mappings
   6. 3.6 HTML Attribute State and Property Mappings
6. 4. Accessible Name and Description Computation
   1. 4.1 Accessible Name Computations By HTML Element
   2. 4.2 Accessible Description Computation
7. 5. Privacy considerations
8. 6. Security considerations
9. A. Appendices
   1. A.1 Change Log
   2. A.2 Acknowledgments
10. B. References
    1. B.1 Normative references
    2. B.2 Informative references

This section is non-normative.

This specification defines how HTML user agents respond to and expose role, state and property information provided for Web content. Unless indicated otherwise, an HTML element or attribute with default Accessible Rich Internet Applications (WAI-ARIA) 1.2 semantics must be exposed to the platform accessibility APIs according to the relevant WAI-ARIA mappings defined in the Core Accessibility API Mappings 1.2 specification.

In some cases, often due to features of the HTML host language or the accessibility API in question, an element or attribute's mapping differs from the corresponding ARIA mappings specified in the [core-aam-1.2]. Where an HTML element or attribute does not have any default WAI-ARIA semantics, the applicable mapping for each platform accessibility API is defined by this specification.

This document also adapts the Accessible Name and Description Computation 1.2 specification for deriving the accessible names and accessible descriptions of [HTML] elements, and provides accessible implementation examples for specific HTML elements and features.

Users often access HTML content using assistive technologies that rely on platform accessibility API to obtain and interact with information from the page. This document is part of the following suite of accessibility API mapping specifications for content rendered by user agents:

• Accessible Name and Description Computation 1.2
• Core Accessibility API Mappings 1.2
• HTML Accessibility API Mappings 1.0 (this specification)
• MathML Accessibility API Mappings 1.0
• SVG Accessibility API Mappings

Accessibility APIs covered by this document are:

• MSAA with IAccessible2 1.3 [IAccessible2]
• User Interface Automation [UI-AUTOMATION]
• ATK - Accessibility Toolkit [ATK] and Assistive Technology Service Provider Interface [AT-SPI], referred to hereafter as "ATK/AT-SPI"
• macOS Accessibility Protocol [AXAPI]

If user agent developers need to expose information using other accessibility APIs, it is recommended that they work closely with the developer of the platform where the API runs, and assistive technology developers on that platform.

For more information regarding accessibility APIs, refer to section 1.1 Accessibility APIs of the Core Accessibility API Mappings 1.2.

As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

The key words MAY, MUST, MUST NOT, and SHOULD in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

The classification of a section as normative or non-normative applies to the entire section and all sub-sections of that section.

Normative sections provide requirements that authors, user agents, and assistive technologies MUST follow for an implementation to conform to this specification.

Non-normative sections provide information useful to understanding the specification. Such sections may contain examples of recommended practice, but it is not required to follow such recommendations in order to conform to this specification.

There are currently no deprecated requirements.

Note

WAI-ARIA support was first introduced to HTML in [HTML5].

Where an HTML element or attribute has default WAI-ARIA semantics, it MUST be exposed to the platform accessibility APIs in a way that conforms to General rules for exposing WAI-ARIA semantics in the Core Accessibility API Mappings 1.2.

Where the host language is [HTML], user agents MUST conform to Conflicts between native markup semantics and WAI-ARIA in the Core Accessibility API Mappings 1.2.

HTML can include features that are not supported by accessibility APIs at the time of publication. There is not a one to one relationship between all features and platform accessibility APIs. When HTML roles, states and properties do not directly map to an accessibility API, and there is a method in the API to expose a text string, user agents MUST expose the undefined role, states and properties via that method.

For HTML elements or attributes with default WAI-ARIA semantics, user agents MUST conform to Exposing attributes that do not directly map to accessibility API properties in the [core-aam-1.2].

A minimum role is the equivalent WAI-ARIA role an element will map to if the element does not have a more specific implicit role or platform role mappings, e.g., a non-generic role. This can help ensure that users of assistive technologies get the best possible experience for commonly-used and valid HTML markup where otherwise a role would not be exposed.

A minimum role is provided when all of the following conditions are true:

• the author has not specified a valid explicit WAI-ARIA role to the element, or the specified role is either none, presentation, or generic;
• the element either has no implicit WAI-ARIA role or platform role mappings, or it has an implicit generic or none computed role;
• and the author has specified attributes which require a minimum role mapping for the element.

The HTML Attribute State and Property Mappings section identifies the specific global attributes which would require an element map to a minimum role.

When these conditions are met, the browser MUST expose an object using the mappings defined in CORE-AAM for the specified minimum role. If the element has multiple attributes specified which require a minimum role be returned as the computed role for the element, prioritize the more specific role in the ARIA taxonomy.

• HTML elements with implicit WAI-ARIA role semantics MUST be mapped to platform accessibility APIs according to the identified WAI-ARIA role mapping as defined in the [core-aam-1.2] specification.
• "Not mapped" means the element does not need to be exposed via an accessibility API. This is usually because the element is not displayed as part of the user interface. However, authors can force some of these elements to be rendered. For instance, by overriding user agent styles to render elements that would have been otherwise set to display: none. In these cases, the user agent SHOULD map such elements to the role of generic, unless other HTML features have been specified which would require a more specific minimum role to be exposed.
• Where an element is indicated as having "No corresponding (WAI-ARIA) role", or is mapped to the generic role, user agents MUST NOT expose the aria-roledescription property value in the accessibility tree unless the element has an explicit, conforming role attribute value which [WAI-ARIA-1.2] does not prohibit the use of aria-roledescription.
• Some HTML elements expose implicit WAI-ARIA roles depending on whether they have been provided an accessible name. How an element participates in the computation of its own or another element's accessible name and/or accessible description is described in the Accessible Name and Description Computation section of this document.

• When HTML elements do not have an exact or equivalent mapping to a valid, non-abstract WAI-ARIA role, a unique computedrole string has been specified to serve as the return value for interoperability testing purposes. For instance, the video element MAY be exposed with a computedrole of "html-video". Authors MUST NOT use any html-prefixed computed role string in the role attribute (such as html-video). User Agents MUST ignore any abstract or invalid role token.

  <video> <!-- computedrole returns 'html-video' --> <main role="html-video"> <!-- Author error. computed role returns 'main' -->

• IAccessible2:
  • All elements with accessible objects should implement the IAccessible, IAccessible2 and IAccessible2_2 interfaces.
• UIA:
  • When a labelable element is referenced by a label element's for attribute, or a descendant of a label element, the labelable element's UIA LabeledBy property points to the UIA element for the label element.
  • Elements mapped to the Text Control Type are not generally represented as accessible objects in the accessibility tree, but are just part of the Text Control Pattern implemented for the whole HTML document. However, if they have any aria- attributes or an explicit tabindex specified, elements mapped to the Text Control Type will be represented as accessible objects in the accessibility tree.
• AXAPI:
  • User agents should return a user-presentable, localized string value for the Mac Accessibility AXRoleDescription.

html-abbr

Roles: ROLE_SYSTEM_TEXT; IA2_ROLE_TEXT_FRAME

"abbr" attribute on the containing

if a single child, text content used as a value

Control Type: Text

Role: ATK_ROLE_STATIC

"abbr" attribute on the containing

if a single child, text content used as a value

AXRole: AXGroup

AXSubrole: (nil)

AXRoleDescription: "group"

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

html-audio

Role: ROLE_SYSTEM_GROUPING

Control Type: Group

Localized Control Type: "audio"

If the

attribute is present, UI controls (e.g., play, volume) are exposed as children of the

element in the

, and mapped as appropriate for the type of control (e.g.,

or

).

Text objects associated with loading or error messages, and any UI control not currently displayed,

be present in the

and marked as hidden or off-screen.

Role: ATK_ROLE_AUDIO

AXRole: AXGroup

AXSubrole: AXAudio

AXRoleDescription: "audio playback"

If the

attribute is present, UI controls (e.g., play, volume) are exposed as descendants of an

with a role of

, and mapped as appropriate for the type of control (e.g.,

or

).

html-canvas

Roles: ROLE_SYSTEM_GRAPHIC; IA2_ROLE_CANVAS

Control Type: Image

Descendants of the canvas element are mapped separately.

Role: ATK_ROLE_CANVAS

AXRole: AXGroup

AXSubrole: (nil)

AXRoleDescription: ""

Use WAI-ARIA mapping

Use WAI-ARIA mapping

with parent

Use WAI-ARIA mapping

The

property for the parent

element points to the UIA element for the

element.

Use WAI-ARIA mapping

with parent

Use WAI-ARIA mapping

with parent

html-cite

No accessible object. Styles used are mapped into text attributes on its text container.

No accessible object. Styles used are exposed by UIA text attributes of the TextRange Control Pattern implemented on a parent accessible object.

No accessible object. Styles used are mapped into text attributes on its text container.

AXRole: AXGroup

AXSubrole: (nil)

AXRoleDescription: "group"

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

list

Note

Editorial Note: This value may change upon resolution of

.

Role: ROLE_SYSTEM_LIST

States: STATE_SYSTEM_READONLY

Control Type: List

Role: ATK_ROLE_DESCRIPTION_LIST

AXRole: AXList

AXSubrole: AXDefinitionList

AXRoleDescription: "definition list"

html-embed

Roles: ROLE_SYSTEM_CLIENT; IA2_ROLE_EMBEDDED_OBJECT

States: STATE_SYSTEM_UNAVAILABLE for windowless plugin

Control Type: Pane

Role: ATK_ROLE_EMBEDDED

Use WAI-ARIA mapping

Role: Use WAI-ARIA mapping

with child

element

Role: Use WAI-ARIA mapping

Role: Use WAI-ARIA mapping

with child

element

Role: Use WAI-ARIA mapping

AXSubrole: AXFieldset

value from child

subtree

Use WAI-ARIA mapping

Roles: ROLE_SYSTEM_TEXT; IA2_ROLE_CAPTION

with parent

element

Control Type: Text

Role: ATK_ROLE_CAPTION

with parent

element

AXRole: AXGroup

AXSubrole: (nil)

AXRoleDescription: "group"

Use WAI-ARIA mapping

Note

Editorial Note: This value may change upon resolution of

.

Use WAI-ARIA mapping

Control Type: Group

Localized Control Type: "footer"

Role: ATK_ROLE_FOOTER

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Note

Editorial Note: This value may change upon resolution of

.

Use WAI-ARIA mapping

Control Type: Group

Localized Control Type: "header"

Role: ATK_ROLE_HEADER

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

If an hr element is a descendant of a select element, user agents MAY expose the element with a role of none.

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Note

ARIA 1.3 adds the image role as the preferred synonym to the ARIA 1.0 img role. The expected computed role for named img elements is now "image".

html-input-color

If implemented as a textbox:

Roles: ROLE_SYSTEM_TEXT

If implemented as a color picker:

Roles: IA2_ROLE_COLOR_CHOOSER

If implemented as a textbox:

Control Type: Edit

Localized Control Type: "edit"

If implemented as a color picker:

Control Type: button

Localized Control Type: "color picker"

If implemented as a button, use

mapping for

.

If implemented as a textbox, use

mapping for

.

If implemented as a textbox:

AXRole: AXTextField

AXSubrole: (nil)

AXRoleDescription: "text field"

If implemented as a color picker:

AXRole: AXColorWell

AXSubrole: (nil)

AXRoleDescription: "color well"

If implemented as a color picker, any UI controls presented for selecting a color are exposed in the

, associated with the

element, and mapped as appropriate for the type of control (e.g., button or slider).

html-input-date

If implemented as a textbox:

Role: ROLE_SYSTEM_TEXT

Object attributes: text-input-type:date

If implemented as a date picker:

Role: IA2_ROLE_DATE_EDITOR

Depends on UI design of implementation. The UI in Windows 10 Edge, for example, is a composite of multiple spinners.

Role: ATK_ROLE_CALENDAR

AXRole: AXDateField

AXSubrole: (nil)

AXRoleDescription: "date field"

html-input-datetime-local

Role: IA2_ROLE_DATE_EDITOR

Depends on UI design of implementation. The UI in Windows 10 Edge, for Example, is a composite of multiple spinners.

Role: ATK_ROLE_CALENDAR

AXRole: AXTextField

AXSubrole: (nil)

AXRoleDescription: "text field"

html-input-file

Implementation dependent. If represented by a container with a button a text label inside then:

Roles: IA2_ROLE_TEXT_FRAME

Children: ROLE_SYSTEM_PUSHBUTTON and IA2_ROLE_LABEL for a button and a text label elements.

Can be rendered as a single button control, or as a button control with a text input field.

Button control:

Control Type: Button

Text input field:

Control Type: Edit

Localized Control Type: "file"

Role: ATK_ROLE_STATIC

Children: ATK_ROLE_PUSH_BUTTON when pressed ATK_ROLE_FILE_CHOOSER dialog shown

AXRole: AXButton

AXSubrole: AXFileUploadButton

AXRoleDescription: file upload button

html-input-month

Role: IA2_ROLE_DATE_EDITOR

Depends on UI design of implementation. The UI in Windows 10 Edge, for Example, is a composite of multiple spinners.

Role: ATK_ROLE_DATE_EDITOR

AXRole: AXTextField

AXSubrole: (nil)

AXRoleDescription: "text field"

Use WAI-ARIA mapping

If implemented as a spin button, use

mapping for

.

If implemented as a text input, use

mapping for

.

Object attributes: text-input-type:number

Use WAI-ARIA mapping

If implemented as a spin button, use

mapping for

.

If implemented as a text input, use

mapping for

.

Object attributes: text-input-type:number

Use WAI-ARIA mapping

html-input-password

Role: ROLE_SYSTEM_TEXT

States: STATE_SYSTEM_PROTECTED; IA2_STATE_SINGLE_LINE; STATE_SYSTEM_READONLY if readonly, otherwise IA2_STATE_EDITABLE

Control Type: Edit

Other properties: isPassword=true

Role: ATK_ROLE_PASSWORD_TEXT

States: ATK_STATE_SINGLE_LINE; ATK_STATE_READ_ONLY if readonly, otherwise ATK_STATE_EDITABLE

AXRole: AXTextField

AXSubrole: AXSecureTextField

AXRoleDescription: "secure text field"

html-input-time

if implemented as a simple

;

with child controls mapped as appropriate if implemented as a complex

Object attributes: text-input-type:time

Depends on UI design of implementation. The UI in Windows 10 Edge, for Example, is a composite of multiple spinners.

Role: ATK_ROLE_SPINBUTTON if implemented as a simple widget.
If implemented as a complex widget use:
Role: ROLE_PANEL and map child controls as appropriate.

AXRole: AXTimeField

AXSubrole: (nil)

AXRoleDescription: "time field"

html-input-week

Role: IA2_ROLE_DATE_EDITOR

Object attributes: text-input-type:week

Depends on UI design of implementation. The UI in Windows 10 Edge, for Example, is a composite of multiple spinners.

Role: ATK_ROLE_CALENDAR

AXRole: AXTextField

AXSubrole: (nil)

AXRoleDescription: "text field"

html-kbd

No accessible object.

Text attributes: font-family:monospace on the text container

No accessible object. Styles used are exposed by UIA text attribute identifiers of the TextRange Control Pattern implemented on a parent accessible object.

No accessible object. Mapped into "font-family:monospace" text attribute on its text container.

AXRole: AXGroup

AXSubrole: (nil)

AXRoleDescription: "group"

html-label

Roles: ROLE_SYSTEM_STATICTEXT; IA2_ROLE_LABEL

with a

that is child to the

or referred to by the

element's

attribute. The associated labelable element has

pointing to the

.

Control Type: Group

When the

element contains a

, the

property for the element points to the UIA element for the

element.

When the

element has a

attribute referencing a

, the

property for the referenced element points to the UIA element for the

element.

Role: ATK_ROLE_LABEL

for a child

or labelable element referred by

attribute. Note, related labelable element provides

pointing to the

.

AXRole: AXGroup

AXSubrole: (nil)

AXRoleDescription: "group"

html-legend

Roles: ROLE_SYSTEM_STATICTEXT; IA2_ROLE_LABEL

with the parent

Control Type: Text

The

property for the parent

points to the UIA element for the

element.

Role: ATK_ROLE_LABEL

with parent

element

AXRole: AXGroup

AXSubrole: (nil)

AXRoleDescription: "group"

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

html-map

Not mapped if used as an image map. Otherwise,

Role: IA2_ROLE_TEXT_FRAME

Not mapped

Not mapped if used as an image map, otherwise:

Role: ATK_ROLE_STATIC

Role: AXImageMap if used as an image map. Otherwise,
Role: AXGroup if associated with an img with no alt. Otherwise,
not mapped if not associated with an img.

html-object

Depends on format of data file. If it contains a plugin then,

Role: IA2_ROLE_EMBEDDED_OBJECT

States: STATE_SYSTEM_UNAVAILABLE for windowless plugin

Depends on format of data file.

Depends on format of data file. If contains a plugin then

Role: ATK_ROLE_EMBEDDED

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Relations: IA2_RELATION_LABELLED_BY with associated label element

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Relations: ATK_RELATION_LABELLED_BY with associated label element

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

html-rp

No accessible object. No child elements are exposed if

is supported by the browser.

No accessible object.

No accessible object. No child elements are exposed if

is supported by the browser.

html-rt

No accessible object. No child elements are exposed if

is supported by the browser.

No accessible object.

No accessible object.

AXRole: AXGroup

AXSubrole: AXRubyText

AXRoleDescription: "group"

html-ruby

Role: ROLE_SYSTEM_TEXT; IA2_ROLE_TEXT_FRAME

Control Type: Text

Localized Control Type: "ruby"

Role: ATK_ROLE_STATIC

AXRole: AXGroup

AXSubrole: AXRubyInline

AXRoleDescription: "group"

Not mapped

Not mapped

Not mapped

Not mapped

Not mapped

There are instances where CSS properties can affect what is exposed by accessibility

. For instance,

or

will remove an element from the

and hide its presence from assistive technologies.

If the element is the first child of its type within a parent details element: html-summary

Otherwise, if it is not the first child of its type of a parent details element, or it is not a child of a details element: generic role

Role: ROLE_SYSTEM_PUSHBUTTON

States: STATE_SYSTEM_EXPANDED / STATE_SYSTEM_COLLAPSED

Actions: expand / collapse

Control Type: Button

Control Pattern: ExpandCollapse

Role: ROLE_TOGGLE_BUTTON

Relations: ATK_RELATION_DETAILS

AXRole: AXDisclosureTriangle

AXSubrole: (nil)

AXRoleDescription: "disclosure triangle"

html-var

No accessible object. Styles used are mapped to text attributes on its text container.

No accessible object. Styles used are exposed by UIA text attribute identifiers of the TextRange Control Pattern implemented on a parent accessible object.

No accessible object. Styles used are mapped to text attributes on its text container.

AXRole: AXGroup

AXSubrole: (nil)

AXRoleDescription: "group"

html-video

Role: ROLE_SYSTEM_GROUPING

Control Type: Group

Localized Control Type: "group"

If the

attribute is present, UI controls (e.g., play, volume) are exposed as children of the

element in the

, and mapped as appropriate for the type of control (e.g.,

or

).

Text objects associated with loading or error messages, and any UI control not currently displayed,

be present in the

and marked as hidden or off-screen.

Role: ATK_ROLE_VIDEO

AXRole: AXGroup

AXSubrole: AXVideo

AXRoleDescription: "video playback"

If the

attribute is present, UI controls (e.g., play, volume) are exposed as descendants of an

with a role of

, and mapped as appropriate for the type of control (e.g.,

or

).

Not mapped

If a line break is added, expose it with IAccessibleText on the text container

Not mapped

A line break if added is exposed via Text interface on its text container

AXRole: AXGroup

AXSubrole: (nil)

AXRoleDescription: "group"

• HTML attributes with default WAI-ARIA state and property semantics MUST be mapped to platform accessibility APIs according to those WAI-ARIA state and property mappings as defined in the [core-aam-1.2] specification.
• A '?' in a cell indicates the data has yet to be provided.
• "Not mapped" (Not Applicable) means the attribute does not need to be exposed via an accessibility API. This is usually because the attribute is not displayed as part of the user interface.

  Note

  In some cases, while not directly exposed to accessibility

  APIs

  , an attribute can still impact the accessibility of an element. e.g.,

  autoplay

  will automatically start playing

  video

  or

  audio

  elements.

• All elements having an accessible object in IAccessible2 mapping are supposed to implement IAccessible, IAccessible2 and IAccessible2_2 interfaces.

Not mapped

"abbr" until child

element is provided

Not mapped

"abbr" until child

element is provided

aria-autocomplete

Note

Note: the ARIA attribute and the HTML attribute have disparate features.

States: STATE_SUPPORTS_AUTOCOMPLETION on text form controls until the value is overridden by control

Not mapped

States: ATK_STATE_SUPPORTS_AUTOCOMPLETION on text form controls until the value is overridden by control

Not mapped

aria-autocomplete

Note

Note: the ARIA attribute and the HTML attribute have disparate features.

States: STATE_SUPPORTS_AUTOCOMPLETION

Not mapped

States: ATK_STATE_SUPPORTS_AUTOCOMPLETION

Not mapped

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

If the associated element is displayed as a popover: aria-expanded=true

If the associated element is hidden: aria-expanded=false

If the associated element is an accessibility ancestor of the element with the command attribute or is not present in the DOM: aria-expanded=undefined

If the associated element is not a valid popover element: no aria-expanded mapping.

Use WAI-ARIA mapping

Object attributes: details-roles:popover

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Object attributes: details-roles:popover

Use WAI-ARIA mapping

User Agents MUST expose an aria-details relationship with the associated element (identified via the specified commandfor attribute) except under the following conditions:

• The associated popover element is the next immediate accessibility sibling to the invoking element,
• The element is a descendant of the popover it is associated with.

Note

A button that represents a submit button or is in the reset state with a form owner cannot invoke a command.

See comments

See comments

See comments

See comments

See comments

The commandfor attribute identifies the associated element for the button element.

The specified command state will determine if a relationship mapping needs to be exposed between the button and its programmatically associated element.

If the element is in the editable state, the following mappings apply to the element and every nested accessible object with the exception of those which have been specified in the false state.

States: IA2_STATE_EDITABLE and IA2_STATE_MULTI_LINE

Interfaces: IAccessibleEditableText

If the element is in the false state: not mapped.

If the element is in the inherit state: match the editable state of its parent element.

If the element is in the editable state, the following mappings apply to the element and every nested accessible object with the exception of those which have been specified in the false state.

Control Pattern: TextEdit

Property: AriaProperties.multiline:true

If the element is in the false state: not mapped.

If the element is in the inherit state: match the editable state of its parent element.

If the element is in the editable state, the following mappings apply to the element and every nested accessible object with the exception of those which have been specified in the false state.

States: ATK_STATE_EDITABLE and ATK_STATE_MULTI_LINE

Interfaces: AtkEditableText

If the element is in the false state: not mapped.

If the element is in the inherit state: match the editable state of its parent element.

Use WAI-ARIA mapping

Not mapped

Defines an accessible object's dimensions (IAccessible::accLocation)

Defines an accessible object's dimensions (BoundingRectangle)

Defines an accessible object's dimensions, exposed via atk_component_get_position and atk_component_get_size

Defines an accessible object's dimensions, exposed via Frame property

Not mapped

Object attributes: datetime: <value>

Properties: FullDescription: <value>

Object attributes: datetime: <value>

Not mapped

Exposed as "writing-mode" text attribute on the text container.

Exposed by TextFlowDirections attribute of the TextRange Control Pattern implemented on a parent accessible object.

Exposed as "writing-mode" text attribute on the text container.

Not mapped

Not mapped

Exposed as "writing-mode" text attribute on the text container.

Exposed by TextFlowDirections attribute of the TextRange Control Pattern implemented on a parent accessible object.

Exposed as "writing-mode" text attribute on the text container.

Not mapped

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Form controls within a valid legend child element of a fieldset with a disabled attribute do not become disabled.

If the element has both the disabled attribute and the aria-disabled attribute with a valid value, User Agents MUST expose only the disabled attribute value.

Not mapped

Not mapped

Not mapped

Not mapped

Not mapped

Not mapped

Relations: IA2_RELATION_CONTROLLED_BY with an element pointed by the attribute. Paired element exposes IA2_RELATION_CONTROLLER_FOR relation.

Not mapped

Relations: ATK_RELATION_CONTROLLED_BY with an element pointed by the attribute. Paired element exposes ATK_RELATION_CONTROLLER_FOR relation.

Not mapped

Not mapped

Creates a link accessible object. For details, refer to

and

element mappings.

Creates a link accessible object. For details, refer to

and

element mappings.

Nodes that are inert are not exposed to an accessibility API.

Note

Note: an inert node can have descendants that are not inert. For example, a modal dialog can escape an inert subtree.

Not mapped

Exposed as "language" text attribute on the text container

The value of the lang attribute is exposed as a locale identifier by Culture property of the UIA element representing the HTML element, and by Culture attribute of the TextRange Control Pattern implemented on a parent accessible object.

Exposed as "language" text attribute on the text container

IA2_RELATION_CONTROLLER_FOR point to the datalist element referred to by the IDREF value of the list attribute.

ControllerFor point to the datalist element referred to by the IDREF value of the list attribute.

ATK_RELATION_CONTROLLER_FOR point to the datalist element referred to by the IDREF value of the list attribute.

Property: AXLinkedUIElements: point to the datalist element referred to by the IDREF value of the list attribute.

Exposed as IAccessibleValue::maximumValue if the element implements the interface

Exposed as atk_value_get_maximum_value if the element implements the AtkValue interface

Exposed as IAccessibleValue::maximumValue if the element implements the interface

Exposed as atk_value_get_maximum_value if the element implements the AtkValue interface

Exposed as IAccessibleValue::minimumValue if the element implements the interface

Exposed as atk_value_get_minimum_value if the element implements the AtkValue interface

Exposed as IAccessibleValue::minimumValue if the element implements the interface

Exposed as atk_value_get_minimum_value if the element implements the AtkValue interface

Not mapped

States: IA2_STATE_INVALID_ENTRY if value doesn't meet the designated minimum length value.

States: IsDataValidForForm if value doesn't meet the designated minimum length value.

States: ATK_STATE_INVALID_ENTRY if value doesn't meet the designated minimum length value.

Property: AXInvalid: true if value doesn't meet the designated minimum length value.

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

When the placeholder and aria-placeholder attributes are both present, and the placeholder attribute's value is non-empty, user agents MUST expose the value of the placeholder attribute, and ignore aria-placeholder. If the placeholder attribute's value is empty, then user agents MUST expose the value of the aria-placeholder attribute.

Not mapped

where

reflects the

type.

Relations: RELATION_DETAILS_FOR points to invoking element. See Comments.

where

reflects the

type.

User agents MUST NOT expose a details relation between a popover and its invoking element under the following conditions:

• when the popover is the next immediate accessibility sibling to the invoking element,
• when the element has a popovertargetaction=hide attribute value,
• or when the element is a descendant of the popover and its popovertarget is the "auto" state.

If specified on an element with an implicit role of generic, then the element's role instead maps to group for all popover states.

Note

There are no unique mappings for the different popover states. Any accessibility mapping changes for the popover element would be the responsibility of the author. e.g., using different base HTML elements, attributes, or ARIA attributes to make such changes.

If the associated element is displayed as a popover: aria-expanded=true

If the associated element is hidden: aria-expanded=false

If the associated element is an accessibility ancestor of the element with the command attribute or is not present in the DOM: aria-expanded=undefined

If the associated element is not a valid popover element: no aria-expanded mapping.

Use WAI-ARIA mapping

Object attributes: details-roles:popover

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Object attributes: details-roles:popover

Use WAI-ARIA mapping

User Agents MUST expose an aria-details relation with the associated popover element except under the following conditions:

• The element's popovertargetaction attribute value is "hide"
• The associated popover element is the next immediate accessibility sibling to the invoking element,
• The element's implicit or explicit popovertargetaction is the "auto" state and the element is a descendant of the popover it is associated with.

Note

A button that represents a submit button with a form owner cannot invoke a popover.

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

If the element includes both the required attribute and the aria-required attribute with a valid value, User Agents MUST expose only the required attribute value.

If an element is required, user agents MUST NOT expose the element with an intitial invalid state (aria-invalid="true"). The user agent SHOULD expose the invalid state only after 1) a user has purposefully interacted with a required element, or attempted to submit a form and 2) the element, or elements, do not meet constraint validation.

Until these conditions are met, user agents MUST expose the elements as (aria-invalid="false").

Not mapped

Reverses the numerical or alphabetical order of the child list item markers.

Reverses the numerical or alphabetical order of the child list item markers.

Reverses the numerical or alphabetical order of the child list item markers.

Reverses the numerical or alphabetical order of the child list item markers.

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Use WAI-ARIA mapping

Not mapped for input elements.

If greater than 1, then creates a listbox accessible object. Refer to

element for details.

Not mapped for input elements.

For select element use WAI-ARIA mapping.

Not mapped for input elements.

For select element use WAI-ARIA mapping.

Not mapped for input elements.

For select element use WAI-ARIA mapping.

Not mapped for input elements.

For select element use WAI-ARIA mapping.

Exposed as IAccessibleTableCell::columnExtent on all cells at the column

Exposed as GridItem.ColumnSpan on all cells at the column

Exposed via atk_table_get_column_extent_at

AXColumnIndexRange.length: <value>

Not mapped

Changes the first number of the child list item accessible objects to match the start attribute's value.

Changes the first number of the child list item accessible objects to match the start attribute's value.

Changes the first number of the child list item accessible objects to match the start attribute's value.

Changes the first number of the child list item accessible objects to match the start attribute's value.

Not mapped

Not mapped

Exposed as atk_value_get_minimum_increment if the element implements the AtkValue interface.

Defines the accessible role, states and other properties, refer to

,

,

, etc.

Defines the accessible role, states and other properties, refer to

,

,

, etc.

Defines the accessible role, states and other properties, refer to

,

,

, etc.

Defines the accessible role, states and other properties, refer to

,

,

, etc.

Defines the list item marker, which has no

, but is exposed as content in the accessible text of the associated list item.

Interfaces: IAccessibleText2

Defines the list item marker, which has no

, but is exposed as content in the accessible text of the associated list item.

Control Pattern: Text

Defines the list item marker, which has no

, but is exposed as content in the accessible text of the associated list item.

Interfaces: ATKText

Defines the list item marker, which is exposed as content in

, and rendered as an

:

AXRole: AXListMarker

AXSubrole: (nil)

AXRoleDescription: "list marker"

Some platforms (IAccessible2, ATK, UIA) do not expose an

for the list item marker, whether it was created and then pruned from the

, or never created in the first place. Instead, they expose the list item marker as part of the associated list item's accessible text. In these cases, implementors need to consider such things as adjusting the offsets (e.g., for caret-moved events, text-selection events, etc.) for the updated list item text that now also contains the list item marker as content, rather than just taking the offsets unmodified from the list item renderer.

Not mapped

Responsible for image map creation.

Responsible for image map creation.

Responsible for image map creation.

Responsible for image map creation.

Associates the accessible value for entry type input elements and

for button type input elements

Associates the accessible value for entry type input elements and

for button type input elements

Associates the accessible value for entry type input elements and

for button type input elements

Not mapped

Exposed as first text node of li's accessible object.

Expose the value of the value attribute as the first text node in the list item. If the value of the value attribute is an integer, set the UIA PositionInSet property to the integer value.

Exposed as first text node of li's accessible object.

Exposed as AXValue: <value> with accessible object:

AXRole: AXListMarker

AXSubrole: (nil)

AXRoleDescription: list marker

The terms accessible name and accessible description are properties provided in all accessibility APIs. The name of the properties may differ across APIs but they serve the same function: as a container for a short (name) or longer (description) string of text.

The text alternative computation is used to generate both the accessible name and accessible description. There are different rules provided for several different types of elements, nodes, and combinations of markup.

1. If the control has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. Otherwise use the associated label element or elements accessible name(s) - if more than one label is associated; concatenate by DOM order, delimited by spaces.
3. If the accessible name is still empty, then: use the control's title attribute.
4. Otherwise use the control's placeholder value.
5. If none of the above yield a usable text string there is no accessible name.

1. If the control has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. Otherwise use the associated label element(s) accessible name(s) - if more than one label is associated; concatenate by DOM order, delimited by spaces.
3. Otherwise use the value attribute.
4. For input type=submit and type=reset: if the prior steps do not yield a usable text string, and the value attribute is unspecified use the implementation defined string respective to the input type.
5. Otherwise, if the control still has no accessible name use title attribute.
6. If none of the above yield a usable text string there is no accessible name.

1. If the control has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. Otherwise use the associated label element(s) accessible name(s) - if more than one label is associated; concatenate by DOM order, delimited by spaces.
3. Otherwise use alt attribute if present and its value is not the empty string.
4. Otherwise use title attribute if present and its value is not the empty string.
5. Otherwise if the previous steps do not yield a usable text string, use the implementation defined string respective to the input type (an input in the image state represents a submit button). For instance, a localized string of the word "submit" or the words "Submit Query".
6. If none of the above yield a usable text string there is no accessible name.

1. If the button element has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. Otherwise use the associated label element(s) accessible name(s) - if more than one label is associated; concatenate by DOM order, delimited by spaces.
3. Otherwise use the button element subtree.
4. Otherwise use title attribute.
5. If none of the above yield a usable text string there is no accessible name.

1. If the fieldset element has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. If the accessible name is still empty, then: if the fieldset element has a child that is a legend element, then use the subtree of the first such element.
3. If the accessible name is still empty, then:, if the fieldset element has a title attribute, then use that attribute.
4. Otherwise, there is no accessible name.

1. If the output element has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. Otherwise use the associated label element or elements accessible name(s) - if more than one label is associated; concatenate by DOM order, delimited by spaces.
3. Otherwise use title attribute.
4. If none of the above yield a usable text string there is no accessible name.

1. If the control has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. Otherwise use label element.
3. Otherwise use title attribute.
4. If none of the above yield a usable text string there is no accessible name.

1. If the first summary element, which is a direct child of the details element, has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. Otherwise use summary element subtree.
3. Otherwise use title attribute.
4. If there is no summary element as a direct child of the details element, the user agent should provide one with a subtree containing a localized string of the word "details".
5. If there is a summary element as a direct child of the details element, but none of the above yield a usable text string, there is no accessible name.

1. If the figure element has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. If the accessible name is still empty, then: if the figure element has a child that is a figcaption element, then use the subtree of the first such element.
3. If the accessible name is still empty, then: if the figure element has a title attribute, then use that attribute.
4. Otherwise, there is no accessible name.

1. If the img element has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. Otherwise use alt attribute, even if its value is the empty string.

   Note

   An

   img

   with an

   alt

   attribute whose value is the empty string is mapped to the

   presentation

   role. It has no accessible name.

3. Otherwise, if there is no alt attribute use the title attribute.
4. Otherwise there is no accessible name.

1. If the table element has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. If the accessible name is still empty, then: if the table element has a child that is a caption element, then use the subtree of the first such element.
3. If the accessible name is still empty, then: if the table element has a title attribute, then use that attribute.
4. Otherwise, there is no accessible name.

1. If the element has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. Otherwise use the title attribute.
3. If none of the above yield a usable text string there is no accessible name.

1. If the a element has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. Otherwise use a element subtree.
3. Otherwise use the title attribute.
4. If none of the above yield a usable text string there is no accessible name.

1. If the area element has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. Otherwise use area element's alt attribute.
3. Otherwise use the title attribute.
4. If none of the above yield a usable text string there is no accessible name.

1. If the element has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. Otherwise use the title attribute.
3. If none of the above yield a usable text string there is no accessible name.

Note

The document referenced by the src of the iframe element gets its name from that document's title element, like any other document. If there is no title provided, there is no accessible name.

1. If the element has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. Otherwise use the title attribute.
3. If none of the above yield a usable text string there is no accessible name.

abbr, b, bdi, bdo, br, cite, code, dfn, em, i, kbd, mark, q, rp, rt, ruby, s, samp, small, strong, sub and sup, time, u, var, wbr

1. If the element has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
2. Otherwise use the title attribute.
3. If none of the above yield a usable text string there is no accessible name.

An accessible description MAY be provided to any HTML element that is a valid child of the body element. The following list represents the order of precedence for user agents to compute the accessible description of an element. As defined by Accessible Name and Description Computation: Description Computation , user agents MUST use the first applicable description source, even if its use results in an empty description.

1. If the element has an aria-describedby or aria-description attribute refer to the computation conditions defined in Accessible Name and Description: Computation and API Mappings.
2. Otherwise, if the accessible description is still empty, and the element is:
   • a table element which has a child caption element, use the text equivalent computation of the subtree of the first caption element if it was not used as the accessible name.
   • a summary element, use the text equivalent computation of its subtree if it was not used as the accessible name.
   • an input element whose type attribute is the button, submit or reset state, and it has a value attribute, then use the flat string of the attribute if it was not used as the accessible name.
3. Otherwise, use the flat string of the title attribute if it was not used as the accessible name for the element.
4. If none of the above are applicable, there is no accessible description.

In accordance with Web Platform Design Principles, this specification provides no programmatic interface to determine if information is being used by Assistive Technologies. However, this specification does allow an author to present different information to users of Assistive Technologies from the information available to users who do not use Assistive Technologies. This is possible using many features of the ARIA and CORE-AAM specifications, just as this is possible using many other parts of the web technology stack. This content disparity could be abused to perform active fingerprinting of users of Assistive Technologies.

This specification introduces no new security considerations.

Review the commit history of this document on GitHub.

• 2-April-2025: Add command and commandfor attribute mappings. See GitHub ARIA PR 2354.
• 11-July-2024: User Agents ignore aria-hidden=true on body and html elements. See GitHub PR 516.
• 06-June-2024: Add concept of Minimum Role. See GitHub PR 454.
• 06-June-2024: Add popover, popovertarget and popovertargetaction mappings. See GitHub PR 481.
• 09-Oct-2023: Acknowledge use of hr element within select element. See GitHub PR 504.
• 03-Oct-2023: Update image mappings to reference the primary synonym roles (image and none). See GitHub PR 498.
• 03-Oct-2023: Clarify when to expose required field as invalid. See GitHub PR 429.
• 06-Jun-2023: Add computed roles for all HTML elements. See GitHub PR 465.
• 28-Mar-2023: Add inert attribute mapping. See GitHub PR 410.
• 24-Mar-2023: Add search element and its mappings. See GitHub PR 355.
• 08-Mar-2023: Update hgroup element to be mapped to role=group. See GitHub PR 398.
• 08-Mar-2023: Clarify naming algorithm for output element. See GitHub PR 402.
• 12-Dec-2022: Revise mapping for s element to be role=deletion. See GitHub PR 442.
• 28-Nov-2022: Simplify accessible description computation section. See GitHub PR 444.
• 19-Jul-2022: Update address element to be mapped to role=group. See GitHub PR 420.
• 03-Apr-2022: Update aside mappings based on its nesting context. See GitHub PR 350.
• 06-Mar-2022: Update the following elements to map to the generic role: a no href, footer not scoped to body, header not scoped to body, samp, span. See GitHub PR 364.
• 06-Feb-2022: Update mark to point to Core AAM mapping for the role. See GitHub Issue 316.
• 02-Nov-2021: Updating blockquote, caption, code, del, em, ins, meter, paragraph, strong, sub, sup and time to ARIA 1.2 mappings in Core AAM. Fix body mapping to generic, and html mapping to document. Fix hgroup mapping to generic. Update details to map to group with additional information specific to ATK, UIA. See GitHub issue #348
• 12-May-2021: Add FACES references to attributes table - readonly, name, form, disabled. See Issue 257.
• 12-Dec-2019: Adds hgroup, slot, autonomous custom element and form associated custom element. See GitHub issue #189.
• 26-Nov-2019: Updates mappings for disabled, scope, spellcheck, tabindex to point to WAI-ARIA. Adds AX pattern, reversed, rows, size, span, src, start, step, type attribute mappings. Adds min-length, ping, playsinline, referrerpolicy, sizes, srcset, data[value] attribute mappings. See GitHub pull request #245.

• 30-Sept-2019: Remove mappings for rb and rtc elements as they are marked as obsolete in HTML. See GitHub issue #115 and pull request #253.
• 23-Sept-2019: Update attribute mappings for high, low, max, min, and meter and progress's value attribute. See GitHub pull request #244.
• 18-Sept-2019: Update mark element's UIA LocalizedControlType and AX AXRoleDescription. See GitHub issue #236.
• 18-Sept-2019: Update ATK mappings for summary and details elements. See GitHub issue #142 and GitHub issue #147.
• 18-Sept-2019: Update MSAA mappings for sub and sup. See GitHub pull request #252.
• 11-Sept-2019: Update mapping for menu to match HTML Living Standard. Remove element and attribute mappings that are not applicable to menu and menuitem. Update mapping of menu to role="list". See GitHub issue #188.
• 10-July-2019: Further updated mappings for ins and del elements. See GitHub pull request #219.
• 13-June-2019: Update mappings for ins and del elements. See GitHub issue #141.
• 10-June-2019: Update ATK mappings for header and footer when not scoped to the body. See GitHub issue #129.
• 21-May-2019: Update AXAPI mappings for map element. Add accessible name and description computation for area. See GitHub issue #176.
• 11-Apr-2019: Update UIA mappings for sub and sup elements. See Pull request #177.
• 20-Mar-2019: Updated IA2 mappings for sup and sub elements. See GitHub issue #174.
• 26-Feb-2019: Updated mappings for the address element. See GitHub issue #170.
• 19-Feb-2019: Added placeholder attribute to accessible name computation for various input elements. See GitHub issue #167.
• 07-Feb-2018: Added entries for the rb and rtc elements, and updated AXAPI mappings for the rb, rt and ruby elements. See GitHub issue #115.
• 07-Feb-2018: Updated mappings for the svg element. See GitHub issue #43.
• 07-Feb-2018: Updated AXAPI mappings for the del and ins elements, and the datetime attribute.
• 07-Feb-2018: Aligned mappings with CORE-AAM as appropriate for header and footer when scoped to body, aside, and output. See GitHub issue #119.
• 07-Feb-2018: Updated ATK and AX mappings for the multiple attribute on input element. See GitHub issue #96.
• 07-Feb-2018: Updated ATK mappings for the sub and sup elements. See GitHub issue #121.
• 07-Feb-2018: Updated mappings for the body element. See GitHub issue #117.
• 01-Feb-2018: Updated IA2 mapping for the meter element. See GitHub issue #2.
• 29-Jan-2018: Updated heading mapping to reflect implementations. See GitHub issue #116.
• 23-Jan-2018: Added note regarding effect of some CSS properties. See GitHub issue #234.
• 23-Jan-2018: Updated mappings for the address element. See GitHub issue #33.
• 23-Jan-2018: Updated mappings for the dt element. See GitHub issue #78.
• 23-Jan-2018: Updated AXAPI mappings for the mark element.
• 08-Jan-2018: Updated mappings for the input element with the type attribute in the Color state. See GitHub issue #48.
• 06-Jan-2018: Updated IA2 mappings for the pre, q, and ruby elements, and the multiple attribute for the input element. See GitHub issue #94.
• 18-Dec-2017: Rewrote first paragraph in Introduction to better reflect the relationship between the HTML-AAM and CORE-AAM specifications. See GitHub issue #66.
• 18-Dec-2017: Updated readonly attribute to use aria-readonly="true" WAI-ARIA mappings. See GitHub issue #93.
• 08-Dec-2017: Changed AXAPI mapping for the canvas element from AXImage to AXGroup.
• 01-Dec-2017: Updated mappings for the dfn element. See GitHub issue #6.
• 30-Nov-2017: Updated mappings for the meter element. See GitHub issue #2.
• 24-Nov-2017: Updated mappings for the audio and video elements. See GitHub issue #80.
• 23-Nov-2017: Updated figure element mappings to reflect the WAI-ARIA figure role mappings.
• 23-Nov-2017: Updated mappings for the form element based on presence of accessible name. See GitHub issue #106.
• 23-Nov-2017: Removed the accessible name computation requirement to ignore an img element's title attribute when the element's alt attribute is empty. See GitHub issue #99.
• 23-Nov-2017: Added note to not expose aria-roledescription unless element also a conforming role attribute value. See GitHub issue #98.
• 09-Aug-2017: Updated mappings for the type attribute on the ol element. See GitHub issue #91.
• 25-July-2017: Updated UIA mappings for multiple elements and attributes. See GitHub issue #95 and GitHub pull request #101.
• 02-June-2017: Updated AXAPI mappings for title attribute on abbr element, and abbr attribute on th element. See GitHub issue #16.
• 31-May-2017: Updated mappings for hidden attribute. See GitHub issue #38.
• 24-May-2017: Updated mappings for selected attribute. See GitHub issue #92.
• 01-May-2017: Updated AXAPI mapping for time element. See GitHub issue #88.
• 27-Apr-2017: Updated UIA mappings for lang and dir attributes. See GitHub issue #19.
• 19-Apr-2017: Updated mapping for colspan and rowspan attributes. See GitHub issue #56 and issue #57.
• 03-Apr-2017: Updated mapping for section element. See GitHub issue #79.
• 23-Dec-2016: No mapping for datalist element if not linked with input element. See GitHub issue #26.
• 23-Dec-2016: Updated IA2 mapping for list attribute. See GitHub issue #21.
• 22-Dec-2016: Sync mappings for footer and header elements. See GitHub issue #59.
• 22-Dec-2016: Updated IA2 mapping for input@type='date' attribute. See GitHub issue #61.
• 22-Dec-2016: Updated IA2 mapping for input@type='file' element. See GitHub issue #62.
• 22-Dec-2016: Updated IA2 mapping for summary element. See GitHub issue #64.
• 14-Dec-2016: Updated wording distinguishing when header and footer elements are or are not ARIA landmarks. See GitHub issue #65.
• 07-Dec-2016: Modified aria-multiselectable mapping for datalist to reflect listbox selection model. See GitHub issue #71.
• 07-Dec-2016: Mappings for the multiple attribute on input and select elements. See GitHub issue #72.
• 27-Nov-2016: Added implementation rules for the checked, contenteditable, disabled, and indeterminate attributes.
• 21-Nov-2016: Removed placeholder attribute from accessible description computation for various input elements.

This section is non-normative.

The following people contributed to the development of this document.

• Adam Page
• Alex Lloyd
• Alexander Surkov
• Bogdan Brinza
• Carolyn MacLeod
• Dan Clark
• Denis Ah-Kang
• Dominique Hazael-Massieux
• einSelbst
• James Craig
• James Nurthen
• Jason Kiss
• joanmarie
• Johanna
• Jon Gunderson
• Léonie Watson
• Marcos Cáceres
• Melanie Richards
• Nick Schonning
• Peter Krautzberger
• Philippe Le Hegaret
• Rahim Abdi
• Sid Vishnoi
• Simon Pieters
• Steve Faulkner
• Valerie Young
• Vikas Parashar
• Xiaoqian Wu
• Yummy_Bacon5
• Yves Lafon

• Rahim Abdi (Apple Inc.)
• NAVYA AGARWAL (Adobe)
• Mario Batušić (Fabasoft)
• Benjamin Beaudry (Microsoft Corporation)
• Curt Bellew (Oracle Corporation)
• Zoë Bijl (W3C Invited Experts)
• Aleksandar Cindrikj (Netcetera)
• Keith Cirkel (Mozilla Foundation)
• Daniel Clark (Microsoft Corporation)
• James Craig (Apple Inc.)
• Chris Cuellar (Bocoup)
• Hidde de Vries (Logius)
• Joanmarie Diggs (Igalia)
• Howard Edwards (Bocoup)
• James Edwards (TPGi)
• Mayuri Faldu (Navy Federal Credit Union)
• Betsy Fanning (PDF Association)
• Steve Faulkner (TetraLogical Services Ltd)
• Jaunita Flessas (Navy Federal Credit Union)
• Jane Fulton (Cisco)
• Bryan Garaventa (W3C Invited Experts)
• Rashmi Garimella (Google LLC)
• Matt Garrish (DAISY Consortium)
• Doug Geoffray (Microsoft Corporation)
• Ariella Gilmore (IBM Corporation)
• Shirisha Gubba (Google LLC)
• Eloisa Guerrero (Rakuten Group, Inc.)
• Jon Gunderson (University of Illinois)
• Oliver Habersetzer (SAP SE)
• Theo Hale (Microsoft Corporation)
• Sunny Hardasani (Adobe)
• Matthew Hardy (Adobe)
• Peter Heumader (Fabasoft)
• Sarah Higley (Microsoft Corporation)
• Hans Hillen (TPGi)
• Isabel Holdsworth (TPGi)
• Stanley Hon (Microsoft Corporation)
• Michael Jackson (Microsoft Corporation)
• Duff Johnson (PDF Association)
• Summer Jones (Thomson Reuters Corp.)
• William Kilian (TargetStream Technologies)
• Matthew King (Meta)
• Zachary Kinsey (TargetStream Technologies)
• Greta Krafsig (The Washington Post)
• Peter Krautzberger (krautzource UG)
• Nina Krauß (SAP SE)
• JaEun Jemma Ku (University of Illinois)
• Joe Lamyman (TetraLogical Services Ltd)
• Charles LaPierre (Benetech)
• Philip Lazarevic (Level Access)
• Aaron Leventhal (Google LLC)
• Brett Lewis (TPGi)
• Andy Luhrs (Microsoft Corporation)
• Sazzad Mahamud (Google LLC)
• Alison Maher (Microsoft Corporation)
• Mark McCarthy (University of Illinois)
• Eduardo Meza Etienne (Navy Federal Credit Union)
• Clay Miller (Microsoft Corporation)
• Daniel Montalvo (W3C)
• James Nurthen (Adobe)
• Scott O'Hara (Microsoft Corporation)
• Lola Odelola (W3C Invited Experts)
• Adam Page (Hilton)
• Michael Pennisi (Bocoup)
• Roberto Perez (Microsoft Corporation)
• Giacomo Petri (UsableNet)
• Noah Praskins (TPGi)
• Daniel Pöll (Fabasoft)
• Paul Rayius (Allyant)
• Adrian Roselli (W3C Invited Experts)
• Marco Sabidussi (UsableNet)
• Trisha Salas (Level Access)
• Stefan Schnabel (SAP SE)
• Harris Schneiderman (Deque Systems, Inc.)
• Raymond Schwartz (Navy Federal Credit Union)
• Cynthia Shelly (W3C Invited Experts)
• Tzviya Siegman (W3C)
• Arturo Silva (The Washington Post)
• Avneesh Singh (DAISY Consortium)
• Michael[tm] Smith (sideshowbarker) (W3C)
• Francis Storr (Intel Corporation)
• Jennifer Strickland (MITRE Corporation)
• Melanie Sumner (IBM Corporation)
• Alexander Surkov (Igalia)
• James Teh (Mozilla Foundation)
• Jocelyn Tran (Google LLC)
• Léonie Watson (TetraLogical Services Ltd)
• Jan Williams (TPGi)
• Valerie Young (Igalia)
• Kate Zhao (Thomson Reuters Corp.)
• Xiao (Helen) Zhou (University of Illinois)
• Filippo Zorzi (UsableNet)

This publication has been funded in part with U.S. Federal funds from the Department of Education, National Institute on Disability, Independent Living, and Rehabilitation Research (NIDILRR), initially under contract number ED-OSE-10-C-0067, then under contract number HHSP23301500054C, and now under HHS75P00120P00168. The content of this publication does not necessarily reflect the views or policies of the U.S. Department of Education, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government.

[accname-1.2]

Accessible Name and Description Computation 1.2. Bryan Garaventa; Melanie Sumner. W3C. 3 April 2025. W3C Working Draft. URL: https://www.w3.org/TR/accname-1.2/

[core-aam-1.2]

Core Accessibility API Mappings 1.2. Valerie Young; Alexander Surkov. W3C. 27 March 2025. CRD. URL: https://www.w3.org/TR/core-aam-1.2/

[HTML]

HTML Standard. Anne van Kesteren; Domenic Denicola; Dominic Farolino; Ian Hickson; Philip Jägenstedt; Simon Pieters. WHATWG. Living Standard. URL: https://html.spec.whatwg.org/multipage/

[RFC2119]

Key words for use in RFCs to Indicate Requirement Levels. S. Bradner. IETF. March 1997. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc2119

[RFC8174]

Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words. B. Leiba. IETF. May 2017. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc8174

[svg-aam-1.0]

SVG Accessibility API Mappings. Amelia Bellamy-Royds; Ian Pouncey. W3C. 10 May 2018. W3C Working Draft. URL: https://www.w3.org/TR/svg-aam-1.0/

[WAI-ARIA]

Accessible Rich Internet Applications (WAI-ARIA) 1.1. Joanmarie Diggs; Shane McCarron; Michael Cooper; Richard Schwerdtfeger; James Craig. W3C. 14 December 2017. W3C Recommendation. URL: https://www.w3.org/TR/wai-aria-1.1/

[WAI-ARIA-1.2]

Accessible Rich Internet Applications (WAI-ARIA) 1.2. Joanmarie Diggs; James Nurthen; Michael Cooper; Carolyn MacLeod. W3C. 6 June 2023. W3C Recommendation. URL: https://www.w3.org/TR/wai-aria-1.2/

[AT-SPI]

Assistive Technology Service Provider Interface. The GNOME Project. URL: https://gnome.pages.gitlab.gnome.org/at-spi2-core/libatspi/

[ATK]

ATK - Accessibility Toolkit. The GNOME Project. URL: https://developer.gnome.org/atk/stable/

[AXAPI]

The NSAccessibility Protocol for macOS. Apple, Inc. URL: https://developer.apple.com/documentation/appkit/nsaccessibility

[dom]

DOM Standard. Anne van Kesteren. WHATWG. Living Standard. URL: https://dom.spec.whatwg.org/

[HTML5]

HTML5. Ian Hickson; Robin Berjon; Steve Faulkner; Travis Leithead; Erika Doyle Navara; Theresa O'Connor; Silvia Pfeiffer. W3C. 27 March 2018. W3C Recommendation. URL: https://www.w3.org/TR/html5/

[IAccessible2]

IAccessible2. Linux Foundation. URL: https://wiki.linuxfoundation.org/accessibility/iaccessible2/

[infra]

Infra Standard. Anne van Kesteren; Domenic Denicola. WHATWG. Living Standard. URL: https://infra.spec.whatwg.org/

[UI-AUTOMATION]

UI Automation. Microsoft Corporation. URL: https://docs.microsoft.com/en-us/windows/win32/winauto/ui-automation-specification

↑

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.3