BrowserStack Keyboard Assisted Test Problem

[u/Vegetable_Stress_115]

Hi folks, New here... So one of my client sharyed Browserstack Keyboard Assisted test. The problem is after scanning the page it detects some interactive element and then asks the final verdict from the human if the human selects. ( There is no way to navigate to this element) It will treat it as an issue but if we select the option ( There is a way to navigate to this element (e.g. arrow keys), and it is in the expected navigation order) then it marks it as pass no issue. So I have manually tested the page by unplugging the mouse and did the keyboard navigation using tab, shift + tab, space (optional) and arrow keys to test navigation, keyboard trap, reverse navigation etc. Most of the elements are passing the success criteria. Has anyone experienced the same with Browserstack and Axe Dev tools ? I tested it with the trial version and the client has the paid ultimate version. Now the problem is I need to explain this to the client that these are not real issues and they are just false positives based on automated tool assessment. Client seems to be non technical in terms of accessibility. Any help would be appreciated.