[phillipcarter]

There's a bunch of reasons why this model doesn't hold up in the long run, and I'll give one of them: accessibility. Once your business decides that your app must be sufficiently accessible to reach the many people who need accessibility work, your backlog explodes.

[MacsHeadroom]

So ignore accessibility. It's not a legal requirement and it doesn't pay.

McDonald's restaurants have handicap accessible ramps but they don't staff ESL speakers. Apps and web services are no different.

Clubhouse, for example, isn't accessible to the hearing impaired and that's ok.

[XorNot]

Technically it isn't: if you run an American business, you are subject to the Americans With Disabilities act as it is pursuant to electronic services [1].

Uber specifically would definitely fall under a "public transportation" service - accessibility is non-optional if someone decides to sue. [2]

[1] https://www.ada.gov/2010ADAstandards_index.htm

[2] https://www.businessnewsdaily.com/10900-ada-website-requirem...

[NickRandom]

>> So ignore accessibility. It's not a legal requirement and it doesn't pay.

Firstly that is just plain incorrect in a lot of areas (of business) and jurisdictions. Secondly your outlook on accessibility is just ... SMH and walks away from keyboard.

[DrJokepu]

says who? accessibility is not that hard to achieve if you know what you're doing and make efforts from the very beginning to build your product in an accessible fashion

[dwaite]

The problem is that accessibility is not a common high priority requirement for most software, making people with accessibility experience rare.

[phillipcarter]

Show me a single piece of successful software that didn't suffer the "new business requirement upends everything about how we built it" problem.