Known Issues

Link to Known Issues copied to clipboard

If you're experiencing any of the below issues, please contact us at helpdesk@deque.com or support.deque.com. We will then be able to notify you once it's resolved or of an identified workaround if none is listed.

important
  • axe DevTools Mobile automated testing runs on native iOS, native Android, and React Native applications. Please contact your Deque representative for accessibility testing solutions on your tech stack.
  • Rules will not run in web views or rendered PDFs. To test against HTML content, please utilize axe DevTools HTML. axe Monitor supports scanning PDFs for accessibility.

axe DevTools Mobile for iOS

axeDevToolsUIKit.xcframework

Views built with SwiftUI cannot be tested using this framework

Use the axeDevToolsXCUI framework in UITesting for SwiftUI views.

Custom rule support is available only in Swift

The custom rule API is not open to Objective-C.

False Positives: InScrollView, SupportsDynamicType, Colliding Views

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

InScrollView
InScrollView may report issues for text within banner-behaving elements. To make these elements available to those that require larger text, use UILargeContentViewer.

SupportsDynamicType
You may see false positives in the following scenarios:

  • If using the UIContentSizeCategoryDidChange notification, the framework may incorrectly report that text does not respond to Dynamic Type in UITests.
  • If using NotificationCenter.default.addObserver(forName:.., object:.., queue:.., using:..) to respond to the UIContentSizeCategoryDidChange notification.
  • If using traitCollectionDidChange on a text's parent view or view controller to respond to Dynamic Type.
Colliding Views
When a scrollable subview contains text, and that subview does not span to the edge of the screen's bounds, you will see failures for text located within the view's bounds.

axeDevToolsXCUI.xcframework

SwiftUI Picker and UIKit Picker

Picker views in SwiftUI and UIKit may cause the framework to get stuck on simulators or devices.

False Positives: InScrollView, Colliding Views

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

InScrollView
InScrollView may report issues for text within banner-behaving elements. To make these elements available to those that require larger text, use UILargeContentViewer. Colliding Views
When a scrollable subview contains text, and that subview does not span to the edge of the screen's bounds, you will see failures for text located within the view's bounds.

False Negative: Focusable Text in iOS 13 through iOS 14.8.1

Elements marked as non-accessibility elements may not report proper results due to a bug in Apple's framework.

axe DevTools Mobile for Android

Crash when using Proguard

If your debug or test build is utilizing Proguard, follow the steps to ignore Deque in your Proguard settings.

Crash when `minifiedEnabled` is set to true

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.

Errors Compiling with Java8 Project and axe DevTools Android 3.1.0

Try the following imports: 

implementation 'androidx.core:core-ktx:1.9.0'
implementation 'org.jetbrains.kotlinx:kotlinx-coroutines-core:1.6.4'
implementation 'org.jetbrains.kotlinx:kotlinx-coroutines-android:1.6.4'
After importing the above library, if you see errors related to minSDK version for core-ktx library try the following in your project’s Android Manifest:
<uses-sdk tools:overrideLibrary="androidx.core" />

Builds with r8 enabled throw an error

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)
To resolve this error add the following line to your ProGuard file to keep axeDevTools classes:
keep class com.deque.** { *; }

Error message similar to:
Expected exactly '1' node but found '2' nodes that satisfy: (isRoot)

If you encounter an error along the lines of `Expected exactly '1' node but found '2' nodes that satisfy: (isRoot)`, please contact us at helpdesk@deque.com or support.deque.com for assistance. Under certain conditions, there may be two Compose root nodes existing at the same time.

axe DevTools Mobile Dashboard

Some Android scan names are unformatted

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

Is this page helpful?

Help us improve this page

Still need help?