Experimental

Experimental rules are accessibility checks that are still being developed and tested. These rules address new technologies, emerging accessibility concerns, or areas where understanding is still evolving. Because they're in development, experimental rules may produce false positives and shouldn't be relied upon in production environments. However, they can provide early insights into potential accessibility issues.

Default Value

When you don't specify an experimental rules override, axe Watcher uses the setting from your organization's global configuration. Experimental rules are typically disabled by default to prevent false positives from affecting your test results.

Overriding

You can enable or disable experimental rules when your organization's global configuration permits this override. Enabling experimental rules is useful during development or when you want to stay ahead of upcoming accessibility requirements. They're typically disabled for production testing to avoid noise from potential false positives.

Available Options

• true - Enable experimental rules
• false - Disable experimental rules

JavaScript/TypeScript Example

const config = {
  axe: {
    apiKey: process.env.AXE_API_KEY,
    projectId: process.env.AXE_PROJECT_ID,
    configurationOverrides: {
      experimentalRules: true
    }
  }
};

Java Example

ConfigurationOverrides overrides = new ConfigurationOverrides()
    .setEnableExperimental(true);

AxeWatcherOptions options = new AxeWatcherOptions()
    .setApiKey(System.getenv("AXE_API_KEY"))
    .setProjectId(System.getenv("AXE_PROJECT_ID"))
    .setConfigurationOverrides(overrides);