<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: 10 Design Standards to Create Better eLearning!</title>
	<atom:link href="http://elearningbrothers.com/10-design-standards-to-create-better-elearning/feed/" rel="self" type="application/rss+xml" />
	<link>http://elearningbrothers.com/10-design-standards-to-create-better-elearning/</link>
	<description>eLearning games, challenges, flash templates, and development</description>
	<lastBuildDate>Wed, 10 Mar 2010 15:03:03 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Emma Robert</title>
		<link>http://elearningbrothers.com/10-design-standards-to-create-better-elearning/comment-page-1/#comment-412</link>
		<dc:creator>Emma Robert</dc:creator>
		<pubDate>Mon, 07 Dec 2009 07:36:42 +0000</pubDate>
		<guid isPermaLink="false">http://elearningbrothers.com/?p=1173#comment-412</guid>
		<description>Very descriptive post i really like to read.</description>
		<content:encoded><![CDATA[<p>Very descriptive post i really like to read.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bonnie Boden</title>
		<link>http://elearningbrothers.com/10-design-standards-to-create-better-elearning/comment-page-1/#comment-383</link>
		<dc:creator>Bonnie Boden</dc:creator>
		<pubDate>Wed, 25 Nov 2009 15:59:40 +0000</pubDate>
		<guid isPermaLink="false">http://elearningbrothers.com/?p=1173#comment-383</guid>
		<description>Nice list Andrew.

I&#039;d add a Capitalization section. Make it consistent throughout. For instance, are you capitalizing button names (on the buttons and in instructional references -- all lowercase, all caps, title case)? What about certain terms (and if so, which ones)?

And then in the Colors section, I&#039;d make note to be more aware of issues related to learners with loss of color perception and color deficiencies. Keep that in mind when choosing colors, and also when providing instruction (don&#039;t tell the learner to select the red button, for instance -- tell them to select the &quot;Stop&quot; button).</description>
		<content:encoded><![CDATA[<p>Nice list Andrew.</p>
<p>I&#8217;d add a Capitalization section. Make it consistent throughout. For instance, are you capitalizing button names (on the buttons and in instructional references &#8212; all lowercase, all caps, title case)? What about certain terms (and if so, which ones)?</p>
<p>And then in the Colors section, I&#8217;d make note to be more aware of issues related to learners with loss of color perception and color deficiencies. Keep that in mind when choosing colors, and also when providing instruction (don&#8217;t tell the learner to select the red button, for instance &#8212; tell them to select the &#8220;Stop&#8221; button).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Matas</title>
		<link>http://elearningbrothers.com/10-design-standards-to-create-better-elearning/comment-page-1/#comment-381</link>
		<dc:creator>Eric Matas</dc:creator>
		<pubDate>Tue, 24 Nov 2009 16:54:51 +0000</pubDate>
		<guid isPermaLink="false">http://elearningbrothers.com/?p=1173#comment-381</guid>
		<description>Sound and sound effects should be standardized. 

Is there background music? Do pop-ups make a sound? Do buttons make a sound when clicked? Is narration noted with a visual cue? Where on the screen will Closed Captioning be?</description>
		<content:encoded><![CDATA[<p>Sound and sound effects should be standardized. </p>
<p>Is there background music? Do pop-ups make a sound? Do buttons make a sound when clicked? Is narration noted with a visual cue? Where on the screen will Closed Captioning be?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Bowen</title>
		<link>http://elearningbrothers.com/10-design-standards-to-create-better-elearning/comment-page-1/#comment-380</link>
		<dc:creator>Andrew Bowen</dc:creator>
		<pubDate>Tue, 24 Nov 2009 15:55:58 +0000</pubDate>
		<guid isPermaLink="false">http://elearningbrothers.com/?p=1173#comment-380</guid>
		<description>Thanks for the concise list. As basic as these sound, I have found that it is necessary to gain agreement on these foundational approaches for consistency and user comfort.</description>
		<content:encoded><![CDATA[<p>Thanks for the concise list. As basic as these sound, I have found that it is necessary to gain agreement on these foundational approaches for consistency and user comfort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rose Jorgensen</title>
		<link>http://elearningbrothers.com/10-design-standards-to-create-better-elearning/comment-page-1/#comment-378</link>
		<dc:creator>Rose Jorgensen</dc:creator>
		<pubDate>Tue, 24 Nov 2009 12:22:32 +0000</pubDate>
		<guid isPermaLink="false">http://elearningbrothers.com/?p=1173#comment-378</guid>
		<description>Thanks Brother Andrew - a worthwhile topic indeed, and one that I feel strongly about.

My team writes documentation, ILT materials, and elearning for technical applications, and we are rabid about standards. Not only do standards have to be maintained within a course or document, but also across all products and formats within the company.

When writing process-oriented content, language is an important standard.

- Component names: Do you call it a &quot;dropdown menu&quot; or a &quot;list box&quot;?

- How do you tell learners to access components? Do you tell them to choose a menu item or select it? Do you tell them to enter text into a field, or type it?

- Menu items: Do you say, &quot;Click on the File menu and select Save&quot;. Or do you say, &quot;Click File &gt; Save&quot;?

When working across multiple formats, there are also differences to take into account. For example, image quality. Web-based images for elearning don&#039;t need to be as high-quality (nor should they be) as those for print-based products. Yet for single-sourcing purposes, it is wise to create a print version and a web version of every image used.

These are a fraction of the decisions a development team has to make for development standards. Then there are formatting standards, application-specific standards, graphic standards, reference standards, metadata standards, and many many more.

Designers should also be aware, that while it is essential to maintain styles and standards, it is also of utmost importance to understand the sin of “absolutism”. Styles and standards provide the foundation for consistency within courseware, but there is always the exception to the rule. Never stifle creativity for the sake of “sticking to the rules”.</description>
		<content:encoded><![CDATA[<p>Thanks Brother Andrew &#8211; a worthwhile topic indeed, and one that I feel strongly about.</p>
<p>My team writes documentation, ILT materials, and elearning for technical applications, and we are rabid about standards. Not only do standards have to be maintained within a course or document, but also across all products and formats within the company.</p>
<p>When writing process-oriented content, language is an important standard.</p>
<p>- Component names: Do you call it a &#8220;dropdown menu&#8221; or a &#8220;list box&#8221;?</p>
<p>- How do you tell learners to access components? Do you tell them to choose a menu item or select it? Do you tell them to enter text into a field, or type it?</p>
<p>- Menu items: Do you say, &#8220;Click on the File menu and select Save&#8221;. Or do you say, &#8220;Click File &gt; Save&#8221;?</p>
<p>When working across multiple formats, there are also differences to take into account. For example, image quality. Web-based images for elearning don&#8217;t need to be as high-quality (nor should they be) as those for print-based products. Yet for single-sourcing purposes, it is wise to create a print version and a web version of every image used.</p>
<p>These are a fraction of the decisions a development team has to make for development standards. Then there are formatting standards, application-specific standards, graphic standards, reference standards, metadata standards, and many many more.</p>
<p>Designers should also be aware, that while it is essential to maintain styles and standards, it is also of utmost importance to understand the sin of “absolutism”. Styles and standards provide the foundation for consistency within courseware, but there is always the exception to the rule. Never stifle creativity for the sake of “sticking to the rules”.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
