Bug 273589 - AX: dynamic meter elements are not accessible
Summary: AX: dynamic meter elements are not accessible
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: WebKit Nightly Build
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2024-05-01 16:12 PDT by James Craig
Modified: 2024-05-02 15:44 PDT (History)
3 users (show)

See Also:

Attachments
test case (1.88 KB, text/html)
2024-05-01 16:12 PDT, James Craig 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James Craig 2024-05-01 16:12:10 PDT 
Created attachment 471244 [details]
test case

AX: dynamic meter elements are not accessible

WebKit uses AXValueDescription, which doesn't seem to be the best choice for a dynamic meter like an audio level meter. (First example in the test case)

Instead of verbose string concatenation, WebKit should convey these like native audio meter elements (at time of filing, I'm not sure which API to use). Among other things, VO/WebKit doesn't ever seem to pass along any value updates to the user.
Comment 1 Radar WebKit Bug Importer 2024-05-01 16:13:34 PDT 
<rdar://problem/127392049>
Comment 2 Dominic Mazzoni 2024-05-01 16:36:45 PDT 
I think the correct role mapping on macOS is AXLevelIndicator, treat it as similar to an AXSlider in terms of the attributes to implement
Comment 3 James Craig 2024-05-02 15:44:30 PDT 
Role is already AXRole:AXLevelIndicator/AXSubrole:AXMeter... Min, Max, and value exposed already. Value description (example "optimal value") is overriding the numeric value here, and VoiceOver isn't speaking updates.


Should the overriding value description instead be a status indicator instead?