Skip to content

(Accessibility)(Meta) Track nested-interactive axe-core violations in product UI so we can re-enable the rule  #152494

@1Copenut

Description

@1Copenut

Description
@bhavyarm is working to bump our axe-core to a more current version in #144940 and has been running into a number of nested-interactive violations. We opted to ignore the nested-interactive rule temporarily to get the benefit of other new rulesets, with the understanding we do want to fix the identified violations. Opening this meta issue to track those so they can be assigned to product teams and added to future roadmaps.

Actual Result

  • Buildkite shows a number of unique nested-interactive element violations

Expected Result

  • Buildkite shows 0 nested-interactive-element violations when the rule is re-enabled

Relevant WCAG Criteria:
SC 4.1.2: Name, Role, Value (Level A)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions