4 ms·
>Developers should be building accessible websites in the first place. Sorry, we've got like ten other people telling us we need to "build websites with <this>
by FLUX-YOU 9y ago
>Developers should be building accessible websites in the first place.
Sorry, we've got like ten other people telling us we need to "build websites with <this> in first place". Accessibility is just another line item at the same point as security, scalability, and resilience.
And for what it's worth, I would prioritize security over accessibility any day of the week.
It's very easy of you to ask all developers to design websites with accessibility in mind. To push all of these requirements onto someone else.
But keep piling on responsibility onto your devs and watch how they build everything in mediocrity because you don't give them time to become good at anything.
The field is utter chaos.
- sbarre 9y agoFYI I'm not sure what you've assumed about me, but I am a developer, and I treat accessibility just as seriously as all the other must-have requirements, and my team makes it work on budget and on time. Just because you need to build an accessible website doesn't mean it can't be secure and scalable too. I'm not sure where you've layered in all these constraints I never brought up (perhaps projecting from your own situation?) but it goes without saying that all aspects of a project need to be properly scoped and planned and given the correct amount of time to be built, and need to be done by people who know what they're doing. If you just see accessibility as "yet another thing I need to do that I don't have time for", then maybe you just need a better job?
- technojunkie 9y agoVery often, if not almost always, there is no competition between security and accessibility. I'm not sure how you get this impression. The two can also go hand in hand, building features that render server-side with security in mind in addition to the existing client-side functionality.