> First, there's not enough information in the serialized accessibility tree to reconstruct the DOM. There doesn't have to be enough in there to reconstruct t

> First, there's not enough information in the serialized accessibility tree to reconstruct the DOM. There doesn't have to be enough in there to reconstruct the original DOM, just enough to expose all of the information that screen readers and other accessibility tools need. The fact that that information would be exposed through an HTML DOM in this case is irrelevant; we know the Chromium accessibility tree has all the necessary information. > Second, the serialization format is an internal API, so there are no constraints on backwards compatibility. OK, you got me there. Maybe the server side has to go all the way and construct the HTML. > Third, the bandwidth and latency requirements for inter-process communication are far higher than what is available for most client-server communication. OK, again, maybe the server side has to digest the data some more before sending it. But at least Chromium is already pushing serialized tree updates. I'll withhold a rant on how it could be much worse.