Bug 220086

Summary: AX: <details> element cannot be interacted with using Voice Control
Product: WebKit Reporter: Oliver Byford <oliver.byford>
Component: AccessibilityAssignee: Joone Hur <joone>
Status: RESOLVED MOVED    
Severity: Normal CC: aboxhall, apinheiro, cfleizach, dmazzoni, ews-watchlist, jcraig, jdiggs, joone, samuel_white, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Safari 14   
Hardware: Mac (Intel)   
OS: macOS 10.15   
Attachments:
Description Flags
Screenshot of numbers overlay without an overlay for the details element
none
Example HTML
none
Patch cfleizach: review-

Description Oliver Byford 2020-12-22 08:11:39 PST
Created attachment 416664 [details]
Screenshot of numbers overlay without an overlay for the details element

Given the following markup:

    <a href="https://www.google.com">Google</a>

    <br><br>

    <details>
    <summary>Details</summary>
    <p>These are the details!</p>
    </details>

    <br><br>

    <button type="button">Click me</button>

    <br><br>

    <a href="https://www.google.com">Google</a>


With Voice Control enabled, say 'Click Details'

Expected behaviour: The details element should be expanded.
Actual behaviour: Nothing happens.


Alternatively, you might try saying 'Show numbers' –

Expected behaviour: A number overlay should appear near the 'Details' summary, allowing you to interact with it by saying 'Click [number]'
Actual behaviour: No number overlay is shown for the 'Details' summary element (see screenshot)
Comment 1 Radar WebKit Bug Importer 2020-12-22 08:11:50 PST
<rdar://problem/72588051>
Comment 2 Oliver Byford 2020-12-22 08:12:01 PST
Created attachment 416665 [details]
Example HTML
Comment 3 Joone Hur 2021-03-08 00:54:14 PST
Created attachment 422549 [details]
Patch
Comment 4 chris fleizach 2021-03-09 12:44:59 PST
Comment on attachment 422549 [details]
Patch

Hi Joone. Thanks for the patch. But I think this needs to be fixed by Voice Control. Marking this as a button is not technically correct. VC needs to allow this object to be tappable I think
Comment 5 chris fleizach 2021-03-09 12:46:13 PST
Moved to internal component. Voice control will need to support this
Comment 6 Oliver Byford 2021-03-10 01:38:30 PST
Thanks both for looking into this.

Is there any way to stay up to date with the bug now it's been moved to Voice Control? Or is it just internally tracked from here?
Comment 7 chris fleizach 2021-03-10 07:11:05 PST
Unfortunately not really. You could create a duplicate feedback and follow along with that but that’s a bit of unnecessary work.