<?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>Fair Use Lab &#187; technology</title>
	<atom:link href="http://fairuselab.net/tag/technology/feed/" rel="self" type="application/rss+xml" />
	<link>http://fairuselab.net</link>
	<description>Re-Imagining Accessibility, Disability &#38; the Public Sphere</description>
	<lastBuildDate>Wed, 02 Nov 2011 20:50:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>U.S. Department of Education Issues Guidance on Rights of Students With Disabilities When Educational Institutions Use Technology</title>
		<link>http://fairuselab.net/2011/05/26/u-s-department-of-education-issues-guidance-on-rights-of-students-with-disabilities-when-educational-institutions-use-technology/</link>
		<comments>http://fairuselab.net/2011/05/26/u-s-department-of-education-issues-guidance-on-rights-of-students-with-disabilities-when-educational-institutions-use-technology/#comments</comments>
		<pubDate>Thu, 26 May 2011 20:19:34 +0000</pubDate>
		<dc:creator>Mark Willis</dc:creator>
				<category><![CDATA[disability]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[education]]></category>
		<category><![CDATA[K-12]]></category>
		<category><![CDATA[technology]]></category>

		<guid isPermaLink="false">http://fairuselab.net/?p=1078</guid>
		<description><![CDATA[The U.S. Department of Education's Office for Civil Rights (OCR) issued guidance through Dear Colleague Letters to elementary and secondary schools and institutions of higher education along with a Frequently Asked Questions document on the legal obligation to provide students with disabilities an equal opportunity to enjoy the benefits of technology. This guidance is a critical step in the Department's ongoing efforts to ensure that students with disabilities receive equal access to the educational benefits and services provided by their schools, colleges and universities. All students, including those with disabilities, must have the tools needed to obtain a world-class education that prepares them for success in college and careers. <a href="http://fairuselab.net/2011/05/26/u-s-department-of-education-issues-guidance-on-rights-of-students-with-disabilities-when-educational-institutions-use-technology/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>via <a href="http://www.ed.gov/news/press-releases/department-education-issues-guidance-rights-students-disabilities-when-education">Dept. of Education news release</a> issued 052611:</p>
<blockquote><p>Today, the U.S. Department of Education&#8217;s Office for Civil Rights  (OCR) issued guidance through Dear Colleague Letters to elementary and  secondary schools and institutions of higher education along with a  Frequently Asked Questions document on the legal obligation to provide  students with disabilities an equal opportunity to enjoy the benefits of  technology. This guidance is a critical step in the Department&#8217;s  ongoing efforts to ensure that students with disabilities receive equal  access to the educational benefits and services provided by their  schools, colleges and universities. All students, including those with  disabilities, must have the tools needed to obtain a world-class  education that prepares them for success in college and careers.</p>
<p>Today&#8217;s guidance provides information to schools about their  responsibilities under Section 504 of the Rehabilitation Act of 1973 and  Title II of the Americans with Disabilities Act. The guidance  supplements a June 2010 letter issued jointly by OCR and the Civil  Rights Division of the U.S. Department of Justice. The June letter  explains that technological devices must be accessible to students with  disabilities, including students who are blind or have low vision,  unless the benefits of the technology are provided equally through other  means. Today&#8217;s guidance highlights what educational institutions need  to know and take into consideration in order to ensure that students  with disabilities enjoy equal access when information and resources are  provided through technology.</p>
<p>&#8220;Technology can be a critical investment in enhancing educational  opportunities for all students,&#8221; said Russlynn Ali, assistant secretary  for civil rights. &#8220;The Department is firmly committed to ensuring that  schools provide students with disabilities equal access to the benefits  of technological advances.&#8221;</p>
<p>Today&#8217;s guidance is part of a larger effort by the Department and  Obama administration to better serve the needs of people with  disabilities. Last month, U.S. Secretary of Education Arne Duncan joined  Kareem Dale, associate director for the White House Office of Public  Engagement and special assistant to the President for disability policy,  for a conference call with stakeholders to talk about some of the  Department&#8217;s efforts. During the call, Duncan discussed the Department&#8217;s  commitment to maintaining accountability in No Child Left Behind for  all subgroups, including students with disabilities, and highlighted the  Department&#8217;s proposal to increase funding for students with  disabilities in the fiscal year 2012 budget. Ali will also join Dale for  a stakeholder conference call where she will discuss today&#8217;s guidance  and address the Department&#8217;s work to ensure that all schools are  fulfilling their responsibilities under the federal disability laws that  OCR enforces.</p>
<p>To read the Dear Colleague Letter to elementary and secondary schools, see <a href="http://www2.ed.gov/about/offices/list/ocr/letters/colleague-201105-ese.html">http://www2.ed.gov/about/offices/list/ocr/letters/colleague-201105-ese.html</a>.</p>
<p>To read the Dear Colleague Letter to institutions of higher education, see <a href="http://www2.ed.gov/about/offices/list/ocr/letters/colleague-201105-pse.html">http://www2.ed.gov/about/offices/list/ocr/letters/colleague-201105-pse.html</a>.</p>
<p>The FAQ is available at <a href="http://www2.ed.gov/about/offices/list/ocr/docs/dcl-ebook-faq-201105.html">http://www2.ed.gov/about/offices/list/ocr/docs/dcl-ebook-faq-201105.html</a>.</p>
<p>To read the June 29, 2010 letter, see <a href="http://www2.ed.gov/about/offices/list/ocr/letters/colleague-20100629.html">http://www2.ed.gov/about/offices/list/ocr/letters/colleague-20100629.html</a>.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://fairuselab.net/2011/05/26/u-s-department-of-education-issues-guidance-on-rights-of-students-with-disabilities-when-educational-institutions-use-technology/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Re-Imagining Accessibility Via Digital Companions</title>
		<link>http://fairuselab.net/2009/12/15/re-imagining-accessibility-via-digital-companions/</link>
		<comments>http://fairuselab.net/2009/12/15/re-imagining-accessibility-via-digital-companions/#comments</comments>
		<pubDate>Tue, 15 Dec 2009 20:20:50 +0000</pubDate>
		<dc:creator>Mark Willis</dc:creator>
				<category><![CDATA[accessibility]]></category>
		<category><![CDATA[Berkman Center]]></category>
		<category><![CDATA[robots]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[virtaul assistant]]></category>

		<guid isPermaLink="false">http://fairuselab.net/?p=738</guid>
		<description><![CDATA[I’ve written elsewhere about what I desire in a virtual assistant. I want one that can find and read anything to me, breaking down every barrier to accessibility. It would know as much as I do, if not more, about hacking text and code. It would know when to take out those noxious flashing scripts before I ever arrive at a web page. It would remember the floes and eddies of my attention. And unlike that stupid Microsoft wizard, it wouldn’t make me waste time trying to undo its unwanted prescience. Is that too much to ask? It’s certainly part of what I mean by re-imagining accessibility. <a href="http://fairuselab.net/2009/12/15/re-imagining-accessibility-via-digital-companions/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.dcs.shef.ac.uk/~yorick/">Yorick Wilks</a> is a researcher with the <a href="http://www.companions-project.org/">Companions Project</a>. He envisions a future with “digital companions” (don’t call them robots) who have long and memorable conversations with us &#8212; knowing our wants and foibles, getting things done, telling us jokes, maybe even laughing at the jokes we tell over and over again.</p>
<p>According to the Companions Project:</p>
<blockquote><p>This will be an agent or &#8216;presence&#8217; that stays with the user for long periods of time, developing a relationship and &#8216;knowing&#8217; its owners preferences and wishes. It will communicate with the user primarily by using and understanding speech.</p></blockquote>
<p>Yorick Wilks talked about the concept of digital companions on <a href="http://blogs.law.harvard.edu/mediaberkman/2009/12/03/radio-berkman-138-my-friend-the-robot/">Radio Berkman</a>, and a longer version of his Berkman lecture is available as a<a href="http://blogs.law.harvard.edu/mediaberkman/2009/11/09/yorick-wilks-on-internet-companions-technical-and-social-issues/"> video</a>.</p>
<p>I’ve written elsewhere about <a href="http://blindflaneur.com/?p=1727">what I desire in a virtual assistant</a>. I want one that can find and read anything to me, breaking down every barrier to accessibility. It would know as much as I do, if not more, about hacking text and code. It would know when to take out those noxious flashing scripts before I ever arrive at a web page. It would remember the floes and eddies of my attention. And unlike that stupid Microsoft wizard, it wouldn’t make me waste time trying to undo its unwanted prescience. Is that too much to ask? It’s certainly part of what I mean by re-imagining accessibility.</p>
]]></content:encoded>
			<wfw:commentRss>http://fairuselab.net/2009/12/15/re-imagining-accessibility-via-digital-companions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Who Will Write The History of Accessible Technology?</title>
		<link>http://fairuselab.net/2009/06/01/who-will-write-the-history-of-accessible-technology/</link>
		<comments>http://fairuselab.net/2009/06/01/who-will-write-the-history-of-accessible-technology/#comments</comments>
		<pubDate>Mon, 01 Jun 2009 18:25:53 +0000</pubDate>
		<dc:creator>Mark Willis</dc:creator>
				<category><![CDATA[accessibility]]></category>
		<category><![CDATA[media studies]]></category>
		<category><![CDATA[journalism]]></category>
		<category><![CDATA[technology]]></category>

		<guid isPermaLink="false">http://fairuselab.net/?p=405</guid>
		<description><![CDATA[I&#8217;d like to see an extension of the Poynter Timeline documenting the parallel development of computer-based information accessibility. Here are several of my milestones: 1976: The first time I heard about CCTV reading systems for visually impaired people. It wasn’t &#8230; <a href="http://fairuselab.net/2009/06/01/who-will-write-the-history-of-accessible-technology/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;d like to see an extension of the <a href="http://poynter.org/content/content_view.asp?id=75953">Poynter Timeline </a> documenting the parallel development of computer-based information accessibility. Here are several of my milestones:</p>
<p><strong>1976:</strong> The first time I heard about CCTV reading systems for visually impaired people. It wasn’t a doctor, an educator, or a rehab counselor who told me about it, but a friend’s landlord, a bureaucrat who purchased them on behalf of the state government.</p>
<p><strong>1977:</strong> A rehab doctor at OSU told me the state might buy a CCTV for a writer like Ernest Hemingway if he were going blind, but it would never buy one for the likes of me.</p>
<p><strong>1979:</strong> The first time I saw (and heard) a Kurzweil reading machine in action. It was as big as a refrigerator, and it had its own priestess who wouldn’t allow blind students to touch it.</p>
<p><strong>1984:</strong> I used a talking computer for the first time. I finally acquired a CCTV, and it still works 25 years later!</p>
<p><strong>2009:</strong> After working for 30 years with generations of speech synthesizers that cost thousands of dollars, I installed the Odiogo “Listen” plugin on this blog for <em>free</em>.</p>
<p><a href="http://poynter.org/content/content_view.asp?id=75953">Poynter Online &#8211; New Media Timeline (1969-2008)</a>:</p>
<blockquote>
<div>Our timeline looks at the history of new media and online journalism from <a href="http://poynter.org/content/content_view.asp?id=75818">1969</a> to <a href="http://poynter.org/content/content_view.asp?id=135080&amp;sid=26">2008</a>.</div>
<div>We are presenting it in two parts, with parallel sections on &#8220;Technology/Services/Social&#8221; and &#8220;The Media.&#8221;</p>
<p><a href="http://poynter.org/profile/profile.asp?user=1634">David Shedden</a>, Library Director of the <a href="http://poynter.org/">Poynter</a> Institute&#8217;s Eugene Patterson Library, began compiling this timeline and <a href="http://poynter.org/content/content_view.asp?id=899">bibliography</a> in 1995.</p>
<p>We hope the timeline serves as a useful reference tool for journalists, students, and researchers.</p></div>
<div>We also hope it helps preserve the history of new media and online journalism, a history that isn&#8217;t very new after all.</div>
</blockquote>
]]></content:encoded>
			<wfw:commentRss>http://fairuselab.net/2009/06/01/who-will-write-the-history-of-accessible-technology/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

