Known Issues

To utilize the desktop app, please continue to use an earlier version of Java.

Use the axeDevToolsXCUI framework in UITesting for SwiftUI views.

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

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

CollidingViews
Currently the CollidingViews rule utilizes the size of the UILabel frame. When the frame is larger than the visible text, it may incorrectly flag text as colliding with another element on the screen.

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 UIFontMetrics with the default iOS font.
• 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.
• If using UIButton.Configuration in iOS 15+.
• SupportsDynamicType may report issues for text within banner-behaving elements. To make these elements available to those that require larger text, use UILargeContentViewer.
• Text within collection view cells.

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

Help make this filter more robust by providing an example snippet of how the modal is implemented to the email above.

This will be addressed in a later version.

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

Various rules may report false positives for elements within header or footer behaving elements (ie: navigation or tab bars), on simulators without a home button.

A11yElementFocusBox
For views that are off-screen, this rule may incorrectly report the VoiceOver focus box is not encapsulating the view.

CollidingViews
Currently the CollidingViews rule utilizes the size of the UILabel frame. When the frame is larger than the visible text, it may incorrectly flag text as colliding with another element on the screen.

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

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)`, 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.

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

EditTextName
EditTextName may report issues for TextInputLayout components.

LabelInName
Text that contains special characters, such as the '/' for 'or' will report issues for LabelInName.