Rule engine configuration: scope, options, and impact

Learn how enforcing accessibility standards and configuring rulesets affect report metrics in App Accessibility.

Configuring the App Accessibility rule engine standardizes accessibility checks across your organization. You can enforce an accessibility standard, select the rules and categories that apply, and toggle whether Best Practice and Experimental rules contribute to issues.

These configuration changes directly affect the following metrics in App Accessibility reports:

• Issue counts
• Accessibility scores
• Compliance claims
• Trend comparability

Key impacts of rule engine configuration

Configuring the App Accessibility rule engine has the following effects:

• Issue counts and score: Disabling rules, rule categories, or the Best Practice and Experimental rulesets reduces reported issues and can inflate accessibility scores. Changing the accessibility standard changes the specific set of rules that run during each scan.
• Cross-tool impact: Organization-level rule engine configurations override user-level rule selections in Workflow Analyzer sessions and automated test runs. However, the Include Needs Review Issues toggle remains user-controlled per session.
• Organizational scope: Changes to the rule engine configuration apply to the entire organization. Only owners and admins can modify these settings or revert them to the defaults.
• Compliance mapping: Compliance assertions, such as “WCAG 2.2 AA compliant,” must accurately reflect your configured scope. Disabling core rules can invalidate your compliance claims.
• Trends and baselines: Historical comparisons might become inconsistent after configuration changes. To maintain accurate tracking, establish new baselines or document the dates when your configuration changed.
• Dashboards and APIs: Build summaries from automated tests, session reports from Workflow Analyzer, and API responses all reflect the ruleset that was active at the time of the scan.

Scope of rule engine configuration

When you configure the rule engine at the organization level, the configured ruleset applies to:

• Workflow Analyzer: All sessions started after the change.
• Automated tests: All test runs initiated after the change.

Sessions and test runs that started before the change continue using their original ruleset until they complete.

Rule engine configuration options

• Set the accessibility standard: Enforce a specific standard, such as WCAG 2.2 AA or RAAM 1.1, across the organization.
• Enable or disable rules and categories: Select entire rule categories, or expand a category to manage individual rules.
• Toggle best practices and experimental rules: Control whether best practices and experimental rules are included in scans.

Use cases for rule engine configuration

• Enforce a single accessibility standard: Set an organization-wide standard, such as WCAG 2.2 AA or RAAM 1.1, to ensure every team tests against the same standard.
• Reduce noise and focus on critical issues: Disable specific rules or rule categories, or turn off Include Experimental Rules and Include Best Practices Issues, so that your reports highlight only actionable issues.
• Adopt accessibility standards in phases: Start by disabling complex rulesets, and then enable stricter configurations as your organization’s accessibility standards grow.

Related links

• How to configure rules in the rule engine
• Rule repository
• Accessibility score calculation