Windows applications can be scanned for accessibility issues using the tools in the Axe.Windows repo. These tools do not currently produce Sarif files. The general pattern is as follows:
- Use your favorite framework (eg, Appium with WinAppDriver or similar framework) to get your application to the state that needs to be scanned
- Trigger a scan using the Axe.Windows tools.
- Consume the scan results--this will vary depending on your test framework.
If your tests are written in .NET Core or .NET Framework, you can trigger a scan by using the axe-windows automation layer. Results will be returned as a .NET object, which you can then consume as you wish. You also have the option to automatically create an A11yTest file (openable in Accessibility Insights for Windows) if any errors are found. An example of this usage can be found here. Your project can directly reference the Axe.Windows package from NuGet.
It is possible to use the Axe.Windows CLI to trigger scans from any scripting system that can start a process. These results will always be returned as an A11yTest file. Documentation of the CLI can be found here. The Axe.Windows CLI can be downloaded from the Axe.Windows release page.