break
Jun 11

The following points were written originally to pull my thoughts together for a accessibility briefing on the status of web sites belonging to the state of Alaska, I thought I would add them here for you to read as well.


The issue here is as follows:

  • Alt stands for Alternative text. This means a text alternative to the information held or represented by an image. The popular misconception is that you need describe the image or say what the image is. This is not quite the point. The text is meant as an alternative to inform the user of any info they may be missing. If the image has no informative value it need not have alt text.
  • The alt attribute however is required on every image. If there is no information to be shared, it may be left blank, alt=”".
  • If an image has information like a “Pie chart” you would wish to offer the same info as an alt attribute. You would textually show the same info, you can decide if the fact that the image is a pie chart is of importance or not. If not, then simply add the % shown. alt=”Jueau: Rainfall 70%, Cloudy 20%, Sunshine 10%”. You would not describe the image as in alt=”3D pie chart using the colors red, yellow and green. Green being sunny days, red rain and yellow cloudy…”
  • Do not use alt text for decorative images. Common is alt=”bottom right corner”. Although correct, this has no informative value as it pertains only to the look of the site for visual users. In these cases having a screen reader notify the user during the flow of the information that it has reached an image representing the bottom right corner is of no importance and adds to the general “noise.” By leaving the alt in place but empty, the screen reader will skip the image and the user will either not know an image is present or will understand that the image is of no real value and they are missing nothing.
  • By default, the screen reader will read the name of the image if an alt text is not available. The user would hear “image snodgrass-sen-center.jpg.” This of course has no value to them. By adding the alt attribute it will either ignore the image or read the alt text given.
  • For the above image a correct alt attribute would be to describe the information in the image… not the image itself. In this case alt=”Commissioner Snuffy Smith and Director Gomer Pile visit with seniors at the Snodgrass Senior Center on Wednesday, May 23, 2007.”, no description of the surroundings or even in what position the officials are standing in is given as it is of no value for the visually impaired.
  • Again the same image, if the image does however have a caption, in this case you would not want a caption and an alt text as this would result in the screen reader reading both and the information is doubled. You do not want the alt alone as the visual user will not have access to it. However the caption, due to it’s positioning would be clear enough to a screen reader user that the two belong together. So in the case of captions, as there are no HTML elements to deal with captions, it is justified to leave the alt attribute blank as the caption text already describes the information of the image and you would leave the left and right specifications in place for the visual users to identify which person fits which name and title.

So in closing, it is imperative that all images regardless are given a alt attribute, alt text should only be used if the image portraits important information. If the image is purely decorative the alt attribute is left empty and in the case of images with captions the alt attribute should be left empty.

In her article “Reviving Anorexic Web Writing,” Amber Simmons makes a very good point about how alt text can make even decorative images more interesting and give an emotional alternative meaning to the vision impaired.

Thoughtfully constructed alt text is valuable because it provides emotional content; it should make the reader feel something. Given a photograph of the University of Texas tower, for example, simple alt text that says, “UT tower” might not be terribly useful to someone who has never seen the tower, though it may be useful to someone who knows what the tower looks like. But alt text that says, “Evening view of UT tower aglow after a big Texas win” is better, because it is meaningful to anyone, sighted or not - it projects pride, kinship, tradition. It conveys very particular emotions using revealing language. - Amber Simmons

The “longdesc” is the big brother of the alt attribute. It stands for “Long description.” The specs do not limit the length of the alt attribute. Usually the alt attribute is kept fairly short. Longdesc in unlimited, rule of thumb is that it would be more sentences. The issue here is the opinion of many in the community that if an image is of such importance and complexity to need a long description, then the content deserves a page itself or a description directly in the content of the original page with the image as a visual aid to the textual information. For years longdesc was not widely supported by user agents, I have heard comments suggesting it is still not well supported and from others that it is widely supported now. The longdesc is added as an attribute with the alt attribute and links to a separate file with the description. <img src="example.jpg" alt="Romeo, Juneau's Black Wolf" longdesc="romeo.html">

I discovered a interesting use for the “Longdesc” attribute in the Section508.gov FAQ:

For pictures illustrating a tone or mood you may wish to convey, a good method is to have both a 3-5 word “alt” and a long description of 1-3 sentences, or more if required. This will allow a screen reader user to access the longer description, but does not require the user to hear it every time that he/she returns to the page.

[Edited May 2008]

Jun 11

The following is something I wrote to get my thoughts together for a briefing on accessibility of Alaskan state web sites, I thought it worth noting here to help others perhaps better understand accessibility law.


