axe DevTools Mobile September 18, 2024 Release Notes

Functionality with testing an application by bundle identifier was broken in version 2.8.1 which resulted in an error titled "No target application path specified via test configuration: ...". Update to 2.8.2 or the latest version to resolve the error. Update to the latest within the iOS Analyzer project.

Some screens may report false positives with LabelInName and LabelAtFront due to an incorrect associatedText property being found (#1622)

There is an issue affecting the iPhone 15 Pro simulator that prevents the Supports Dynamic Type rule from running. If you are opted in to the Supports Dynamic Type rule, you will not be able to test it using an iPhone 15 Pro simulator. A bug has been filed with Apple.

While looking at an improvement for our rules, we found that in XCTest, nested controls are not returned in the accessibility tree. A bug has been filed with Apple. (#1110)

In UIKit apps, an image without an `accessibilityLabel` is not focusable with assistive technology by default.
The properties we use to check focusability from Apple may be inaccurate when an `accessibilityIdentifier` is set on the image. Due to this unexpected behavior, results for ImageView Name issues in UIKit apps will report as Needs Review. A bug report has been filed with Apple. (#1633)

We are actively working on fixes for the following false positives and will update this list as fixes are released.

In Scroll View
May report issues for text within banner-behaving elements. To make these elements available to those that require larger text, use UILargeContentViewer. (#622)

v2.11.0 Image View Name & Active Control Name
If an UIImageView has an `accessibilityIdentifier` set but is not focusable by VoiceOver, and it has focusable controls nested within it, ActiveControlName may report a false positive on the UIImageView. Removing the `accessibilityIdentifier` resolves the issue. A bug has been filed with Apple. (#1633)

Label In Name and Label At Front
These two rules look for a control's visible label amongst nearby elements to help determine rule status. In some view hierarchies, the incorrect nearby text may be detected causing these rules to fail. (#1622)

Introduced with API 31 (Android 12) is the ability to hide non-system overlays. In order to utilize the axe Analyzer app, please ensure this setting is not turned on. If you have opted to utilize this feature for it's security enhancements, we recommend leaving it off for internal testing builds where you can safely utilize testing data and eliminate security concerns that way. Note: this setting does not affect Google's accessibility scanner app as it's considered a system overlay.

To utilize the axe Accessibility Analyzer app, update any calls to the method setHideOverlayWindows(true) to setHideOverlayWindows(false) on the affected activity windows.

To unlock full functionality of axe DevTools for Mobile, ensure screenshots are enabled. We recommend enabling screenshots on a debug or test version of your app that uses mock data to avoid security concerns. Checkout our guide for enabling screenshots in Android apps.

If minifying your build, you'll see a crash with an error log reporting an adapter could not be found when trying to login to the axe DevTools library. Disable minify for your debug builds with axe DevTools implemented. (#729)

A build with r8 enabled may attempt to minify the axeDevTools library resulting in an error similar to:

Caused by: java.lang.NullPointerException: throw with null exception
at g.b.b.a$a.a(Unknown Source:1)
at g.b.b.a$a.a(Unknown Source:0)
at g.b.b.a.a(AccessToken.java:190)
    

If you encounter an error along the lines of `Expected exactly '1' node but found '2' nodes that satisfy: (isRoot)` or `No View initialized, did you call AxeDevToolsCompose.setComposeTestRule()?`, please refer to Compose setTestTag API.

If you encounter this message, some rule results may not return as expected when that rule is utilizing artificial intelligence. Affected rules include Color Contrast, Focusable Text and Nested Element Name. (#841)

Due to limitations of the MAUI app architecture rendering in the Android ecosystem, the Edit Text Name rule will show as Needs Review in the dashboard when a failure is suspected for SDK version 5.5.0 and up. Please confirm correct behavior manually for this case.

When you're implementing custom dialogs or modals that do not extend the native controls, you may get results for views behind the modal. In this case, we recommend not running our tool against these custom modals or dialogs and instead manually checking them to ensure they behave with assistive technology as desired.

If the screenshot is missing from the scan details page, your app may be preventing screenshots from being taken. Often this is for security reasons in your production application. Consider removing this requirement for your testing build to allow for full functionality in the axe DevTools Mobile Dashboard.

• Android - FLAG_SECURE

Some Android scan names that are defaulted to the screen title will appear as the full class name including the bundle identifier. In a future release, this will be resolved so that the screen title is formatted into a more readable name. As a workaround, you can set the scan name from the dashboard or frameworks. (#1643)