4 ms·
The plain HTML example is a bit of a straw-man. It's beyond "dated", being a faux pas for all but the most ascetic of users. My interpretation of "resources" h
by gnode 9y ago
The plain HTML example is a bit of a straw-man. It's beyond "dated", being a faux pas for all but the most ascetic of users.
My interpretation of "resources" here would be time / money. Making sure a site is accessible by everyone takes effort which is difficult to justify, particularly if you're already stretched to capacity.
- logfromblammo 9y agoThat's a way of saying that accessibility is a low priority. Everyone has a choice between finally making the site usable for a minority of potential users, or putting in a new feature. If you always choose the option that makes the most money, some people always get left out. The ADA was drafted to force physical businesses to make reasonable access a higher priority. Accessibility has the same time/money costs as any other feature. The same goes for internationalization and localization. Or for robust user data protection and security. The longer you wait to consider doing it, the more it's going to cost you.
- jopuwep12489 9y agoYou don't need unstyled HTML to look accessible. But you need to keep accessibility in mind from the very beginning with your project. Of course, I've worked in web design, so I know the workflow doesn't really allow you to do anything right from the beginning. Things get hacked up, and accessibility is sacrificed.