If government regulations are going to insist I have to put that investment in day 1, I'll just take up badminton or something.
It's not that hard, and if every developer spent an afternoon looking into things, they'd realize how easy it is to get it right if the team is aware of it.
I'd not mind if like developers need to go through security and privacy training, they'd also go through accessibility training. A little investment would go really far.
They all handle accessibility well, you just need to remember adding labels to your icon buttons, and you are good to go. If you don't reinvent the wheel thinking your buttons are soooo different that it needs to be rewritten from scratch, things just work.
For example, the ADA doesn't require employers to accommodate disability needs until a business has 15 employees.
Preparing food unhygienically is bad for everyone at the picnic.
A more appropriate analogy is disallowing watermelon at the picnic because one person can't eat watermelon.
> Please go play badminton.
Love the irony of including this comment in a post about making your app inclusive
> Love the irony of including this comment in a post about making your app inclusive
Why is that ironic? There's a broad gap between being unable to use an app due to a disability, and unwilling to write apps that will be usable to people with disabilities. One is an immutable characteristic of a person, and the other is a personal choice to be calous. Inclusivity doesn't mean you can't kick people out for being jerks.
And in this case, if I were to hire a developer for an app, and they were so dismissive of accessibility concerns, I would end their interview with abrupt and direct feedback and the law would be on my side.
And, yes, I'm with Popper. The "Paradox of tolerance" is real. It's OK to tell intolerant people that they're not welcome.
Of course, culture is a huge factor. The US wasn't built on "regulation, or else", it was built on "if you can, do". This makes business boom, but makes other concerns, like welfare, an afterthought. And it's up to debate which system is better to exist in. People dislike the rules, until it ends up benefiting them.
I haven't found anything in that vein and I'm curious if anyone's working on it.
It's part of why I've really tried to stay employed with smallish businesses, because they're more human.
That aside, the work of prioritizing accommodations is already done. Just read through the WCAG criteria, start with level A, then AA. They already determined what the most critical issues are to accommodate everyone who uses your app. I find it extremely callous to frame people's ability to use your product in terms of the revenue they have to offer you. A storefront has to build a ramp because everyone deserves basic human decency, not because they want wheelchair users to spend money inside.
My apologies for the math inaccuracy is in the mail.
I wasn't really trying for pedantry, but, if the check's in the mail, thanks for 0.666% of a coffee ;)
[1] https://www.accessibility.works/blog/avoid-accessibility-ove...
>16% of people have some kind of accessibility requirement
16% is 4 in 25 people, also no guarantee you'll be able to accommodate their specific accessibility requirement, depending on the app, and depending on the requirement.
That's not to say the app shouldn't be accessible, more that, you should think about when you spend the money to implement things like this, and how that money may best be spent to accommodate the highest number of people. Figure out who those people are, then figure out what your revenue growth would be if you captured those people, then compare those numbers to how much you'll have to spend to accommodate their needs. That's no different than any feature upgrade really.
Where you'll likely arrive at is the same place many apps have, unfortunately, arrived at, which is to probably just get text scaling quasi working and leave it at that because anything more is throwing cash into a black hole.