I have tested JAWS 17 reader with Chrome and with IE 11. While testing in Chrome, I was able to reproduce the error, which was not present in IE 11. Generally, Chrome is known for causing issues
like the observed, while using JAWS as screen reader. The reason for that is, that each screen reader is developed to work best in one of the browsers
, therefore issues, while using it with others may arise.
Because of the above inconsistency of browsers and readers, the Kendo UI suite is tested to follow the Section 508
and the WAI AREA
specification. A reliable tool for performing the abode validation is the WAVE validator
I hope, that the above explains a bit, why issues as the discussed could be observed while using different screen readers in different browsers.
Telerik by Progress