The lawsuits filed so far have been based on these issues:

  1. Massive lack of accessibility resulting in the user not being able to use the web site at all to reach information or services.
  2. Complaints made and requests to correct the issues have been ignored.

Lawsuits against the state would be made under Sec. 508 of the ADA. The only current lawsuit in progress is against the state of Texas from Feb. 2007 in which 3 state employees with visual impairments were not able to do their job which required working with Oracle Databases. Complaints were filed and software requested and nothing was done so they sued the state of Texas and Oracle for lack of accessible software under Sec. 508. This is not directly web related but shows how the system works. The state of Alaska would not be sued immediately for lack of a alt attribute. A user must complain first and then if we did not improve the site (which we would) a lawsuit could be filed.

The court would decide of the case was warranted. The legal rule of thumb seems to be whether “reasonable attempts” have been made to make the web site accessible. Failing one minor issue on some (not all) pages would likely not justify a court case. I am, however, no legal authority.

All other news worthy lawsuits have been brought against commercial sites, and as Sec. 508 does not cover commercial sites, these lawsuits in the US, and Australia under the British Disability Discrimination Act (DDA), have not been based on the web sites themselves, but on the fact that a service/product was not made available to those with disabilities in the same manner as those without. So those with disabilities were being discriminated against. Hence it is not the accessibility of the web site that was brought before the court but the discrimination against the disabled as they are not able to access the service/product over the net in the same manner as those without disabilities. The web site is not required by law to be accessible, but the service/product offered by the web site is required by law to be accessible to those with disabilities.

One final note on the past lawsuits, in all but the first web accessibility lawsuit brought against Soutwest Airlines, the web site owners have lost the case. However in the instances of Ramada and Priceline, although they lost the case, almost no changes were required of the web sites as the court agreed that doing so would be to expensive and therefore an undue burden on the companies, also the suit only covers accessibility for the visually impaired and not all disabilities. They are wrong for not ensuring their services are available to those with disabilities however are not required to do much to correct the problem.

Jun 7

They are back, the WCAG Samurai have come slinking out of their cellar into the light of day. The open question is: Will they change the world?

The WCAG Samurai are a secret list of top Web Developers chosen by Joe Clark who dismayed by the weak points of WCAG 1 (Web Content Accessibility Guidelines) and not impressed with WCAG 2 drafts and blatantly unhappy with the bureaucracy and power mongering going down inside of the W3C working groups by international corporations… simply decided to do their own thing.

So they backed up some junk food and beer, invited a few fellows they respected, walked into the cellar and shut the door on the rest of us for a year.

Well they are back with sword in hand. This sword is what they have dubbed the “Errata.”

The WCAG Samurai Errata is a list of guidelines that are to be followed (if you choose to accept the mission) along side WCAG 1. Learn and follow WCAG 1 and then pic up the Errata and slice the needed corrections. The errata follows along WCAG lines but corrects some that never worked or are to old. In other places it deletes guidelines or check points or modifies them. Oh, and it executed Priority three completely.

Now I am having a bit of fun with this. I also have my concerns about us being locked out… but then again democracy has it’s limits and the larger the group the harder it is to get anything done.

I have read the introduction to the Errata and it is drastic and severe, but hey look at some of the garbage coming out of W3C these days. It will take some getting use to and I have my doubts on a few points. But I think I will build LSW following the Errata if I can.

As I see it, it is like a big election. If you vote for some new upstart party, are they going to win? No, hardly. But the loss of your vote along with thousands to millions of others does send a note to the big parties that they are not doing what we the people want.

So the Errata will not overthrow the W3C or likely change it. But it can send the message that:
A) WCAG 1 is not bad, just update and modify it.
B) WCAG 2, we are not impressed
C) The web and accessibility is just not a play thing for big business.

Remember the old saying “What if there was a war and nobody came?”, well what if their was a WCAG 2 and nobody used it, or what if the W3C put out a new anything and nobody cared?

We are not required by law to listen to or accept W3C or WCAG and WCAG is just guidelines.

So I will not bow to the Samurai elite, but you have a nod of consent and I will be rooting for the Errata to make waves if not change. In the end accessibility is about the people and doing what is right, whether it meets WCAG or does not… or goes beyond it.

Peer Reviews

Update: The comments by Cerbera below did remind me that this was a first reaction to the errata, some things have changed and I did remove the comment that Ben was part of the Samurai. As for not being impressed with WCAG 2, as Joe himself has said, this was written between the original draft of WCAG 2 and the newest WCAG 2 draft. In deed the newest draft is much improved.

« Previous Entries Next Entries »