I wonder if they ever got around to implementing accessibility, e.g. for screen readers, in their remote browser. That's an interesting problem. Do you send serialized accessibility trees (and hopefully incremental updates) down to the local machine so it can implement the platform accessibility API and work with a user's existing assistive technology (e.g. screen reader)? Or do you run the AT remotely as well? I believe the former is feasible with Chromium (though I haven't yet proven it), but Cloudflare went with the latter in their Browser Isolation product, probably because converting the Chromium accessibility tree back to HTML in the local browser would compromise the security benefit of Cloudflare's product. But Mighty didn't have that concern AFAIK.