gridcell role (aria)
Screen reader support level: partial (19/20)
Voice Control support level: partial (2/9)
On this page
About this feature
A cell in a grid or treegrid.
Age of results
Results across all tests for this feature range from 5 months ago to 7 months ago. Detailed dates and version information can be found in associated tests.
Failing and partial results are between 7 months ago and 7 months ago.
Expectations
Screen Reader support by expectation
| Expectation | JAWS | Narrator | NVDA | Orca | TalkBack | VoiceOver (iOS) | VoiceOver (macOS) | |||
|---|---|---|---|---|---|---|---|---|---|---|
| Chrome | IE | Firefox | Edge | Chrome | Firefox | Firefox | Chrome | Safari | Safari | |
| MUST convey an appropriate role | supported | supported | supported | supported | supported | supported | supported | partial | supported | supported |
| MUST convey an appropriate name | supported | supported | supported | supported | supported | supported | supported | supported | supported | supported |
Voice Control support by expectation
| Expectation | Dragon Naturally Speaking | Voice Access (Android) | Voice Control (iOS) | Voice Control (MacOS) | Windows Speech Recognition |
|---|---|---|---|---|---|
| Chrome | Chrome | Safari | Safari | Chrome | |
| MUST convey an appropriate role | none | supported | not applicable | none | none |
| MUST convey an appropriate name | none | partial | supported | none | none |
Expectation: convey an appropriate role
Rationale: A screen reader user needs to know how they can interact with the element. Voice control software might use the role to help users activate controls that do not have a visible name.
Strength of these expectations for different types of assistive technologies:
- Screen Readers: MUST
- Voice Control: MUST
Examples of assistive technologies support this expectation:
- A screen reader might announce "grid cell"
- A screen reader might announce "cell"
- A screen reader might imply the role by announcing other table semantics
- A screen reader might imply the role by support table navigation
| Test | JAWS | Narrator | NVDA | Orca | TalkBack | VoiceOver (iOS) | VoiceOver (macOS) | |||
|---|---|---|---|---|---|---|---|---|---|---|
| Chrome | IE | Firefox | Edge | Chrome | Firefox | Firefox | Chrome | Safari | Safari | |
| ARIA gridcell role | supported | supported | supported | supported | supported | supported | supported | partial | supported | supported |
| Test | Dragon Naturally Speaking | Voice Access (Android) | Voice Control (iOS) | Voice Control (MacOS) | Windows Speech Recognition |
|---|---|---|---|---|---|
| Chrome | Chrome | Safari | Safari | Chrome | |
| ARIA gridcell role | none | supported | not applicable | none | none |
Expectation: convey an appropriate name
Rationale: A screen reader user needs to know what to enter.
Strength of these expectations for different types of assistive technologies:
- Screen Readers: MUST
- Voice Control: MUST