Specifically, if the div mentioned in the error does not have tabindex=1, tabbing from the header causes the browser to focus that area, which is not the expected behavior. Ideally, the focus should move to the first cell, as that intermediate area is not user-interactive.

On the other hand, if tabindex=-1 is used, tools like Аxe and Lighthouse report errors. Removing the tabindex attribute altogether still results in errors, and the browser continues to focus that area.

We are actively exploring possible approaches to address this, but at the moment, there is no immediate solution we can apply without side effects.