The tabs feature requires nested interactive controls which are not allowed from an accessibility perspective

We run the AXE accessibility checker on our application.
This flags an issue on the elements we use  for the tabs feature.

See the following documentation on this issue.

https://dequeuniversity.com/rules/axe/4.10/nested-interactive?application=axeAPI

There needs to be a way to structure the elements for this tabs feature without nesting interactive controls.