[marcellus23]

> The approach of creating an accessibility tree can take extra work from developers instead of it just working.

Because this isn’t true unless you’re using a nonnative framework like Flutter. If you write your apps in HTML or native frameworks, the tree is built automatically. You only have to fiddle with it if you’re doing really custom stuff (which almost no one is).

[charcircuit]

The project that is being linked to renders everything into a canvas. It's extra work to create a separate tree for another program to digest.

[marcellus23]

You asked why not. That's the answer -- why should platforms create an overcomplicated ML-based solution to try to screen read (assuming such a thing is even possible, which I don't believe it is), when existing solutions using standard frameworks work fine and _don't_ require devs to spend extra time?