[mwcampbell]

Congrats on your launch. I do have one concern though:

> a Chromium instance that you embed inside your own web app

Have you considered the accessibility ramifications of this, e.g. for blind people using screen readers? It will certainly be possible to make this accessible; indeed, that's an advantage of your approach over screen sharing. It won't be easy, but of course I believe it's still important and worth doing. My email address is in my profile if you want to discuss this further.

[ScottyFillups]

Thank you!

> Have you considered the accessibility ramifications of this, e.g. for blind people using screen readers?

We are considering the accessibility ramifications now since we've pivoted toward a general API. We didn't focus on accessibility for blind people initially because we were building a watch party platform.

I think offering accessibility features would give us a massive edge against technologies like screenshare! Is there a specific use-case you're thinking of?

[mwcampbell]

> Is there a specific use-case you're thinking of?

The OP mentioned a tutoring use case. If you're going to sell this to educational institutions or companies that serve them, at least in the US, then accessibility is important.

[ScottyFillups]

I see. Sorry! I got excited and went in founder mode — for a moment I thought you had a problem we could solve for you :)

Thank you for stressing the importance of accessibility. We're really impressed with the quality of the questions so far.

[unfocussed_mike]

> indeed, that's an advantage of your approach over screen sharing.

In what way, particularly? it's streaming the video and audio from a remote browser instance, so surely that means all participants will have the same accessibility settings in the remotely viewed instance.

[mwcampbell]

Yes, that's true today. But since they're running a version of Chromium that they control, they can in principle modify it to push semantic information from the Chromium accessibility implementation along with the video stream. That would be much harder for, say, Zoom screen sharing to do, because of the way the platform accessibility APIs are designed.

[unfocussed_mike]

Ahh -- I see. Informative answer, thank you :-)

[ScottyFillups]

To add to mwcampbell's response, my cofounder Amby proposed a possible solution:

> But now that we are looking at the bigger picture, we could implement full-fledged accessibility support where we serialize the accessibility tree and send that over instead of the video stream.

What are your thoughts on this approach?

[mwcampbell]

You probably want to send the accessibility tree in addition to the video stream, not instead of it. Luckily the Chromium accessibility tree can already be serialized and pushed, because Chromium does that between the renderer and browser processes.