Releases: microsoft/axe-windows
Releases · microsoft/axe-windows
May 19 2020 [v0.9.6]
April 25 2020 [v0.9.5]
April 25 2020 [v0.9.5]
Bug fixes
- #352 - False-negative result for the rule "An element's IsOffScreen property must be false when its clickable point is on screen."
- Change the default order in which event handlers are registered (PR #356). Fixes Accessibility Insights bug #694.
April 9 2020 [v0.9.4]
April 9 2020 [v0.9.4]
Internal bug fixes
April 1 2020 [v0.9.3]
April 1 2020 [v0.9.3]
Internal bug fixes
March 17 2020 [v0.9.1]
March 17 2020 [v0.9.1]
Welcome to the March 17, 2020 release of Axe-Windows
Bug fixes
- #320 - AI-Win not properly reporting text pattern on Win32 …
- #322 - “An element's BoundingRectangle must not obscure its container element” should exclude dialogs
- #283 - axe-windows not reporting UIA Patterns for some elements
- #161 - Add rule to ensure the descendants of off screen elements are also off screen.
February 12 2020 [v0.9.0]
February 12 2020 [v0.9.0]
Welcome to the February 12, 2020 release of Axe-Windows
New features
- Axe.Windows libraries are now .NET Standard 2.0 compatible. That means they will integrate successfully with applications built on versions of .NET Core and .NET Framework that support the .NET Standard 2.0 API.
- IScanner.Scan now takes an optional scan ID as a parameter. If provided, the scan ID will be used as the output file name, as well as a scan identifier anywhere such an identifier might be useful in the future.
- Created a .NET Core CLI to make it easy to trigger automated scans.
Bug fixes
- Fix Issue #239 -- [false positive] Update ProgressBarRangeValue allowed minimum and maximum values
- Fix Issue #240 -- [false positive] Rule NameIsReasonableLength should not apply to text elements
- Fix Issue #162 -- [Feature Request] Add rules to ensure that an element's clickable point and IsOffscreen property agree.
- Fix Issue #263 -- UIA HeadingLevel values are reported incorrectly
- Fix Issue #265 -- UIA StyleId property values are always reported as "Unknown"
December 5 2019 [v0.3.5]
December 5 2019 [v0.3.5]
Welcome to the December 5th release of Axe-Windows
Bug fixes
- Fix: #220 Add null check to TreeTracker to avoid exception (this fix affects Accessibility Insights for Windows)
September 10 2019 Release [v0.3.4]
September 10 2019 [v0.3.4]
Welcome to the September 10th release of Axe-Windows
Bug Fixes
- Fixed false positives created by change to ControlShouldSupportTextPattern rule [#140]
September 4 2019 release [v0.3.3]
September 4 2019 release [v0.3.3]
Package
https://www.nuget.org/packages/Axe.Windows/0.3.3-prerelease
Details
- Fix [BUG] BoundingRectangleNotNull rule should exclude non-focusable buttons that are children of sliders · Issue #139
- Fix [BUG] False positive for BoundingRectangleNotNull for group elements in Edge · Issue #142
- Add [feature] Add a rule to detect characters in the private unicode range · Issue #129
August 5 2019 release [v0.3.2]
August 5 2019 release [v0.3.2]
Package
https://www.nuget.org/packages/Axe.Windows/0.3.2-prerelease
Details
- Fix a problem where older versions of Axe.Windows could not open a11ytest files generated by a newer version of Axe.Windows if a new rule was added. Please see PR #119 (Ignore RuleId in serialized file -- for details.