grid role (aria)
Screen Reader support level: partial (27/33)
On this page
About this feature
A composite widget containing a collection of one or more rows with one or more cells where some or all cells in the grid are focusable by using methods of two-dimensional navigation, such as directional arrow keys.
Age of results
Results across all tests for this feature range from a month ago to 5 years ago. Detailed dates and version information can be found in associated tests.
Caution
Failing or partial results may be out of date. The oldest result is from 5 years ago. Consider running the associated tests and contributing results.
Expectations
Screen Reader support by expectation
| Expectation | JAWS | Narrator | NVDA | Orca | TalkBack | VoiceOver (iOS) | VoiceOver (macOS) | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Chrome | Edge | Firefox | Edge | Chrome | Edge | Firefox | Firefox | Chrome | Safari | Safari | |
| MUST convey its name | supported | supported | supported | supported | supported | supported | supported | supported | supported | supported | supported |
| MUST convey its role | supported | supported | supported | supported | partial | partial | partial | partial | supported | supported | partial |
| SHOULD switch to interaction mode | supported | supported | supported | none | supported | supported | supported | supported | not applicable | not applicable | not applicable |
| MUST convey boundaries | supported | supported | supported | supported | supported | supported | supported | partial | supported | supported | supported |
Expectation: convey its name
Rationale:
A user needs to know the name of the grid so that they understand what it is for
Strength of this expectation for different types of assistive technologies:
- Screen Readers: MUST
- Voice Control: NA
Examples:
- A screen reader might announce the name when entering the grid
Expectation: convey its role
Rationale:
A screen reader user needs to be aware that they are entering a grid so that they know that grid keyboard commands are available.
Strength of this expectation for different types of assistive technologies:
- Screen Readers: MUST
- Voice Control: NA
Examples:
- Screen readers might convey the role as something like "grid"
Expectation: switch to interaction mode
Rationale:
Grids are usually navigated via arrow keys, so those keys presses need to be sent directly to the browser and not intercepted by the screen reader.
Strength of this expectation for different types of assistive technologies:
- Screen Readers: SHOULD
- Voice Control: NA
Examples:
- Screen readers might convey an earcon when the mode switches
- Arrow keys will work for navigation without manually switching modes
| Test | JAWS | Narrator | NVDA | Orca | TalkBack | VoiceOver (iOS) | VoiceOver (macOS) | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Chrome | Edge | Firefox | Edge | Chrome | Edge | Firefox | Firefox | Chrome | Safari | Safari | |
| ARIA readonly grid | supported | supported | supported | none | supported | supported | supported | supported | not applicable | not applicable | not applicable |
Expectation: convey boundaries
Rationale:
Screen reader users need to know when they enter and exist a grid
Strength of this expectation for different types of assistive technologies:
- Screen Readers: MUST
- Voice Control: NA
Examples:
- Screen readers might say something like "entering grid" and "exiting grid"