[Webkit-unassigned] [Bug 179012] New: AX: VoiceOver skips legends after following in-page link on iOS 10
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Oct 30 08:05:56 PDT 2017
https://bugs.webkit.org/show_bug.cgi?id=179012
Bug ID: 179012
Summary: AX: VoiceOver skips legends after following in-page
link on iOS 10
Product: WebKit
Version: Safari 10
Hardware: iPhone / iPad
OS: iOS 10.3
Status: NEW
Severity: Normal
Priority: P2
Component: Accessibility
Assignee: webkit-unassigned at lists.webkit.org
Reporter: anika.henke at digital.cabinet-office.gov.uk
CC: webkit-bug-importer at group.apple.com
When following in-page links, VoiceOver doesn't always read out the next text. This is at least true for paragraphs, inputs and legends. This is not too bad because the text gets read out when swiping further, except for legends. When jumping to a legend and swiping further, the text of the legend is entirely skipped, even when swiping back and forth again. This does not happen when swiping without having followed the link.
It's difficult to tell if this is still true on iOS 11 due to another bug [https://bugs.webkit.org/show_bug.cgi?id=179011].
Steps to reproduce:
1. Activate VoiceOver (on iOS 10)
2. Open http://jsbin.com/wumitiw in Safari
3. Navigate to "link to legend"
4. Follow the link (i.e. double tap)
5. Swipe further
Result:
The text for the legend is not read out.
Expected:
The legend should be read out, if not directly after following the link, at least after swiping further.
Why is this a problem?
Legends (and fieldsets) are not always just used to group form elements, they can contain information that is vital to understand and complete a form. E.g. with Yes and No questions, you would have Yes and No labels for the radio buttons but the actual question would often be in a legend. It would be impossible for screen reader users to know what the question was if they followed a link to it. And in-page links are typical for pointing users to specific errors after they submitted a form.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20171030/48f62028/attachment-0001.html>
More information about the webkit-unassigned
mailing list