--- id: ui-coverage/configuration/significantattributes title: Significant Attributes | Cypress UI Coverage description: >- The `significantAttributes` configuration property allows users to specify custom attributes that should be considered "significant" for the purpose of identification and grouping in UI Coverage. section: ui-coverage source_path: docs/ui-coverage/configuration/significantattributes.mdx version: b82d075e7d560239a9c938b7b6c3c16ac1b76370 updated_at: '2026-05-31T02:23:30.549Z' --- # significantAttributes The `significantAttributes` property allows you to specify which attributes should be considered significant when identifying elements in UI Coverage. ## Why use significant attributes? Cypress uses a [default set of attributes](/llm/markdown/accessibility/core-concepts/element-identification.md) (such as common test ID patterns), in a priority order, as the preferred way to identify elements in reports. The values of these attributes are used as element identifiers, which helps us recognize the same element in multiple contexts and deduplicate the findings. This helps when reviewing run reports, or comparing reports in Branch Review. You may have attributes already in place in your application that would help with element organization, such as `data-component-name`. If you would like Cypress to use and prioritize these attributes, or you want to change the default priority order, you can define your own list of significant attributes. ## Scope **Note:** setting `significantAttributes` 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. If a nested value exists it will override one defined at the root level for that product. ## Syntax `significantAttributes` is an array of strings, with each string being the name of a HTML attribute. ``` { "significantAttributes": [ string ]} ``` ## Examples ### Marking specific attributes as significant #### Config ``` { "significantAttributes": ["class", "id", "data-context"]} ``` #### HTML ``` ``` #### Significant attributes tracked ``` class="primary", id="submit", data-context="user-signup" ```