Bug 232569

Summary: AX: meter and progress elements are ignored when -webkit-appearance: none is set
Product: WebKit Reporter: Nathan Knowler <nathan>
Component: AccessibilityAssignee: Nobody <webkit-unassigned>
Status: NEW ---    
Severity: Normal CC: akeerthi, andresg_22, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Safari 15   
Hardware: Mac (Intel)   
OS: macOS 11   
Attachments:
Description Flags
This HTML document is a minimal reproduction of the issue. none

Description Nathan Knowler 2021-11-01 09:51:26 PDT
Created attachment 442984 [details]
This HTML document is a minimal reproduction of the issue.

Overview:

Both the meter and progress elements are ignored in the accessibility tree when `-webkit-appearance: none` is set. This CSS rule is required to provide custom styles for the element.

Steps to Reproduce:

The following has been reproduced in the attached HTML document.

1. Use a meter or progress element in a document.
2. Set `-webkit-appearance: none` on the element in order to "remove" the UA styles to provide custom ones.
3. Test the accessibility of the element.
  a. Using VoiceOver, try to select the element on the page. It’s not possible.
  b. Using the Web Inspector, in the Elements panel, select the element, and, then in Node panel of the Details sidebar, go to the Accessibility section to see that Ignored is set to "Yes" and Role is set to "No matching ARIA role."

Actual Results:

The element can be styled as expected, however, it is no longer accessible by virtue of the fact that `-webkit-appearance: none` has been set. The element seems to have lost its implicit ARIA role and therefore is ignored.

Expected Results:

Authors should be allowed to use `-webkit-appearance: none` to remove the user agent styles for the meter and progress element (as currently works in Safari) without breaking the accessibility of the elements.

Build Date & Hardware:

- macOS 11.6
- Safari Version 15.0 (16612.1.29.41.4, 16612)
Comment 1 Radar WebKit Bug Importer 2021-11-01 09:51:55 PDT
<rdar://problem/84885223>
Comment 2 Nathan Knowler 2021-11-01 10:53:28 PDT
This is reproducible in Safari Technology Preview Release 134 (Safari 15.4, WebKit 16613.1.6.1) as well.