Bug 244973 - AX: Invalid summary elements should not be exposed as interactive
Summary: AX: Invalid summary elements should not be exposed as interactive
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: WebKit Nightly Build
Hardware: All All
: P2 Normal
Assignee: Tyler Wilcock
URL:
Keywords: InRadar
Depends on:
Blocks: 252223
  Show dependency treegraph
 
Reported: 2022-09-09 06:46 PDT by Scott
Modified: 2023-02-20 10:27 PST (History)
11 users (show)

See Also:


Attachments
Patch (5.54 KB, patch)
2023-02-18 23:42 PST, Tyler Wilcock
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Scott 2022-09-09 06:46:10 PDT
If a summary element is misused - e.g., specified outside of a details element, or multiple summary elements are specified within a details element, the errant summary element(s) are not rendered as interactive elements (good). However, Firefox still exposes them as interactive elements, which is not reflective of their behavior.

For instance, the following codepen has a summary element without a details parent, as well as two summary elements within a details parent https://codepen.io/scottohara/pen/poVyeNV

The invalid summary elements are visually rendered as static text. But as they are not interactive, they should be exposed as generic elements. However, VoiceOver will announce the elements no differently than correctly used summary elements.

I've made a PR to HTML AAM to clarify this in the spec as well.
https://github.com/w3c/html-aam/pull/436
Comment 1 Radar WebKit Bug Importer 2022-09-09 06:46:24 PDT
<rdar://problem/99743056>
Comment 2 Radar WebKit Bug Importer 2022-09-09 06:47:06 PDT
<rdar://problem/99743073>
Comment 3 Tyler Wilcock 2023-02-18 23:42:15 PST
Created attachment 465071 [details]
Patch
Comment 4 EWS 2023-02-20 10:27:43 PST
Committed 260546@main (96801f719dfc): <https://commits.webkit.org/260546@main>

All reviewed patches have been landed. Closing bug and clearing flags on attachment 465071 [details].