Practices

ARIA landmark roles provide a powerful way to identify the organization and structure of a web page.

Providing elements with accessible names, and where appropriate, accessible descriptions, is one of the most important responsibilities authors have when developing accessible web experiences.

Unlike native HTML form elements, browsers do not provide keyboard support for graphical user interface (GUI) components that are made accessible with ARIA; authors have to provide the keyboard support in their code.

Live regions can be used to inform assistive technology users of important changes as they happen.

To fully present and describe a grid or table, in addition to parsing the headers, rows, and cells using the roles described in the grid pattern or table pattern, assistive technologies need to be able to determine other structural and presentation characteristics, such as the number and visibility of rows and columns.

ARIA defines the following roles as range widgets, which means they communicate a value that is typically numeric and constrained to defined limits.

ARIA provides a set of roles that convey the accessibility semantics of structures on a page.

While ARIA is primarily used to express semantics, there are some situations where hiding an element’s semantics from assistive technologies is helpful.