Carbon: AVT 3 - Tile Selectable: VoiceOver does not announce when a selectable tile is checked or unchecked

Created on 18 Apr 2019  ·  9Comments  ·  Source: carbon-design-system/carbon

Environment

macOS Mojave version 10.14.2
Chrome version 72.0.3626.96 (Official Build) (64-bit)

Detailed Description

With VoiceOver enabled tab to the selectable tile that is checked (selectable tile 2)

Expected Result

VoiceOver announces when the selectable tile is checked and unchecked.

Note: Based on the selectable tiles type="radio" the selectable component should follow the ARIA Authoring Practices 1.1 design pattern for radio group which requires aria-checked attribute set on the selectable tiles.

high 😱 react 1 🚨 a11y ♿

All 9 comments

Testing on latest macOS and chrome here's what I have:

VO on selected tile:
Screen Shot 2019-04-22 at 12 22 39 AM

VO when another tile is selected:
Screen Shot 2019-04-22 at 12 23 28 AM

Maybe specifically we need "checked" and "unchecked" here _according to the letter of the law_, but since the component is described by VO as a "selectable tile" describing it as "selected" seems to make more sense.

@dakahn The issue is not that about the word "selected" vs "checked". When I test with VO the announcement of the selected state is inconsistent. For example, If I tab to the default tile (2) VO announces that it is selected... as in your screenshot. If I then tab to the next tile and hit the Enter key to select it, VO announces "You are currently on a group. To interact with items in this group press Control-Option-Shift-Down Arrow."
Screen Shot 2019-04-22 at 8 07 11 AM

In order to hear VO announce the selected state, I have to tab back to the selected radio button. In the ARIA Authoring practices example, the state is announced as soon as the selection is made.

We've marked this issue as stale because there hasn't been any activity for a couple of weeks. If there's no further activity on this issue in the next three days then we'll close it. You can keep the conversation going with just a short comment. Thanks for your contributions.

@dakahn This issue needs to be labeled A11y and React.

We've marked this issue as stale because there hasn't been any activity for a couple of weeks. If there's no further activity on this issue in the next three days then we'll close it. You can keep the conversation going with just a short comment. Thanks for your contributions.

@dakahn Retested and this is still an issue.

Hi @snidersd! I am not able to reproduce this problem with VO on Safari, would you be able to check for me to see if this is still a problem you're encountering?

@abbeyhrt Retested and I no longer see the issue.

Okay great, thanks for looking into it! I'm going to close this issue since it has been addressed 👍

Was this page helpful?
0 / 5 - 0 ratings