2 ms·

Of course the community doesn't care. You can spend your time learning to make a better visually designed project or spend your time learning to make an accessi

Of course the community doesn't care. You can spend your time learning to make a better visually designed project or spend your time learning to make an accessible project. You can't do both (to the same degree and in the same amount of time) and one is way more likely to make a difference in your likelihood to get a job. I agree that the community should care but am not at all surprised that hardly anybody does. There's no incentive to do so. I'm not saying it's solely on businesses to make people care. They don't have the incentives, either. This is where regulations might've helped.

wwweston 9y ago
> There's no incentive to do so Well, the incentives to do so aren't obvious. Having worked on a bunch of (a) web applications with no dynamic client behavior to speak of (b) SPAs that are essentially a dynamic client talking to a service layer speaking JSON and/or XML (c) things in between... I think I've noticed a pattern, and it's that web applications where people take the time to think about how things would work with no dynamic client behavior, going through a process that more or less represents domain logic as HTTP operations on resources that can be represented as HTML (among other representations), these applications end up being more legible over time than projects with client engineering/experience as most of the focus. Not all applications fit this model, so there are limits to the approach. And accessibility is a somewhat different domain. But the concerns overlap, so one tl;dr might be this: Site accessibility is one canary in the web application mines. If it's dead, you might be accumulating technical debt.