<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Writing for the Web</title>
	<atom:link href="http://www.deyalexander.com.au/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.deyalexander.com.au/blog</link>
	<description>Useful, usable, accessible. The way web content should be.</description>
	<lastBuildDate>Mon, 01 Mar 2010 05:42:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>The 5 Es of content usability</title>
		<link>http://www.deyalexander.com.au/blog/2010/02/the-5-es-of-content-usability/</link>
		<comments>http://www.deyalexander.com.au/blog/2010/02/the-5-es-of-content-usability/#comments</comments>
		<pubDate>Sun, 28 Feb 2010 04:50:35 +0000</pubDate>
		<dc:creator>Dey</dc:creator>
				<category><![CDATA[Conciseness]]></category>
		<category><![CDATA[Findability]]></category>
		<category><![CDATA[Readability]]></category>
		<category><![CDATA[Scannability]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[effective]]></category>
		<category><![CDATA[efficient]]></category>
		<category><![CDATA[engaging]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[learnable]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.deyalexander.com.au/blog/?p=192</guid>
		<description><![CDATA[I&#8217;ve long been a fan of Whitney Quesenbery&#8217;s 5 Es of usability: effective, efficient, engaging, error tolerant and easy to learn. They&#8217;re a great way to explain what usability is — to make &#8216;easy to use&#8217; or &#8216;user friendly&#8217; more meaningful to clients, designers, developers.
I think the 5 Es can also be helpful for understanding [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve long been a fan of <a href="http://www.wqusability.com/articles/more-than-ease-of-use.html">Whitney Quesenbery&#8217;s 5 Es of usability</a>: effective, efficient, engaging, error tolerant and easy to learn. They&#8217;re a great way to explain what usability is — to make &#8216;easy to use&#8217; or &#8216;user friendly&#8217; more meaningful to clients, designers, developers.</p>
<p>I think the 5 Es can also be helpful for understanding content usability. And given the state of content on many websites, we can do with a little more understanding! So here&#8217;s my version of the 5 Es applied to content.</p>
<h3>Effective</h3>
<p>Effective content is:</p>
<ul>
<li>Relevant. It meets users information needs, answers their questions, helps them complete their tasks or meet their goals.  It is not fluff, happy talk, welcome messages or things people already know or don&#8217;t care about.</li>
<li>Complete. There are no gaps or pieces missing. Users can get what they need from it.</li>
<li>Clear and unambiguous. The message is communicated effectively. No risks are taken by trying to be cute or clever.</li>
<li>Accurate and up-to-date.</li>
</ul>
<h3>Efficient</h3>
<p>Efficient content is:</p>
<ul>
<li>Fast to find via navigation or search.</li>
<li>Easy to read. It uses common, everyday words. It does not force users to look up dictionaries or glossaries or memorise acronyms or abbreviations. It uses short sentences. It avoids passive voice, weak verbs and double negatives.</li>
<li>Concise.  It has been reviewed and edited, and non-essential words removed.</li>
<li>Structured well. The important or most frequently used information is at the top. Related information is grouped together. It has a logical sequence.</li>
<li>Designed for scan-reading. Headings, lists, tables and graphics make it easy for users to see what they&#8217;re looking for.</li>
</ul>
<h3>Engaging</h3>
<p>Engaging content is:</p>
<ul>
<li>Presented well on screen. It looks clean and uncluttered rather than busy and dense.</li>
<li>Neither too formal, nor too informal.</li>
<li>Not afraid to use personal pronouns. It speaks to &#8216;you&#8217; rather than &#8216;customers&#8217;, and it  is from &#8216;us&#8217; rather than &#8216;the Department of Some Excruitiatingly Long Name&#8217;.</li>
</ul>
<h3>Error tolerant</h3>
<p>Error tolerant content is:</p>
<ul>
<li>Clear and unambiguous. The content is unlikely to be misundertood by users.</li>
<li>Accurate and up-to-date.</li>
</ul>
<h3>Easy to learn</h3>
<p>Easy to learn content is:</p>
<ul>
<li>Written using familiar terms. Users do not have to struggle with jargon or words they are unfamiliar with.</li>
<li>Structured and presented to aid comprehension.</li>
<li>Supported by examples, images or illustrations where needed.</li>
</ul>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.deyalexander.com.au%2Fblog%2F2010%2F02%2Fthe-5-es-of-content-usability%2F&amp;linkname=The%205%20Es%20of%20content%20usability"><img src="http://www.deyalexander.com.au/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.deyalexander.com.au/blog/2010/02/the-5-es-of-content-usability/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t make me read (useless words)</title>
		<link>http://www.deyalexander.com.au/blog/2010/01/dont-make-me-read-useless-words/</link>
		<comments>http://www.deyalexander.com.au/blog/2010/01/dont-make-me-read-useless-words/#comments</comments>
		<pubDate>Thu, 07 Jan 2010 07:38:22 +0000</pubDate>
		<dc:creator>Dey</dc:creator>
				<category><![CDATA[Conciseness]]></category>
		<category><![CDATA[concise]]></category>
		<category><![CDATA[verbose]]></category>
		<category><![CDATA[wordy]]></category>

		<guid isPermaLink="false">http://www.deyalexander.com.au/blog/?p=189</guid>
		<description><![CDATA[If you&#8217;ve ever watched people read online, you&#8217;ll know they rarely read closely. Most people scan read most of the time.  When we ask them why, they tell us they just want the information they need and can&#8217;t be bothered with the rest.
One of the key issues is that so much of what gets published [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;ve ever watched people read online, you&#8217;ll know they rarely read closely. Most people scan read most of the time.  When we ask them why, they tell us they just want the information they need and can&#8217;t be bothered with the rest.</p>
<p>One of the key issues is that so much of what gets published online is unnecessarily wordy. There are two problem areas  — wordy writing and content that isn&#8217;t of any real value, such as:</p>
<ul>
<li>Welcome messages — as though someone will be offended if we don&#8217;t welcome them every time they come to our website</li>
<li>Instructions that don&#8217;t tell us anything we didn&#8217;t already know — &#8216;click on the links below to find the information you want&#8217;</li>
<li>Introductions that state the obvious or repeat information that appears further down the page</li>
<li>Background that people already know or don&#8217;t care much about.</li>
</ul>
<p>An article in the current edition of <cite>The Atlantic</cite> suggests that people have moved to using online newspapers because the print versions are unnecessarily long. It includes some great examples. Although the analysis relates to journalism, there are lessons here for web writers too.</p>
<p>See: <a href="http://www.theatlantic.com/doc/201001/short-writing">Cut this story, by Michael Kinsley</a></p>
<ul></ul>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.deyalexander.com.au%2Fblog%2F2010%2F01%2Fdont-make-me-read-useless-words%2F&amp;linkname=Don%26%238217%3Bt%20make%20me%20read%20%28useless%20words%29"><img src="http://www.deyalexander.com.au/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.deyalexander.com.au/blog/2010/01/dont-make-me-read-useless-words/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A resolution for the new year: don&#8217;t forget the &#8216;C&#8217; in WCAG!</title>
		<link>http://www.deyalexander.com.au/blog/2009/12/a-resolution-for-the-new-year-dont-forget-the-c-in-wcag/</link>
		<comments>http://www.deyalexander.com.au/blog/2009/12/a-resolution-for-the-new-year-dont-forget-the-c-in-wcag/#comments</comments>
		<pubDate>Tue, 29 Dec 2009 16:41:45 +0000</pubDate>
		<dc:creator>Dey</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[authors]]></category>
		<category><![CDATA[CMS]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[WCAG]]></category>
		<category><![CDATA[WCAG 2.0]]></category>
		<category><![CDATA[writers]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.deyalexander.com.au/blog/?p=182</guid>
		<description><![CDATA[With the likely adoption of WCAG 2.0 (the second version of the Web Content Accessibility Guidelines) in Australia, organisations might be reviewing their website design and templates to meet the new standards in 2010. What they might forget though, is to check their content or update the skills and knowledge of those who produce it.
Lack [...]]]></description>
			<content:encoded><![CDATA[<p>With the likely adoption of WCAG 2.0 (the second version of the Web Content Accessibility Guidelines) in Australia, organisations might be reviewing their website design and templates to meet the new standards in 2010. What they might forget though, is to check their content or update the skills and knowledge of those who produce it.</p>
<h3>Lack of knowledge around content production and accessibility</h3>
<p>In my experience:</p>
<ul>
<li>many web writers have little understanding of web accessibility</li>
<li>some have heard of &#8216;alt tags&#8217; but few know how to write them or what they are for</li>
<li>organisations are not aware of the impact writers and publishers can have on accessibility</li>
<li>web writers rarely get training in web accessibility.</li>
</ul>
<h3>Content management systems do not prevent accessibility problems</h3>
<p>Even within a tightly controlled environment such as a content management system, writers can affect compliance with the new guidelines. There are 19 WCAG 2.0  &#8217;success criteria&#8217; that a site may fail if those who write the content are not trained in accessibility.</p>
<h3>Make a resolution to address this issue in 2010</h3>
<p>Do your organisation, writers and users a favour. Make a new year&#8217;s resolution to address this issue.  To help you get started, I&#8217;ve attached a presentation I gave on this topic at the OZeWAI conference in Melbourne a few weeks ago.  Let me know if you have any queries.  In the meantime &#8230;</p>
<p>Happy New Year!</p>
<div id="__ss_2562552" style="width: 425px; text-align: left;"><a style="font: 14px Helvetica,Arial,Sans-serif; display: block; margin: 12px 0 3px 0; text-decoration: underline;" title="Don't forget the 'C' in WCAG" href="http://www.slideshare.net/deyalexander/dont-forget-the-c-in-wcag">Don&#8217;t forget the &#8216;C&#8217; in WCAG</a><object style="margin: 0px;" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="425" height="355" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowScriptAccess" value="always" /><param name="src" value="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=wcag2-4-writers-ozewai-091123002817-phpapp02&amp;stripped_title=dont-forget-the-c-in-wcag" /><param name="allowfullscreen" value="true" /><embed style="margin: 0px;" type="application/x-shockwave-flash" width="425" height="355" src="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=wcag2-4-writers-ozewai-091123002817-phpapp02&amp;stripped_title=dont-forget-the-c-in-wcag" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
<div style="font-size: 11px; font-family: tahoma,arial; height: 26px; padding-top: 2px;"></div>
</div>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.deyalexander.com.au%2Fblog%2F2009%2F12%2Fa-resolution-for-the-new-year-dont-forget-the-c-in-wcag%2F&amp;linkname=A%20resolution%20for%20the%20new%20year%3A%20don%26%238217%3Bt%20forget%20the%20%26%238216%3BC%26%238217%3B%20in%20WCAG%21"><img src="http://www.deyalexander.com.au/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.deyalexander.com.au/blog/2009/12/a-resolution-for-the-new-year-dont-forget-the-c-in-wcag/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The trouble with page titles</title>
		<link>http://www.deyalexander.com.au/blog/2009/10/the-trouble-with-page-titles/</link>
		<comments>http://www.deyalexander.com.au/blog/2009/10/the-trouble-with-page-titles/#comments</comments>
		<pubDate>Mon, 12 Oct 2009 00:55:27 +0000</pubDate>
		<dc:creator>Dey</dc:creator>
				<category><![CDATA[Findability]]></category>
		<category><![CDATA[doc]]></category>
		<category><![CDATA[page titles]]></category>
		<category><![CDATA[pdf]]></category>
		<category><![CDATA[Powerpoint]]></category>
		<category><![CDATA[ppt]]></category>
		<category><![CDATA[search engine]]></category>
		<category><![CDATA[search results]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[SERP]]></category>
		<category><![CDATA[titles]]></category>
		<category><![CDATA[Word]]></category>

		<guid isPermaLink="false">http://www.deyalexander.com.au/blog/?p=101</guid>
		<description><![CDATA[Page titles play a critical role on the web. The words we use in them are important for search engine optimisation. And well-written page titles help users sort through search results. However, too many pages have poor titles. The trouble is, we don't pay enough attention to them. ]]></description>
			<content:encoded><![CDATA[<p>Writing good page titles is one of the more challenging aspects of writing for the web. We only have 60-70 characters to work with — characters that are extremely important.</p>
<p>The words we use in page titles play a key role in search engine optimisation. Most search engines give them more weight than words elsewhere on the page. And given scan-reading behaviour, well-written page titles are more likely to be noticed by web users in a page of search results.</p>
<p>The trouble with page titles is that we don&#8217;t give them enough  attention.</p>
<h3>When <acronym title="What You See Is What You Get">WYSIWYG</acronym> editors ruled, page titles were invisible</h3>
<p>When <acronym title="What You See Is What You Get">WYSIWYG</acronym> editors were the most popular publishing tools, many people didn&#8217;t even realise they had to write a page title. The title edit field was rarely displayed in the content editing area. Out of sight meant out of mind, and loads of web pages never got a title.</p>
<p>Google&#8217;s timeline option shows the problem increasing from the mid-90&#8217;s and easing after 2006.</p>
<div id="attachment_105" class="wp-caption alignleft" style="width: 610px"><img class="size-full wp-image-105" title="Google timeline results for 'untitled document'" src="http://www.deyalexander.com.au/blog/wp-content/uploads/2009/10/google-timeline-untitled-documents1.gif" alt="Google timeline results for 'untitled document'" width="600" height="223" /><p class="wp-caption-text">Google timeline results for &#39;untitled document&#39;</p></div>
<h3>Content management systems help, but only a little</h3>
<p>Content management systems help address this problem because they can write the page title for us. However they can introduce a new set of problems.</p>
<p>Many systems are set up to take the main heading (the H1) and use that as the page title. This is better than &#8216;untitled document&#8217;, but only just. Using only the main heading of the page, such as &#8216;contact us&#8217;, will not provide enough context in search results. Who is &#8216;us&#8217; when users see a whole page of similar search results on Google?</p>
<div id="attachment_107" class="wp-caption alignleft" style="width: 610px"><img class="size-full wp-image-107" title="Many pages may have 'Contact us' as the page title" src="http://www.deyalexander.com.au/blog/wp-content/uploads/2009/10/google-contact-us.gif" alt="Many pages may have the same page title, such as 'Contact us'" width="600" height="369" /><p class="wp-caption-text">Many pages may have the same page title, such as &#39;Contact us&#39;</p></div>
<p>Some systems add the organisation name to the main heading. This gives some context, but for large organisations there may still be  several  &#8216;contact us&#8217; or &#8216;about us&#8217; pages in search results: one for each business unit.</p>
<p>And that&#8217;s not the only problem with this approach.  The image below shows a page from the State Library of Western Australia. The page title — &#8216;Australia: State library of Western Australia&#8217; —  has been created by adding the organisation name to the main heading.</p>
<p>The page is about Australian family history resources, but that&#8217;s not at all obvious from the page title.</p>
<div id="attachment_112" class="wp-caption alignleft" style="width: 610px"><img class="size-full wp-image-112" title="Australian family history resources, State Library of Western Australia" src="http://www.deyalexander.com.au/blog/wp-content/uploads/2009/10/title-context-slwa.gif" alt="Australian family history resources, State Library of Western Australia" width="600" height="470" /><p class="wp-caption-text">Australian family history resources, State Library of Western Australia</p></div>
<p>Content management systems can help writers by adding some text to the title field to get started with. But they should always allow the writer to edit it.</p>
<h3>And now we&#8217;re overrun by untitled PDF, Word and Powerpoint documents</h3>
<p>While the number of untitled web pages has dropped, the problem of untitled or poorly titled documents continues with PDF, Word and Powerpoint files.</p>
<p>Again, a key problem is that the title field is not visible when writers produce the content. However many writers are also unaware that the title will be used as the link text in search results, and that it is important for search engine optimisation.</p>
<div id="attachment_123" class="wp-caption alignleft" style="width: 610px"><img class="size-full wp-image-123" title="Untitled Powerpoint slides in Google search results" src="http://www.deyalexander.com.au/blog/wp-content/uploads/2009/10/google-untitled-ppt.gif" alt="Untitled Powerpoint slides in Google search results" width="600" height="433" /><p class="wp-caption-text">Untitled Powerpoint slides in Google search results</p></div>
<h3>Pay more attention to page titles</h3>
<p>To fix this problem, we need to pay more attention to page titles.</p>
<p>Web writers need to understand their role and how to write them well — for all the documents they publish online, not just web pages. And website managers need to check how their content management system handles the creation of page titles. It&#8217;s OK to start with the main heading and organisation name, but it&#8217;s important to ensure that writers can edit this text.</p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.deyalexander.com.au%2Fblog%2F2009%2F10%2Fthe-trouble-with-page-titles%2F&amp;linkname=The%20trouble%20with%20page%20titles"><img src="http://www.deyalexander.com.au/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.deyalexander.com.au/blog/2009/10/the-trouble-with-page-titles/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Getting the planning process right</title>
		<link>http://www.deyalexander.com.au/blog/2009/09/getting-the-planning-process-right/</link>
		<comments>http://www.deyalexander.com.au/blog/2009/09/getting-the-planning-process-right/#comments</comments>
		<pubDate>Wed, 30 Sep 2009 03:14:33 +0000</pubDate>
		<dc:creator>Dey</dc:creator>
				<category><![CDATA[Planning content]]></category>
		<category><![CDATA[content approvers]]></category>
		<category><![CDATA[content owners]]></category>
		<category><![CDATA[discuss]]></category>
		<category><![CDATA[draft]]></category>
		<category><![CDATA[outline]]></category>
		<category><![CDATA[plan]]></category>
		<category><![CDATA[planning process]]></category>
		<category><![CDATA[stakeholders]]></category>

		<guid isPermaLink="false">http://www.deyalexander.com.au/blog/?p=95</guid>
		<description><![CDATA[Yesterday, a participant in my workshop said she felt there was no point planning content for a web page. In her experience, content approvers made so many changes to the content, that it barely resembled the original draft. Here's how you could deal with this ...]]></description>
			<content:encoded><![CDATA[<h3>What’s the point in planning when approvers make so many changes?</h3>
<p>Yesterday, a participant in my workshop said she felt there was no point planning content for a web page. In her experience, content approvers made so many changes to the content, that it barely resembled the original draft. She felt any work she did to plan a page would just be wasted.</p>
<p>Fair point, but is this a good practice?  At the very least, it wastes her time. It probably also wastes the time of content approvers. And who knows if this kind of process leads to useful, usable content for their customers?  I doubt that it does.</p>
<h3>Involve content approvers in planning</h3>
<p>One solution is to involve content approvers in the planning process.  Before drafting anything at all, sit down and talk with them about their expectations.</p>
<p>Some issues you could discuss are:</p>
<ul>
<li>Why has      this new content been requested? What      business objective will the content help the organisation meet?</li>
<li>Who is      the target audience for the content? What  will they want from it?</li>
<li>What      should the focus of the page be? What is the key message?</li>
<li>How      does this page relate to other content on the site? How does it relate to other communication channels?</li>
</ul>
<h3>Get content approvers to check an outline</h3>
<p>Before you write a draft, prepare an outline of the content. You could draft some of the main headings and jot down the key points to be covered. Get the content approver to check this before you go any further.</p>
<p>If you have approvers who are reluctant to give you their time, do this second step first.  When talking to them about your outline, you can explore their views of the business objectives and audience needs for the content.</p>
<h3>Planning is worth it</h3>
<p>Some sort of discussion like this — it doesn’t have to be very formal — should always happen before new content is written. You shouldn’t start drafting until you’ve got all the information you need.</p>
<p>A little planning is likely to save time, and produce better results.</p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.deyalexander.com.au%2Fblog%2F2009%2F09%2Fgetting-the-planning-process-right%2F&amp;linkname=Getting%20the%20planning%20process%20right"><img src="http://www.deyalexander.com.au/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.deyalexander.com.au/blog/2009/09/getting-the-planning-process-right/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Content is king? Not in WCAG 2.0!</title>
		<link>http://www.deyalexander.com.au/blog/2009/09/content-is-king-not-in-wcag-2-0/</link>
		<comments>http://www.deyalexander.com.au/blog/2009/09/content-is-king-not-in-wcag-2-0/#comments</comments>
		<pubDate>Wed, 23 Sep 2009 01:33:31 +0000</pubDate>
		<dc:creator>Dey</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Readability]]></category>
		<category><![CDATA[abbreviations]]></category>
		<category><![CDATA[headings]]></category>
		<category><![CDATA[idioms]]></category>
		<category><![CDATA[links]]></category>
		<category><![CDATA[shortened forms]]></category>
		<category><![CDATA[WCAG 2.0]]></category>

		<guid isPermaLink="false">http://www.deyalexander.com.au/blog/?p=64</guid>
		<description><![CDATA[I gave a talk called &#8216;WCAG 2.0 for writers&#8217; at an accessibility forum recently. Preparing for it gave me the time to think some more about WCAG 2.0 — the new(ish) version of the Web Content Accessibility Guidelines.
As a web content specialist, I found the new guidelines disappointing. Content is the reason people use websites, [...]]]></description>
			<content:encoded><![CDATA[<p>I gave a talk called &#8216;WCAG 2.0 for writers&#8217; at an accessibility forum recently. Preparing for it gave me the time to think some more about WCAG 2.0 — the new(ish) version of the Web Content Accessibility Guidelines.</p>
<p>As a web content specialist, I found the new guidelines disappointing. Content is the reason people use websites, but these guidelines do little to foster quality content. In fact, they do less than in version 1.0.</p>
<h3>Writing readable content is now optional</h3>
<p>In version 1.0, writers were urged to <q>Use the clearest and simplest language appropriate for a site&#8217;s content</q>. As a &#8216;priority 1&#8242; requirement, this was mandatory.</p>
<p>Version 2.0 says: <q>When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available</q>.</p>
<p>While this is more specific, and more easily measured, it is now at the lowest priority level (known as level AAA). Level AAA guidelines are <q>not recommended &#8230; as a general policy for entire sites</q>.  In effect, this makes it optional to write readable content!</p>
<h3>Organising content with headings is also optional</h3>
<p>Version 2.0 of the guidelines say <q>Section headings are used to organise the content</q>. In version 1.0, using headings was a medium priority—a &#8217;should do&#8217;. In the new guidelines it has been moved to the lowest level. Using headings is now optional.</p>
<h3>It&#8217;s also OK to write poor link text</h3>
<p>The first version of the guidelines said <q>Clearly identify the target of each link</q>. This was a  &#8217;should do&#8217;.</p>
<p>There are now two guidelines for links. The stronger one that requires clear link text  is at level AAA.  The weaker one, allowing links such as &#8216;read more&#8217; (and on my reading, &#8216;click here&#8217;) is at level A. Again, the new guidelines seem to lower the standard for good writing.</p>
<h3>Workarounds aren&#8217;t great solutions</h3>
<p>The new guidelines tell writers to define <q>&#8230; words or phrases used in an unusual or restricted way, including idioms and jargon.</q> But this is just a workaround. Let&#8217;s look at an example.</p>
<p>An old page from the Westpac website (shown below, with <a href="http://bit.ly/t9fAw">full text on the Internet Archive</a>) is full of idioms.</p>
<div id="attachment_68" class="wp-caption aligncenter" style="width: 510px"><img class="size-full wp-image-68" title="Screen capture of a Westpac bank web page" src="http://www.deyalexander.com.au/blog/wp-content/uploads/2009/09/westpac1.gif" alt="Screen capture of a Westpac bank web page" width="500" height="392" /><p class="wp-caption-text">Screen capture of a Westpac bank web page</p></div>
<p>Researchers in Italy recently tested this kind of language on a group of students. They found that the students took longer to understand idioms than literal language. Cutting back on them, rather than adding definitions, will benefit everyone.</p>
<p>Ah, but I forgot to mention this guideline is only a suggestion. At level AAA, it&#8217;s optional. So you won&#8217;t need to fix the problem at all if you don&#8217;t want to.</p>
<h3>Writers need to aim higher</h3>
<p>To produce good, accessible content, writers will need to do more than the new guidelines suggest. If content is to be king again, we’ll all have to aim higher.</p>
<h3>References</h3>
<ul>
<li><a href="http://bit.ly/19n215">Figures of speech — understanding idioms requires both sides of the brain (eScience News)</a></li>
<li><a href="http://www.w3.org/TR/WCAG20/">Web Content Accessibility Guidelines (WCAG) 2.0</a></li>
<li><a href="http://www.w3.org/TR/WCAG10/">Web Content Accessibility Guidelines (WCAG) 1.0</a></li>
<li><a href="http://bit.ly/t9fAw">Full text of Westpac sample page (Internet Archive)</a></li>
</ul>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.deyalexander.com.au%2Fblog%2F2009%2F09%2Fcontent-is-king-not-in-wcag-2-0%2F&amp;linkname=Content%20is%20king%3F%20Not%20in%20WCAG%202.0%21"><img src="http://www.deyalexander.com.au/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.deyalexander.com.au/blog/2009/09/content-is-king-not-in-wcag-2-0/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Don’t publish online just because you can</title>
		<link>http://www.deyalexander.com.au/blog/2009/09/don%e2%80%99t-publish-online-just-because-you-can/</link>
		<comments>http://www.deyalexander.com.au/blog/2009/09/don%e2%80%99t-publish-online-just-because-you-can/#comments</comments>
		<pubDate>Sun, 13 Sep 2009 01:10:18 +0000</pubDate>
		<dc:creator>Dey</dc:creator>
				<category><![CDATA[Planning content]]></category>
		<category><![CDATA[decision-making]]></category>
		<category><![CDATA[editorial control]]></category>
		<category><![CDATA[governance]]></category>
		<category><![CDATA[publishing]]></category>

		<guid isPermaLink="false">http://www.deyalexander.com.au/blog/?p=61</guid>
		<description><![CDATA[Publishing content online is relatively easy, fast and cheap. It’s one of the great things about the web, but also one of its downsides.
Too much content gets published online because it can, rather than because it should. Many websites heave and groan under the weight of too much low (or no) value content. Sadly, their [...]]]></description>
			<content:encoded><![CDATA[<p>Publishing content online is relatively easy, fast and cheap. It’s one of the great things about the web, but also one of its downsides.</p>
<p>Too much content gets published online because it can, rather than because it should. Many websites heave and groan under the weight of too much low (or no) value content. Sadly, their users do too.</p>
<h3>Decentralised control can mean no control at all</h3>
<p>Most of my clients are large organisations, many in the public sector. There is rarely any centralised control over publishing.  Website managers or editors are often in a low-ranking, undervalued positions with no real authority. There&#8217;s rarely a policy or strategy that gives them the teeth to stop low-value, poor quality content being published.</p>
<p>Business area managers often make the call about what goes online. They have varying levels of understanding of what’s valuable or needed content and what’s already out there on the site.</p>
<h3>Lower costs lower the barriers</h3>
<p>When there is no upfront cost to publish online content, poor decisions can be made:</p>
<ul>
<li>‘We      have it, so we may as well put it online’</li>
<li>‘Someone      might find it useful’</li>
<li>‘Our      part of the site looks a bit bare—we need to fill it up’</li>
<li>‘It      is policy to publish everything we produce in print on the website’</li>
<li>‘I      want’ … (not ‘users want’ or &#8216;we need&#8217;)</li>
</ul>
<p>You’re unlikely hear someone use this kind of rationale for publishing print content. Brochures don&#8217;t get produced just because they can. When there is a cost, people think more carefully before they publish.</p>
<h3>Publishing on the web involves hidden costs</h3>
<p>Publishing online is not cost-free. It takes time for staff to prepare and publish content (even if they just ‘PDF it and put it online’). Then there is time in editing, reviewing and approval.</p>
<p>Once published, content has to be maintained.  All too often, more content gets published than there are resources to manage it. It doesn&#8217;t take long to end up with a very out-of-date website.</p>
<h3>The cost to user experience</h3>
<p>The biggest cost can be to the user experience.  More content means a more complex information architecture: more main navigation choices, more links to work through and more search results to choose from.</p>
<p>If your publishing decisions are unrestrained, users may find too much low value, poorly focused, poor quality content.  If you publish more than you can manage, they&#8217;ll  find out of date and inaccurate content as well.</p>
<p>The bottom line for all this is loss of trust or damage to your organisation’s reputation. For some, it may mean loss of business. For others, may mean an increase in call centre costs as users give up trying to find what they need on your website and make a more direct enquiry.</p>
<p>And all of this costs money—even though it does not appear as a line item in your publishing budget.</p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.deyalexander.com.au%2Fblog%2F2009%2F09%2Fdon%25e2%2580%2599t-publish-online-just-because-you-can%2F&amp;linkname=Don%E2%80%99t%20publish%20online%20just%20because%20you%20can"><img src="http://www.deyalexander.com.au/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.deyalexander.com.au/blog/2009/09/don%e2%80%99t-publish-online-just-because-you-can/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Defining and refining the purpose of a page</title>
		<link>http://www.deyalexander.com.au/blog/2009/09/defining-and-refining-the-purpose/</link>
		<comments>http://www.deyalexander.com.au/blog/2009/09/defining-and-refining-the-purpose/#comments</comments>
		<pubDate>Mon, 07 Sep 2009 10:48:21 +0000</pubDate>
		<dc:creator>Dey</dc:creator>
				<category><![CDATA[Planning content]]></category>
		<category><![CDATA[content purpose]]></category>
		<category><![CDATA[purpose]]></category>

		<guid isPermaLink="false">http://www.deyalexander.com.au/blog/?p=43</guid>
		<description><![CDATA[I&#8217;ve been reviewing and editing a lot of web content lately. Two current clients have large information-dense websites.  The content is produced by staff who are not professional writers, and they probably have little time to devote to writing— let alone planning.  But lack of planning has been a key problem.
Not enough planning
The first problem [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been reviewing and editing a lot of web content lately. Two current clients have large information-dense websites.  The content is produced by staff who are not professional writers, and they probably have little time to devote to writing— let alone planning.  But lack of planning has been a key problem.</p>
<h3>Not enough planning</h3>
<p>The first problem I usually notice is poorly focused content. Some pages ramble, seemingly covering every aspect, every detail that a user would (n)ever want. Others repeat information that is published elsewhere on the site.  In some cases, I&#8217;m left scratching my head about what information need the content was trying to fill. Clearly, the author has not done enough planning.</p>
<h3>Understanding the purpose for the page</h3>
<p>A key problem is that the purpose of the content has not been given enough thought.  If you cannot clearly identify what the content is for, it is very easy to ramble and lose focus. Poor structure is also a symptom of not having a clear enough idea of the page purpose.</p>
<p>In my writing workshops, participants always tell me that a key part of planning content is  knowing the page purpose. But when I ask them how they work this out, often they can&#8217;t say.</p>
<h3>Review and refine the page purpose</h3>
<p>One of my current clients uses templates to guide content development. The planning document has a section asking the content owner to state the purpose of the page. I&#8217;ve sometimes found this part of the documentation has been left blank.  Often, it is very vague and doesn&#8217;t provide enough information to guide my editorial decisions.</p>
<p>Working with the client&#8217;s staff, we&#8217;ve found the need to review or refine the purpose as the content drafting (or in my case, reviewing) progresses. It seems it&#8217;s not easy to get it right up front. For key pages, or pages where the purpose is hard to articulate, it may be necessary to do this refinement.</p>
<h3>Questions to help you uncover the purpose of the content</h3>
<p>These questions might  help you get closer to identifying the purpose of the content. Think about these along with considerations about your audience.</p>
<ul>
<li>Why are you publishing this content? What does it have to achieve? What information need does it address? What content gap does it fill?</li>
<li>What will users be wanting to know or do after they have read this content? What do you want them to know/do?</li>
<li>Are you creating the content in response to customer feedback? What have customers been asking for or telling you? If it is an existing page, what feedback have you been getting about this page?</li>
<li>Is there more than one purpose that this content will address? If so, what is the main purpose? What are secondary or less important purposes? Where should the focus or emphasis be?</li>
<li>Is there content similar to this on the site? If so, what does this content need to do that the related content does not do? Should you avoid repetition or overlap?</li>
<li>Is content similar to this published somewhere else (in a brochure, for instance)? Is it referred to somewhere else (on a TV ad, perhaps)? How will the online content relate to the content published or referred to elsewhere?</li>
</ul>
<h3>Other things you can do</h3>
<ul>
<li>Brainstorm content planning with your colleagues</li>
<li>Talk to people who have direct contact with your customers</li>
<li>Gather customer feedback—from your call centre,  your email enquiry office, other sources</li>
<li>Talk to your web team to see if you can get reports on search queries that may be relevant to this content.</li>
</ul>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.deyalexander.com.au%2Fblog%2F2009%2F09%2Fdefining-and-refining-the-purpose%2F&amp;linkname=Defining%20and%20refining%20the%20purpose%20of%20a%20page"><img src="http://www.deyalexander.com.au/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.deyalexander.com.au/blog/2009/09/defining-and-refining-the-purpose/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Two words that need to go under!</title>
		<link>http://www.deyalexander.com.au/blog/2009/08/two-words-that-need-to-go-under/</link>
		<comments>http://www.deyalexander.com.au/blog/2009/08/two-words-that-need-to-go-under/#comments</comments>
		<pubDate>Fri, 28 Aug 2009 09:54:14 +0000</pubDate>
		<dc:creator>Dey</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Readability]]></category>

		<guid isPermaLink="false">http://www.deyalexander.com.au/blog/?p=34</guid>
		<description><![CDATA[I blame journalists for the growing use of these two awful words: &#8216;undertake&#8217; and &#8216;undergo&#8217;.
They litter newspaper headlines and articles:
&#8216;BHP to undertake study of rockfall mine&#8217;
&#8216;Optus to undertake major network upgrade&#8217;
I hear them on the evening news program almost every night:
&#8216;[some football player] will undergo tests to see if he has a stress fracture &#8230; [...]]]></description>
			<content:encoded><![CDATA[<p>I blame journalists for the growing use of these two awful words: &#8216;undertake&#8217; and &#8216;undergo&#8217;.</p>
<p>They litter newspaper headlines and articles:</p>
<blockquote><p>&#8216;BHP to <strong>undertake</strong> study of rockfall mine&#8217;</p>
<p>&#8216;Optus to <strong>undertake</strong> major network upgrade&#8217;</p></blockquote>
<p>I hear them on the evening news program almost every night:</p>
<blockquote><p>&#8216;[some football player] will <strong>undergo</strong> tests to see if he has a stress fracture &#8230; &#8216;</p>
<p>&#8216;[some poor victim of crime] will <strong>undergo</strong> surgery &#8230; &#8216;</p></blockquote>
<p>And of course, they&#8217;re never far from a politician&#8217;s lips:</p>
<blockquote><p>&#8216;There are an enormous number  of functions which ministers <strong>undertake</strong>, and which I <strong>undertake</strong>, which people don’t pay to attend.&#8217;</p></blockquote>
<p>Government websites are crawling with them:</p>
<blockquote><p>&#8216;It is a requirement under s. 36 of the <em>Safety, Rehabilitation and Compensation Act 1988</em> that organisations <strong>undertake</strong> or arrange an assessment of an injured worker&#8217;s capability to <strong>undertake</strong> a rehabilitation program.&#8217;</p>
<p>&#8216;b. agree to <strong>undergo</strong> a security clearance and civil records check;<br />
c. <strong>undergo</strong> an enlistment medical and be classified Class One;<br />
d. <strong>undergo</strong> psychological testing/assessment;<br />
e. <strong>undergo</strong> Recruiting Officer (RO) assessment;&#8217;</p></blockquote>
<p>And our university websites wouldn&#8217;t want to be left out:</p>
<blockquote><p>&#8216;Many high-achieving students elect to <strong>undertake</strong> a research degree &#8230; &#8216;</p>
<p>&#8216;The Menzies Building is about to <strong>undergo</strong> a dramatic facelift&#8217;</p></blockquote>
<h3>What&#8217;s wrong with ordinary words?</h3>
<p>Why can&#8217;t people, organisations or politicians &#8216;do&#8217;,  &#8216;have&#8217; or &#8216;go to&#8217; things rather than &#8216;undertake&#8217; or &#8216;undergo&#8217; them?</p>
<p>What&#8217;s wrong with ordinary words?  Do they lack the syllables needed to make their writers or speakers feel smart?</p>
<p>Why can&#8217;t  &#8216;BHP study rockfall mine&#8217;? What&#8217;s wrong with &#8216;Optus upgrades network&#8217;? Footballers and victims of crime can still &#8216;have&#8217; tests or surgery, and politicians could &#8216;go to&#8217; functions &#8211; as long as it&#8217;s not on my taxpaying dollar.</p>
<p>High achieving students could &#8217;study&#8217; or &#8216;enrol in a research degree&#8217;, and the Menzies building could &#8216;have a dramatic facelift&#8217; &#8211; it certainly needs one!</p>
<p>Why do we have to undergo such crusty writing?  I want an undertaking that only undertakers use the word.  The rest of us should just write in plain language, surely?</p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.deyalexander.com.au%2Fblog%2F2009%2F08%2Ftwo-words-that-need-to-go-under%2F&amp;linkname=Two%20words%20that%20need%20to%20go%20under%21"><img src="http://www.deyalexander.com.au/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.deyalexander.com.au/blog/2009/08/two-words-that-need-to-go-under/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Improving the usability of tweets</title>
		<link>http://www.deyalexander.com.au/blog/2009/08/improving-the-usability-of-tweets/</link>
		<comments>http://www.deyalexander.com.au/blog/2009/08/improving-the-usability-of-tweets/#comments</comments>
		<pubDate>Mon, 24 Aug 2009 23:51:42 +0000</pubDate>
		<dc:creator>Dey</dc:creator>
				<category><![CDATA[Scannability]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[front-loading]]></category>
		<category><![CDATA[microcontent]]></category>
		<category><![CDATA[nanocontent]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://deyalexander.com.au/blog/?p=22</guid>
		<description><![CDATA[Jakob Nielsen&#8217;s latest Alertbox article is on writing usable messages for Twitter. The advice he offers is also helpful for improving email subject lines, headings, link text. In fact, it&#8217;s good for any time where you have a limited number of characters that need to carry a lot of meaning.
He recommends:

Iteration &#8211; you&#8217;re unlikely to [...]]]></description>
			<content:encoded><![CDATA[<p>Jakob Nielsen&#8217;s latest Alertbox article is on writing usable messages for Twitter. The advice he offers is also helpful for improving email subject lines, headings, link text. In fact, it&#8217;s good for any time where you have a limited number of characters that need to carry a lot of meaning.</p>
<p>He recommends:</p>
<ul>
<li>Iteration &#8211; you&#8217;re unlikely to get the best outcome without a few edits</li>
<li>Start with information-carrying words &#8211; scan readers often only look at the first 11 characters</li>
<li>Highlight key terms &#8211; for tweets you can use CAPITALS, but this isn&#8217;t a good idea for web pages</li>
<li>Using short, punchy expressions &#8211; but don&#8217;t try to be cute!</li>
</ul>
<p>For businesses using Twitter to spread the word about products, services, events and so on, the advice is invaluable.</p>
<p>See: <a href="http://www.useit.com/alertbox/twitter-iterations.html">Twitter postings: iterative design</a></p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.deyalexander.com.au%2Fblog%2F2009%2F08%2Fimproving-the-usability-of-tweets%2F&amp;linkname=Improving%20the%20usability%20of%20tweets"><img src="http://www.deyalexander.com.au/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>]]></content:encoded>
			<wfw:commentRss>http://www.deyalexander.com.au/blog/2009/08/improving-the-usability-of-tweets/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
