Accessibility: Navigate

[Jan]

Hello,

 

if you navigate through the listview items, the parents aria-activedescendant is never updated. Just the elements get an updated ID attribute. This is a wrong behaviour. Every item needs an ID and the aria-activedescendant needs to be updated.

„When the composite widget contains focus and the user presses a navigation key that moves focus within the widget, such as an arrow key: Change the value of aria-activedescendant on the container to refer to the element that should be reported to assistive technologies as active“ (http://www.w3.org/TR/wai-aria-practices-1.1/#kbd_focus_activedescendant).

I would also prefer to get an updated aria-selected on navigate and not on "mark" an item. You should test the widgets with a screenreader like JAWS. When I navigate through the listview, the screenreader is not triggered, so it is impossible for a person who relies on a screenreader to control this widget.

[Jan]

I just found out that I need to apply an ID to every item (extend the root item of my template by the ID attribute). Now the aria-activedescendant gets updated correctly!

[Jan]

I have to correct my first post. The problem does not begin, that the screenreader is not reading the item, but I cant navigate, because the screenreader does not recognize the focused listview as form item in IE11 (Although I added the ID attribute). The arrows are reserved for the screenreader to jump between the textual content of the page but if you are in form mode, it disables this function to control the form item. As I said this does not happen in IE11 with the listview.

[Stefan]

Hello Jan,

I made an example where every list item has a unique ID attribute and the aria-activedescendant attribute gets updated accordingly when navigating through the items in Internet Explorer 11:

http://dojo.telerik.com/AkumuD

Could you please modify the example to demonstrate the described issue?

Also, providing a short video demonstration will be helpful as well.

This will help us improve our widgets accessibility.

Please have in mind that sometimes the readers are may behave differently depending on the browser and the Kendo UI team has no full control over this if the aria specific attributes are set correctly.

Regards,
Stefan
Progress Telerik

[Jan]

Totally correct. You can see this thread as solved.

The problems continue here: http://www.telerik.com/forums/accessibility-screenreader