<?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>Thinking Accessible &#187; News</title>
	<atom:link href="http://thinkingaccessible.com/category/news/feed/" rel="self" type="application/rss+xml" />
	<link>http://thinkingaccessible.com</link>
	<description>Making accessiblity accessible to you.</description>
	<lastBuildDate>Sun, 21 Feb 2010 18:12:07 +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>Reviewing an authoring tool</title>
		<link>http://thinkingaccessible.com/reviewing-an-authoring-tool/</link>
		<comments>http://thinkingaccessible.com/reviewing-an-authoring-tool/#comments</comments>
		<pubDate>Wed, 17 Jun 2009 22:06:34 +0000</pubDate>
		<dc:creator>Rocío</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[guidelines]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[validity]]></category>
		<category><![CDATA[W3C]]></category>
		<category><![CDATA[WCAG]]></category>
		<category><![CDATA[Web Accessibility]]></category>

		<guid isPermaLink="false">http://thinkingaccessible.com/?p=138</guid>
		<description><![CDATA[I was going to do an evaluation of an authoring tool, but the WAI have thought of it already at www.w3.org/WAI/AU/2002/tools.
I found that the reviews were all a little outdated and I didn’t get a definite conclusion from any review. So I finally decided to go ahead and check out an authoring tool myself. I [...]]]></description>
			<content:encoded><![CDATA[<p>I was going to do an evaluation of an authoring tool, but the WAI have thought of it already at <a href="http://www.w3.org/WAI/AU/2002/tools">www.w3.org/WAI/AU/2002/tools.</a></p>
<p>I found that the reviews were all a little outdated and I didn’t get a definite conclusion from any review. So I finally decided to go ahead and check out an authoring tool myself. I went for the markup editor developed in collaboration with the W3C, <a href="http://www.w3.org/Amaya/">Amaya</a>. It’s a WYSIWYG editor/browser. Many distributions are available. I will be looking at the Windows one.</p>
<p>I opened an existing file that I know is made to standard and it came out all distorted. I then created a page from scratch. I must admit that I’m not used to any kind of authoring tool. I have been using Notepad++ for a while. So it was a little strange. At first it took me some time to get used to the application itself, but after a while of playing with it, it was fairly simple to use. I did a trivial page with a menu, an unordered list, a form and an image.<br />
Page done with Amaya</p>
<div id="attachment_176" class="wp-caption aligncenter" style="width: 410px"><img class="size-full wp-image-176" title="Page done with authoring tool Amaya" src="http://thinkingaccessible.com/wp-content/uploads/amaya1.jpg" alt="Page done with authoring tool Amaya" width="400" height="200" /><p class="wp-caption-text">Page done with authoring tool Amaya</p></div>
<p>Formatting done to some text resulted in inlining style, there were extra open and close paragraphs, inserting the image required to enter an alternative text, and as for the other elements they were pretty intuitive.</p>
<p>It’s clear that you still need to know some basic concepts in web standards to make any web page complaint or accessible. This tool might be good for someone just starting, but I think I’ll just stay with my simple text editor.</p>
]]></content:encoded>
			<wfw:commentRss>http://thinkingaccessible.com/reviewing-an-authoring-tool/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Examples of assistive technologies</title>
		<link>http://thinkingaccessible.com/examples-of-assistive-technologies/</link>
		<comments>http://thinkingaccessible.com/examples-of-assistive-technologies/#comments</comments>
		<pubDate>Sun, 24 May 2009 15:49:32 +0000</pubDate>
		<dc:creator>Rocío</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Reviews]]></category>
		<category><![CDATA[assistive technologies]]></category>
		<category><![CDATA[WCAG]]></category>

		<guid isPermaLink="false">http://thinkingaccessible.com/?p=89</guid>
		<description><![CDATA[So I saw this story on the news by Chris Brown and was happy to learn that assistive technologies are being researched actively in Canadian Universities.  The University of Victoria has a unit named CanAssist, they develop technologies and provide services for people with disabilities. Naturally this is relevant in terms of web accessibility because [...]]]></description>
			<content:encoded><![CDATA[<p>So I saw this story on the news by Chris Brown and was happy to learn that assistive technologies are being researched actively in Canadian Universities.  The University of Victoria has a unit named CanAssist, they develop technologies and provide services for people with disabilities. Naturally this is relevant in terms of web accessibility because a lot of these devices interact with computers. I encourage you to read their <a title="Page on CanAssist" href="http://www.canassist.ca/technology-showcase">technology showcase</a> as it describes the uses of these technologies by people with different types of disabilities. For example, instead of using a mouse for navigation, it is possible to use one’s mouth. And as the news piece revealed, the team of researchers have created a device that detects the movement of the pupils and allows the cursor to move accordingly. Pretty ingenious!</p>
<p>It is obvious that these researchers and developers are not waiting for websites to get their act together in terms of web accessibility, but it just proves that this demographic has the possibility to access the world wide web. We can all make it a little bit easier for researchers to make these products more effective by implementing WCAG.</p>
<p>Watch the video entitled “<a title="CBC article by Chris Brown" href="http://www.cbc.ca/national/blog/video/environmentscience/communication_research.html">Communication Research</a>” at the CBC. Unfortunately, this video has no caption and thus not accessible.</p>
]]></content:encoded>
			<wfw:commentRss>http://thinkingaccessible.com/examples-of-assistive-technologies/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Forget CSS Opacity for now</title>
		<link>http://thinkingaccessible.com/forget-css-opacity-for-now/</link>
		<comments>http://thinkingaccessible.com/forget-css-opacity-for-now/#comments</comments>
		<pubDate>Fri, 08 May 2009 00:58:09 +0000</pubDate>
		<dc:creator>Rocío</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[CSS2]]></category>
		<category><![CDATA[CSS3]]></category>
		<category><![CDATA[validity]]></category>

		<guid isPermaLink="false">http://thinkingaccessible.com/?p=60</guid>
		<description><![CDATA[It&#8217;s been trendy for a while now to play with transparency to simulate layers, but guess what? Yeap, you know it. It&#8217;s not valid under CSS2.
Stuff like opacity: .4 -moz-opacity: .4 filter: alpha(opacity=40) for the moment out of the question. We all have to wait patiently until CSS3. Yeah you heard me CSS3. If you [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s been trendy for a while now to play with transparency to simulate layers, but guess what? Yeap, you know it. It&#8217;s not valid under CSS2.</p>
<p>Stuff like opacity: .4 -moz-opacity: .4 filter: alpha(opacity=40) for the moment out of the question. We all have to wait patiently until CSS3. Yeah you heard me CSS3. If you did&#8217;t know, CSS2 is the current cascading style sheet language recognized by most of your browsers and it&#8217;s getting a face lift. Alas, the due date is unknown at this point.</p>
<p>If you want more information on this check out these important websites:<br />
<a href="http://www.css3.info ">www.css3.info </a><br />
<a href="http://www.w3.org/Style/CSS/current-work">www.w3.org/Style/CSS/current-work</a></p>
]]></content:encoded>
			<wfw:commentRss>http://thinkingaccessible.com/forget-css-opacity-for-now/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
