Bug 221065
Summary: | AX: VoiceOver for iOS does not announce required state for an input with both aria-required="true" and aria-roledescription | ||
---|---|---|---|
Product: | WebKit | Reporter: | Michael Jordan <mijordan> |
Component: | Accessibility | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED MOVED | ||
Severity: | Normal | CC: | andresg_22, cfleizach, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | Safari 14 | ||
Hardware: | iPhone / iPad | ||
OS: | iOS 14 | ||
URL: | https://codepen.io/majornista/pen/gOLYgZd |
Michael Jordan
VoiceOver for iOS does not announce the required state for an input element with both aria-required="true" and aria-roledescription.
For a numeric input stepper that can render its value using currency or other Intl.NumberFormat options, we use aria-roledescription to identify the text input as a "Number field".
With VoiceOver for iOS, the input role is announced using the aria-roledescription value, however the required state gets omitted.
With VoiceOver for macOS, the input role is announced as "edit text", and the required state is announced, which I suspect may be because aria-roledescription is being ignored entirely.
The expected behavior would be for states like aria-required to be announced for elements using aria-roledescription.
Here is a url to an example comparing the behavior of two inputs, one that has aria-roledescription and a second without: https://codepen.io/majornista/pen/gOLYgZd
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/73682673>
Smoley
Thanks for filing, I can reproduce this on iOS 13.6.1 and the latest 14.4 beta. Ccing relevant folks.
chris fleizach
The macOS bug reported (lack of role desc on text field) is a VoiceOver bug. I've sent a clone of the issue to them: (<rdar://problem/73777103>
chris fleizach
The iOS issue is also in VoiceOver. I will use this radar to fix the issue there. since no webKit change is required, I will close out this bug. You'll be able to check on the iOS issue in the next update. Not sure about macOS right now