{"id":47,"date":"2006-06-27T20:52:36","date_gmt":"2006-06-28T00:52:36","guid":{"rendered":"http:\/\/unitstep.net\/blog\/2006\/06\/27\/web-accessibility-both-sides-of-the-coin\/"},"modified":"2006-06-27T21:08:57","modified_gmt":"2006-06-28T01:08:57","slug":"web-accessibility-both-sides-of-the-coin","status":"publish","type":"post","link":"https:\/\/unitstep.net\/blog\/2006\/06\/27\/web-accessibility-both-sides-of-the-coin\/","title":{"rendered":"Web accessibility: Both sides of the coin"},"content":{"rendered":"

Web accessibility<\/a> is a hot topic nowadays. Many articles<\/a> have been written<\/a> about the topic, so that there’s no shortage of information should you want to design an accessible website that at least aims to be usable by all, regardless of any disabilities. This, after all, is a good thing, since if public buildings are mandated to be accessible by the disabled, shouldn’t public websites be as well?
\n<\/p>\n

Necessarily accessible<\/h3>\n

In fact, many governments, both at the upper and lower levels, have been mandating accessibility for public websites. In the United States, there’s Section 508<\/a>, and in Europe, they’re working on making it mandatory<\/a>. Here in Canada, I don’t think there’s any federal law on it, though I might be mistaken. However, in Ontario, I believe the ODA<\/abbr><\/a> applies, or will apply, to most institutions that receive government funding, including universities, which is all the more reason for them to adopt standards<\/a>. <\/p>\n

Doing it right<\/h3>\n

Designing an accessible website is not particularly hard, but it does take some extra planning. Not being a public institution, I’ll admit I haven’t taken accessibility to heart, as there are many things I could do to improve it. Thankfully, there are plenty of resources out there. The Web Accessibility Initiative<\/a> is a good starting point, and the Watchfire WebXACT<\/a> tool will help evaluate your site for accessibility. My site fails horribly right now, however, it wouldn’t be too<\/em> hard to fix this, but I just haven’t bothered because I’m not aiming to reach everyone; a weak excuse, but an excuse nonetheless. With a good platform like WordPress, site-wide changes aren’t hard to implement, and structured blogging<\/a>, a sort of microformat<\/a>, could help even more. <\/p>\n

In essence, making an accessible website is closely related to making your site semantically sound. The two aren’t exactly the same, but if you use semantic markup and get used to it, making things accessible becomes a lot easier. Every web designer (and also web developers) should be aware of this, and take these best practices to heart. If I were to design a site for a company or any institution that aimed to reach out to as many people as possible, I would definitely factor in accessibility and semantically sound markup from the beginning, despite the extra planning it would take. Any time you spent in during this stage would more than make up for any extra time you’d have to spend converting a poorly-designed site to be accessible. <\/p>\n

The other side of accessibility<\/h3>\n

However, one aspect I think is often missed out on is the other side of web accessibility; what I mean by this is that not only must content be accessible, but the ability to produce content<\/em> should also be accessible to all, regardless of their technical knowledge about web standards.<\/p>\n

In the past, this was almost impossible. Before there were WYSIWYG<\/acronym> editors, people had to write HTML<\/acronym> by hand, something not everyone can do. Even when people did know how to use HTML<\/acronym>, it was not always used correctly, and rarely with accessibility in mind. The dawn of WYSIWYG<\/acronym> editors did not improve this at all, as most of them tended to produce a tag soup of HTML<\/acronym> that was rarely valid, much less accessible. (Versions of Microsoft Frontpage are perhaps a good example.) <\/p>\n

Thus, the web turned into a jumble of unsound pages and examples of the ineffective use of HTML<\/acronym>, and later, XHTML<\/acronym><\/a>. I don’t believe this was the fundamental fault of the authors, as I don’t believe everyone who wants to publish content on the web should have to understand all the details of XHTML<\/acronym><\/a> – after all, does the author of a book usually have to understand all the intricate details of book publishing? I believe the fault lay with the lack of an easy-to-use editor that could produce structurally sound markup.<\/p>\n

Thankfully, things are getting better. Ever since web accessibility standards were clearly defined<\/a>, there have been movements to make publishing well marked-up content easier on the web. Firstly, many online blogging services offer fairly easy-to-use editors, and the next version of Word<\/a> will support blogging, and hopefully, valid XHTML<\/acronym><\/a> output. TinyMCE<\/a>, a WYSIWYG<\/acronym> editor written entirely in JavaScript, can be used with WordPress<\/a> and Drupal<\/a>, popular blog and CMS<\/acronym> platforms, respectively. It effectively provides a word-processor-like interface for document creation, and should greatly improve people’s ability to easily publish web content within a CMS<\/acronym> without having to burden a tech services department. <\/p>\n

Let’s hope these editors continue to improve to increase accessibility, on both sides of the coin.<\/p>","protected":false},"excerpt":{"rendered":"

Web accessibility is a hot topic nowadays. Many articles have been written about the topic, so that there’s no shortage of information should you want to design an accessible website that at least aims to be usable by all, regardless of any disabilities. This, after all, is a good thing, since if public buildings are […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[37,39,2],"tags":[],"_links":{"self":[{"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/posts\/47"}],"collection":[{"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/comments?post=47"}],"version-history":[{"count":0,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/posts\/47\/revisions"}],"wp:attachment":[{"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/media?parent=47"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/categories?post=47"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/tags?post=47"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}