Idea: expect(getAccessibilityTree(page)).toMatchInlineSnapshot()

It would be cool to write snapshot tests against the accessibility tree, something like:

test(
  'asdf',
  withBrowser(async ({ utils }) => {
    // ...
    expect(await getAccessibilityTree(pageOrNode)).toMatchInlineSnapshot(`
      heading "accessible name"
        link "accessible name"
          text "asdf"
          text "asdf"
      paragraph "some text in a paragraph"
        text "some text in a paragraph"
    `)
  }),
)

The tree would be as similar as possible to the accessibility tree shown in Chrome/Firefox

[gerardo-rodriguez]

@calebeby I like your idea!

Even at the basic level of “list all headings” or “list all articles” or “list all links” would be good. It’s another lens to help us see when we could enhance the experience. For example, if all articles on the page were listed as “article, article, article” then it would give us insight to consider making that experience better. 👍

[calebeby]

Closing this as getAccessibilityTree has been implemented/published. There are some ideas in this issue that are not implemented and might be worth implementing down the road. We can come back to them as we try out getAccessibilityTree on real work and find the pain points.