This is great! I’m curious about the accessibility tree noted in the unsupported-for-now APIs. Accessing the accessibility tree was something that was in Playwright for the big 3 engines but got removed about a year ago. I think it was partly because as noted it was a dump of engine-specific internal data structures: “page.accessibility.snapshot returns a dump of the Chromium accessibility tree”.
I’d like to advocate for more focus on these accessibility trees. They are a distillation of every semantic element on the page, which makes them fantastic for snapshot “tests” or BDD tests.
My dream would be these accessibility trees one day become standardized across the major browser engines. And perhaps from a web dev point-of-view accessible from the other layers like CSS and DOM.
I’d like to advocate for more focus on these accessibility trees. They are a distillation of every semantic element on the page, which makes them fantastic for snapshot “tests” or BDD tests.
My dream would be these accessibility trees one day become standardized across the major browser engines. And perhaps from a web dev point-of-view accessible from the other layers like CSS and DOM.