ARIA 1.1 Changes
From Accessible Rich Internet Applications Working Group
- 1 ARIA 1.1 Testing Wiki Pages
- 2 Notes
- 3 Features introduced in 1.1 and requiring full testing
- 4 Existing features changed in 1.1
- 5 New or changed user agent normative statements
ARIA 1.1 Testing Wiki Pages
- ARIA 1.1 Automated Testing
- Testable Statements
- ARIA 1.1 Changes
- ARIA 1.1 Test Case Coverage
- ARIA 1.1 Testable Statements JSON
The text alternative calculation is now a separate spec. Joanie has not done any diffs with it. "Patches welcome." :)
Features introduced in 1.1 and requiring full testing
States and properties
Existing features changed in 1.1
Properties with changed types and/or default values
- aria-haspopup's type is now token. Values:
- aria-hidden's type is now true/false/undefined
- undefined is new default
- undefined means user agent determines state based on rendering
- aria-level's implicit value for heading is now 2
- Changes to value of aria-orientation:
- aria-valuemin now has a default implicit value on some roles (when author does not specify aria-valuemin):
- aria-valuemax now has a default implicit value on some roles (when author does not specify aria-valuemax):
- aria-valuenow now has a default implicit value on some roles (when author does not specify aria-valuenow):
Properties added to or removed from roles
- aria-busy is (more clearly) applicable to all elements. Note that this technically was the case for 1.0. But the text in 1.0 implies busy was intended for live regions.
- aria-orientation added to:
- aria-posinset and aria-setsize added to:
- aria-readonly added to:
- aria-valuemin, aria-valuemax, aria-valuenow added as required properties of focusable separator elements
Miscellaneous Role Changes
- application is no longer a landmark
- region is now a landmark
- spinbutton subclasses composite and can have children
New or changed user agent normative statements
- Applying the aria-selected state on a columnheader MUST not cause the user agent to automatically propagate the aria-selected state to all the cells in the corresponding column.
- User agents SHOULD not expose (aria-readonly or aria-required) to assistive technologies unless the columnheader descends from a grid.
- NOTE: The previous requirement is also stated for role rowheader.
- If aria-readonly is set on an element with role grid, user agents MUST propagate the value to all gridcell elements owned by the grid and expose the value in the accessibility API. An author may override the propagated value of aria-readonly for an individual gridcell element.
- The previous requirement is also stated for role treegrid.
- The ARIA 1.0. specification describes a combobox pattern where a text input element has the combobox role and owns a listbox element. User agents, assistive technologies, and conformance checkers SHOULD continue to support the ARIA 1.0 pattern.
- User agents MUST treat any value of aria-haspopup that is not included in the list of allowed values, including an empty string, as if the value false had been provided.
- To provide backward compatibility with ARIA 1.0 content, user agents MUST treat an aria-haspopup value of true as equivalent to a value of menu.