Bug 136687

Summary: AX: VoiceOver in Safari on Mac OS misidentifies text fields as search fields
Product: WebKit Reporter: Kasper Munck <kmunck>
Component: AccessibilityAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: bfulgham, cfleizach, commit-queue, darin, jcraig, webkit-bug-importer
Priority: P4 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: Mac   
OS: OS X 10.9   
Attachments:
Description Flags
Sample html file illustrating the problem. none

Description Kasper Munck 2014-09-09 16:49:48 PDT 
When VoiceOver encounters an input field with a "search" keyword in one of the attributes, it believes the field in question is a search field.

Steps to Reproduce:
1. Launch VoiceOver with CMD-F5 and open Safari.
2. Load the attached file.
3. Tab to the "First Name" field and listen to the feedback from VoiceOver.

Expected Results:
VoiceOver should say "first name text field".

Actual Results:
VoiceOver says "first name search text field".
Comment 1 Kasper Munck 2014-09-09 16:50:38 PDT 
Created attachment 237872 [details]
Sample html file illustrating the problem.
Comment 2 WebKit Commit Bot 2014-09-09 16:51:37 PDT 
Attachment 237872 [details] did not pass style-queue:


Total errors found: 0 in 0 files


If any of these errors are false positives, please file a bug against check-webkit-style.
Comment 3 Darin Adler 2014-09-10 08:38:13 PDT 
This problem is an intentional strategy.

See the function AccessibilityNodeObject::isSearchField.

So we won’t take the code out just because of this test case. VoceOver needs to treat fields as search fields when that’s appropriate, not just when the web engine is using its special search field styling and support. If we wanted to change the heuristic here about which fields are treated as search fields, we’d need some evidence that it would help on more websites than it would hurt on.
Comment 4 Radar WebKit Bug Importer 2014-09-11 15:29:37 PDT 
<rdar://problem/18312423>