Unplanned
Last Updated: 28 Oct 2019 21:02 by Jeff
Jeff
Created on: 02 Apr 2019 14:16
Category: AutoCompleteBox
Type: Bug Report
1
AutoCompleteBox with ARIA support enabled, JAWS 18 does not read individual list items when selecting

https://demos.telerik.com/aspnet-ajax/autocompletebox/examples/accessibility-and-internationalization/wai-aria-support/defaultcs.aspx

While JAWS will announce all of the items in the list as results are first read, it only says "Blank" as you arrow through the available options. Tabbing out of the control and back in, also does not read the selected content.

This is basically the opposite of what happens when ARIA support is turned off.

 https://demos.telerik.com/aspnet-ajax/autocompletebox/examples/default/defaultcs.aspx

In that case, there is no announcement when results come back, but JAWS will read each individual item as you arrow through the available choices. Tabbing out of the control and back in still does not cause JAWS to read the selected item. 

This makes it seem like the ARIA version of the autocomplete box is missing either the appropriate ARIA roles or some other piece of rendered markup that is present in the non-ARIA-enabled version.

 

Ideally, when working with screen readers,  we would like to see something like the following behaviors:

* The number of items are announced when results are loaded, including empty results

* Each item is announced as the focus is moved through the list

* The selected item is announced when picked or whenever focus returns to the field. 

2 comments
Jeff
Posted on: 28 Oct 2019 21:02
This appears to work better with JAWS 19 and Telerik 2019.3. Behavior is different in different browsers, but the experience seems better in all of them. Chrome announces the first item and the count on focus and then reads each item as you move through the list. IE announces the entire list of items, but also announces each item as you move through the list.
ADMIN
Peter Milchev
Posted on: 02 Apr 2019 14:25
Hello Jeff,

The issue can be replicated with a simple HTML and JS scenario(index.zip attachment) and it seems to be an issue with the Reader or the browsers. Unfortunately, we do not have any workaround that would fix this. 

Once we have a solution or a workaround for this case, we will share it here.

Regards,
Peter Milchev
Progress Telerik
Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
Attached Files: