Testing: Accessibility UI Walkthrough
-
Sample Workbooks to use for testing:
After opening, run the whole whole workbook to bring up the UI in the agent app in order to prime the View Inspector tab for testing.
The workbook editor surface is an embedded web browser hosting an HTML-and-JavaScript-based UI.
This component is actively being replaced with accessibility in mind, leveraging the Office team's Fabric UI components. As such, it does not make sense to perform testing against the old UI as indicated in screenshots below.
The native UI (WPF on Windows and Cocoa on macOS) workbook outline tree to the left of the workbook editor surface should be tested however.
The property inspector on the right side of the view inspector tab is a component that the Workbooks & Inspector team does not own.
It will receive its own specific accessibility testing outside of the Workbooks & Inspector testing scope.
Eventually, Workbooks & Inspector will inherit any fixes and improvements made to the property inspector as a result of the separate testing pass.
All other dialogs and windows in both the macOS and Windows apps should be tested.
The "agent apps" are external apps that are driven by UI code as authored by an end-user of Workbooks. These app windows do not need any testing since they are not actually part of the Workbooks deliverables.
A tree-hierarchy and "exploded" 3D representation of these windows is the main focus of the View Inspector tab.
