October 31 2024 [v2.4.2]

Welcome to the October 31 2024 release of Axe.Windows
NuGet package

Highlights

Bug fixes

• Fixed CVE-2024-43484. (#1062, #1063)

September 24 2024 [v2.4.1]

Welcome to the September 24 2024 release of Axe.Windows
NuGet package

Highlights

Bug fixes

• Axe.Windows can once again traverse the UIA tree as expected on Windows 11 Germanium (version 24H2). (microsoft/accessibility-insights-windows#1837)
• The SiblingUniqueAndFocusable rule has been downgraded to NeedsReview in Win32 applications due to a high rate of false positives. (microsoft/accessibility-insights-windows#1838, #1046)

May 24 2024 [v2.4.0]

Welcome to the May 24 2024 release of Axe.Windows

NuGet package

Highlights

New Features

• Scans can now be rooted at a particular window handle to target a particular subtree. (#1022, @blackcatsonly)
  • Added a NativeWindowHandle property to A11yElement which contains the element's hwnd.
• Added a LogicalSize property to A11yElement which contains the element's bounding rectangle in logical (scaled for DPI) pixels. (#1020)

March 26 2024 [v2.3.1]

Welcome to the March 26 2024 release of Axe.Windows

NuGet package

Highlights

Bug Fixes

• The CLI installer now detects Windows 7 and warns the user that .NET 6 doesn't support Windows 7 (#980)
• The binary files are now signed with the certificate used for Microsoft-built binaries (#995)

September 11 2023 [v2.3.0]

Welcome to the September 11 2023 release of Axe.Windows

NuGet package

Highlights

New Features

• The CLI and the automation layer can now be configured to include all Chromium HTML elements in test results, as requested by browser development teams. (#935)

August 3 2023 [v2.2.0]

Welcome to the August 3 2023 release of Axe.Windows

NuGet package

Highlights

New Features

• The CLI and the automation layer can now be configured to always create an .a11ytest file even when no errors are found. (#935)

Rule Changes

• The IsChromiumContent rule has been modified to evaluate Chromium documents. Other rules have been disabled for children of Chromium documents. (#836)

June 16 2023 [v2.1.3]

Welcome to the June 16 2023 release of Axe.Windows

NuGet package

Highlights

Rule Updates

• In Chromium-based applications, we now only apply the ChromiumComponentsShouldUseWebScanner rule to web content (controls within UI Automation elements with ControlType of Document). (microsoft/accessibility-insights-windows#1625)

Bug Fixes

• On Windows 11, exclude the Alt+Tab "task switching" UI from focus tracking. (microsoft/accessibility-insights-windows#1610)
• Various updates to translations.

May 23 2023 [v2.1.2]

Welcome to the May 23 2023 release of Axe.Windows

NuGet Package

Highlights

Rule Updates

• Only run LocalizedControlTypeReasonable on systems whose locale is set to English (microsoft/accessibility-insights-windows#1572)

May 1 2023 [v2.1.1]

Welcome to the May 1 2023 release of Axe.Windows

NuGet Package

Highlights

Rule Updates

• Exclude Group and Text elements from the NameIsInformative rule due to high false positive rate (#874)

Bug Fixes

• The localized strings for several rules contained incorrectly localized UIA property names. These have now been corrected.

November 16, 2022 [v2.1.0]

Welcome to the November 16, 2022 release of Axe.Windows

NuGet Package

Highlights

New features

Localization support when using the IScanner interface

Objects returned from the IScanner interface are now available in 13 languages other than English. The NuGet package now includes the localized files where .NET expects to find them. One caveat: Accessibility Insights for Windows is not localized, so opening .a11ytest files created in non-English languages will result in a mixed-language experience.

Rule Updates

• Exclude elements inside Telerik.Sparklines controls from the BoundingRectangleSizeReasonable rule, since these elements can reasonably be very small. (#780)
• Improve the "How to Fix" description of several rules that did not provide actionable information. (#790)

Deprecation of .NET Core 3.1

As described in this blog post, .NET Core 3.1 will reach its end of support on December 13 2022. Many support libraries are dropping support of .NET Core 3.1, and so are we. Supported CLR environments now include .NET Framework and .NET 6.0 or newer.