Add defensive checks for the trap focus implementation

Progress® Telerik® UI for Blazor Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Unplanned

Last Updated: 04 Aug 2025 14:55 by Sean

Alexander

Created on: 18 Sep 2024 10:52

Category: Window

Type: Feature Request

Add defensive checks for the trap focus implementation

If the last element in the window has tabindex="-1" or the last element is hidden using "display: none", the focus is no longer trapped inside the window and can go to elements outside of it.

4 comments

Sean

Posted on: 04 Aug 2025 14:55

Also happens when a Telerik PanelBar is the only/last component in a Telerik modal window...focus trap does not work. Focus goes to the first item in the PanelBar and then focus goes to the browser window and then to all controls underneath overlay.
After reading this and as a work-around, I have to put a button in the window as the last focusable component. This is extraneous and not necessary.

Alexander

Posted on: 24 Sep 2024 13:33

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" ...

ADMIN

Hristian Stefanov

Posted on: 23 Sep 2024 11:09

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.

Stefan

Posted on: 23 Sep 2024 09:14

Important: This is not a feature but a bug. It means that the software does not meet our customers' requirements when checking accessibility. Please change the type. Thanks.