scrollbar is not output (Firefox, Chrome)

JAWS-test commented 5 years ago

Summary

scrollbar is not output

save as HTML file:

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="utf-8">
    <title>scrollbar</title>
</head>
<body>
    <a href="#">test</a>
    <div id=1>scrollable area</div>
    <div tabindex='0' role='scrollbar' aria-valuemax=30 aria-valuemin=0 aria-valuenow=15 aria-label=scrollbar aria-controls=1 aria-orientation=vertical>---</div>
</body>
</html>

Navigate with Tab key

Expected result

Correct output of role, label and value (aria-valuemin, -max, -now), alignment (aria-orientation) and if necessary of scrollable area (aria-controls) for the different navigation methods (tab, linear reading, quick navigation (F)) and in the element overview (INS+F5). See: https://www.w3.org/TR/wai-aria-1.2/#scrollbar

Actual result

Chrome: tab navigation: Output of the previous interactive element; no output when reading with arrow keys
Firefox: no output (only "graphic" when reading with arrow keys)
IE 11: tab navigation: output as "scrollbar", reading with arrow keys: output as "slider". No output of aria-valuemin/max

Additional Information

JAWS version and build number

JAWS 2019.1906.10

Operating System and version

Windows 10

Browser and version:

Internet Explorer 11.0.9600.19400 Chrome 75.0.3770.100 Firefox 60.8.0 ESR

lamador commented 4 years ago

When using JAWS 2020.2008.24 (JAWS) with IE11 11.1139.18362.0 on Windows 10, the accessible name, {{scrollbar}} role and the {{aria-valuenow}} value announced when using tab navigation. When using arrow keys/virtual cursor, "up down slider" and the {{aria-valuenow}} value are announced.

When using JAWS with Firefox 81.0.2 on Windows 10, the ARIA role and attributes are properly exposed in the accessibility tree, but only the accessible name is announced when using tab navigation. When using arrow keys/virtual cursor, the dashed are annouced as a graphic.

When using JAWS with Chrome 86.0.4240.75 on Windows 10, the ARIA role and attributes are properly exposed in the accessibility tree, but the accessible name is announced and the control is misidentified as a visited link when using tab navigation.. The virtial cursor does not detect/place focus on the scrollbar at all.

stevefaulkner commented 11 months ago

JAWS does not announce the scrollbar role/accessible name test case

FreedomScientific / standards-support