<?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: The Accessibility Chronicles	</title>
	<atom:link href="https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles/feed" rel="self" type="application/rss+xml" />
	<link>https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles</link>
	<description>A running commentary of occasionally interesting things — from Mike Davidson.</description>
	<lastBuildDate>Thu, 26 May 2016 06:34:36 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.3</generator>
	<item>
		<title>
		By: Ed		</title>
		<link>https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles#comment-6703</link>

		<dc:creator><![CDATA[Ed]]></dc:creator>
		<pubDate>Tue, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-6703</guid>

					<description><![CDATA[Myk writes:
&lt;blockquote&gt;&lt;p&gt;It would be nice if Firefox would give us a screen-reader simulation mode, right. They don&#039;t need to do the whole screenreader software, but perhaps a sort of debugging mode, see what I mean?&lt;/p&gt;&lt;/blockquote&gt;

Do a search for Fangs Screen Reader Emulator. It&#039;s a plugin for Mozilla-based browsers that creates a text output mimicking what a screenreader would output.

Or do a search for WebbIE, a standalone app that can do the same thing.]]></description>
			<content:encoded><![CDATA[<p>Myk writes:</p>
<blockquote>
<p>It would be nice if Firefox would give us a screen-reader simulation mode, right. They don&#8217;t need to do the whole screenreader software, but perhaps a sort of debugging mode, see what I mean?</p>
</blockquote>
<p>Do a search for Fangs Screen Reader Emulator. It&#8217;s a plugin for Mozilla-based browsers that creates a text output mimicking what a screenreader would output.</p>
<p>Or do a search for WebbIE, a standalone app that can do the same thing.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Zach		</title>
		<link>https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles#comment-6694</link>

		<dc:creator><![CDATA[Zach]]></dc:creator>
		<pubDate>Tue, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-6694</guid>

					<description><![CDATA[I work in a technology department at my college and we recently purchased a JAWS license.  After installation I quickly realized how difficult it must be to learn to use this application.  

I first checked out Zeldman.com and Mikeindustries.com, and boy what a disaster.  First of all, the program read a whole bunch of garbage that left me entirely confused.  I looked through the manual (itself, a beast) and the number of shortcuts and CTRL combinations made me nearly wet myself.  Eventhough I could *SEE* exactly what was on the monitor, I still couldn&#039;t figure out what or where the scary voice was reading.

I have since discovered that the program needs to be &quot;configured&quot; and I need to browse the web &quot;in a certain way&quot; for JAWS to function properly, but I think this is folly in and of itself.  JAWS should just work right out of the box and websites should be clearly rendered verbally.

This would make it much more pleasant for people like myself, who need to use JAWS in order to test for Section 508 compliance.  As of now I am damned to reading sites in print only mode (and even then sometimes doing something as simple as reading the previous or next paragraph is a challenge.)]]></description>
			<content:encoded><![CDATA[<p>I work in a technology department at my college and we recently purchased a JAWS license.  After installation I quickly realized how difficult it must be to learn to use this application.  </p>
<p>I first checked out Zeldman.com and Mikeindustries.com, and boy what a disaster.  First of all, the program read a whole bunch of garbage that left me entirely confused.  I looked through the manual (itself, a beast) and the number of shortcuts and CTRL combinations made me nearly wet myself.  Eventhough I could *SEE* exactly what was on the monitor, I still couldn&#8217;t figure out what or where the scary voice was reading.</p>
<p>I have since discovered that the program needs to be &#8220;configured&#8221; and I need to browse the web &#8220;in a certain way&#8221; for JAWS to function properly, but I think this is folly in and of itself.  JAWS should just work right out of the box and websites should be clearly rendered verbally.</p>
<p>This would make it much more pleasant for people like myself, who need to use JAWS in order to test for Section 508 compliance.  As of now I am damned to reading sites in print only mode (and even then sometimes doing something as simple as reading the previous or next paragraph is a challenge.)</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Myk		</title>
		<link>https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles#comment-6695</link>

		<dc:creator><![CDATA[Myk]]></dc:creator>
		<pubDate>Tue, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-6695</guid>

					<description><![CDATA[If we want lower-cost, I suppose the easy answer is going to go back to browsers.  It would be nice if Firefox would give us a screen-reader simulation mode, right.  They don&#039;t need to do the whole screenreader software, but perhaps a sort of debugging mode, see what I mean?

So like, I design my page, do all my web standards and accessibility stuff, test it in FF, Safari, IE, etc.  Then my final bit of testing would be to run it through the firefox JAWS simulator:

Screen goes blank, split in two.  On the top, the text that the screenreader would be reading to the listener.  On the bottom, source code with highlighting.

This sounds feasible, doesn&#039;t it?  Someone smarter than me should just make the firefox plugin.  You could even throw in all the keyboard shortcuts and stuff of JAWS.

I imagine that the tricky part of the screen-reader, the part that costs 985 of the 1000 dollars, is the voice and reading and etc, right?  So, a mocked up display of what would be reading should be simple enough to anyone who knows how JAWS works?  

Or am I just naive?  That would be a handy, handy tool.  Or is there one?]]></description>
			<content:encoded><![CDATA[<p>If we want lower-cost, I suppose the easy answer is going to go back to browsers.  It would be nice if Firefox would give us a screen-reader simulation mode, right.  They don&#8217;t need to do the whole screenreader software, but perhaps a sort of debugging mode, see what I mean?</p>
<p>So like, I design my page, do all my web standards and accessibility stuff, test it in FF, Safari, IE, etc.  Then my final bit of testing would be to run it through the firefox JAWS simulator:</p>
<p>Screen goes blank, split in two.  On the top, the text that the screenreader would be reading to the listener.  On the bottom, source code with highlighting.</p>
<p>This sounds feasible, doesn&#8217;t it?  Someone smarter than me should just make the firefox plugin.  You could even throw in all the keyboard shortcuts and stuff of JAWS.</p>
<p>I imagine that the tricky part of the screen-reader, the part that costs 985 of the 1000 dollars, is the voice and reading and etc, right?  So, a mocked up display of what would be reading should be simple enough to anyone who knows how JAWS works?  </p>
<p>Or am I just naive?  That would be a handy, handy tool.  Or is there one?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Chris		</title>
		<link>https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles#comment-6696</link>

		<dc:creator><![CDATA[Chris]]></dc:creator>
		<pubDate>Tue, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-6696</guid>

					<description><![CDATA[Can we stop putting everyone in a group.

I have seen many people who have lots of ways of using the internet so to simply say &quot;sit down with a blind person&quot; solves nothing.]]></description>
			<content:encoded><![CDATA[<p>Can we stop putting everyone in a group.</p>
<p>I have seen many people who have lots of ways of using the internet so to simply say &#8220;sit down with a blind person&#8221; solves nothing.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Greg		</title>
		<link>https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles#comment-6697</link>

		<dc:creator><![CDATA[Greg]]></dc:creator>
		<pubDate>Tue, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-6697</guid>

					<description><![CDATA[I just posted this a response about screen readers on Veerle&#039;s blog and thought I&#039;d share it here too.

For those of you who have never seen Adaptive Technology in use on the web (especially in person), I think that these videos will help give you some more insight. I hope they help others. I know they helped me.

These are definitely worth watching.

&lt;a href=&quot;http://www.doit.wisc.edu/accessibility/video/&quot; rel=&quot;nofollow&quot;&gt;http://www.doit.wisc.edu/accessibility/video/&lt;/a&gt;]]></description>
			<content:encoded><![CDATA[<p>I just posted this a response about screen readers on Veerle&#8217;s blog and thought I&#8217;d share it here too.</p>
<p>For those of you who have never seen Adaptive Technology in use on the web (especially in person), I think that these videos will help give you some more insight. I hope they help others. I know they helped me.</p>
<p>These are definitely worth watching.</p>
<p><a href="http://www.doit.wisc.edu/accessibility/video/" rel="nofollow">http://www.doit.wisc.edu/accessibility/video/</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Eric Blaska		</title>
		<link>https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles#comment-6698</link>

		<dc:creator><![CDATA[Eric Blaska]]></dc:creator>
		<pubDate>Tue, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-6698</guid>

					<description><![CDATA[I see more people in wheel chairs during the day then 1000 pound people, actually I don&#039;t think I&#039;ve ever seen one in persons besides on the internet or TV.  

Good Article.  I currently work for a Construction company that has to deal with ADA standards on a constant basis.  After having completing a project having a handicap person roll up a ramp in a wheel chair is heart warming.]]></description>
			<content:encoded><![CDATA[<p>I see more people in wheel chairs during the day then 1000 pound people, actually I don&#8217;t think I&#8217;ve ever seen one in persons besides on the internet or TV.  </p>
<p>Good Article.  I currently work for a Construction company that has to deal with ADA standards on a constant basis.  After having completing a project having a handicap person roll up a ramp in a wheel chair is heart warming.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Andy Davies		</title>
		<link>https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles#comment-6699</link>

		<dc:creator><![CDATA[Andy Davies]]></dc:creator>
		<pubDate>Tue, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-6699</guid>

					<description><![CDATA[As someone who&#039;s currently working with some developers on making accessible eLearning content I though I&#039;d throw my $0.02 worth in...

One of the problems with using lists and then styling then is that Jaws etc don&#039;t fully understand the styling so the user get&#039;s &#039;bullet&#039; read out before each item (if it&#039;s a long list it soon get&#039;s frustrating)

You also shouldn&#039;t just think of blind people as the only ones who need support - there are all kinds of visual, cognitive and motor difficulties around. One of the things that helps some people is alternate color schemes e.g. hi/low contrast e.g white or blue, and have come across situations where it makes it easier for people with things like dyslexia.

Lots of able people find things like Jaws really intimidating but if you watch an experienced user with it they really motor.

There are free trial copies of accessibility tools like Jaw, SuperNova etc available to download and try - give them a go there an interesting experience!]]></description>
			<content:encoded><![CDATA[<p>As someone who&#8217;s currently working with some developers on making accessible eLearning content I though I&#8217;d throw my $0.02 worth in&#8230;</p>
<p>One of the problems with using lists and then styling then is that Jaws etc don&#8217;t fully understand the styling so the user get&#8217;s &#8216;bullet&#8217; read out before each item (if it&#8217;s a long list it soon get&#8217;s frustrating)</p>
<p>You also shouldn&#8217;t just think of blind people as the only ones who need support &#8211; there are all kinds of visual, cognitive and motor difficulties around. One of the things that helps some people is alternate color schemes e.g. hi/low contrast e.g white or blue, and have come across situations where it makes it easier for people with things like dyslexia.</p>
<p>Lots of able people find things like Jaws really intimidating but if you watch an experienced user with it they really motor.</p>
<p>There are free trial copies of accessibility tools like Jaw, SuperNova etc available to download and try &#8211; give them a go there an interesting experience!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Kristopher Leslie		</title>
		<link>https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles#comment-6700</link>

		<dc:creator><![CDATA[Kristopher Leslie]]></dc:creator>
		<pubDate>Tue, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-6700</guid>

					<description><![CDATA[Well I look at it like this, considering all the blame/pointing fingers and other abstract views of accessibility, the core of the topic is that there is a issue with accessiblity. This is a by product from the OS, Browser, and software/hardware manufactor&#039;s lack of design, ability to hear a customers opinion and explain why or why not there isn&#039;t such good accessiblity (x) on the market now, and the overall denying that people don&#039;t want to cater to that &quot;group&quot; of users.

I for one am happy to be a webdesigner. I have been designing since I left high school which will make it 7 years and counting. However, I can always recall as a kid all this crap about improving the accessible design  blah functions of this here device (x) or this here piece of software (x) when really I didn&#039;t see anything out that helped but really just generalized idea&#039;s and ideals that were suppose to be active by the year 2k and beyond again this was fueled by all your famous magazines, and other tech related shows we all have seen.

I for one wish I could have stuck it out to contine being a programmer but its not my forte even though I dabble in it. To me it seems that manufactor&#039;s need to 1) Get a group started 2) get user opinions 3) develop core commitment  to fixing the problem  4) Do user research / test and gather as much info as possible  5) Define a scope to go by 6) Implement  7) Test again and finally realease a set of software/hardware that work efficiently together to get the desired results.

Had I been born with genious of the developers of apple,mac,linux I would have already released my own OS, Browser, and UAC ( User Accessibility Core ) on my own. But alas, I only care about designing print/web data.

I do have something to point out. When I was a kid and was making crap pages for excite.com I recall dozens, hundreds of people running to make websites. I didn&#039;t recall but only a few people at that time that were impared that even cared about the web. I didn&#039;t know then to cater to the blind, death, diabled etc.

Funny, I went to our cpu lab and asked some of these people how do they use the computer when they have impairments.  Some say well &quot;if the gov. gives me my 10k grant money to get my new pc and screen reader software and magnification hardware I&#039;ll make it,&quot;. Some never were even that lucky some were lucky your school even cared about you.

I then thought about it but never realized how important it would be to me and others to get data accessible to other people. I currently read a book called &quot; Thinker Toys -A Handbook of Business Creativity for the 90&#039;s&quot; by: Michael Michalko. Which all of you should read but it is dated but its a good book.

I think if we can definately get a want to develop the right core set of tools and software for accessiblity then we can but at who&#039;s expense? BILL maybe?  Laws of physics say to get energy something has to be given. Who&#039;s gonna give this time for the good guys/gals?]]></description>
			<content:encoded><![CDATA[<p>Well I look at it like this, considering all the blame/pointing fingers and other abstract views of accessibility, the core of the topic is that there is a issue with accessiblity. This is a by product from the OS, Browser, and software/hardware manufactor&#8217;s lack of design, ability to hear a customers opinion and explain why or why not there isn&#8217;t such good accessiblity (x) on the market now, and the overall denying that people don&#8217;t want to cater to that &#8220;group&#8221; of users.</p>
<p>I for one am happy to be a webdesigner. I have been designing since I left high school which will make it 7 years and counting. However, I can always recall as a kid all this crap about improving the accessible design  blah functions of this here device (x) or this here piece of software (x) when really I didn&#8217;t see anything out that helped but really just generalized idea&#8217;s and ideals that were suppose to be active by the year 2k and beyond again this was fueled by all your famous magazines, and other tech related shows we all have seen.</p>
<p>I for one wish I could have stuck it out to contine being a programmer but its not my forte even though I dabble in it. To me it seems that manufactor&#8217;s need to 1) Get a group started 2) get user opinions 3) develop core commitment  to fixing the problem  4) Do user research / test and gather as much info as possible  5) Define a scope to go by 6) Implement  7) Test again and finally realease a set of software/hardware that work efficiently together to get the desired results.</p>
<p>Had I been born with genious of the developers of apple,mac,linux I would have already released my own OS, Browser, and UAC ( User Accessibility Core ) on my own. But alas, I only care about designing print/web data.</p>
<p>I do have something to point out. When I was a kid and was making crap pages for excite.com I recall dozens, hundreds of people running to make websites. I didn&#8217;t recall but only a few people at that time that were impared that even cared about the web. I didn&#8217;t know then to cater to the blind, death, diabled etc.</p>
<p>Funny, I went to our cpu lab and asked some of these people how do they use the computer when they have impairments.  Some say well &#8220;if the gov. gives me my 10k grant money to get my new pc and screen reader software and magnification hardware I&#8217;ll make it,&#8221;. Some never were even that lucky some were lucky your school even cared about you.</p>
<p>I then thought about it but never realized how important it would be to me and others to get data accessible to other people. I currently read a book called &#8221; Thinker Toys -A Handbook of Business Creativity for the 90&#8217;s&#8221; by: Michael Michalko. Which all of you should read but it is dated but its a good book.</p>
<p>I think if we can definately get a want to develop the right core set of tools and software for accessiblity then we can but at who&#8217;s expense? BILL maybe?  Laws of physics say to get energy something has to be given. Who&#8217;s gonna give this time for the good guys/gals?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Faruk Ateş		</title>
		<link>https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles#comment-6701</link>

		<dc:creator><![CDATA[Faruk Ateş]]></dc:creator>
		<pubDate>Tue, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-6701</guid>

					<description><![CDATA[During his presentation at @media, Robin Christopherson of AbilityNet explained to us that the closest we (= non-disabled webdevelopers)  can get to doing a reasonably reliable form of accessibility testing is by grabbing the 30-minute trial of JAWS, turning off our monitor and doing a quick run through our page.

If we can navigate through it and find the content we were looking for, chances are big that an experienced JAWS (or other screenreader) user will be able to use the site very well. They know their screenreader much better than we do, they can use it much faster and more efficiently, so if &lt;em&gt;we&lt;/em&gt; can use a screenreader to access our site&#039;s content, they &lt;em&gt;definitely&lt;/em&gt; can.

It&#039;s just one rule of thumb to go by, mind you, but at least it&#039;s something.

Personally, I more or less did this a long time ago when I first tested my site using a screenreader. This was about 6 months ago, very shortly after actually launching my site. It was far from perfect, but it was a CSS-pure design. I didn&#039;t turn off my monitor, because I was too fascinated by watching JAWS move the cursor around on my screen. However, the overall experience did make me feel like things were much better with this method.

Robin Christopherson&#039;s presentation was an eye-opener to many people when it comes to true accessibility and the impact of inaccessible code to a blind web user. Along with Joe Clark, Ian Lloyd and Derek Featherstone&#039;s presentations, it pointed out two very important things:

1) true accessibility is nearly impossible, as there are too many factors and complications that we simply cannot tend to effectively considering today&#039;s technology
2) you can get very far nonetheless through some basic principles and best practices. CSS layouts do help with this

The subsidy idea for assistive technology producers is a great one. I&#039;d much rather see governments spend their time and money on that than on legislating accessibility for websites.

Damn, &lt;a href=&quot;http://www.stuffandnonsense.co.uk&quot; rel=&quot;nofollow&quot;&gt;Malarkey&lt;/a&gt; is gonna love me for saying that.]]></description>
			<content:encoded><![CDATA[<p>During his presentation at @media, Robin Christopherson of AbilityNet explained to us that the closest we (= non-disabled webdevelopers)  can get to doing a reasonably reliable form of accessibility testing is by grabbing the 30-minute trial of JAWS, turning off our monitor and doing a quick run through our page.</p>
<p>If we can navigate through it and find the content we were looking for, chances are big that an experienced JAWS (or other screenreader) user will be able to use the site very well. They know their screenreader much better than we do, they can use it much faster and more efficiently, so if <em>we</em> can use a screenreader to access our site&#8217;s content, they <em>definitely</em> can.</p>
<p>It&#8217;s just one rule of thumb to go by, mind you, but at least it&#8217;s something.</p>
<p>Personally, I more or less did this a long time ago when I first tested my site using a screenreader. This was about 6 months ago, very shortly after actually launching my site. It was far from perfect, but it was a CSS-pure design. I didn&#8217;t turn off my monitor, because I was too fascinated by watching JAWS move the cursor around on my screen. However, the overall experience did make me feel like things were much better with this method.</p>
<p>Robin Christopherson&#8217;s presentation was an eye-opener to many people when it comes to true accessibility and the impact of inaccessible code to a blind web user. Along with Joe Clark, Ian Lloyd and Derek Featherstone&#8217;s presentations, it pointed out two very important things:</p>
<p>1) true accessibility is nearly impossible, as there are too many factors and complications that we simply cannot tend to effectively considering today&#8217;s technology<br />
2) you can get very far nonetheless through some basic principles and best practices. CSS layouts do help with this</p>
<p>The subsidy idea for assistive technology producers is a great one. I&#8217;d much rather see governments spend their time and money on that than on legislating accessibility for websites.</p>
<p>Damn, <a href="http://www.stuffandnonsense.co.uk" rel="nofollow">Malarkey</a> is gonna love me for saying that.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Eric Meyer		</title>
		<link>https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles#comment-6702</link>

		<dc:creator><![CDATA[Eric Meyer]]></dc:creator>
		<pubDate>Tue, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-6702</guid>

					<description><![CDATA[Only one problem, Mike: you assume that&#039;s I&#039;m someone in the know.  I might be as much an observer as anyone else, right?]]></description>
			<content:encoded><![CDATA[<p>Only one problem, Mike: you assume that&#8217;s I&#8217;m someone in the know.  I might be as much an observer as anyone else, right?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Redesign &#124; Internet. Marketing. Environment.		</title>
		<link>https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles#comment-6711</link>

		<dc:creator><![CDATA[Redesign &#124; Internet. Marketing. Environment.]]></dc:creator>
		<pubDate>Tue, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-6711</guid>

					<description><![CDATA[&lt;strong&gt;Redesigning the Wheelchair&lt;/strong&gt;

When will a designer take on the challenge of making a wheelchair that looks great? Instead, everywhere you look, they are made of harsh looking metals and awkward moving parts. It&#039;s wonderful that people are trying to develop a...]]></description>
			<content:encoded><![CDATA[<p><strong>Redesigning the Wheelchair</strong></p>
<p>When will a designer take on the challenge of making a wheelchair that looks great? Instead, everywhere you look, they are made of harsh looking metals and awkward moving parts. It&#8217;s wonderful that people are trying to develop a&#8230;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Webler		</title>
		<link>https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles#comment-6709</link>

		<dc:creator><![CDATA[Webler]]></dc:creator>
		<pubDate>Tue, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-6709</guid>

					<description><![CDATA[&lt;strong&gt;Accessibility woes&lt;/strong&gt;

As Mike Davidson did point out, the buzz over what accessibility is or isn&#039;t has increased a lot over the last weeks.

Having been immersed in an Actionscript project for the better part of those days, I managed to miss the comments to the posts, and...]]></description>
			<content:encoded><![CDATA[<p><strong>Accessibility woes</strong></p>
<p>As Mike Davidson did point out, the buzz over what accessibility is or isn&#8217;t has increased a lot over the last weeks.</p>
<p>Having been immersed in an Actionscript project for the better part of those days, I managed to miss the comments to the posts, and&#8230;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: boagworld		</title>
		<link>https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles#comment-6710</link>

		<dc:creator><![CDATA[boagworld]]></dc:creator>
		<pubDate>Tue, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-6710</guid>

					<description><![CDATA[&lt;strong&gt;Accessibility Guidance planned&lt;/strong&gt;

It would appear that the Disability Rights Commission might be taking its first small steps towards introducing definitive guidelines in regards to web accessibility.]]></description>
			<content:encoded><![CDATA[<p><strong>Accessibility Guidance planned</strong></p>
<p>It would appear that the Disability Rights Commission might be taking its first small steps towards introducing definitive guidelines in regards to web accessibility.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jack		</title>
		<link>https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles#comment-6708</link>

		<dc:creator><![CDATA[Jack]]></dc:creator>
		<pubDate>Tue, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-6708</guid>

					<description><![CDATA[Is this going to be released in Australia sometime? And is it released yet do you have a set price? Look forward to the reply!! :)

Thankyou,

Jack A Dexter]]></description>
			<content:encoded><![CDATA[<p>Is this going to be released in Australia sometime? And is it released yet do you have a set price? Look forward to the reply!! :)</p>
<p>Thankyou,</p>
<p>Jack A Dexter</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Mr. Leveille's Computer Classes		</title>
		<link>https://mikeindustries.com/blog/archive/2005/06/the-accessibility-chronicles#comment-6712</link>

		<dc:creator><![CDATA[Mr. Leveille's Computer Classes]]></dc:creator>
		<pubDate>Tue, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-6712</guid>

					<description><![CDATA[&lt;strong&gt;Standards and Accessibility&lt;/strong&gt;

In my Web Design classes I typically try to convey to my students the importance of standards and accessibility when creating a web site: Standards because without a unified format for creating web pages, the web becomes a cluttered, ugly...
]]></description>
			<content:encoded><![CDATA[<p><strong>Standards and Accessibility</strong></p>
<p>In my Web Design classes I typically try to convey to my students the importance of standards and accessibility when creating a web site: Standards because without a unified format for creating web pages, the web becomes a cluttered, ugly&#8230;</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
