Skip to main content


While many are praising him for his transparency, it reveals a major problem and hurdle with building accessible products. Not to mention the ableism in stating several times, the need to "let everyone in" while choosing not to make sure the application is accessible. Statements like "Our number one focus is letting in the 300K+ users on our waitlist" assume that none of those people have a disability and/or all use technology in the same way.

#a11y

post.news/article/2I8KY7PphGpE…

#a11y
in reply to Homer, CPACC

I might be misinterpreting you, but I'm not sure the issue here is that there is a (real) major problem and hurdle with building accessible products. If they're built accessible/inclusive from the beginning, the hurdle usually doesn't exist in the first place, at least not any more than any other software dev challenge. They'll certainly hit a massive challenge if they do it later. I agree there's a "perceived" hurdle, though.
in reply to Jamie Teh

@jcsteh ... Correct. The problem is not with making sure products are accessible but the idea that accessibility is a feature that can be cut from scope. When in reality, if the process included accessibility best practices early on, and devs authored semantic markup, accessibility would be baked in so to speak. I could go deeper into how It's everyone's responsibility but I feel you understand that already.
in reply to Jamie Teh

@jcsteh ... it's all good. No worries. It's good to clarify just in case someone else was thinking the same thing.

Also, I'd like to thank you. It's very cool that you worked on NVDA! That's my screen reader of choice.