Text-only version of your site?
In the past, sites had no real structure and multimedia elements were used heavily without any thought of alternate content.
When these sites had to be made accessible the knee-jerk reaction was often to create a text-only version of the site. This allowed those unable to access the main site a means of reading the content, but at a cost.
Adding a text-only site in those days effectively doubled the web team's workload as it was a whole other site to maintain. Text-only sites contained content that was incomplete or of lower quality and over time gradually became more and more out of sync with the main site. An often used analogy, is the idea of having a restaurant where quality food is served upstairs and passable food is served on the ground floor in the kitchen. Diners unable to tackle the stairs are forced to have a lower quality experience. The dual-site approach ticked all the boxes for accessibility in theory, but in practice rarely offered value.
To counter these problems, text-only sites became dynamic and shared the databases that powered the live site. The main site would then link off to a 'text only' site (the same site, but using different HTML templates that removed all styling). This was an improvement, but it missed an important point.
Most screen-readers and assistive technologies work by screen scraping; reading all the visible text on the page. This happens regardless of whether the site is text-only or not. Although text-only sites can help users who have visual difficulties, a better approach would be to provide alternative colour schemes or advise and educate the user on how to create and apply user stylesheets.
To make sure that assitive technologies can make sense of your website, it is more important to structure your pages well. The templates supplied with your website will give you a good base structure to work from, but it's important that the copy you add through the CMS maintains the standard.
Good structuring tips include using heading elements rather than simply making text bold (and bigger!) to both clarify what the following section is about and to create a heirarchy (e.g. h3 is considered a sub-section of h2). Additionally, when creating links to other pages it's good practice to ensure that the linking text makes sense when read out of context - try to resist typing 'click here'!
By taking accessibility into account at the start of a project and making it a part of the project instead of a bolt-on as in the past, your site will be more accessible with less effort. With a little care, keeping your site maintained and accessible to all can be a piece of cake. Stop trying to be accessible and start being accessible!
- Published: 7 November 2007
I think the concept of 'accessible' design has moved on considerably since the heady days of pure text versions of sites, theres no reason why a screen reader shouldn't be able to navigate and correctly convey the content of a website, so long as that site is properly constructed from the outset with web standards and accessibility in mind.
Obviously if there is any kind of CMS attached to the site the end user of that system needs to be educated too, or have facilities provided for them within the CMS to ensure they're kept in check.
If someone could adapt FCKeditor or HTMLarea to include standards parsing (warning! you have neglected to add alt/title attributes to the following images!) We'd have alot less headaches over clients ruining perfectly good websites after hand-over :)
In reference to the previous comment, I think perhaps integrating that kind of stuff into the visual editor is possibly overkill; yes sure, some of the images may not have alt attributes but as long as the actual website is navigable and content accessible then i'd say "job well done" to be honest.
I still work with someone who has the mindset of "accessibility is an additional feature" when in fact it should be "the way" of doing things, end of story (because it's the correct way).
The fact is, if the site is coded properly then you're in a win-win situation of being WELL on the way to having produced:
* an accessible website
* a search engine friendly website
* a bandwidth-saving, fast-loading website
* a warm patch in your trousers (mebbe thats me, lol).
Good article ...