You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
@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.
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
The text was updated successfully, but these errors were encountered: