> If you want to truly help the blind, [...] all of that requires hard work, countless hours and numerous trials-and-errors.
I do work hard on products to help blind people, and I have been for years, but I can't solve every problem by myself. I even quit my cushy job at Microsoft (on the Windows accessibility team) to develop a product that works around the inaccessibility of screen sharing in online meetings -- imperfectly, but still better than nothing. But neither I nor my tiny company are well-positioned to compete with Cloudflare in the field of security products (such as Browser Isolation) targeted at corporate IT departments. And unfortunately, this particular accessibility problem is not one that we can work around from the outside, at least not yet. So I felt it was worth some of my time to advocate for Cloudflare to make this product accessible.
> And because it is physically impossible to make a blind person as productive at certain tasks as a non-blind one,
Of course; vision is a higher-bandwidth medium than hearing or touch. But that full bandwidth isn't always needed. And unless you've watched a blind person who's proficient with their screen reader, you may be surprised at how productive they can be at a great many tasks.
> there will be always room for improvement and room for more demands.
I appreciate that you and others on this thread don't know me, but I've been active in the online blind community for about 20 years, and I don't believe I'm known for making endless demands of mainstream tech companies. And in this case, there's a natural stopping point: when the remote browser is either as accessible as a local browser on the same website, or as accessible as it can be within the constraints of the web platform (where the client for that remote browser runs). And my original advice to Cloudflare on this subject was targeted at getting the product all the way to that logical endpoint.
Having said all that, I realize that what you said may reflect what people at Cloudflare think; after all, they don't know me either. I vouched for your comment when it was dead because I felt someone should be allowed to say what others might well be thinking, and I didn't think your comment was too inflamatory. I'd appreciate suggestions on how to better signal that I won't, in fact, put them in a bad PR situation by making ever more demands of them.
I don't work at Cloudflare. I am merely trying to share my personal pragmatic point of view.
In this specific case I would argue that the problem is taken out of scope. The idea of browser isolation is to specifically replace the "smart" stream of data that is prone to attacks with a "dumb" pre-rendered version that is much more rigid. This eliminates the whole class of attacks by design.
Sure, it won't work for blind people. So if your organization employs them and you want to achieve comparable level of security, you set them up with a properly isolated VM, install the accessibility software there, and add an exception rule for that VM. Problem solved: the blind person has comparable experience to a regular browser, while the average level of security in the company has raised. If the employer specifically refuses to set up such a VM, it would be reasonable to demand it or sue them.
To put it into a perspective, a blind person cannot drive a car in regular traffic due to obvious reasons. So it's reasonable to provide them with alternate means of transportation, but it would be unreasonable to demand that all cars should be banned until they can accommodate blind drivers. It can be technically done if you make every car remote-drivable, but the cost and safety considerations make it completely unviable.
> I appreciate that you and others on this thread don't know me
mwcampbell has also been active on HN itself for a pretty long time, and reading over his past comments should make it pretty obvious that:
A) he knows what he's talking about.
B) he is putting in a lot of effort to be reasonable and accommodating to other people and businesses.
C) he is personally contributing to and supporting efforts to build products and tools to make things better, not just complaining.
mwcambell's response above is very charitable, and I applaud that; it's good to reach out to people diplomatically. But personally, I also feel like it really wouldn't require that much work for skeptics to go over a few of his past posts and to see for themselves whether or not he is the type of person who would "use the buzzwords to throw the mob at [Cloudflare]."
None of mwcambell's past or present advocacy efforts are secretive, he is probably one of the most recognizable blind/vision-impared advocates on HN right now. I'll risk being slightly less charitable than he is being, and I'll say that people can put in the 5 minutes of effort it would take to figure out whether or not he's a good faith actor -- especially in the context of suggestions to him that the blind community should go out and build their own Cloudflare competitor.
Beware the good intentions. You likely left the big company because you hated being a small cog in the machine filling out the TPS reports.
You went to work in a smaller company because you feel that you are actually making a change. You see the direct result of your actions and motivates much more than a steady paycheck.
I understand that making a small niche product and having to monetize it yourself could be extremely tough, and it looks like a much bigger change to talk a huge player like Cloudflare in following your path, although there's a caveat. If you want them to do the job, you will be always seen as an extra expense line and dealt with it accordingly.
Imagine that you are approached by another blogger demanding that you add support for right-to-left languages to your program, and due to some technicalities, it would push your release date another 6 months on. Or some people find the voice used in the program offensive. Would you happily take on the extra work, or would you just try to sweep them under the rug?
It's always the same formula. Requiring others to do what you believe is right (and they don't) sparks tensions. Offering others something that solves a specific problem they need gives money to you and satisfaction to them. Unfortunately, recently we see too much of the former and too little of the latter.
I do work hard on products to help blind people, and I have been for years, but I can't solve every problem by myself. I even quit my cushy job at Microsoft (on the Windows accessibility team) to develop a product that works around the inaccessibility of screen sharing in online meetings -- imperfectly, but still better than nothing. But neither I nor my tiny company are well-positioned to compete with Cloudflare in the field of security products (such as Browser Isolation) targeted at corporate IT departments. And unfortunately, this particular accessibility problem is not one that we can work around from the outside, at least not yet. So I felt it was worth some of my time to advocate for Cloudflare to make this product accessible.
> And because it is physically impossible to make a blind person as productive at certain tasks as a non-blind one,
Of course; vision is a higher-bandwidth medium than hearing or touch. But that full bandwidth isn't always needed. And unless you've watched a blind person who's proficient with their screen reader, you may be surprised at how productive they can be at a great many tasks.
> there will be always room for improvement and room for more demands.
I appreciate that you and others on this thread don't know me, but I've been active in the online blind community for about 20 years, and I don't believe I'm known for making endless demands of mainstream tech companies. And in this case, there's a natural stopping point: when the remote browser is either as accessible as a local browser on the same website, or as accessible as it can be within the constraints of the web platform (where the client for that remote browser runs). And my original advice to Cloudflare on this subject was targeted at getting the product all the way to that logical endpoint.
Having said all that, I realize that what you said may reflect what people at Cloudflare think; after all, they don't know me either. I vouched for your comment when it was dead because I felt someone should be allowed to say what others might well be thinking, and I didn't think your comment was too inflamatory. I'd appreciate suggestions on how to better signal that I won't, in fact, put them in a bad PR situation by making ever more demands of them.