Bug 204049

Summary: AX: VoiceOver on iOS 13 cannot click input type date elements
Product: WebKit Reporter: awumstead
Component: AccessibilityAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: bdakin, cfleizach, diane.ko, jcraig, me, nurthen, pxlcoder, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Other   
Hardware: All   
OS: All   

awumstead
Reported 2019-11-09 09:06:12 PST
When double-tapping an input type=date element in VoiceOver in Safari on iOS 13, the date picker does not open. Tapping it without VoiceOver on works fine. Tested on iOS 13.2, but I’ve seen this on earlier versions of 13. This does not seem to be an issue in iOS 12. Steps to reproduce: 1. Open https://codepen.io/mra11yx/pen/bGGKOYQ when VoiceOver is running 2. Swipe to any of the inputs and double tap.
Attachments
Radar WebKit Bug Importer
Comment 1 2019-11-09 09:06:28 PST
Diane Ko
Comment 2 2019-12-02 16:15:51 PST
FYI - I did find that if there's another input field (like a text field), if you activate that with VoiceOver first and then go back to the date field, it'll open. Example pen to test this on: https://codepen.io/backwardok/pen/WNbNyBW.
awumstead
Comment 3 2020-05-24 19:48:09 PDT
What’s the latest update on resolving this bug? It still exists in iOS 13.5, six months after I logged this issue. Voiceover users are almost completely blocked from being able to use native date pickers on Web right now, unless they can figure out unintuitive hacks like manually browsing to the input label (which isn’t swipeable) and double-tapping it.
James Nurthen
Comment 4 2020-08-05 12:59:52 PDT
can still reproduce on iOS14 beta 4
chris fleizach
Comment 5 2020-09-15 23:45:05 PDT
This should be resolved in iOS14 beta 6
awumstead
Comment 6 2020-09-16 09:00:07 PDT
I’ve seen the same thing in beta 6 and later ones. Waiting to see if the fix still persists in the production release.
chris fleizach
Comment 7 2020-09-16 10:05:21 PDT
(In reply to awumstead from comment #6) > I’ve seen the same thing in beta 6 and later ones. Waiting to see if the fix > still persists in the production release. this appears to work for me with this website
Note You need to log in before you can comment on or make changes to this bug.