Focus Lock navigates to wrapper with tabIndex="-1" when using props "shards"

[siarhei-epam]

Issue Description

When using react-focus-lock (version 2.13.5) with props shards and rendering a dialog wrapped in a component with tabIndex="-1", the focus lock incorrectly includes the wrapper in the tab navigation sequence.

According to accessibility standards, elements with tabIndex="-1" should be programmatically focusable but not included in the keyboard tab sequence. However, the focus lock is navigating to this wrapper when tabbing through the dialog.

Steps to Reproduce

1. Open the CodeSandbox demo
2. Click the "Open modal 2" button to open the dialog
3. Press 'Tab' once
4. Observe that the component with tabIndex="-1" receives focus, which should not happen

Expected Behavior

The focus lock should skip elements with tabIndex="-1" during keyboard navigation, as these elements should only be focusable programmatically but not part of the tab sequence.

Environment

• react-focus-lock version: 2.13.5
• React version: (as specified in the CodeSandbox)

[theKashey]

I dont have any verification on this yet, I probably without autofocus enabled it just cannot understand what it should be doing. Ideally mark one of the buttons as default focus reciever - wrap with AutoFocusInside

[siarhei-epam]

I expect focus movement according to HTML specifications and published on MDN. This means that when sequentially moving the focus when pressing Tab, I should not focus on elements with tabindex="-1".

[theKashey]

This moment is less what it should do and more about why it decided to do something.
It's obviously a bug, and likely related to another one

[siarhei-epam]

Can I expect a fix for this bug? This is a blocker for releasing a component improvement in the "@epam/uui" open-source library

[siarhei-epam]

This issue is relevant and awaits resolution
dependency

[stale]

This issue has been marked as "stale" because there has been no activity for 2 months. If you have any new information or would like to continue the discussion, please feel free to do so. If this issue got buried among other tasks, maybe this message will reignite the conversation. Otherwise, this issue will be closed in 7 days. Thank you for your contributions so far.

[dsv-sergey]

Sorry but it doesn't completed