{ "doc": { "id": "accessibility/configuration/axe-core-configuration", "title": "Axe Core® configuration in Cypress Accessibility", "description": "How Cypress Accessibility runs the Axe Core® ruleset, which rules are off by default, and how Cypress can tune rules for your project.", "section": "accessibility", "source_path": "/llm/markdown/accessibility/configuration/axe-core-configuration.md", "version": "fbc9225067c51c52ee13224e3b702cf8a025ec12", "updated_at": "2026-08-14T12:36:26.878Z", "headings": [ { "id": "accessibility/configuration/axe-core-configuration#axe-core-configuration", "text": "Axe Core® configuration", "level": 1 }, { "id": "accessibility/configuration/axe-core-configuration#how-cypress-can-tune-the-ruleset-for-your-project", "text": "How Cypress can tune the ruleset for your project", "level": 2 }, { "id": "accessibility/configuration/axe-core-configuration#adjustments-you-can-make-yourself", "text": "Adjustments you can make yourself", "level": 3 }, { "id": "accessibility/configuration/axe-core-configuration#rules-that-are-off-by-default", "text": "Rules that are off by default", "level": 2 }, { "id": "accessibility/configuration/axe-core-configuration#component-testing", "text": "Component testing", "level": 2 }, { "id": "accessibility/configuration/axe-core-configuration#axe-core-library-version-and-updates", "text": "Axe-Core® library version and updates", "level": 2 }, { "id": "accessibility/configuration/axe-core-configuration#see-also", "text": "See also", "level": 2 } ] }, "chunks": [ { "id": "accessibility/configuration/axe-core-configuration#how-cypress-can-tune-the-ruleset-for-your-project", "doc_id": "accessibility/configuration/axe-core-configuration", "heading": "How Cypress can tune the ruleset for your project", "heading_level": 2, "content_markdown": "## How Cypress can tune the ruleset for your project\n\nTeams reach out for a few common adjustments. In each case, Cypress applies the change on your behalf and can regenerate historical runs so you can preview the effect before adopting it:\n\n* **Enable a rule that is off by default.** The most common request is turning on [color contrast checking](#rules-that-are-off-by-default) for a project where you've confirmed it produces reliable results.\n* **Turn off a rule that is a known false positive.** If a specific rule consistently misfires because of a third-party framework you can't change, it can be disabled project-wide so it stops adding noise to your reports.\n* **Scope the report to a conformance target.** Cypress can narrow the ruleset to the standard your team is committed to, such as WCAG 2.1 Level A and AA, so the report reflects exactly the criteria you're measuring against.\n\nWe're happy to have a call to dial in your report configuration and make sure you're getting the most useful reports possible.\n\n### Adjustments you can make yourself\n\nSome ways of shaping your results don't require any rule configuration and are fully in your control:\n\n* To ignore a specific rule for individual elements, add the [`data-a11y-ignore` attribute](/llm/markdown/accessibility/configuration/ignoring-rules-per-element.md) in your application code.\n* To keep a rule enabled but stop a particular element or page from being reported, use [`elementFilters`](/llm/markdown/accessibility/configuration/elementfilters.md) or [`viewFilters`](/llm/markdown/accessibility/configuration/viewfilters.md).\n* To decide which findings block a build in CI, parse your run's results with the [Results API](/llm/markdown/accessibility/results-api.md). Leaving a rule reported but non-blocking is often the best choice, since you keep full visibility into the issue.\n", "section": "accessibility", "anchors": [ "how-cypress-can-tune-the-ruleset-for-your-project" ], "path": "/llm/json/chunked/accessibility/configuration/axe-core-configuration.json", "token_estimate": 356 }, { "id": "accessibility/configuration/axe-core-configuration#adjustments-you-can-make-yourself", "doc_id": "accessibility/configuration/axe-core-configuration", "heading": "Adjustments you can make yourself", "heading_level": 3, "content_markdown": "### Adjustments you can make yourself\n\nSome ways of shaping your results don't require any rule configuration and are fully in your control:\n\n* To ignore a specific rule for individual elements, add the [`data-a11y-ignore` attribute](/llm/markdown/accessibility/configuration/ignoring-rules-per-element.md) in your application code.\n* To keep a rule enabled but stop a particular element or page from being reported, use [`elementFilters`](/llm/markdown/accessibility/configuration/elementfilters.md) or [`viewFilters`](/llm/markdown/accessibility/configuration/viewfilters.md).\n* To decide which findings block a build in CI, parse your run's results with the [Results API](/llm/markdown/accessibility/results-api.md). Leaving a rule reported but non-blocking is often the best choice, since you keep full visibility into the issue.\n", "section": "accessibility", "anchors": [ "adjustments-you-can-make-yourself" ], "path": "/llm/json/chunked/accessibility/configuration/axe-core-configuration.json", "token_estimate": 129 }, { "id": "accessibility/configuration/axe-core-configuration#rules-that-are-off-by-default", "doc_id": "accessibility/configuration/axe-core-configuration", "heading": "Rules that are off by default", "heading_level": 2, "content_markdown": "## Rules that are off by default\n\nA small number of Axe-Core® rules are turned off in Cypress Accessibility by default. Color contrast can be enabled per project on request. The other two depend on live runtime behavior that isn't reproduced when Cypress re-renders a captured snapshot for analysis, so they can't be evaluated reliably.\n\n| Rule | Why it's off by default |\n| --- | --- |\n| Elements must meet minimum color contrast ratio thresholds | This is the slowest rule in the Axe-Core® ruleset and the one most likely to produce false positives or incomplete results. It works well in many projects, so we're happy to turn it on for you on request. |\n| `