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 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.