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".
Created attachment 237872 [details] Sample html file illustrating the problem.
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.
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.
<rdar://problem/18312423>