Mobile Rule Configuration
How your organization's Axe DevTools Mobile rule configuration affects mobile project results
Enterprise admins can choose which iOS and Android rules report issues for their whole organization. They do this in the Axe DevTools Mobile section of Axe Configuration. For mobile projects in Axe Developer Hub, this configuration determines which rules run and report issues in your sessions.
Where to Configure Mobile Rules
Mobile rule configuration is managed in Axe Configuration, not in Axe Developer Hub. It is available to enterprises with an Axe DevTools Mobile subscription, and only enterprise admins can change it. See Axe DevTools Mobile Rule Configuration for how to turn rules on and off and how to allow users to change them.
The rule configuration only takes effect with supported versions of the Axe DevTools Mobile SDKs and Appium drivers. See Mobile Rule Configuration in the Axe DevTools Mobile documentation for the minimum versions.
How It Affects Your Results
- Rules turned off by an admin don't run. Your mobile sessions don't report issues for those rules.
- Changes apply to future sessions only. The Axe DevTools Mobile SDKs and Appium drivers read the configuration when a testing session starts. Sessions that already ran keep the results and totals from the configuration that was active at the time.
- Developers can turn off additional rules only if an admin allows it. When the Allow users to change setting is on, developers can ignore more rules in their test code. They can never turn back on a rule that an admin turned off. For how to ignore rules in tests, see the Axe DevTools Mobile documentation for iOS, Android, and Appium.
- Custom rules always run. They aren't part of the rule configuration.
When the Configuration Has Changed
If a session ran with a different rule configuration than your organization uses now, its mobile session page shows a warning banner. Sessions with no recorded configuration, such as those that ran before mobile rule configuration became available or were sent by an SDK version or tool that doesn't report its configuration, don't show the banner. The issue counts and accessibility score for that session reflect the configuration it ran with. See Configuration Warning Banner.