Aria Roles

Definitions

Active
The Enterprise is currently using Roles marked 'active'
Inactive
The Enterprise is currently not using Roles marked 'inactive'

General Roles Guidelines

  • Do not use role="presentation" or aria-hidden="true" on a visible focusable element. This would result in some users focusing on 'nothing'.

Active Widget Roles

  • Alert

    A message with important, and usually time-sensitive information. See related alertdialog and status .

    The alert role goes on the node containing the alert message.

    Authors should NOT require users to close an alert. If an alert requires focus to close the alert, authors should use alertdialog instead.

  • Alertdialog

    A type of dialog that contains an alert message. See related alert and dialog .

    When the alertdialog is displayed, authors should set focus to an active element within the alert dialog, such as a form field or an OK button.

    The alertdialog role goes on the node containing both the alert message and the rest of the dialog.

    Authors should make alert dialogs modal.

    Authors should use aria-describedby on an alertdialog to point to the alert message in the dialog.

  • Dialog

    An application window that is designed to interrupt the current processing in order to prompt the user to enter information of require a response. See related alertdialog .

    Authors should provide a dialog label with the aria-label or aria-labelledby attribute if other mechanisms are not available.

    Authors should ensure each active dialog has a focused descendant element that has keyboard focus.

Active Document Stucture Roles

  • Region

    A large perceivable section of a web page or document, that is important enough to be included in a page summary or table of contents.

    Authors should ensure that a region has a heading referenced by aria-labelledby .

Active Landmark Roles

  • Banner

    A region that contains mostly site-oriented content, rather than page-specific content like a logo or site-specific search tool.

    Authors should mark no more than one (1) element with the banner role.

  • Contentinfo

    A large perceivable region that contains information about the parent document like copyrights and links to privacy statements.

    Authors should mark no more than one (1) element with the contentinfo role.

  • Main

    The main content of a document.

    Authors should mark no more and one (1) element with the main role.

  • Navigation

    A collection of navigational elements (usually links) for navigation the document or related documents.

Inactive Abstract Roles

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

  • Command

  • Composite

  • Input

  • Landmark

  • Range

  • Roletype

  • Section

  • Sectionhead

  • Select

  • Structure

  • Widget

  • Window

Inactive Widget Roles

  • Button

  • Checkbox

  • Gridcell

  • Link

  • Log

  • Marquee

  • Menuitem

  • Menuitemcheckbox

  • Menuitemradio

  • Option

  • Progressbar

  • Radio

  • Scrollbar

  • Slider

  • Spinbutton

  • Status

  • Tab

  • Tabpanel

  • Textbox

  • Timer

  • Tooltip

  • Treeitem

Composite Widget Roles

  • Combobox

  • Grid

  • Listbox

  • Menu

  • Menubar

  • Radiogroup

  • Tablist

  • Tree

  • Treegrid

Inactive Document Stucture Roles

  • Article

  • Columnheader

  • Defintion

  • Directory

  • Document

  • Group

  • Heading

  • Img

  • List

  • Listitem

  • Math

  • Note

  • Presentation

  • Row

  • Rowgroup

  • Rowheader

  • Separator

  • Tollbar

Inactive Landmark Roles

  • Application

  • Complementary

  • Form

  • Search