---
id: accessibility/configuration/attributefilters
title: Attribute Filters | Cypress Accessibility
description: >-
The `attributeFilters` configuration property allows users to specify patterns
for attributes and their values that should not be used for identifying and
grouping elements.
section: accessibility
source_path: docs/accessibility/configuration/attributefilters.mdx
version: 524ff5211e60b5d53e55d6ad976d83966f66e7cd
updated_at: '2026-04-30T14:20:05.396Z'
---
# attributeFilters
Cypress Accessibility [identifies elements](/llm/markdown/ui-coverage/core-concepts/element-identification.md) based on a combination of attributes and the surrounding DOM structure.
Some attributes used for identification may be auto-generated, dynamic, or state-based, leading to inaccurate identification or grouping. The `attributeFilters` configuration property allows you to **exclude** specific attributes or patterns that should not be used for these purposes.
By using `attributeFilters`, you can ensure Cypress selects more appropriate identifiers, leading to cleaner and more accurate reports, with better element de-deduplication across distinct states of the application being tested.
## Why use attribute filters?
* **Handling library-specific attributes**: Attributes generated by libraries may not represent the element's purpose and should be ignored.
* **Improving grouping accuracy**: By filtering out irrelevant attributes, you ensure similar elements are grouped correctly.
* **Avoiding state-based duplication**: Classes like `link--focused` can clutter report findings.
## Scope
**Note:** setting `attributeFilters` impacts both Cypress Accessibility and UI Coverage reports if set at the root of the configuration. Nesting this property under an `accessibility` or `uiCoverage` key is supported, if you need to split them up.
## Syntax
```
{ "attributeFilters": [ { "attribute": string, "value": string, "include": boolean, "comment": string } ]}
```
### Options
Whether Cypress is allowed to use a certain attribute to identify an element when processing it for UI Coverage or Cypress Accessibility reports will be controlled by the **first** filter that matches the name and value of that attribute.
This means that catch-all rules can be added at the bottom of the list by setting `include` to `false`, and exceptions can be defined earlier in the list using `include: true`. For example, you could avoid all use of `aria-label` for identification of elements as a catch-call filter, but then define exceptions for certain values it may have where it is a good identifier.
Attributes that do not match any rules are included by default and used if needed, so `include: true` is only required for defining exceptions. If you want to make sure an attribute is preferred as an identifier when available, add it to your [attributeFilters](/llm/markdown/accessibility/configuration/attributefilters.md).
| Option | Required | Default | Description |
| --- | --- | --- | --- |
| `attribute` | Required | | A regex string to match attribute names |
| `value` | Optional | `.*` | A regex string to match attribute values |
| `include` | Optional | `true` | A boolean to specify whether the matched attribute should be included. |
| `comment` | Optional | | A comment describing the purpose of this filter rule. |
## Examples
### Excluding common auto-generated ID values
Some component libraries generate
```
{ "attributeFilters": [ { "attribute": "id", "value": ":r.*", "include": false } ]}
```
#### HTML
```
```
#### Element identifiers displayed
```
[name="my-button"][name="other-button"]
```
* * *
### Filtering related dynamic attributes
When filtering dynamic `id` attributes, you should also filter attributes that reference those IDs to prevent elements from being identified by these related dynamic values. Common relationships include:
* Form associations (`for` attributes on labels)
* ARIA relationships (`aria-labelledby`, `aria-describedby`, `aria-controls`, `aria-owns`, `aria-details`)
* Name attributes that may mirror IDs in certain frameworks
```
{ "attributeFilters": [ { "attribute": "id|for|name|aria-.*", "value": "dynamic-.*", "include": false } ]}
```
#### HTML
```