Accessibility Checker warnings never fail the build — how to gate them before shipping a WPF app

Observed behavior

Visual Studio 2022's Accessibility Checker (Tools > Accessibility Checker) scans our WPF XAML at design time and reports issues like a missing AutomationProperties.Name as warnings in the Error List. The build succeeds regardless, so these warnings accumulate unnoticed until a manual audit finds them.

Goal and constraints

We want accessibility violations to block a release the same way analyzer errors do, but the IDE checker appears to have no documented command-line or MSBuild integration, and its coverage is limited to XAML-based WPF projects — dynamically generated UI and runtime-only defects are not scanned. We also cannot assume that zero warnings means WCAG conformance, so any gate would only cover the detectable subset.

Options under consideration: treat the Error List warnings as build-breaking via warning-as-error configuration (unclear whether the checker's diagnostics participate), or run a separate tool such as Accessibility Insights in CI alongside the IDE workflow.

Questions

• Can Accessibility Checker diagnostics be promoted to build errors in Visual Studio 2022, or are they strictly informational Error List entries outside the compiler pipeline?
• Is there any supported way to run the same rule set from the command line in CI, or is a third-party scanner the only option for gating?
• Which Visual Studio 2022 update changed the supported project types, so we can pin a minimum version for the team?