It's too bad that the legal angle is currently the most likely way to get buy-in from management.
It's also unfortunate what these legal disputes could do if used as a weapon to shut down small teams with less resources, when wieled by corporate legal teams. I'm thinking of teams of devs that are already under pressure and don't have the tools or know-how to quickly implement accessibility into their projects. They could be shut down too easily.
There's a big need and a big opportunity here: to make accessibility easier to implement for every developer by making the knowledge more available and by building dev tools that can help make the job easier.
I'm thinking of challenges like understanding the various ARIA roles and the differences between them, and many developers don't even know that ARIA roles exist because they've never needed to implement them.
Then knowing which ones to use for each of your custom UI controls, and maintaining it all as your UI changes.
What happens if the accessibility attributes get out of sync with the UI because a new developer hasn't been onboarded about accessibility yet? Are incorrect accessibility attributes worse than not having accessibility attributes at all? This is the kind of question that's on my mind when I think about the potential difficulties.
I'm a self-taught Front End & JS Dev and professional learner with accessibility expertise. I'm passionate about breaking down concepts into relatable concepts, making it more approachable.
I'm a self-taught Front End & JS Dev and professional learner with accessibility expertise. I'm passionate about breaking down concepts into relatable concepts, making it more approachable.
I'm really thankful for auditing tools such as Google's Lighthouse. I had read about accessibility but it seemed very complicated to me. ARIA attributes, form labels, contrast ratios?? But when you're able to click one button and get an itemized list of everything to fix and how to do it, suddenly it's not so hard. I was able to get a site which was not created with accessibility in mind at all, to 100% compliant, in an afternoon 😀
I'm a self-taught Front End & JS Dev and professional learner with accessibility expertise. I'm passionate about breaking down concepts into relatable concepts, making it more approachable.
// , “It is not so important to be serious as it is to be serious about the important things. The monkey wears an expression of seriousness... but the monkey is serious because he itches."(No/No)
It's too bad that the legal angle is currently the most likely way to get buy-in from management.
It's also unfortunate what these legal disputes could do if used as a weapon to shut down small teams with less resources, when wieled by corporate legal teams. I'm thinking of teams of devs that are already under pressure and don't have the tools or know-how to quickly implement accessibility into their projects. They could be shut down too easily.
There's a big need and a big opportunity here: to make accessibility easier to implement for every developer by making the knowledge more available and by building dev tools that can help make the job easier.
I'm thinking of challenges like understanding the various ARIA roles and the differences between them, and many developers don't even know that ARIA roles exist because they've never needed to implement them.
Then knowing which ones to use for each of your custom UI controls, and maintaining it all as your UI changes.
What happens if the accessibility attributes get out of sync with the UI because a new developer hasn't been onboarded about accessibility yet? Are incorrect accessibility attributes worse than not having accessibility attributes at all? This is the kind of question that's on my mind when I think about the potential difficulties.
@marek , I am working on creating some course content on this, but I also did an ARIA presentation a year or so ago about some of this nuance.
Amazing, thank you for sharing that.
Thank you for adding your voice to this issue. Accessibility is the right thing to do, always.
Out of curiosity, what do you find difficult about implementing accessibility?
I find it very simple to implement because a large part of accessibility is using semantic HTML. There's also plenty of dev tools that already exist!
Thanks for sharing!
I'm really thankful for auditing tools such as Google's Lighthouse. I had read about accessibility but it seemed very complicated to me. ARIA attributes, form labels, contrast ratios?? But when you're able to click one button and get an itemized list of everything to fix and how to do it, suddenly it's not so hard. I was able to get a site which was not created with accessibility in mind at all, to 100% compliant, in an afternoon 😀
YAY! I love hearing that!!!
Did that happen with the IRL ADA?