Skip to content

nested-interactive and details elements #2958

@connorjclark

Description

@connorjclark

This is enough to fail this rule:

<details>
    <summary>
      <a href=#>click</a>
    </summary>
    ...
  </details>

Is this intentional?

This is a simplified example of a failure seen for this element: https://lighthouse-n9rg3umip-googlechrome.vercel.app/english/#:~:text=these%20items%20address%20areas%20which%20an%20automated%20testing%20tool Even with summary>a fixed, I think we'd still fail b/c we have nested details elements. What is the suggested fix for this? tabindex=-1 all the things until details is expanded?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    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