3 ms·

I generally agree, just a small nitpick: > Are you making sites for blind people? Use/support tools that are thinking about WAI-ARIA/semantic markup. I think

I generally agree, just a small nitpick: > Are you making sites for blind people? Use/support tools that are thinking about WAI-ARIA/semantic markup. I think developers should always have accessibility in their mind. People (or organizations they work for) may choose to use IE8 and yes, it makes sense to draw a line somewhere regards to supporting browsers. They can decide if an upgrade effort is worth to use your application. However people do not choose to have less abilities and it's possible that they can't do anything to change that. I'm not a dictator who says everyone must use all the accessibility best-practices but usually there's a small effort which can be made with huge gains.

pas 9y ago
Absolutely. But that's still a trade off (between using a tool that might be better in some other sense, but then you might not have time to add ARIA tags, or reshape the markup a bit). And usually it's not an explicit requirement. So it's up to the developer/team. And I agree with doing the minimum. There was a great site that shows sites as they "look" like to a screen reader, but I can't find it now. (But it was very much like WAVE http://wave.webaim.org http://wave.webaim.org )