BoundingRectangle failures reported for hidden tab control in old style wizards

[microsoft]

BoundingRectangle failures reported for hidden tab control in old style wizards

[msft-github-bot]

This issue has been marked as requiring additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, please update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights!

This issue has been marked as requiring additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, please update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights!

[karanbirsingh]

@chrisoldwood The rule engine used by insights lives in this GitHub repo so I've transferred the issue. We will take a look at this - thanks!

[karanbirsingh]

Hi @chrisoldwood, I chatted with @RobGallo about this. Thanks for the report & let us know what you think.

I have attached an a11ytest file below of SourceMonitor. To open it in Accessibility Insights, please rename it to SourceMonitor.a11ytest (GitHub doesn't allow custom extension uploads).
SourceMonitor.zip

bounding rectangles:
The BoundingRectangle failures were changed to warnings in Axe.Windows 0.2. Accessibility Insights uses 0.2 in canary, but not in production yet.

names:
It would be interesting to filter these cases out - the challenge is distinguishing this wizard case from other applications with empty-name tab items. Like you mention, it's unlikely a keyboard user will encounter the tab items in this dialog (they're not in the tab order). Axe.Windows only has access to the UI Automation tree, in which the tab items report themselves as keyboard-focusable. Unless we can exclude this wizard case via UI Automation properties, it's difficult to change the rule without introducing false negatives in other Win32 applications.

The team requires additional author feedback; please review their replies and update this issue accordingly. Thank you for contributing to Accessibility Insights!

[chrisoldwood]

Thanks for acknowledging the issue. I agree that it is going to be tricky to distinguish old style wizards because the point is to abstract the UI from the client 😃. If you want to close this issue then go ahead, my main aim was to document the problem for myself and others. In the meantime I will look into finding a way to make this detectable in a safe way.

[karanbirsingh]

Thanks @chrisoldwood - we'll close this. Do let us know if something comes to mind!