[SLJ7]

>I'm sure the mechanism for configuring this bypass is documented. But does your documentation specifically call out the accessibility limitation of your product, the need for this workaround, and the recommended additional safeguards for these employees' machines?

This is super important. Remember that while a bunch of us are nerds who know how computers work, some blind people might just know enough to use the web and do their job--as most people in the world do. They won't understand why the product doesn't work, let alone know how to fix it. The problem with a solution this transparent is that a request will have to go way up the chain before someone will actually know enough to address it and determine the problem. Of course it's not the job of Cloudflare to fix corporate ignorance, but a note like this one in the documentation might be a good start.

[mwcampbell]

Also, it's worth noting that when using Browser Isolation with a screen reader, the product itself doesn't tell the user anything informative, e.g. through one of those off-screen messages that are sometimes added to websites specifically for screen reader users. Instead, the user gets a debug UI that isn't even visible on the screen, followed by an unlabeled graphic. So as far as anyone on the outside can tell (at least, before today's conversation), Cloudflare has done nothing about accessibility in this product.