It's easy to do when you implement. Links should be links. Buttons should be buttons. Lists should be lists. And so forth.
The problem IMO is that a lot of people see the default styling of, say, a button, and go 'screw that' and make a div do the work of a button instead of trying to override browser button styling. A fair amount of people learn web development very informally, and in my experience very few tutorials or education sources actually talk about accessibility other than as something that sounds like something nice to have. So they don't know why doing this is bad, or they don't think it's a huge problem.
And it's very easy to do these small little accessibility kludges instead of modifying default behavior, and you don't realize what the cost of that is until lots of kludges later you get slapped with a lawsuit. If you're on a team prioritizing composability, this isn't necessarily very difficult to fix, but for websites that exist pre-composable frameworks and use a hodgepodge of older technologically, this is actually very difficult, especially since many of the people who wrote the original logic are probably gone and the code probably isn't commented sufficiently.
Accessibility is just another form of tech debt. I don't know of any places that would hire a tech debt specialist.
The problem IMO is that a lot of people see the default styling of, say, a button, and go 'screw that' and make a div do the work of a button instead of trying to override browser button styling. A fair amount of people learn web development very informally, and in my experience very few tutorials or education sources actually talk about accessibility other than as something that sounds like something nice to have. So they don't know why doing this is bad, or they don't think it's a huge problem.
And it's very easy to do these small little accessibility kludges instead of modifying default behavior, and you don't realize what the cost of that is until lots of kludges later you get slapped with a lawsuit. If you're on a team prioritizing composability, this isn't necessarily very difficult to fix, but for websites that exist pre-composable frameworks and use a hodgepodge of older technologically, this is actually very difficult, especially since many of the people who wrote the original logic are probably gone and the code probably isn't commented sufficiently.
Accessibility is just another form of tech debt. I don't know of any places that would hire a tech debt specialist.