<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Killersites.com Web Design Forums]]></title>
		<link>http://www.killersites.com/forums/</link>
		<description><![CDATA[The most recent topics at Killersites.com Web Design Forums.]]></description>
		<lastBuildDate>Mon, 09 Mar 2009 22:49:21 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Understanding the effects of Cognitive Disorders (3 Parts)]]></title>
			<link>http://www.killersites.com/forums/topic/924/understanding-the-effects-of-cognitive-disorders-3-parts/new/posts/</link>
			<description><![CDATA[[b]Part 1 - Naturally occurring[/b]

On the baseline, cognitive disorders are about the brain and problems understanding things. So there is no easy fix like slapping an alt attribute in code, increasing color contrast and we will not understand something whether written or read in a screen reader, using flexible widths where the content paragraphs are to long can even cause more trouble for us even though free flexing sizes are considered accessible.

So there is no easy fix for cognitive disorders, no good techniques have emerged yet. So I will try to explain our lives to you per real life examples. I am lucky that my issues are more minor, also one our members at Killersites has been effected and allowed me to tell her story. What I hope to share with you is both light and extreme cognitive disabilities as well as natural occurring and accidental disabilities so you see that you may have no users like this today, but may tomorrow and smack dab in your target group. Then finally that it is not always about disabilities either.

I am 44, a professional web developer/analyst programmer and web accessibility advocate instructing employees of the state of Alaska. I have a physical disability not related to the web, I have been diagnosed as depressive (cognitive disorder) and although not yet official, unofficially I am listed as having Asperger Syndrome (a cognitive disorder and a sub-section or High form of Autism). Yet meeting me in person you would not tag me as traditionally Autistic or depressive. Asperger did not exist when I was a kid so I was likely diagnosed late. It is also possible that I have a lesser known version of ADHD.
So how do these react with the web?

Patience: I tend to grow more impatient than I used to. I am immediately turned off by long stretches of content. It is like a switch being thrown, I see the long length of text and something just drops in me, I cringe and maybe buckle down to read, but mostly just go back and try to find a different source. I just cannot face long text on a computer screen... but enjoy a nice long book.

I also tend to feel I don't have enough time, even though I may, so again long text turn me off.

Medication: I am on anti-depressants, Cholesterol lowering meds and pain killers for my physical pains. This cocktail, of which 2 make you drowsy, can really effect my surfing habbits. Being tired makes it hard to read and concentrate on technical issues. The meds and drowsiness make it hard for me to focus on a web site, especially those with smaller fonts, and result in headaches or closing my eyes to rest them and falling a sleep. Web design does effect this to a small extent, a boring site design is just marginally worse than and interesting one... but more the colors and font sizes directly effect me. Poor choices cause eye strain and can result in headaches (and that really for anyone).

Attention: As touched on above, the meds cause attention issues, but so does Asberger and ADHD. So when trying to concentrate on complicated issues... any distracting Gif or Flash animations just compound that. If I am having trouble comprehending the content, I easily switch to something easier... I have to fight to stay focused. I think that is why I hate the modern design concept of multiple boxes and almost all content of the site smashed onto the index page. It overwhelms me and gives to to much straying of my attention. I despise such sites as M$N and the others with links upon links and all trying to offer subjects I care nothing for like news, stocks, weather.

Motivation: This is a direct reflection of both the depression and the Meds. I am not motivated, I tire of things easily. I don't care. In the Killersites forum I used to help allot, less these days because I am not motivated to do so. Just as described above I shy away from complicated subjects that I will have to think about. It is to straining to do so. To repeatedly answer the same questions, repeatedly argue with people who do not care about those with disabilities, those who want to be told how good they are and not listen to criticism. I patrol for spam more than anything. My own Blog suffers from this as well, I do not feel motivated to write and even have to fight to write this. Now that I am one of those with disabilities, I find myself drifting away from web accessibility advocacy. I do not even go on my computer much these days... I just do not feel like it. If Google gives me lots of hits I cringe, in no mood for reading through pages and pages of useless info to find the gem.

Problem Solving: This is the biggest issue for me I guess and is made up of all above. Asperger and depression both affect problem solving skills. I of course am now a programmer... wonderful. Programming is in fact problem solving. "This is what I need, who do I do it?", "This is what someone wrote, what were they thinking, what does it do, why is it broken and how to I fix it?", I earn my living doing exactly that which comes hardest to me these days. When I started in the Killersites Forums I helped people with problems, but now I cannot break down other peoples code to find the mistake... I give tips and hints at what to look for and hope the other regulars can figure it out. I feel headaches coming on as soon as I see a complicated issue before me.

I have just touched on a few items here, both to keep it short and because I have lost my train of thought... my concentration... what my point was to be. My conditions are minor... for those who are full fledged Autistic, these issues are multiplied!

So I would like to mention one of my favorite projects: Zac Browser (Zone for Autistic Children). It is the brain child of a Software Engineer who's grandson Zack is Autistic and was overwhelmed by to many buttons and actions in modern browsers. He created a browser for Autistic children with very few, large buttons using images that make their use clear and the browser has web sites embedded in it that are clean and built for children so Zack will be fairly focused and not torn between multiple decisions. I have played with it and find it excellent. Any one with children should have a go with it.

If I have raised your awareness to the issues and you are interested in more, I offer you these reference points:
[list=*]
[*]Job Accommodation Network (JAN) - [url=http://www.jan.wvu.edu/media/atoz.htm]Disabilities A-Z[/url]. Explanations on how to accommodate employees with given disabilities.[/*]
[*]JAN - [url=http://www.jan.wvu.edu/media/asperger.html]Asperger Syndrome[/url]
          "People with Asperger Syndrome can excessively elaborate on their own topics of interest, however, be unable or unwilling to participate in other parts of conversation or to end a conversation, partially because of the inability to gauge social context or interpret social cues (Klin et al., 2000)."
      [i]- My regular readers should recognize this :D.[/i][/*]
[*]JAN - [url=http://www.jan.wvu.edu/media/depr.htm]Depression[/url][/*]
[*]JAN - [url=http://www.jan.wvu.edu/media/lear.htm]Attention Deficit Disorder[/url] (Learning Disabilities)[/*]
[*]JAN also discusses other cognitive disorders that can affect use of the web. Consider Anxiety Disorders, Cognitive Impairments, Bipolar Disorders, Epilepsy, Migraine Headaches... as well as some web related physical disabilities.[/*]
[/list]]]></description>
			<author><![CDATA[dummy@example.com (LSW)]]></author>
			<pubDate>Mon, 09 Mar 2009 22:49:21 +0000</pubDate>
			<guid>http://www.killersites.com/forums/topic/924/understanding-the-effects-of-cognitive-disorders-3-parts/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[Survey of Preferences of Screen Readers Users]]></title>
			<link>http://www.killersites.com/forums/topic/584/survey-of-preferences-of-screen-readers-users/new/posts/</link>
			<description><![CDATA[WebAIM has done a [url=http://webaim.org/projects/screenreadersurvey/]Survey of Preferences of Screen Readers Users[/url] that may be of interest to some of you.]]></description>
			<author><![CDATA[dummy@example.com (LSW)]]></author>
			<pubDate>Mon, 02 Feb 2009 22:02:13 +0000</pubDate>
			<guid>http://www.killersites.com/forums/topic/584/survey-of-preferences-of-screen-readers-users/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[Disability does not mean permanent]]></title>
			<link>http://www.killersites.com/forums/topic/383/disability-does-not-mean-permanent/new/posts/</link>
			<description><![CDATA[Usually when people speak of disabilities and web accessibility, they talk of permanent problems surfing. This is not always the case.

About a year ago a member here had his PC die. For a while he was stuck surfing the web with his Wii. It was a wake up call and he said he would pay more attention to accessibility. It was temporary and bad from what he said.

Another example is myself. Not a speed typer, I am typing with one finger. It is raining here on packed snow, I slipped and broke my collar bone last night. So one arm is strapped to my chest and hurts like the devil, leaving me one finger and hand to type with. Luckily it was my left shoulder, so I can use the mouse still.

See, accessibility is not just about a minor group, it is about everyone and you can loose you PC or break a bone... what will you do then if most sites are inaccessible? Just do what you can and hope that others do the same.]]></description>
			<author><![CDATA[dummy@example.com (LSW)]]></author>
			<pubDate>Wed, 14 Jan 2009 21:39:53 +0000</pubDate>
			<guid>http://www.killersites.com/forums/topic/383/disability-does-not-mean-permanent/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[Notice Concerning The Americans With Disabilities Act (ADA) Amendments]]></title>
			<link>http://www.killersites.com/forums/topic/382/notice-concerning-the-americans-with-disabilities-act-ada-amendments/new/posts/</link>
			<description><![CDATA[On Sep. 25th 2008, President Bush signed an Ammendment to the Americans with Disabilities Act (ADA) that effectively redefines what is to be considered a disability.

[quote][b]Notice Concerning The Americans With Disabilities Act (ADA) Amendments Act Of 2008[/b]

On September 25, 2008, the President signed the Americans with Disabilities Act Amendments Act of 2008 ("ADA Amendments Act" or "Act"). The Act makes important changes to the definition of the term "disability" by rejecting the holdings in several Supreme Court decisions and portions of EEOC's ADA regulations. The Act retains the ADA's basic definition of "disability" as an impairment that substantially limits one or more major life activities, a record of such an impairment, or being regarded as having such an impairment. However, it changes the way that these statutory terms should be interpreted in several ways. Most significantly, the Act:

    * directs EEOC to revise that portion of its regulations defining the term "substantially limits";
    * expands the definition of "major life activities" by including two non-exhaustive lists:
          - the first list includes many activities that the EEOC has recognized (e.g., walking) as well as activities that EEOC has not specifically recognized (e.g., reading, bending, and communicating);
          - the second list includes major bodily functions (e.g., "functions of the immune system, normal cell growth, digestive, bowel, bladder, neurological, brain, respiratory, circulatory, endocrine, and reproductive functions");
    * states that mitigating measures other than "ordinary eyeglasses or contact lenses" shall not be considered in assessing whether an individual has a disability;
    * clarifies that an impairment that is episodic or in remission is a disability if it would substantially limit a major life activity when active;
    * provides that an individual subjected to an action prohibited by the ADA (e.g., failure to hire) because of an actual or perceived impairment will meet the "regarded as" definition of disability, unless the impairment is transitory and minor;
    * provides that individuals covered only under the "regarded as" prong are not entitled to reasonable accommodation; and
    * emphasizes that the definition of "disability" should be interpreted broadly.

EEOC will be evaluating the impact of these changes on its enforcement guidances and other publications addressing the ADA.

Effective Date:

The ADA Amendments Act is effective as of January 1, 2009.
[url=http://www.eeoc.gov/ada/amendments_notice.html]http://www.eeoc.gov/ada/amendments_notice.html[/url][/quote]

This can be very important to anyone with disabilities so please pass it on. This could overturn the VA's rejection of my request for reevaluation. It may also redefine disabilities for web design.]]></description>
			<author><![CDATA[dummy@example.com (LSW)]]></author>
			<pubDate>Wed, 14 Jan 2009 20:54:34 +0000</pubDate>
			<guid>http://www.killersites.com/forums/topic/382/notice-concerning-the-americans-with-disabilities-act-ada-amendments/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA["Colorblind" tools list]]></title>
			<link>http://www.killersites.com/forums/topic/216/colorblind-tools-list/new/posts/</link>
			<description><![CDATA[Similar  thread was a while ago in old forum but could be  quite useful to have another good list of color tools:

[url]http://www.colblindor.com/2008/12/23/15-tools-color-blindness/[/url]]]></description>
			<author><![CDATA[dummy@example.com (lm)]]></author>
			<pubDate>Wed, 14 Jan 2009 18:55:06 +0000</pubDate>
			<guid>http://www.killersites.com/forums/topic/216/colorblind-tools-list/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[GrayBit - Accessibility testing tool that displays a full-color Web...]]></title>
			<link>http://www.killersites.com/forums/topic/221/graybit-accessibility-testing-tool-that-displays-a-fullcolor-web/new/posts/</link>
			<description><![CDATA[[url=http://graybit.com/main.php]GrayBit[/url] - Accessibility testing tool that displays a full-color Web page in grayscale.

Look how [url=http://graybit.com/files/graybit.php?url=http%3A%2F%2Fwww.visibilityinherit.com%2Findex.php]good my site does[/url]! I always new I was Accessible at heart :lol: :lol:]]></description>
			<author><![CDATA[dummy@example.com (LSW)]]></author>
			<pubDate>Tue, 13 Jan 2009 17:08:52 +0000</pubDate>
			<guid>http://www.killersites.com/forums/topic/221/graybit-accessibility-testing-tool-that-displays-a-fullcolor-web/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[Accessibility in an internal environment]]></title>
			<link>http://www.killersites.com/forums/topic/306/accessibility-in-an-internal-environment/new/posts/</link>
			<description><![CDATA[I'm trying to move accessibility and usability into the forefront with our IT department, and have received quite a bit of pushback.

Can anyone cite litigation that resulted in disabled users being unable to access company information?]]></description>
			<author><![CDATA[dummy@example.com (LSW)]]></author>
			<pubDate>Thu, 08 Jan 2009 00:18:34 +0000</pubDate>
			<guid>http://www.killersites.com/forums/topic/306/accessibility-in-an-internal-environment/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[Google shows interest in Accessibility... so should you.]]></title>
			<link>http://www.killersites.com/forums/topic/38/google-shows-interest-in-accessibility-so-should-you/new/posts/</link>
			<description><![CDATA[Here are some reading material to show how Google is now getting interested in accessibility... so it is about time developers do to.

[list=*]
[*][url=http://googlewebmastercentral.blogspot.com/2008/09/workin-it-on-all-browsers.html]Workin' it on all browsers[/url]
To web surfers, Google Chrome is a quick, exciting new browser. As webmasters, it's a good reminder that regardless of the browser your visitors use to access your site "Firefox, Internet Explorer, Google Chrome, Safari, etc." browser compatibility is often a high priority. When your site renders poorly or is difficult to use on many browsers you risk losing your visitors' interest, and, if you're running a monetized site, perhaps their business.[/*]
[*][url=http://google.com/support/webmasters/bin/answer.py?answer=100782]Making sure your site appears properly in different browsers[/url].
Users typically view your website using a browser. Each browser interprets your website code in a slightly different manner, which means that it may appear differently to visitors using different browsers. In general, you should avoid relying on browser specific behavior, such as relying on a browser to correctly detect a content-type or encoding when you did not specify one. In addition, there are some steps you can take to make sure your site doesn't behave in unexpected ways.[/*]
[*][url=http://labs.google.com/accessible/]Google Accessible Search[/url].
Accessible Web Search for the Visually Impaired[/*]
[*][url=http://www.456bereastreet.com/archive/200607/google_accessible_search_rewards_accessibility/]Google Accessible Search rewards accessibility[/url].
Google Accessible Search is a new Google product that is under development. It is designed to prioritize search results that are more usable to blind and visually impaired people. - 456BereraStreet.com[/*]
[*][url=http://www.456bereastreet.com/archive/200609/google_meet_web_standards/]Google, meet Web Standards[/url].
The intention was, of course, to make the code used for the GSA's search interface conform to Web standards, be accessible, and work in all devices. Joe asked me if I would be interested in taking a look and suggest improvements. You can?t really say no to a request like that, can you?[/*]
[*][url=http://www.joesapt.net/2006/09/22/10.00.00/]Google Goes To Web Standardsville, Part Two[/url].
(HTML). This stylesheet has been revised and improved by Google countless times over the years and has its roots, of course, in Google.com.[/*]
[/list]]]></description>
			<author><![CDATA[dummy@example.com (LSW)]]></author>
			<pubDate>Mon, 22 Dec 2008 17:45:20 +0000</pubDate>
			<guid>http://www.killersites.com/forums/topic/38/google-shows-interest-in-accessibility-so-should-you/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[Cognitive disorders or just the new reality?]]></title>
			<link>http://www.killersites.com/forums/topic/39/cognitive-disorders-or-just-the-new-reality/new/posts/</link>
			<description><![CDATA[[Note: For those who have not followed the subject, I recently wrote a pair of articles,  "[url=http://www.lsw-webdesign.com/2008/05/27/understanding-and-the-cognitive-disorder/]Understanding and the Cognitive Disorder[/url] " and "[url=http://www.lsw-webdesign.com/2008/07/10/from-the-inside-depression-the-cognitive-disorder/]From the inside: Depression & the Cognitive Disorder[/url]."] 

We are all just human and we do what humans do, one of those things is to get so involved in things that we loose site of the larger picture. Accessibility advocates are no different and from time to time we have to be reminded that accessibility is not just about disabled persons, accessibility is about everyone.

I recently posted a thread about my above linked depression article over at Accessify forum where it was well taken. A member going by the name of "atu" posted some links on the subject of concentration loss and distraction in modern society. This is not directly related to web design exactly, but the articles are quite interesting and make you think and that is what web design is all about. 

If in fact the "Web" is dumbing people down, then it is something we need to take into consideration in our designs. I would like to say we need to fight this new reality. But truth be told we are part of the problem, we build the sites that cause these issues and our customers pay us to do just that. So help fight it where you can, but before it can be fixed it must be recognized and these articles may be to early to truly prove a problem, but they certainly are a dire warning and worth reading. As usual, we must be aware of what is happening to our users.

[url=http://www.theatlantic.com/doc/200807/google]Is Google Making Us Stupid?[/url] by Nicholas Carr

[url=http://www.theatlantic.com/doc/200711/multitasking]The Autumn of the Multitaskers[/url] by Walter Kirn

[url=http://technology.timesonline.co.uk/tol/news/tech_and_web/the_web/article4362950.ece]Stoooopid .... why the Google generation isn?t as smart as it thinks[/url]  by Bryan Appleyard

[url=http://encarta.msn.com/encnet/features/Columns/?Article=imshorthandmain]Does IM Make U Dum?[/url] by Martha Brockenbrough (one of my all time favorites from a few years ago)]]></description>
			<author><![CDATA[dummy@example.com (LSW)]]></author>
			<pubDate>Mon, 22 Dec 2008 17:44:42 +0000</pubDate>
			<guid>http://www.killersites.com/forums/topic/39/cognitive-disorders-or-just-the-new-reality/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[Understanding and the Cognitive Disorder]]></title>
			<link>http://www.killersites.com/forums/topic/40/understanding-and-the-cognitive-disorder/new/posts/</link>
			<description><![CDATA[As developers interested in accessibility, we use tools to aid us. Whether these be assistive technologies or tools of the language like alt attributes. But the problem with cognitive disorders is they are not something you can nail down, it is about the inability to understand content, not the inability to access it. No real tools here for us and no way to really simulate it. It is hard to really even understand it as it is all about not understanding.

So we have to deal with something we cannot really understand and help people with this problem to better handle our web sites. My eye opener after 7 years of accessible design was just a few weeks ago. I had just listened to a web cast on the subject when I was asked to come up with examples for accessible tables. I did all the right things, with an eye on WCAG 2 that will likely go final in the next year. So although using all the tricks and tools available I built a table that is by all normal standards... but is it understandable for cognitive disorders? I don't know, but accessibility is about choice and alternatives. We offer those with disabilities or other wishes to access our information in alternative manners.

So in theory it is quite possible that someone with a cognitive problem may not find such data tables to be understood, so even here maybe we should do that little extra work to give them a choice.

Ok, being a top designer you have created a table, you use TH for column or row headers, you may have used scope or IDs, you have a perfect coded table explaining what menu is served which day and all is easy to understand at first sight, your are finished. But is it the most understandable form for all people?

Then consider this. If your table is dynamic you can draw the same info from the database and show it in multiple forms. So you could take a simple table showing days of the week and the menu needed for it in a textual format that someone may find easier to understand.

[code]<table border="1" summary="This table showing our lunch service gives the three lunch courses (column headings)"> 
  <caption>Today's Lunch Menu</caption>   
  <thead>
      <tr>
        <td colspan="3">The following information is based on the preferences we have seen based on 3 years
of lunch statistics showing the most often ordered food on this day historically.</td>
    </tr>
  </thead>
  
  <tfoot>
      <tr>
        <td colspan="3">This information was collected by Joe Blow, please contact Mike if you have any questions.</td>
      </tr>
  </tfoot>

  <tbody>
    <tr>
      <th scope="col">Salad</th> 
      <th scope="col">Meal</th>
      <th scope="col">Dessert</th>
    </tr>
    <tr>
      <td>Caesar</td>
      <td>T-bone Steak</td>
      <td>Pineapple Upside down Cake</td>
    </tr>
  </tbody>
</table>[/code]

OK now, the above is a proper accessible table that uses best practices and should be usable for the normal disabled users. But is it clear for someone with a cognitive disorder? Maybe, maybe not, we have no way to know until they complain... if they complain.

So maybe plain text would be better for some people and is not all that hard as long as it changes daily. Imagine a simple text paragraph with a feed from the database, the same data as in the table (Indicated by {}).

[quote][b]Today's Lunch Menu[/b]
Today we will be serving {Caesar} Salad, {T-bone Steak} and {Pineapple Upside down Cake} as dessert.

This information is based on the preferences we have seen based on 3 years of lunch statistics showing the most often ordered food on this day historically. The information was collected by Joe Blow.  Please contact Mike if you have any questions.[/quote]

So as you see, this simple paragraph style is not as clear at a quick glance, but could be more understandable than a table to some forms of Cognitive Disorders. If both paragraph and table draw from a database, the entries are automatically updated and need not be manually changed. Both versions can be offered on the same page with a heading that allows choice, a screen reader user may find the second preferable to the table as well and choose to skip the table and listen to the paragraph.

So unlike normal accessibility tricks, I cannot say that this is a better way for any number of people. What I would like you to consider is simply that accessibility is about offering choices to allow alternative methods for those with special needs are simply other preferences, to access information in another manner. So when it works, data type info in a data table as well as plain text. Offer an RTF document & a PDF version, offer multiple style sheets, offer two forms of navigation, offer alternative text to images. Just always try to ask yourself if this is not the best format for the user to read information, what can you do to offer an alternative form, give the user a choice to what best suites them.

WebAIM has a good article on the subject of Cognitive disorders: [url=http://www.webaim.org/articles/cognitive/]Cognitive Disabilities[/url].]]></description>
			<author><![CDATA[dummy@example.com (LSW)]]></author>
			<pubDate>Mon, 22 Dec 2008 17:43:01 +0000</pubDate>
			<guid>http://www.killersites.com/forums/topic/40/understanding-and-the-cognitive-disorder/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[From the mouth of the users  [May 2008]]]></title>
			<link>http://www.killersites.com/forums/topic/41/from-the-mouth-of-the-users-may-2008/new/posts/</link>
			<description><![CDATA[It is my hope to find and place articles here that will give you an idea of how those with disabilities "see" and use the web site. So here is the first and I hope to have more to follow.
[list=*]
[*][url=http://www.accessiblecontent.com/online/v1n1/index.php?view=max]Surfing Blind[/url]  by Max Robinson (on visual Impairment)[/*]
[*][url=http://www.accessiblecontent.com/online/v1n3/index.php?view=uhlw]Staying Focused[/url]  By Stephanie May (on Text - to - Speech)[/*]
[*][url=http://www.accessiblecontent.com/online/v2n1/index.php?view=uglw]Multiple Technologies Clear Obstacles[/url]  By Jonathan Avila (on being legally blind, while having usable vision)[/*]
[*][url=http://www.nomensa.com/resources/articles/accessibility-articles/a-christmas-tale.html]A Christmas tale about accessible shopping[/url]  by Léonie Watson is Nomensa's Head of Accessibility and visually impaired.[/*]
[*][url=http://www.webaim.org]WebAIM[/url]  offers an article called "[url=http://www.webaim.org/intro/#people]Introduction to Web Accessibility[/url] " that includes two videos where people with disabilities are interviewed on camera. The first, "Keeping Web Accessibility in Mind," is a bit long and about accessibility in general. The second, "Experiences of Students with Disabilities," is shorter and exclusively interviews.[/*]
[/list]

[b]Videos[/b]
[list=*]
[*][url=http://www.assistiveware.com/videos.php]AssistiveWare offers videos[/url]  of some of the most extreme uses of assistive technologies. Mike, who suffers spinal muscular atrophy plays many video games including first person shooters using a Mac. A woman with ALS controlling her computer with a switch taped to her cheek. A woman with cerebral palsy who uses her computer to do graphic design work. These videos are well worth watching.[/*]
[*][url=http://www.youtube.com/watch?v=9-ivQDrn0wk&feature=related]Blind Computing - How do we do it?[/url] - Cathy Anne, Created a YouTube Video to show how Screen Readers work. 6 min.[/*]
[*][url=http://www.youtube.com/watch?v=bQpNYDvQ010&feature=related]Web Accessibility - through the "eyes" of a screen reader[/url] - YouTube video highlighting the importance of Skip Links descriptive links rather than "click here". 3 min.[/*]
[*][url=http://www.youtube.com/watch?v=SpmB2DLrkTE]WebAnywhere: A Screen Reader On-the-Go[/url] - YouTube video of a brief by Jeff Bingham of Washington Sate University. This is technically a brief to Google employees about a project for a faux screen reader they have developed. It is long, but the beginning at least has some very good info and statistics for the first half.[/*]
[/list] 

If these people can do these things... imagine what they can do with a simple accessible web site.

After seeing these... I really do not want to here developers saying that accessibility is to hard and not enough people benefit from it.]]></description>
			<author><![CDATA[dummy@example.com (LSW)]]></author>
			<pubDate>Mon, 22 Dec 2008 17:42:00 +0000</pubDate>
			<guid>http://www.killersites.com/forums/topic/41/from-the-mouth-of-the-users-may-2008/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[Screen reader & AT issues]]></title>
			<link>http://www.killersites.com/forums/topic/42/screen-reader-at-issues/new/posts/</link>
			<description><![CDATA[21/22 May 2008 I was an instructor at the State of Alaska's first web accessibility Training at the University of Alaska Anchorage.

It was an eye opener.

I have been preaching accessibility for 8 years, most all in theory. But for the first time I was able to watch and speak with a Blind user and the instructor who teaches blind users how to use software such as JAWS. Here are some points worth mentioning.
[list=*]
[*]alt attributes - to a screen reader, it makes no difference if you use alt="" or alt=" ", it means the same, just be sure to use it.[/*]
[*]Headers (H1 - H6) are of major importance. Not just semantics, but headers can be and are used all the time by screen reader users to navigate. A structured layout with headers is more efficient for users than a skip link (but please keep offering those too).[/*]
[*]Lists - not only are lists a semantically correct form for a menu, and allow us to easily format menus with rollover, focus and hover effects... but lists are the next best for navigation as the screen reader can skip from one list to another navigating the site and the list is announced as being a list with 7 items and then the items are read off. Always use lists for listed items and menus, never use code to make a faux list with bullet symbols as this takes away it usefulness for everyone.[/*]
[*]Real screen reader users do so with an amazing speed, I could hardly follow what he was doing at default speed. when he upped it to his normal speed he uses it sounded like some alien in a cartoon played at high speed, I understood nothing.[/*]
[*]Screen readers can have other voices downloaded for a price, some as worthless as Wing Dings, "Bob in a hallway," sound like bob in a tin can. Many screen reader users have many voice files and dictate which are used where like on a cell phone. A female may read the site, but a form may be read by a male voice so it indicates aside from the announcements what they are doing.[/*]
[*]Refreshable Brail user agents are far more common then I had thought, many blind really prefer them. A 32 character display like we were shown costs around $5,000, it will display half an average sentence. 64 character ones will do a whole sentence, smaller are available that cover just a web words, but are more mobile.[/*]
[*]There are portable screen readers about the size of an old walkman. These can be hung around the neck and plugged into any computer and offer earphones for the user. They can be uses without earphones when plugged into the speakers directly. [url=http://www.enablemart.com/Catalog/Screen-Readers/Icon-Mobile-Manager]Icon[/url] was used by the demonstrator.[/*]
[*]Programs like JAWS can be used with JavaScript/Ajax, but with extreme care. Always use DOM and change the DOM on the page on the fly so that the page reflects the current status.[/*]
[*]Never set a drop down so that it automatically goes to the focus/highlighted target, Jaws will always go directly to the very first link as that will always be the first with focus and the user is stuck.[/*]
[*]Always handle forms with either immediate error handling on the field they are in, or if error handling is later after the form is sent off, the error message must always be the top of the page, otherwise it goes back to the page and starts reading the whole form again and the user does not know why. With the error message topside it is read first "I have found the following errors: Format incorrect in date field", the error statement where the error is can then link to take the user directly to that field rather than have to tab all the way through for each.[/*]
[*]If you use Ajax for a page and it constantly refreshes, it interrupts the user. If you type into Goggle search bar and that triggers a list of possible searches, the screen reader will begin to read those, when you add the next letter and the list refreshes, the screen reader starts again at the top, breaking it off where it was in mid word and starting again... fast tippers will get allot of syllables. So be aware of this.[/*]
[*]Any time the page itself is refreshed the screen reader will start again at the top, so dom changes should be in the page so the reader starts where you changed the content and not all the way at the top every time.[/*]
[*]Forcing new windows will not cause a new instance of the screen reader so two are reading, not in the new generations. However by opening a new window or tab, it steals the focus and the screen reader will stop reading the current content, and begin reading the new content before the old is finished. Allowing the user to choose a new tab gives them control with the reader over what they want to hear.[/*]
[*]Screen readers have two pointers. A visual pointer you can see and move with your mouse and a virtual pointer that is controlled by the keyboard that is what the blind use. When testing, disconnect your mouse or you can get lost of the virtual pointer is at one place and the mouse pointer at another.[/*]
[*]Test with a Demo. [url=http://www.freedomscientific.com/fs_downloads/jaws.asp]JAWS has a demo[/url]  that is good for 30 minutes after you boot your computer (it reads everything, OS actions and browser/software actions). You are sighted and will not use it like a blind user will, so it does not mean it is accessible, but turn of your monitor when you can, close your eyes if you can't and unplug the mouse so you use only the keyboard. This will not only give you an idea of the difficulties, but you will hear where you misspelled words, where you have made mistakes, where your text is not as clear as you thought (faux proof reading. your eyes know what you wanted to write, your ears will hear the truth). It is worth testing and even practicing... but remember that you do not use it like a longtime blind user.[/*]
[*]You can have a look at a sampling of available Assistive Technology and their prices at [url=http://www.enablemart.com/]www.Enablemart.com[/url][/*]
[/list]]]></description>
			<author><![CDATA[dummy@example.com (LSW)]]></author>
			<pubDate>Mon, 22 Dec 2008 17:40:48 +0000</pubDate>
			<guid>http://www.killersites.com/forums/topic/42/screen-reader-at-issues/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[Browsers, what to test in]]></title>
			<link>http://www.killersites.com/forums/topic/43/browsers-what-to-test-in/new/posts/</link>
			<description><![CDATA[During some recent accessibility training I was asked what browsers should be tested in and while explaining I discovered that many people do not know how browsers tie together, what ones are for what Operating Systems and what are even common. So here is a explanation of the big 4 and what to watch for in the future.
[list=*]
[*][url=http://www.mozilla.com/en-US/firefox/]Firefox[/url]  - Firefox is the second growing browser, on many sites I run it has in fact taken over the lead spot in statistics. Basically Firefox runs the same on Linux and Mac as it does on windows, so if the site works in windows it will on the others as well, it is the most used browser in Mac and Linux. It is standards compliant.
     At one time Netscape was the lead browser, it's code name was Mozilla. Later Mozilla broke away and became it's own project and the Mozilla suite was the basis of Netscape 6. Mozilla began powering Netscape and Mozilla became it's own browser as well. Then they decided that rather than have a bloated app with email, chat and what all else in, they would break each out into it's own module. This gave birth to Firefox Browser, Thunderbird email client and Sunbird Calendar as a few examples. With the final release of Firefox, Mozilla was retired. However Mozilla lives on due to the work of some fans and with Mozilla's support they are continuing to improve it and it is called [url=http://www.seamonkey-project.org/doc/features]Seamonkey[/url]  now.
     Gecko is the rendering engine. If you test in Firefox, you can be sure it will work just as well in any gecko client, so Netscape (now retired), Mozilla/Seamonkey and Camino (Mac only).[/*]
[*][url=http://www.opera.com/]Opera[/url]  - Opera has or had a cult following as it was the fastest browser on the market at one time, however i was privately funded and needed to be purchased. It has been free now for a few years still ignored, i will do a separate article on why you should check out Opera. But it has the easiest internal style switching available, first to incorporate a zoom mechanism, first to include spatial navigation, first to include voice command, first to include a mobile view for testing, first to offer a speed dial screen in new tabs... it has been unduly ignored. Opera is standards compliant but does show some things slightly different than other browsers. Opera was also the first browser to pass Acid 3.
     Opera is not just a interesting alternative browser, it is the only commercial browser available for mobile use. There is a Firefox version being developed for mobile user agents but Opera has been in use for years along with a lesser known mobile only browser. By testing in Opera with Opera's specialized tools will help insure it is working well for users, opera is also used on many cell phones as well as the Wii when surfing, so odds are good the web site will work better in those tools as well.[/*]
[*][url=http://www.apple.com/safari/download/]Safari[/url]  - Safari has been around for years and is the Mac in house browser. It is well used in the community but still falls behind Firefox in statistics of Mac users. Safari is standards compliant.
     There is now a version of Safari for Windows. Windows users can now install Safari 3 beta on a windows machine and test. There are some oddities between Safari Mac and Safari Windows, more to do with the presentation of Text. But for the most art if it works in one it will work in the other. The presentation may differ slightly, but the functionality is close enough to be sure the site can be used on Mac.[/*]
[*][url=http://www.microsoft.com/windows/downloads/ie/getitnow.mspx]IE[/url]  - Well what is to be said here, we all pretty well realize the quirks of IE. IE has never been standards friendly. The IE team has spent years trying to create their own standards even thought Microsoft is part of the W3C. IE 6 does not support Standards, IE 7 supports standards somewhat, IE 8 is supposed to support Standards when released. IE7 only works on XP SP2, SP3 and Vista. IE8 will I believe only work on Vista and later. IE6 will work on XP SP1 and anything before. As long as people are unwilling to upgrade, IE6 will be around like a zombie, dead but still attacking & eating our web sites. IE5.5 and below do not even register on most statistics or ring in at less than 1%. They are dead, we have to draw a line somewhere. IE support for Mac ended with IE5.2 and IE no longer supports Mac and never supported Linux.
     So IE does it's own thing. What do we do about it? Well traditionally hacks, but hacks are using a browser weakness to do something, if the weakness is then corrected as with IE7, many sites designed with hacks for IE6 broke. So stay away from hacks. Conditional Comments are the way to go. They were created by Microsoft and allow you to pick and choose versions. They are a form of CData comments and If loops. If IE6 do this, if IE7 do that. These are ignored by all other browsers. So it is a form of IE specific sniffing. You can for instance either load different style sheets or just specific commands to overwrite styles in a style sheet. IF IE6, use this H! style rather than the default style... sort of thing.
     IE8 is a whole new ball game. IE8 was to launch a poorly thought out plan that was flamed in designer communities. This idea has been named Version Targeting. The idea is simple, a meta tag in the header of every page will tell IE what version of the browser the web site is meant for. IE8 can then choose from multiple rendering engines to show the site as it should be. So you may now be lazy and never update your site, just add the meta and tell it to render as IE6. I am sure laziness will overcome, but it is good for older sites that may have archived material, you need not rewrite everything, just say that that page was written for IE5 years ago and it should render as IE5, that is good, but using it as an excuse not to update a active site is laziness. Another problem is the size, IE8 will have to include multiple rendering engines to render old pages as old browsers... so each version of IE will be more bloated as it's rendering engine is included with all the others. It was poorly thought out because the default was to be IE6, why should IE8 default to IE6? Why should those of us not wishing to use it have to use it to say we do not wish to use it (by telling it to act like what it is IE8). They finally saw the light and have announced that IE8 will default to IE8 standards mode, and you must add the meta tag for anything else. IE8 will still not support XHTML, so there will still be no reason to use it.[/*]
[*][url=http://www.freedomscientific.com/fs_downloads/jaws.asp]JAWS[/url]  - JAWS is the most common screen reader and hails from Freedom Scientific. It is expensive so you won't be buying one, but the demo version runs for the first 30 minutes after booting your machine and it is not just a browser (actually piggy backs on the browser), it will read anything you do on your operating system as well. Now you can listen to your site, test it in a manner as well. Just remember that yu will not use it as a sighted person the same manner a blind person will. It has a visual pointer that you can move with the mouse and a virtual pointer. It can get problematic if you try to test as a blind user while using the mouse to point at things. So if you are going to use it, use it right. Unplug the mouse and turn off the monitor if you can, close your eyes or sue a blindfold if you can not. Then test your site. It will help you find structural problems, missing alt attributes and even misspellings. Then if you can, get a hold of a Assistive Technologies organization and have them test the site out using real users with disabilities.[/*]
[*][url=http://www.google.com/chrome]Google Chrome[/url] - Not yet a contender, but it may become one, especially in mobile units. I personally like this light and simple app and do use t often, but not as my primary browser.[/*]
[/list]]]></description>
			<author><![CDATA[dummy@example.com (LSW)]]></author>
			<pubDate>Mon, 22 Dec 2008 17:40:15 +0000</pubDate>
			<guid>http://www.killersites.com/forums/topic/43/browsers-what-to-test-in/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[Funhouse mirrors and the Address tag]]></title>
			<link>http://www.killersites.com/forums/topic/45/funhouse-mirrors-and-the-address-tag/new/posts/</link>
			<description><![CDATA[The W3C are known for being vague, often due to trying to please everyone. This vagueness has caused issues in the past as developers understood the specs differently, a good example is IE's showing of the alt attribute as a tooltip and all others browsers understanding it to be only visible when the image is not.

I have seen references before to the <address> tag and like all beginners did not look into it as it is clear isn't it? You use it to create addresses. Well this is the web and the W3C and not everything is what it seems.

Here are two authorities on the subject:
[quote]The ADDRESS element may be used by authors to supply contact information for a document or a major part of a document such as a form. This element often appears at the beginning or end of a document.
- W3C[/quote]

[quote]The <address> tag defines contact information for a document or a section.

[b]Note:[/b] The <address> tag should NOT be used as describing a postal address, unless it is a part of the contact information.
- W3Schools.com[/quote]

For me this is fairly clear, but not what I thought as a beginner. The address tag is not for addresses, it is for contact information about the author. If I post this in an ezine for instance, the author information about me with my email and or URL would be the address. I am the contact person and not the newsletter that posts this. KillerSites is not the contact when I post it on their forum. If you have questions, you contact me.

So if you use it for a street or postal address you are clearly wrong.

Or are you?

In a comment section at a [url=http://www.simplebits.com/notebook/2004/08/04/sq.html]SimpleBits' SimpleQuiz from 2004[/url] , some very good comments are to be found (126 in all, but good reading). It became and issue of how best to markup physical addresses and rather than people saying A, B, C or D, may began tweaking the offered solutions.

Comments here are long closed, I was dismayed that it took almost half the comments before someone pointed out the semantics of Address as many were stating simply "A is correct because that is what the tag is there for." Well no, no it isn't, read the specs. It is the contact information on the author. So name, email, URL and such.

Some posters blatantly ignore this but towards the bottom more and more reference it and some begin to point out other ways of seeing it than what [i]I know to be the meaning[/i] of Address.

Now the easy to understand has become vague indeed. Let us look again, this time with my highlights:

[quote]The ADDRESS element [i]may[/i] be used by authors [i]to supply contact information for a document or a major part of a document[/i]< such as a form. This element often appears at the beginning or end of a document.
- W3C[/quote]

Are you seeing what I missed and others saw?

Once again by generously using their favorite word, "may," the W3C's use of it opens the definition to be used and abused in many ways aside from it?s intended use.

Also look at it from a corporate point of view. We looked earlier at me as the author. Now let's say it is a page on a corporate web site. Who is the "contact information for a document or a major part of a document?"

It depends, but it would be either a division or department or the corporation as a whole. So if I have a question or issue with the content who is my contact person? Likely the Public Affairs people for the corporation. How would I contact them? URL and email of course as before, but I may wish to send a letter. Now suddenly a postal address or street address I can visit to speak to someone in person is now fitting snuggly in the definition, especially with that "may" thrown in. A local part of a nationwide chain would not be the owner so the corporate headquarters would be the owner.

Personally, I find that stretching it as this tag is really meant to be directly on each page. So I do not agree with the full address use of the tag, To use it on one page to represent ownership and responsibility for an entire site is not in the spec. The spec clearly states it is "for a document or a major part of a document," meaning singular, as under this theory you need to place the physical address of the company on every page. But I must admit that I can not hotly dispute it because in theory, even stretched theory they are partly right at least and you can liken a web site to a document, like a brochure of many pages.

Another repeated argument is that telephone numbers should not be included, they are not part of the address (usually meaning physical address), but they are however "contact information for a document or a major part of a document" and by that definition better candidates for the address tag than a complete physical or postal address.

So the <address> tag turns out to be not so simple after all. Like a Mirror you identify way off, when you take a closer look it is a funhouse mirror and depending on what angle you look at the specs for address. It means different things to different people and warps to be seen however you wish to use it like a funhouse mirror warping your reflection depending on the angle you see it. With W3C specs, things are not always what they seem.]]></description>
			<author><![CDATA[dummy@example.com (LSW)]]></author>
			<pubDate>Mon, 22 Dec 2008 17:39:25 +0000</pubDate>
			<guid>http://www.killersites.com/forums/topic/45/funhouse-mirrors-and-the-address-tag/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[Breadcrumbs]]></title>
			<link>http://www.killersites.com/forums/topic/35/breadcrumbs/new/posts/</link>
			<description><![CDATA[In a recent thread a reader asked what they are ad someone explained and typed out a example.

So what is it really? Think of Hansel and Grettel leaving bread crumbs to help them track their movements.

Breadcrumb navigation is the same. It helpes you track your position in the navigation scheme.

Example for a school would be: [b]Home > Classes > 1982 > 7b[/b]
This would be Home page lead to Classes lead to the year and in the case of a German school that usually has more than one class, class 7b. If what I want is to here I see I can back track to 1982 and chose a different class, or backtrack to 1983 and check class 7b.

So the Bread crumb is a trail that allows you to backtrack logically to higher instances, so if your navigation has different sub levels under different menu items, it can be a useful tool to offer the user.

[size=3]Problems:[/size] 
It is really not tested or standard yet. Many visual surfers do not notice it or know what to do with it.

Visually impaired people seem to be in two groups, Those who do not understand what it is and those who do and can use it, but some who know what it is find it hard to deal with still. So the final call on whether it is useful in accessibility or a hindrance is not out yet, seems close to equal right now.

Also the choice of separators should be considered. Most often seen is > which acts as a visual arrow in the direction. But this symbol has a semantic meaning, "Greater than". So a screenreader would usually read  "Home greater than classes greater than 1982 greater than 7b".

Some argue that even that makes some sense as each level is less important that the previous.

Other opinions are a colon (:) is better and suggests a menu while still others choose to use the | key which visually compares to the line separators often used.

But fact is > when considered wrong by some is so widespread that many visually impaired are used to it even though it may not be the best choice, it has become a form of default set by visual people but now do to it's widespread use accepted by the visually impaired.

At this time their is no right or wrong answer, just opinions. I myself have not totally decided yet as to which I will use as standard, but currently tend towards "|".]]></description>
			<author><![CDATA[dummy@example.com (LSW)]]></author>
			<pubDate>Mon, 22 Dec 2008 17:33:45 +0000</pubDate>
			<guid>http://www.killersites.com/forums/topic/35/breadcrumbs/new/posts/</guid>
		</item>
	</channel>
</rss>
