{
  "doc": {
    "id": "accessibility/configuration/ignoring-rules-per-element",
    "title": "Ignoring rules for specific elements | Cypress Accessibility",
    "description": "Elements can avoid failing certain rules using a data-a11y-ignore attribute",
    "section": "accessibility",
    "source_path": "/llm/markdown/accessibility/configuration/ignoring-rules-per-element.md",
    "version": "3cf5b86b3403f604bdf7f3e35025c3bc3865e02c",
    "updated_at": "2026-05-07T17:44:31.931Z",
    "headings": [
      {
        "id": "accessibility/configuration/ignoring-rules-per-element#ignore-rules-for-specific-elements",
        "text": "Ignore rules for specific elements",
        "level": 1
      },
      {
        "id": "accessibility/configuration/ignoring-rules-per-element#ignore-multiple-rules",
        "text": "Ignore multiple rules",
        "level": 2
      },
      {
        "id": "accessibility/configuration/ignoring-rules-per-element#where-to-find-rule-ids",
        "text": "Where to find rule IDs",
        "level": 2
      },
      {
        "id": "accessibility/configuration/ignoring-rules-per-element#when-to-use-this",
        "text": "When to use this",
        "level": 2
      },
      {
        "id": "accessibility/configuration/ignoring-rules-per-element#handle-false-positives",
        "text": "Handle false positives",
        "level": 3
      },
      {
        "id": "accessibility/configuration/ignoring-rules-per-element#avoid-blocking-a-code-change",
        "text": "Avoid blocking a code change",
        "level": 3
      }
    ]
  },
  "chunks": [
    {
      "id": "accessibility/configuration/ignoring-rules-per-element#where-to-find-rule-ids",
      "doc_id": "accessibility/configuration/ignoring-rules-per-element",
      "heading": "Where to find rule IDs",
      "heading_level": 2,
      "content_markdown": "## Where to find rule IDs\n\nThe \"Learn more\" link in your accessibility reports will display the ID for each rule. They can also be looked up in the [Axe-Core® rule documentation](https://github.com/dequelabs/axe-core/blob/develop/doc/rule-descriptions.md) directly.\n",
      "section": "accessibility",
      "anchors": [
        "where-to-find-rule-ids"
      ],
      "path": "/llm/json/chunked/accessibility/configuration/ignoring-rules-per-element.json",
      "token_estimate": 44
    },
    {
      "id": "accessibility/configuration/ignoring-rules-per-element#when-to-use-this",
      "doc_id": "accessibility/configuration/ignoring-rules-per-element",
      "heading": "When to use this",
      "heading_level": 2,
      "content_markdown": "## When to use this\n\n### Handle false positives\n\nThis is most useful when there is a known false positive failure for a specific rule and you want to remove it from your report without losing all other insights about an element.\n\nThe `data-a11y-ignore` attribute pattern is used in some libraries like Adobe's React Spectrum, so those UI elements automatically have the defined rules ignored correctly in Cypress Accessibility.\n\n### Avoid blocking a code change\n\nA secondary use case is to avoid certain known issues becoming blocking for a pull request. `data-a11y-ignore` allows for a minimal scope of what to ignore, and creates a paper trail through version control which means these changes are obvious at code review, and comments can be added nearby to explain the reason for ignoring the rule.\n",
      "section": "accessibility",
      "anchors": [
        "when-to-use-this"
      ],
      "path": "/llm/json/chunked/accessibility/configuration/ignoring-rules-per-element.json",
      "token_estimate": 176
    },
    {
      "id": "accessibility/configuration/ignoring-rules-per-element#handle-false-positives",
      "doc_id": "accessibility/configuration/ignoring-rules-per-element",
      "heading": "Handle false positives",
      "heading_level": 3,
      "content_markdown": "### Handle false positives\n\nThis is most useful when there is a known false positive failure for a specific rule and you want to remove it from your report without losing all other insights about an element.\n\nThe `data-a11y-ignore` attribute pattern is used in some libraries like Adobe's React Spectrum, so those UI elements automatically have the defined rules ignored correctly in Cypress Accessibility.\n",
      "section": "accessibility",
      "anchors": [
        "handle-false-positives"
      ],
      "path": "/llm/json/chunked/accessibility/configuration/ignoring-rules-per-element.json",
      "token_estimate": 85
    },
    {
      "id": "accessibility/configuration/ignoring-rules-per-element#avoid-blocking-a-code-change",
      "doc_id": "accessibility/configuration/ignoring-rules-per-element",
      "heading": "Avoid blocking a code change",
      "heading_level": 3,
      "content_markdown": "### Avoid blocking a code change\n\nA secondary use case is to avoid certain known issues becoming blocking for a pull request. `data-a11y-ignore` allows for a minimal scope of what to ignore, and creates a paper trail through version control which means these changes are obvious at code review, and comments can be added nearby to explain the reason for ignoring the rule.\n",
      "section": "accessibility",
      "anchors": [
        "avoid-blocking-a-code-change"
      ],
      "path": "/llm/json/chunked/accessibility/configuration/ignoring-rules-per-element.json",
      "token_estimate": 84
    }
  ]
}