[Webkit-unassigned] [Bug 176710] AX: Fields that are autofill-able but don't have an AutoFill button should still be announced as autofill-able

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Sep 11 11:13:33 PDT 2017


--- Comment #5 from Maureen Daum <mdaum at apple.com> ---
Comment on attachment 320441
  --> https://bugs.webkit.org/attachment.cgi?id=320441

View in context: https://bugs.webkit.org/attachment.cgi?id=320441&action=review

>> Source/WebCore/ChangeLog:12
>> +        * accessibility/AccessibilityObject.cpp:
> can you add a test? thanks

Sure thing!

>> Source/WebCore/accessibility/AccessibilityObject.cpp:2464
>> +    return downcast<HTMLInputElement>(*node).isAutoFillAvailable() || downcast<HTMLInputElement>(*node).autoFillButtonType() != AutoFillButtonType::None;
> will isAutoFillAvailable() always be true if button type == None?
> how will users activate auto fill if there's no button to press?

isAutoFillAvailable() will only be true on the text fields that Safari sets it on. Users can use the arrow keys to activate autofill. The VoiceOver announcement specifies, "To open the autofill menu, press the up or down arrow key, then press the return key to enter it into the 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/20170911/3965aa1f/attachment.html>

More information about the webkit-unassigned mailing list