<?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>jebsblog &#187; blind</title>
	<atom:link href="http://jebswebs.net/blog/tag/blind/feed/" rel="self" type="application/rss+xml" />
	<link>http://jebswebs.net/blog</link>
	<description>comments about accessibility and web design</description>
	<lastBuildDate>Wed, 28 Jul 2010 17:47:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Microsoft Office 2010 and Accessibility</title>
		<link>http://jebswebs.net/blog/2010/07/microsoft-office-2010-and-accessibility/</link>
		<comments>http://jebswebs.net/blog/2010/07/microsoft-office-2010-and-accessibility/#comments</comments>
		<pubDate>Wed, 28 Jul 2010 17:35:58 +0000</pubDate>
		<dc:creator>jeb</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[blind]]></category>
		<category><![CDATA[MS Office]]></category>

		<guid isPermaLink="false">http://jebswebs.net/blog/?p=545</guid>
		<description><![CDATA[Although it is not considered a major update, Microsoft (MS) recently released the latest iteration of its highly popular MS Office. To me, it appears most of the changes to this version (Microsoft Office 2010) are minor in nature and looks very similar to version 2007 &#8211; which WAS a major upgrade. That said, there [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://jebswebs.net/blog/wp-content/uploads/2010/07/clip_image006_thumb.jpg"><img class="alignright size-full wp-image-546" title="View of MS Accessibility Checker in action" src="http://jebswebs.net/blog/wp-content/uploads/2010/07/clip_image006_thumb.jpg" alt="View of MS Accessibility Checker in action" width="203" height="552" /></a>Although it is not considered a major update, Microsoft (MS) recently released the latest iteration of its highly popular MS Office. To me, it appears most of the changes to this version (Microsoft Office 2010) are minor in nature and looks very similar to version 2007 &#8211; which WAS a major upgrade. That said, there are clearly things &#8220;under the hood&#8221; that have been revised and it is always fun to try and discover those new things.</p>
<p>I will not comment on the cost effectiveness of upgrading to MS Office 2010 except to say that if you are still using MS Office 2003, this is probably a worthwhile investment. But if you are responsible for ensuring that the documents coming from your organization meet accessibility requirements, MS Office 2010 might be an excellent investment.</p>
<h3>Accessibility Checker</h3>
<p>For the new version of MS Office (MSO), Microsoft has made accessibility a priority since one of the new features is the Accessibility Checker  (MSO-AC) built into three of the core applications: Word 2010, Excel 2010, and PowerPoint 2010. According to the MS promo, the MSO-AC helps users create more accessible content &#8220;by identifying areas that might be challenging for users with disabilities to view or use, and providing a task pane to review those areas, users can fix potential problems with their content.&#8221; So far, my limited experience with the MSO-AC has been favorable and here is what I have learned so far:</p>
<p>1. To use MSO-AC, click on the File tab [or Alt-F], tab to, or click on Prepare for Sharing and then tab to or click on to Check Accessibility. The MSO-AC dialog panel will appear along the right side of your screen and show you Warnings, Errors or Inspection Results. The MSO-AC works dynamically (see 3 below) and will continue to run as you create or edit your document. To find the location of the error in your document, click or tab to the Warning statement and your screen will refresh showing the error location highlighted.</p>
<p>In the lower panel of the MSO-AC, there is Additional Information which explains the reason for the Warning/Error and step-by-step instructions on how to fix it.</p>
<p>In developing this tool, Microsoft apparently differentiated between accessibility issues that are minor and those considered critical. For example, including extra characters (Warning: Repeated Blank Characters) is considered minor &#8211; issuing a &#8220;Warning,&#8221; whereas the absence of ALT text for an inserted image is considered critical &#8211; issuing an &#8220;Error&#8221;</p>
<p>2. When creating new documents using the default version settings (not documents saved in pre-2007 versions of MSO), the MSO-AC seems to run smoothly as advertised. Documents created in older versions of Office, or saved in the pre-2007 format, may or may not work as expected. For example, testing some 2003 version Excel spreadsheets yielded an error statement: &#8220;Unable to run the Accessibility Checker &#8211; Cannot check the current file type for accessibility issues.&#8221; Attempts at saving the file in the current (2010) version had no effect on this. However, if the data is copied and pasted into a new Excel 2010 spreadsheet, the MSO-AC worked fine.</p>
<p>When using Word and PowerPoint, the MSO-AC worked essentially the same way (error when trying to check documents made by older versions), but sometimes simply saving the document in the new 2010 version allowed MSO-AC to work. Note to Microsoft: I found this to work inconsistently.</p>
<p>3. One of the best features of the MSO-AC is that once activated in the application it will run dynamically and continue to alert you to accessibility issues via the Accessibility Checker task pane (see image on this page) as you continue to create or edit your document. In other words, in PowerPoint, as you add features to a slide such as an image or chart, the MSO-AC immediately notes that the new object is lacking an ALT text description and provides directions and rationale on how to fix the accessibility error. And if you accidently &#8211; or purposely &#8211; remove an accessibility feature, MSO-AC will note this and provide a description of the issue, how to fix it and why it needs to be fixed. This dynamic feature allows the author to add the accessibility on the fly, as the document is being created. This feature alone has the potential of making the process of adding accessibility features faster and easier. The feature should be very helpful in enterprise settings, ultimately reducing the cost of training and accessibility auditing.</p>
<p>4. When adding ALT description text in MS-Office 2010, the procedure has been thankfully standardized across all applications. Right clicking with your mouse (Note: there are a series steps to accomplish this task using keystroke alternatives) brings up the Format Picture dialog box. Choose the &#8220;ALT Text&#8221; option at the bottom of the list and add the alternative text. Unfortunately, Microsoft has chosen to add an input box for adding a &#8220;Title&#8221; and/or a &#8220;Description&#8221; to this option. Even though the MSO-AC will &#8220;approve&#8221; an inserted image that has only a Title and not a Description, if you convert this document into another format (PDF or HTML) the Title will not pass as a valid description for accessibility purposes. In other words, for conversion purposes, the Description is more important than the Title. At this point, it is recommended that users add BOTH a Title and Description to their inserted image and make the content of the Title and Description the same.</p>
<h3>Final Thoughts</h3>
<p>One can only hope that the next version of MS Office will expand the Accessibility Checker to MS Publisher and all of the products within the suite. Hopefully MS will also include this feature in updates to its version of MS Office for the Mac OS.</p>
<p>As I continue to play with MSO-AC, I will no doubt find new and interesting features. I will post them as additions to this blog article or as separate entries. See the Resources below for links to what others have said about MS Office and accessibility.</p>
<h3>Resources</h3>
<p><a href="http://office2010.microsoft.com/en-us/starter-help/accessibility-checker-HA010369192.aspx">MS Tutorial on how to use the MSO-AC</a></p>
<p><a href="http://blogs.technet.com/b/office2010/archive/2010/01/07/office-2010-accessibility-investments-document-accessibility.aspx">A  blog article from MSO2010 Engineering (January 2010)  describing the  how the MSO-AC was developed and more about what it checks for.</a></p>
<p><a href="http://webaim.org/techniques/word/">WebAIM article about how to build accessible documents.  Includes information about the new MSO-AC.</a></p>
<p><a href="http://blogs.msdn.com/b/officewebapps/archive/2010/01/18/9949907.aspx">Another blog article from Microsoft on Office Web  Applications accessibility</a></p>
<p><a href="http://www.mediaaccess.org.au/index.php?option=com_content&amp;view=article&amp;id=931:office-2010-introduces-inbuilt-accessibility-checker&amp;catid=5:new-media&amp;Itemid=18">Media Access Australia blog about the new MSO-AC</a></p>
<p><a href="http://www.youtube.com/watch?v=SIAwWb4EnKo">YouTube Video on MS-Office 2010 Accessibility features</a></p>
]]></content:encoded>
			<wfw:commentRss>http://jebswebs.net/blog/2010/07/microsoft-office-2010-and-accessibility/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Why should my website be accessible?</title>
		<link>http://jebswebs.net/blog/2010/05/why-should-my-website-be-accessible/</link>
		<comments>http://jebswebs.net/blog/2010/05/why-should-my-website-be-accessible/#comments</comments>
		<pubDate>Sun, 23 May 2010 16:09:28 +0000</pubDate>
		<dc:creator>jeb</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[General Information]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[blind]]></category>
		<category><![CDATA[Section 508]]></category>
		<category><![CDATA[universal design]]></category>
		<category><![CDATA[web design]]></category>

		<guid isPermaLink="false">http://jebswebs.net/blog/?p=474</guid>
		<description><![CDATA[It occurred to me while I was posting a response to a potential client that I didn&#8217;t have a resource I could point them to as an answer to the question in the subject line. Certainly, after doing this work for over 10 years, I know the answer to the question, but I had never [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://jebswebs.net/blog/wp-content/uploads/2009/02/voiceovericon200808111.gif"><img class="alignright size-full wp-image-51" title="voiceover icon" src="http://jebswebs.net/blog/wp-content/uploads/2009/02/voiceovericon200808111.gif" alt="VoiceOver logo" width="106" height="106" /></a>It occurred to me while I was posting a response to a potential client that I didn&#8217;t have a resource I could point them to as an answer to the question in the subject line. Certainly, after doing this work for over 10 years, I know the answer to the question, but I had never written in down in exactly that form. Indeed, I have given innumerable workshops and talks over the years and always covered this in the first five minutes. But I guess I have always assumed that everyone already knew this. Silly me.</p>
<p>So here is my answer to the question: <em>Why should my website be accessible? </em>Feel free to comment as a way of adding to the list of reasons. The more (reasons) the merrier.</p>
<p>To begin, not everyone knows that a certain number of people with disabilities must use specialized hardware and software (called <a href="http://en.wikipedia.org/wiki/Assistive_technology">Assistive Technology or A.T.</a>) to use computers and technology. For example, most people who are blind (and many people with visual impairments) use a application called a <em><a href="http://en.wikipedia.org/wiki/Screen_readers">screen-reader</a> </em>which &#8220;translates&#8221; content on a computer (or other technology) into speech or Braille. The screen-reader software also provides a easy way for the blind person to use the various controls on a computer or device by providing audio feedback which tells the user what is being typed on the screen or what controls are being used. There are also &#8220;tools&#8221; built into the screen-reader application that allow the user to &#8220;scan&#8221; the information on the screen and navigate quickly through the content in a way that is purposeful and meaningful. Without screen-reading technology many blind people and those with visual impairments would not be able to use these technologies.  <a href="http://en.wikipedia.org/wiki/Screen_reader">Here is a link to more information about Braille and how screen-readers works</a>.</p>
<p>Consider for a moment all the people in the United States who have some form of visual disabilities &#8211; that is, all the blind and visually impaired folks. Recent estimates are that there are about 15 million people in the United States who have these disabilities (source <a href="http://www.brailleinstitute.org/facts_about_sight_loss">Braille Institute</a>). Can you afford to have your website not be available to 15 million people in the US alone?</p>
<p>If we also consider other people with disabilities, the numbers grow even larger. People with hearing disabilities frequently need to have <a href="http://en.wikipedia.org/wiki/Captioning">video content captioned</a> or audio files transcribed in order to be accessible. People with mobility impairments, that may not be able to use a mouse to navigate around a computer screen, need to have accessible websites that work with the various Assistive Technologies they use.</p>
<p>So the first reason your website should be accessible is because only  accessible websites will work correctly and completely with Assistive  Technologies. Those websites that are  partially accessible or not accessible at all, will be partially usable  or completely unusable by people who have disabilities.<strong> So, if you want everyone to have access to the content on your website, you should make sure your website is accessible.</strong></p>
<p>The next reason for having an accessible website is because accessible websites meet the <a href="http://www.w3.org/">international standards for web design</a> and for this reason will work in every &#8220;user agent,&#8221; that is, every browser, on every operating system, and in every mobile and handheld devices (e.g., mobile phones and small WiFi devices like iPods and iPads). There are literally thousands of different devices and configurations with new technologies being developed every day.  <strong>So, if you want your website to work with virtually all devices that connect to the internet, you should make sure your website is accessible.</strong></p>
<p>The next reason to make your website accessible is because <a href="http://www.google.com/accessibility/">Google</a> will love you for doing so. Well, not really, but if you want people to find and use your website, then you should be concerned about how search engines like Google &#8220;feel&#8221; about your site. The science behind this is called <a href="http://en.wikipedia.org/wiki/Search_engine_optimization">Search Engine Optimization (SEO)</a> which is based upon a set of methodologies that search engine services use to rank websites.</p>
<p>The corporate world spends lots of money tweaking their websites in order to improve their SEO. They understand that the difference of 1% in traffic flowing to a website could mean millions of dollars of profit for their company. Simply put, accessible web sites rank higher on SEO because they are built better than non-accessible sites and Google likes that. <strong>So, if you want to improve your SEO, you should make sure your website is accessible.</strong></p>
<p>The last reason I will give here is one that is not exactly universal &#8211; yet. However, the trends suggest that it is just a matter of time before it becomes universal. What I am talking about is the <em>legal requirement</em> to make your website accessible.</p>
<p>Currently in the United Kingdom, it is the law that websites be accessible to people with disabilities (<a href="http://www.rnib.org.uk/professionals/webaccessibility/lawsandstandards/Pages/uk_law.aspx">here is a summary about the law from Royal National Institute for Blind People</a>). While not everyone is yet in compliance, there has been a steady increase in the number of websites in the United Kingdom that meet accessibilty standards.</p>
<p>In the United States, there is no universal law requiring all websites to meet accessibility standards. However, <a href="http://www.section508.gov/">there are laws on the books that require websites for all federal and state government programs to be accessible</a>. Currently, there are several groups reviewing two federal laws that deal with accessibility and websites, <a href="http://www.section508.gov/">Section 508 of the Rehabilitation Act</a> and the <a href="http://www.ada.gov/">Americans with Disabilities Act</a>, with an eye on expanding these laws to cover more websites. In recent years, various advocacy organizations for disabled Americans have also brought numerous civil rights complaints against businesses for not having accessible websites. And, while there has not been a definitive legal ruling, it is clearly just a matter of time before website accessibility becomes the law of the land in the United States. <strong>So, if you want to get ahead of this and be ready when the laws and rules change, you should make sure your website is accessible.</strong></p>
<p>Here are some links to some other folks who have addressed this issue:</p>
<ul>
<li><a href="http://www.w3.org/standards/webdesign/accessibility">World  Wide Web Consortium (W3C) – Web Accessibility</a></li>
<li><a href="http://www.w3.org/WAI/bcase/">WAI&#8217;s &#8220;Developing a Web Accessibility Business Case for Your Organization&#8221; </a>(thank you Andrew Arch @w3.org)</li>
<li><a href="http://webaim.org/intro/">WebAIM</a></li>
<li><a href="http://www.gawds.org/">Guild of Accessible Web Designers (GAWD)</a></li>
<li><a href="http://www.disabled-world.com/disability/accessibility/websitedesign/accessible.php">Disabled World</a></li>
<li><a href="http://www.admixweb.com/2010/02/09/web-accessibility-6-reasons-why-its-important/">Admixweb</a></li>
<li><a href="http://www.hipertext.net/english/pag1026.htm">Hipertext.net</a></li>
</ul>
<p>And if you think of more reasons, please pass them along by commenting.</p>
]]></content:encoded>
			<wfw:commentRss>http://jebswebs.net/blog/2010/05/why-should-my-website-be-accessible/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>USDOJ smacks down Kindle</title>
		<link>http://jebswebs.net/blog/2010/01/usdoj-smacks-down-kindle/</link>
		<comments>http://jebswebs.net/blog/2010/01/usdoj-smacks-down-kindle/#comments</comments>
		<pubDate>Wed, 20 Jan 2010 22:27:38 +0000</pubDate>
		<dc:creator>jeb</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[education]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[Authors' Guild]]></category>
		<category><![CDATA[blind]]></category>
		<category><![CDATA[e-books]]></category>
		<category><![CDATA[HIGHER ED]]></category>
		<category><![CDATA[kindle]]></category>
		<category><![CDATA[reading]]></category>
		<category><![CDATA[text-to-speech]]></category>
		<category><![CDATA[visual impairment]]></category>

		<guid isPermaLink="false">http://jebswebs.net/blog/?p=329</guid>
		<description><![CDATA[I&#8217;ve reported about the Kindle more than a few times in this blog and have been generally fascinated by e-reader technology. I keep predicting it is the next big thing and with the pending announcement coming from the creatives in Cupertino, we may have another e-reader in the mix very soon. That said, the e-reader, [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://jebswebs.net/blog/wp-content/uploads/2009/03/kindle.jpg"><img class="alignright size-full wp-image-76" title="kindle" src="http://jebswebs.net/blog/wp-content/uploads/2009/03/kindle.jpg" alt="Kindle Reader" width="300" height="390" /></a>I&#8217;ve<a href="http://jebswebs.net/blog/tag/kindle/"> reported about the Kindle more than a few times in this blog</a> and have been generally fascinated by e-reader technology. I keep predicting it is the next big thing and with the pending announcement coming from the creatives in Cupertino, we may have another e-reader in the mix very soon.</p>
<p>That said, the e-reader, and specifically the Kindle by Amazon, has been having a rough time of it. First introduced in November of 2007, the Kindle was a big hit, selling out in the first five hours and on backorder for months after that. The Kindle 2, released two years later was equally well received and the DX version released a couple of months later was also very popular.</p>
<p>Then the fun began. A controversy with The <a href="http://jebswebs.net/blog/2009/03/has-your-kindle-been-hobbled/">Author&#8217;s Guild forced Amazon to hobble the Kindle </a>2 by shutting off the text-to-speech feature. Disability groups stormed the Manhattan offices of The Author&#8217;s Guild to protest and claim discrimination, but the device, it seems, was already inherently inaccessible to people with disabilities.</p>
<p>In May of 2009, Amazon announced a bold move of a offering the Kindles to several large US universities with the goal of taking over the college textbook industry and making paper college textbooks a thing of the past. More fun followed when the inherent inaccessibility of the device became widely known. <a href="http://jebswebs.net/blog/2009/11/kindle-fails-on-accessibility/">A number of the  universities that piloted the program with the Kindle backtracked and dropped out when they started to see the accessibility problems</a>. &#8220;Syracuse University and the University of Wisconsin at Madison, also examined the utility of the Kindle DX as a teaching device and decided that they would not use the Kindle DX until it is accessible to blind individuals&#8221; &#8211; this <a href="http://www.justice.gov/opa/pr/2010/January/10-crt-030.html">according to the US Department of Justice </a>(USDOJ).</p>
<p>The latest news on Kindle is a <a href="http://www.justice.gov/opa/pr/2010/January/10-crt-030.html">settlement with the USDOJ announced this week</a>. It states:</p>
<blockquote><p>Under the agreements reached today, the universities (Case Western Reserve University, Pace University, Reed College, and Arizona State University) generally will not purchase, recommend or promote use of the Kindle DX, or any other dedicated electronic book reader, unless the devices are fully accessible to students who are blind and have low vision. The universities agree that if they use dedicated electronic book readers, they will ensure that students with vision disabilities are able to access and acquire the same materials and information, engage in the same interactions, and enjoy the same services as sighted students with substantially equivalent ease of use. The agreements that the Justice Department reached with these universities extend beyond the Kindle DX to any dedicated electronic reading device.</p></blockquote>
<p>This sounds pretty bad for Amazon and the Kindle.</p>
<p>And given Mr. Jobs recent efforts at making Apple products fully accessible, one can only imagine that the rumored &#8220;Apple Table device&#8221; WILL be fully accessible and perfectly timed to kick butt.</p>
<p>Stay tuned.</p>
]]></content:encoded>
			<wfw:commentRss>http://jebswebs.net/blog/2010/01/usdoj-smacks-down-kindle/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>NFB Protest Authors Guild</title>
		<link>http://jebswebs.net/blog/2009/03/nfb-protest-authors-guild/</link>
		<comments>http://jebswebs.net/blog/2009/03/nfb-protest-authors-guild/#comments</comments>
		<pubDate>Thu, 26 Mar 2009 03:20:49 +0000</pubDate>
		<dc:creator>jeb</dc:creator>
				<category><![CDATA[General Information]]></category>
		<category><![CDATA[Authors' Guild]]></category>
		<category><![CDATA[blind]]></category>
		<category><![CDATA[kindle]]></category>
		<category><![CDATA[NFB]]></category>

		<guid isPermaLink="false">http://jebswebs.net/blog/2009/03/nfb-protest-authors-guild/</guid>
		<description><![CDATA[I blogged a few days ago about a recent decision by Amazon to turn off the text-to-speech feature of the new Kindle 2 after The Authors Guild complained about licensing issues. The National Federation of the Blind are organizing a protest on April 7th at the Authors Guild in New York City. More information about [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignright size-medium wp-image-76" title="kindle" src="http://jebswebs.net/blog/wp-content/uploads/2009/03/kindle-230x300.jpg" alt="kindle" width="230" height="300" />I b<a href="http://jebswebs.net/blog/2009/03/has-your-kindle-been-hobbled/">logged a few days ago</a> about a recent decision by <a href="http://www.amazon.com">Amazon</a> to turn off the text-to-speech feature of the new Kindle 2 after <a href="http://www.authorsguild.org/">The Authors Guild</a> complained about licensing issues. The <a href="http://www.nfb.org/nfb/Default.asp">National Federation of the Blind</a> are organizing a protest on April 7th at the <a href="http://www.authorsguild.org/">Authors Guild</a> in New York City.</p>
<p><a href="http://www.facebook.com/event.php?eid=71921998551">More information about the protest can be found on their Facebook page</a></p>
<p>~j</p>
]]></content:encoded>
			<wfw:commentRss>http://jebswebs.net/blog/2009/03/nfb-protest-authors-guild/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Description Key</title>
		<link>http://jebswebs.net/blog/2009/02/description-key/</link>
		<comments>http://jebswebs.net/blog/2009/02/description-key/#comments</comments>
		<pubDate>Wed, 25 Feb 2009 16:37:18 +0000</pubDate>
		<dc:creator>jeb</dc:creator>
				<category><![CDATA[General Information]]></category>
		<category><![CDATA[blind]]></category>
		<category><![CDATA[description]]></category>
		<category><![CDATA[visual impairment]]></category>

		<guid isPermaLink="false">http://jebswebs.net/blog/?p=23</guid>
		<description><![CDATA[Description is the key to opening a world of information for persons with a vision loss, literacy needs, or loss of cognitive abilities.]]></description>
			<content:encoded><![CDATA[<div id="attachment_24" class="wp-caption alignright" style="width: 220px"><a href="http://www.dcmp.org/descriptionkey/index.html"><img class="size-full wp-image-24" title="Explore the Description Key" src="http://jebswebs.net/blog/wp-content/uploads/2009/02/descriptionkey.png" alt="Explore the Description Key" width="210" height="123" /></a><p class="wp-caption-text">Explore the Description Key</p></div>
<p>I just came across information about a <a href="http://www.dcmp.org/descriptionkey/index.html" target="_blank">website dedicated to Description</a> for persons with a vision loss, literacy needs, or loss of cognitive abilities. This site is dedicated to providing description to educational materials and should be of interest to Assistive Technology specialists working in schools.</p>
<p>From the website, Description is defined as:</p>
<div class="toggle">
<blockquote><p><a title="Learn about Audio Description" href="http://www.dcmp.org/equalaccess/d.html">Description</a> is the verbal depiction of key visual elements in media and live productions. Also known as “audio description” or “video description,” the description of media involves the interspersion of these depictions with the program’s original audio.</p>
<p>The <a title="the vocabulary and language section of the description key" href="http://www.dcmp.org/descriptionkey/how_to_describe.html#how_vocabulary">vocabulary and language</a> structure used in the description of educational media should be consistent with that used in the program being described. It is also important to make a distinction between media that is produced for educational purposes and that which is produced purely for entertainment—the “key visual elements” of an educational program should be those that serve in conveying a specific learning goal.</p></blockquote>
<p>The site goes on to explain:</p>
<blockquote><p>Description is the key to opening a world of information for persons with a vision loss, literacy needs, or loss of cognitive abilities. The American Foundation for the Blind reports that <a title="American Foundation for the Blind Vision Loss Statistics" href="http://www.afb.org/Section.asp?SectionID=15&amp;DocumentID=4398">21.2 million Americans have vision loss</a>. While description was developed for people who are blind or visually impaired, millions of others may also benefit from description’s concise, objective translation of media’s key visual components.</p></blockquote>
<p><a href="http://www.dcmp.org/descriptionkey/index.html">Check out Description Key for educational media</a></p>
<p>~jeb</p></div>
]]></content:encoded>
			<wfw:commentRss>http://jebswebs.net/blog/2009/02/description-key/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
