<?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>Inclusive New Media Design &#187; Top tips</title>
	<atom:link href="http://www.inclusivenewmedia.org/blog/category/id-accessible-websites/top-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.inclusivenewmedia.org/blog</link>
	<description>including people with intellectual disabilities in the WWW</description>
	<lastBuildDate>Mon, 16 Nov 2009 14:38:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Test</title>
		<link>http://www.inclusivenewmedia.org/blog/76/id-accessible-websites/top-tips/test/</link>
		<comments>http://www.inclusivenewmedia.org/blog/76/id-accessible-websites/top-tips/test/#comments</comments>
		<pubDate>Sun, 27 Sep 2009 13:26:15 +0000</pubDate>
		<dc:creator>Helen  Kennedy</dc:creator>
				<category><![CDATA[Test]]></category>
		<category><![CDATA[Top tips]]></category>
		<category><![CDATA[Testing]]></category>

		<guid isPermaLink="false">http://www.inclusivenewmedia.org/blog/?p=76</guid>
		<description><![CDATA[When preparing for user testing:
Test your website as much as possible with people with intellectual disabilities, to be sure it works well for them. Here are some tips on how to carry out a test.

Decide on the sections of your site that you want to test.
Decide which users you need to test your site (find [...]]]></description>
			<content:encoded><![CDATA[<h3>When preparing for user testing:</h3>
<p>Test your website as much as possible with people with intellectual disabilities, to be sure it works well for them. Here are some tips on how to carry out a test.</p>
<ul>
<li>Decide on the sections of your site that you want to test.</li>
<li>Decide which users you need to test your site (find out more about different degrees of intellectual disability in the &#8216;people with intellectual disability&#8217; section of this site).</li>
<li>Define tasks for users to carry out.</li>
<li>Decide if there is anything qualitative you want to test (whether users like the site, find it attractive, would be likely to use it).</li>
<li>Identify what you would need to know about users before the test starts (age, experience of the web, nature of intellectual, learning, sensory and physical impairments).</li>
<li>Draw up an observation template to help you take notes during the test.</li>
<li>Test the test!</li>
</ul>
<p><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/prepare-testing.jpg" alt="prepare-testing" title="prepare-testing" width="280" height="187" class="alignnone size-full wp-image-702" />preparing for testing</span><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/prepare-testing2.jpg" alt="user testing" title="user testing" width="280" height="187" class="alignnone size-full wp-image-703" />user testing</span></p>
<h3>When testing, aim to:</h3>
<ul>
<li>Have a natural discussion.</li>
<li>Go through questions in any order, to help the discussion be natural.</li>
<li>Re-word and repeat the questions if necessary.</li>
<li>Go off on a tangent if the discussion leads that way.</li>
<li>Ask enough questions to build a good picture.</li>
<li>Talk a lot less than your tester does.</li>
<li>Listen, prompt, clarify. Take notes later if doing it while you talk interrupts the flow.</li>
</ul>
<p><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/test-aim1.jpg" alt="discussing the test" title="discussing the test" width="280" height="187" class="alignnone size-full wp-image-707" />discussing the test</span><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/test-aim2.jpg" alt="going through the questions" title="going through the questions" width="280" height="187" class="alignnone size-full wp-image-708" />going through the questions</span></p>
<h3>Before testing, carry out an interview to find out about the tester and gain insight into:</h3>
<ul>
<li>Level of technical awareness.</li>
<li>Attitudes towards the Web.</li>
<li>Experience of Web use.</li>
<li>Any assistive technology normally used (find out more about assistive technologies in the &#8216;<a href="http://www.inclusivenewmedia.org/blog/category/id-accessible-websites/information-about-accessibility/">information about accessibility</a>&#8216; section.</li>
</ul>
<p><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/interview1.jpg" alt="interviewing your tester" title="interviewing your tester" width="280" height="187" class="alignnone size-full wp-image-710" />interviewing your tester</span><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/interview2.jpg" alt="observing technical awareness" title="observing technical awareness" width="280" height="187" class="alignnone size-full wp-image-711" />observing technical awareness</span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.inclusivenewmedia.org/blog/76/id-accessible-websites/top-tips/test/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Pictures</title>
		<link>http://www.inclusivenewmedia.org/blog/78/id-accessible-websites/top-tips/pictures/</link>
		<comments>http://www.inclusivenewmedia.org/blog/78/id-accessible-websites/top-tips/pictures/#comments</comments>
		<pubDate>Sun, 27 Sep 2009 12:26:20 +0000</pubDate>
		<dc:creator>Helen  Kennedy</dc:creator>
				<category><![CDATA[Pictures]]></category>
		<category><![CDATA[Top tips]]></category>
		<category><![CDATA[pictures]]></category>

		<guid isPermaLink="false">http://www.inclusivenewmedia.org/blog/?p=78</guid>
		<description><![CDATA[Images are important. For people with intellectual disabilities, they are core content, not just decoration. Pictures should communicate the content on the page, not just be an add on. Use icons for links. But be aware that it’s hard for people with some intellectual disabilities to understand metaphors.
Alt attributes (which provide text alternatives for blind [...]]]></description>
			<content:encoded><![CDATA[<p>Images are important. For people with intellectual disabilities, they are core content, not just decoration. Pictures should communicate the content on the page, not just be an add on. Use icons for links. But be aware that it’s hard for people with some intellectual disabilities to understand metaphors.</p>
<p>Alt attributes (which provide text alternatives for blind users with screen readers) still need to be used appropriately when designing sites with ID accessibility in mind. </p>
<p>In addition, symbol sets can be used to enhance understanding for some people with intellectual disabilities who are familiar with the symbols. There is a range of symbol sets, used in different contexts. There is more information about the available symbol sets below, and links to further information about them.</p>
<h3>Symbol Sets: Supporting Literacy with Images</h3>
<h5><a href="http://www.makaton.org/">Makaton</a></h5>
<p><a href="http://www.makaton.org/"><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/makaton.jpg" alt="makaton" title="makaton" width="625" height="165" class="alignnone size-full wp-image-713" /></a><br />
Makaton is best known as a Sign-Supported English system. The Makaton charity also produces symbols which are used in a variety of ways (for example on paper and electronically) to enhance all forms of communication. Symbols and signs are closely linked where this is possible. Makaton is mostly used in interpersonal communication contexts. There is some use of Makaton amongst adults, particularly if Makaton signing is in use. The strong line art makes Makaton accessible in terms of visual perception.</p>
<h5><a href="http://www.widgit.com/products/wws2000/about_symbols/WWS2000PCS.htm">PCS</a></h5>
<p><a href="http://www.widgit.com/products/wws2000/about_symbols/WWS2000PCS.htm"><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/pcs.jpg" alt="pcs" title="pcs" width="625" height="165" class="alignnone size-full wp-image-714" /></a><br />
PCS is the most colourful symbol set. The colour adds complexity for perception, however. The imagery is often quite childish. There is not much adult vocabulary. PCS is mostly used for manual picture-exchange (printed on cards) or selectively to supplement Widgit.</p>
<h5><a href="http://www.widgit.com/symbols/about_symbols/widgit_rebus.htm">Widgit Literacy Symbols</a></h5>
<p><a href="http://www.widgit.com/symbols/about_symbols/widgit_rebus.htm"><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/widgit.jpg" alt="widgit" title="widgit" width="625" height="165" class="alignnone size-full wp-image-716" /></a><br />
Widgit is the most popular symbol set in the UK. Line art and limited palette options are also available, along with optimised sets for people with visual impairments. A large library is updated regularly and toolsets from Widgit include a symbol web browser, amongst other applications.</p>
<h5><a href="http://www.changepeople.co.uk/">Change Picture Bank</a></h5>
<p><a href="http://www.changepeople.co.uk/"><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/change.jpg" alt="change" title="change" width="625" height="165" class="alignnone size-full wp-image-719" /></a><br />
Change Picture Bank is used more flexibly in terms of symbol meaning. It is firmly rooted in the adult world and in person-centred planning (PCP) initiatives. It is often easier to understand for non-symbol users, especially where abstract concepts are being represented.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inclusivenewmedia.org/blog/78/id-accessible-websites/top-tips/pictures/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Choices</title>
		<link>http://www.inclusivenewmedia.org/blog/80/id-accessible-websites/top-tips/choices/</link>
		<comments>http://www.inclusivenewmedia.org/blog/80/id-accessible-websites/top-tips/choices/#comments</comments>
		<pubDate>Sun, 27 Sep 2009 10:27:00 +0000</pubDate>
		<dc:creator>Helen  Kennedy</dc:creator>
				<category><![CDATA[Choices]]></category>
		<category><![CDATA[Top tips]]></category>
		<category><![CDATA[choices]]></category>

		<guid isPermaLink="false">http://www.inclusivenewmedia.org/blog/?p=80</guid>
		<description><![CDATA[Structure, choice-making and ID
People with learning disabilities are all different. When it comes to structuring a website, this means that what works for some people with learning disabilities won&#8217;t work for others. 
simple choicessimple navigation
The best practice is to provide several routes through content. Routes which mean lots of steps, but few options, may be [...]]]></description>
			<content:encoded><![CDATA[<h2>Structure, choice-making and ID</h2>
<p>People with learning disabilities are all different. When it comes to structuring a website, this means that what works for some people with learning disabilities won&#8217;t work for others. </p>
<p><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/simplechoice1.jpg" alt="simplechoice1" title="simplechoice1" width="280" height="190" class="alignnone size-full wp-image-789" />simple choices</span><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/simplechoice2.jpg" alt="simplechoice2" title="simplechoice2" width="280" height="190" class="alignnone size-full wp-image-790" />simple navigation</span></p>
<p>The best practice is to provide several routes through content. Routes which mean lots of steps, but few options, may be the most accessible for users with more significant learning disability. So deep structures sometimes work better than wide structures for this group. Or providing access to a small section of content may often be required to meet the needs of more significantly disabled users.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inclusivenewmedia.org/blog/80/id-accessible-websites/top-tips/choices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Text</title>
		<link>http://www.inclusivenewmedia.org/blog/82/id-accessible-websites/top-tips/text/</link>
		<comments>http://www.inclusivenewmedia.org/blog/82/id-accessible-websites/top-tips/text/#comments</comments>
		<pubDate>Sun, 27 Sep 2009 09:10:26 +0000</pubDate>
		<dc:creator>Helen  Kennedy</dc:creator>
				<category><![CDATA[Text]]></category>
		<category><![CDATA[Top tips]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[large text]]></category>
		<category><![CDATA[readable]]></category>
		<category><![CDATA[text]]></category>

		<guid isPermaLink="false">http://www.inclusivenewmedia.org/blog/?p=82</guid>
		<description><![CDATA[Making content accessible
To make the text content of your website as accessible as possible for people with intellectual disabilities, try to do the following:

Use clear, concise headings.
Use pictures to supplement textual content.
Group text into blocks underneath each heading.
Use lists where appropriate.
Left-align text; don’t justify it.
Separate text visually from the borders of the surrounding design.
Ensure lines [...]]]></description>
			<content:encoded><![CDATA[<h3>Making content accessible</h3>
<p>To make the text content of your website as accessible as possible for people with intellectual disabilities, try to do the following:</p>
<ul>
<li>Use clear, concise headings.</li>
<li>Use pictures to supplement textual content.</li>
<li>Group text into blocks underneath each heading.</li>
<li>Use lists where appropriate.</li>
<li>Left-align text; don’t justify it.</li>
<li>Separate text visually from the borders of the surrounding design.</li>
<li>Ensure lines do not exceed 70 &#8211; 80 characters.</li>
<li>Use descriptive link text (not ‘click here’).</li>
<li>Use emphasis on important words that convey the meaning of the text.</li>
<li>Use clear, simple and concise language.</li>
</ul>
<p><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/text2.jpg" alt="text2" title="text2" width="280" height="190" class="alignnone size-full wp-image-795" /></span><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/text1.jpg" alt="text1" title="text1" width="280" height="190" class="alignnone size-full wp-image-796" /></span></p>
<h3>Writing Style and Reading Level</h3>
<p>Meeting the success criteria of WCAG 2.0 at AAA requires text to be written at a reading age equivalent to lower secondary school (or to provide such a version as a supplementary ‘Easy Read&#8217; version). For people with intellectual disabilities, this text level is often too high. Tools such as <img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/10/new-window-blu-mini.png" alt="new-window-blu-mini" title="new-window-blu-mini" width="18" height="14" class="alignnone size-full wp-image-648" /> <a href="http://juicystudio.com/services/readability.php">Juicy Studio&#8217;s Readability Test</a> can provide an indication of reading grade. But text level is ultimately a matter of judgement and awareness.</p>
<p>Here are some further tips on enhancing your text for more severely intellectually disabled audiences:</p>
<ul>
<li>Aim for lower primary school chronological reading age (in the UK,   10-20% of the population will benefit from this).</li>
<li>You are not writing for children, but the task is similar. Assume adult concepts, expectations, and life-experiences.</li>
<li>Don&#8217;t assume that people will feel patronized; they know this is easy read content.</li>
<li>Use short sentences. Where you are using a comma, you sometimes need a full-stop.</li>
<li>Limit use of punctuation to full-stop, question and exclamation marks if possible.</li>
<li>Use short or single sentence paragraphs, and layout with exaggerated spacing.</li>
<li>Aim to build each sentence around a keyword.</li>
<li>If a concept or keyword is important, don&#8217;t be afraid of labouring it.</li>
<li>Word length and number of syllables are a good guide, but not definitive. Think of vocabulary in terms of ‘high frequency words&#8217;.</li>
<li>If jargon is required, it should be explicitly explored as primary content (that is, not marked up).</li>
<li>Ensure the meaning of pronouns is absolutely clear, or use nouns repeatedly. Take particular care with personal pronouns. It&#8217;s better to use a name repeatedly, even though it may be bad style.</li>
<li>Plan your writing in advance. If re-writing longer text, list the key points of each paragraph before beginning.</li>
<li>On longer pieces, separate content using multiple pages. Keep the number of points per page low</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.inclusivenewmedia.org/blog/82/id-accessible-websites/top-tips/text/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Media</title>
		<link>http://www.inclusivenewmedia.org/blog/84/id-accessible-websites/top-tips/media/</link>
		<comments>http://www.inclusivenewmedia.org/blog/84/id-accessible-websites/top-tips/media/#comments</comments>
		<pubDate>Sun, 27 Sep 2009 08:28:04 +0000</pubDate>
		<dc:creator>Helen  Kennedy</dc:creator>
				<category><![CDATA[Media]]></category>
		<category><![CDATA[Top tips]]></category>

		<guid isPermaLink="false">http://www.inclusivenewmedia.org/blog/?p=84</guid>
		<description><![CDATA[Use voicing to narrate text on the page. Include audio versions of all content, so users can listen to it as well as read it. 
use animation, video and sounduse voicing to read text aloud
But go beyond text. Incorporate movement and interesting interaction. A text heavy web page where nothing moves can be boring. Many [...]]]></description>
			<content:encoded><![CDATA[<p>Use voicing to narrate text on the page. Include audio versions of all content, so users can listen to it as well as read it. </p>
<p><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/media1.jpg" alt="media1" title="media1" width="280" height="190" class="alignnone size-full wp-image-792" />use animation, video and sound</span><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/media2.jpg" alt="media2" title="media2" width="280" height="190" class="alignnone size-full wp-image-793" />use voicing to read text aloud</span></p>
<p>But go beyond text. Incorporate movement and interesting interaction. A text heavy web page where nothing moves can be boring. Many people with intellectual disabilities like dynamic, interesting pages which use motion to attract attention or highlight what’s important. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.inclusivenewmedia.org/blog/84/id-accessible-websites/top-tips/media/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Top tips</title>
		<link>http://www.inclusivenewmedia.org/blog/48/id-accessible-websites/top-tips/top-tips-2/</link>
		<comments>http://www.inclusivenewmedia.org/blog/48/id-accessible-websites/top-tips/top-tips-2/#comments</comments>
		<pubDate>Sat, 26 Sep 2009 14:02:51 +0000</pubDate>
		<dc:creator>Helen  Kennedy</dc:creator>
				<category><![CDATA[Top tips]]></category>
		<category><![CDATA[choices]]></category>
		<category><![CDATA[media]]></category>
		<category><![CDATA[pictures]]></category>
		<category><![CDATA[Testing]]></category>
		<category><![CDATA[text]]></category>

		<guid isPermaLink="false">http://www.inclusivenewmedia.org/blog/?p=48</guid>
		<description><![CDATA[
Test: Test your site with intellectually disabled users. Even better, involve people with intellectual disabilities when you are building your site. Contact us if you want help with working with user testers .
Pictures: Use lots of images. Images are important. They are core content, not just decoration, for people with intellectual disabilities. Use icons for [...]]]></description>
			<content:encoded><![CDATA[<ul>
<li><a href="http://www.inclusivenewmedia.org/blog/category/accessible-websites/top-tips/test/">Test:</a> Test your site with intellectually disabled users. Even better, involve people with intellectual disabilities when you are building your site. Contact us if you want help with working with user testers .</li>
<li><a href="http://www.inclusivenewmedia.org/blog/category/accessible-websites/top-tips/pictures-top-tips-acessible-websites/">Pictures:</a> Use lots of images. Images are important. They are core content, not just decoration, for people with intellectual disabilities. Use icons for links, and symbols to supplement text.</li>
<li><a href="http://www.inclusivenewmedia.org/blog/category/accessible-websites/top-tips/choices-top-tips-accessible-websites/">Choices:</a> Keep the menu choices simple, and limit how many there are – five is enough for this user group.</li>
<li><a href="http://www.inclusivenewmedia.org/blog/category/accessible-websites/top-tips/text-top-tips-acessible-websites/">Text:</a> Use big text. Keep your writing simple. Use short sentences, short paragraphs and simple words.</li>
<li><a href="http://www.inclusivenewmedia.org/blog/category/accessible-websites/top-tips/media-top-tips-acessible-websites/">Media:</a> Include audio versions of all content, so users can listen to it instead of reading it. Video and animation also go down well with this user group.</li>
</ul>
<p><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/test-overview1.jpg" alt="test-overview1" title="test-overview1" width="280" height="190" class="alignnone size-full wp-image-827" />test to ensure accessibility</span><span><img src="http://www.inclusivenewmedia.org/blog/wp-content/uploads/2009/09/test-overview2.jpg" alt="test-overview2" title="test-overview2" width="280" height="190" class="alignnone size-full wp-image-828" />use various forms of media</span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.inclusivenewmedia.org/blog/48/id-accessible-websites/top-tips/top-tips-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
