core-aam Mac mappings for aria-valuemax on indeterminate progress bars

Safari on MacOS seems to work well with indeterminate progress bars. Chrome does not seem to work so well (reads a value of 0%)

Looking at the mapping exposed by the browser it seems that safari is exposing AXMaxValue of 0 for an indeterminate progress bar despite what the spec says. This seems to make voiceover read as indeterminate.

Suggest we check with @cookiecrook and maybe update Core-AAM with this information so Chrome can do the same

Dec 19 '19 23:12 jnurthen

See https://bugs.webkit.org/show_bug.cgi?id=142887 for webkit implementation details

Dec 20 '19 16:12 jnurthen

I don't see in the Core AAM table how indeterminate aria-value[*]s are listed for any API, so I'm not sure what edit to propose.

Jan 02 '20 23:01 cookiecrook

@joanmarie Any suggestions for how to document something like this in Core-aam?

Jan 02 '20 23:01 jnurthen

Spitballing: Add a new row for "indeterminate aria-valuenow for progressbar or scrollbar"?

Jan 02 '20 23:01 cookiecrook

@joanmarie Any suggestions for how to document something like this in Core-aam?

The new row proposed by @cookiecrook makes sense to me. If you look in the states and properties tables in Core-AAM, we already have value-specific dedicated entries.

Jan 03 '20 07:01 joanmarie