7 Answers, 1 is accepted
WCAG 2.0 specification has quite a lot of requirements and some of which are related to the web site itself rather than the UI components it is using. Here is a quick checklist for example: http://www.w3.org/WAI/WCAG20/quickref/
What requirements do you need to meet with Kendo UI? Clearly some of the requirements are not applicable for Kendo UI whereas other are.
the Telerik team
I later tried the same keyboard navigation test with the jQueryUI Accordian control, and found the same result: It didn't work.
But, much to my surprise, I later found that inside a Chrome browser, the KendoUI and jQueryUI widgets were both keyboard-navigable. I had previously been using Internet Explorer 9. (I'm most surprised that the Microsoft browser lacked this basic accessability, as they are normally big on such standards.)
I don't know what the technical issue is here. Is there something lacking in IE9 that prevents your widgets from being keyboard-navigable?
Thanks for your great work.
We haven't implemented any keyboard navigation for the panelbar. What you are seeing is entirely browser behavior.
Once we add more accessibility features we would add keyboard navigation which will work cross browser.
the Telerik team
Is there any more information available about WCAG 2.0 accessibility for Kendo UI controls? We're trying to make a decision on which product to use and could really use some up-to-date information.
I'll have a dig around your site but if you could give us an idea of what does and does not work that would be excellent.
It would be very helpful if we can get a timeframe of when Accessibility features (specially Keyboard Navigation) will be added to Kendo UI controls. If there is a road map of when these will be added, please share it.
This is a core requirement and our decision to pick Kendo UI depends on it.