4 ms·
This is sad, but in no way surprising. It has the same root cause as many websites misusing javascript to a point where they become unusable, and that is people
by Grumbledour 8y ago
This is sad, but in no way surprising.
It has the same root cause as many websites misusing javascript to a point where they become unusable, and that is people not really knowing how to use the tools they are given.
One not so dirty secret of accessibility has always been that it is not something you do afterwards, but that you have already done 80% of what needed to be done by just writing valid, standard compliant, semantic HTML.
So I would argue, if you really want to do something to make the web more accessible, usable and a generally nicer place, learn the tools of your trade. No, HTML and CSS are not so simple that they are not worth your time. They are easy to learn, true, but put in the time to get them right. Headings are an H tag, Navs are lists of links, paragraphs are p, not div. Easy stuff like that. And of course, CSS goes hand in hand with that.
You know display: none on a dropdown menu breaks accessibility, right? Of course it does, you tell the browser to not show the content. So use position: absolute; left: -999em or something. These are simple things you could and probably should know and if you do them, you already eliminated most of the problems.
Alt Tag on Images? Yeah, they are easy to forget, but they are also mandatory! So if you tend to be forgetful, use something like pink css borders around images that don't have them, so you won't in the future.
And for using tables for layout: There was a time, way back when, when css 2 was sparkling new and the young guys in the office bought a copy of Zeldmans "Designing with web standards" so the old farts would learn that the world was better now and we didn't need old crutches. If you are still using tables for layout today, you are not a web developer. Harsh but true. They got obsolete with float and position and you also have flexbox or css-grids today. I think you still actually don't need these for 95% of designs, but if you find them easier to use, please do!
And those aria tags or skip to content links? They are actually not the problem. They are icing on the cake. Include them if you like, people might thank you for them, but they also have had tools to compensate for these shortcomings for years, so they are not the real problem. Not displaying content properly or not at all without 500K of JS is, though.
So do something for accessibility and the web and learn the basics, it goes a long way to making you a better and more efficient developer and making the web more pleasant to use for all of us!
- CM30 8y agoWell, tables for layout are necessarily in one very specific case. Namely, coding HTML emails, where CSS support is pretty horrible and (for some reason only known to them), Microsoft decided that they'd use Microsoft Word's rendering engine for Outlook. Yeah, it's screwed up, and god knows what the accessibility of these things is like because of it. Someone needs to start a Zeldman esque web standards push for that media too.
- josephg 8y agoThankfully HTML emails can and should contain a plain text version of their content. Plain text is extremely accessible.
- Grumbledour 8y agoYeah, HTML emails are really a sad state of affairs. So many basic CSS things wont work there consistently. You don't need to even think about position or float when you got trouble setting colors. I actually felt HTML mails were finally coming along and getting better standard support until Microsoft decided to use Words engine instead of IE/Edge. Since then, all is lost on that front.