3 ms·
I agree with you, my only point is that accessibility costs something. It either costs time and money if you want to adhere to some standard like WCAG, it costs
by overshard 8y ago
I agree with you, my only point is that accessibility costs something. It either costs time and money if you want to adhere to some standard like WCAG, it costs in hiring a better designer who doesn't make inaccessible design choices and understands basics like contrast ratios, and/or it costs in hiring a developer who has enough experience and common sense to know what is accessible and what isn't.
Accessibility costs time and money, there is no way around this. Not all companies want to pay that money. I don't think the entirety of the blame can be placed on developers.
- Grumbledour 8y agoYou are right, it is not entirely free. I do see a baseline accessibility as necessary to call yourself a competent developer though. And you are right, a competent developer costs more than a bad one. But we are a community of developers here who, i would assume, think of themselves as competent. Should we not strife for a certain baseline standard instead of partaking in a race to the bottom? In the end, there is always someone that does a bad job cheaper than we can. I know there are often economical circumstances and we all cut corners one time or another, but we as the knowledgeable developers must be the one to educate the clients and put in the work, because no one else will.