meter is not output correctly

[JAWS-test]

Summary

1. Go to https://w3c.github.io/aria-practices/examples/meter/meter.html
2. read with arrow keys

Expected result

• Role is output correctly
• Labeling is output
• Value is output in relation to maximum and minimum value, i.e. as a percentage or maximum and minimum value is also output because it is pointless to output the value alone
• Value changes are not automatically output

Actual result

Chrome, Edge:

• Role is not output correctly (is output as progressbar, this is a Chrome/Edge error (see https://github.com/w3c/html-aam/issues/2), the rest are JAWS errors)
• Labeling is not output
• only the value is output
• Value changes are automatically output (meter is interpreted as live region)
• The HTML element meter is also output without the label, without min, max, low, high, optimum or an output of the colour-coded information. But the output of the role is correct

IE 11, Firefox:

• There is no output at all, the element with role=meter is not available to JAWS
• In Firefox the problem also occurs with the HTML element meter. IE 11 does not know the element and does not display it

Additional Information

JAWS version and build number

JAWS 2020.2013

Operating System and version

Windows 10

Browser and version:

Chrome 84.0.4147.105 IE 11 Firefox ESR 68.11.0 Edge 84.0.522.49

[frex65]

When the text node within an element that acts as a meter is different from its value (for example, when a meter is showing a C exam result as an approx 50% mark), what should be the expected output? The meter's value? Its text node? A hybrid of both such as "C (50%)"?

[JAWS-test]

This should rather be a question for the ARIA specification. This specification requires that aria-valuetext is output instead of aria-valuenow, if present. Otherwise, only aria-valuenow should be output. To what extent the text content of the HTML element meter or the ARIA role meter should be interpreted as aria-valuetext is not known to me and to my knowledge not specified at this time.

In any case, Chrome, for example, currently does not transmit text content of the meter to the Accessibility API and is therefore not available to JAWS