|
|
|
|
|
by ctoth
3314 days ago
|
|
Yes, being in the small group that wants people to actually use proper accessible markup as WCAG indicates does put me in a minority, it's true. However, this concept that there are a lot of minorities so obviously we can't cover all the bases seems a little silly. Do people of color need different markup? Do women require somebody adds special javascript libraries so they can access the content?
Making content accessible to a screen reader is part of our job as web developers. Just like the site isn't done until it renders in IE 11, it's not done until it reads with NVDA. In fact, often times people can install an alternative browser, whereas it is currently impossible to install an alternative pair of eyeballs, so I would go so far as to advocate accessibility before heroic browser compatibility battles but obviously I'm biased here ;-) |
|
Interesting opinion. I'd argue that it's not at all a web developer's job to comply with every single accessibility guideline or support outdated browsers, unless required by their contract and paid for by whoever commissioned the work. These requirements are part of the reason that most governmental contracts are overpriced by a factor of 10 (the other reason being corruption).