Just for reference:
Here is a simple REPL demonstrating the problem with "display: none" by combining two standard Telerik components, "TelerikWindow" and "TelerikTabStrip": https://blazorrepl.telerik.com/cIENwylx16bIoHrU57
Here is a simple REPL demonstrating the problem with "tabindex: -1" by combining two standard Telerik components, "TelerikWindow" and "TelerikGrid": https://blazorrepl.telerik.com/GSaXQelH31FUphsD07
I am not sure combining two standard Telerik components can be considered a "scenario [that] is uncommon" ...
Hi Stefan,
Thank you for sharing your thoughts on the item.
I can confirm that the Window component adheres to the official accessibility standards, following WAI-ARIA best practices for keyboard navigation based on its role. It's also tested with popular screen readers to ensure compliance.
In this particular case, the behavior is not classified as a bug because the keyboard navigation design did not intend to include elements with "display: none" or "tabindex -1" as navigable items. This scenario is uncommon. If the focus did not work correctly on actual focusable elements, we would have considered it a bug rather than an enhancement.
Regards,
Hristian Stefanov
Progress Telerik
Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.