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

Question

Observed behaviorVisual 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 constraintsWe 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.QuestionsCan 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?

Tasadduq Burney · Answer

Can Accessibility Checker diagnostics be promoted to build errors in Visual Studio 2022?

The Accessibility Checker operates as a design‑time extension; its warnings appear in the Error List but are not emitted by the Roslyn compiler. Enabling “Treat warnings as errors” for the project does not affect these diagnostics—the build succeeds regardless. The checker’s output participates only in the IDE’s display pipeline, not the MSBuild exit‑code pipeline.

Is there a supported command‑line or CI integration for the same rule set?

No documented MSBuild target, CLI switch, or exported rule set exists that invokes the Accessibility Checker outside the IDE. To gate accessibility issues in CI, use an external headless scanner such as the Accessibility Insights for Windows CLI, axe‑core via npm, or Pa11y. These tools can be run against compiled XAML files or a running UI and return a non‑zero exit code when violations are present, which CI can treat as a build failure.

Which Visual Studio 2022 update changed the supported project types for WPF?

Support for analyzing .NET 5/6/7 SDK‑style WPF projects was added in Visual Studio 2022 version 17.4 (released March 2022). Earlier versions only scanned legacy .NET Framework WPF projects. Teams can verify the installed version via Help > About Microsoft Visual Studio or by checking the environment, and set a minimum version requirement in contributing guidelines.

Enable “Treat warnings as errors” for the project and rebuild; confirm the build succeeds despite open Accessibility Checker warnings, verifying that the checker does not influence the compiler exit code.
Install the Accessibility Insights for Windows CLI (or an equivalent headless scanner) and run it against the project’s XAML or compiled assembly; a non‑zero exit code will block the CI pipeline when the same issues appear.
Pin Visual Studio 2022 version 17.4 or later if your project uses SDK‑style WPF projects; earlier versions lack coverage for this project format.

To tailor the recommendation, which Visual Studio 2022 version (or build) are you currently running?

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

Observed behavior

Goal and constraints

Questions

1 answer

Can Accessibility Checker diagnostics be promoted to build errors in Visual Studio 2022?

Is there a supported command‑line or CI integration for the same rule set?

Which Visual Studio 2022 update changed the supported project types for WPF?

Your perspective belongs here.

0 question comments