Plus, its not that hard to do correctly, so the “we’re a startup on a critical burn rate” stops working as an excuse rather early
Plus, its not that hard to do correctly, so the “we’re a startup on a critical burn rate” stops working as an excuse rather early
In my previous life at an ad agency we had a number of clients getting pursued by accessibility lawyers and firms. These were typically nothing more than shakedowns for some insignificant settlement (<$10k) - but it was an open-and-shut case if you wanted to take it to court so it was just easier to settle and spend a couple of sprints on WCAG best practices.
IANAL and my agency didn't do the actual implementation so it was typically up to the client to sort out - but having a lawyer on hand should be one of the first things you take care of once you start making or accepting large amounts of money.
Typically it was just an embarrassing experience for some middle manager, some lost budget, and some extra dev hours to add 'WCAG Compliance' to the QA checklist.
It's not a question of it being too hard or easy, but as always, a question of priorities.
Say you can either build feature A which is expected to open up the product to be used by 1% more users, as people been asking for that feature. Or you can build feature B, which enables motionsick people to use your app without getting sick from your wasteful animations. This will help 0.001% of your current users, when you have 10,000 users in total lets say.
Not saying it's right or wrong, but I understand why people (managers/owners) make the choice to do feature A instead of feature B, especially in a startup-context where it might be the (imaginary or not) choice between surviving or not.
I'm personally in the camp of thinking about accessibility as part of all the work done, but it's not exactly the mainstream workflow.