accessibility archives
A study on captchas is being conducted. It only takes a few minutes, and they are looking for anyone to take it (sighted or not). I recognize the styles of many of the audio captchas from various sites including Google, Yahoo and Craigslist.
The results of this study should be quite interesting.
(Update: the link now works. Sorry for the inconvenience.)
posted by
cannona
on Thursday, Jun 19, 2008
case study
Update: The below checklist is now available in German.
I have said on numerous occasions that there is no simple checklist that, when followed, will give you an accessible site without fail. There are simply too many variables. But, what do you do when you want to create accessible pages and you have dozens or even hundreds of developers who (like most of their peers) have little to no experience with accessibility? What do you do when it just simply isn’t practical to have someone review all of your pages? In short, how do you insure that a very large organization creates pages that can be accessed by the largest audience possible without drastically increasing your budget? This is one of the questions we have been (and continue to) struggle with.
I believe that in order to solve this problem, we will need to take a multi-faceted approach. However, one element which seems inevitable is training for our designers and developers. I don’t think it’s reasonable (no matter how much I would like to try) to make our devs and designers into accessibility experts, so what can we do? If we can’t yet achieve excellent accessibility, what about simply doing better than we are doing now?
When I wrote the below checklist, I attempted to answer the question, “What concise pieces of advice can I give to designers that will have the greatest impact on accessibility in the majority of cases?”
Again, this list is not the perfect solution, nor is it the only solution, but I believe it is a good first step, and it gives our developers and designers a place to start from.
It is my hope that most of the below points should be easily understood, but on our internal WIKI, we will also be providing links from most checkpoints to supporting documentation that gives more details. For everyone else, I recommend WebAIM or failing that, Google.
A printable version is available here.
Accessibility Checklist
Markup
- Separate structure from presentation and use proper markup for that structure. For example, mark up lists as lists (
<ul>, <ol>, <dl>) rather than text with a <br> tag after each list item.
- HTML headings (e.g.
<h1>) are very helpful for blind users. Properly mark up the sections of a page and body copy with HTML headings rather than something such as a <p> tag with CSS styling that makes it look like a heading.
- Give pages meaningful and accurate titles using the
<title> tag.
- Indicate the primary human language of the document using the
lang attribute in the <html> tag, and indicate any passages in a secondary language using the lang attribute on other tags wrapping the relevant text (e.g. "<span lang="es">Hola</span> means Hello”).
- Provide “Skip to content” links at the top of the markup order in pages with large numbers of navigational links before the main content.
- Always indicate headers in data tables using
<th> tags, and associate all data cells with their header.
- Be sure tab order is logical using
tabindex, if necessary. (If your HTML is in the proper order, then using tabindex isn’t necessary.)
Visual Appearance and Content
- Be sure your page is still usable when images are turned off. (This may include making sure that contrast is still sufficient if you happen to be using a background image and that image is removed.)
- Be sure pages remain usable when users enlarge text up to twice its original size.
- Be sure each element on a page is reachable and can be manipulated via the keyboard.
- Whenever possible, write descriptive headings and link texts which can be understood when read out of context (e.g. no “click here” links).
- For color-blind and low-vision users, be sure your content and background have sufficient contrast.
- Do not use content that flashes or blinks more than three times a second.
- Do not hide the focus indicator. When a user uses the keyboard to tab from element to element, it should always be apparent where they are.
- Do not require users to perceive font, color, or other styling changes in order to understand meaning. For instance, don’t say, “The highlighted word in the previous paragraph is the most important,” or “Items marked in red are errors and need to be corrected,” unless the word or items are indicated in some other way.
Dynamic Content
- Do not use JavaScript events that radically alter the page or load a new page when fired.
Images and Multimedia
- Be sure all images have an
alt attribute, leaving the text for decorational images blank (e.g. alt="").
- Always add
alt text when images are also links.
- In general, be brief with
alt text (e.g. “the Christus statue”), but provide detail when it conveys meaning (e.g. “President Hinckley’s son standing at his graveside with family in arms”).
- Provide a transcript, captions, and/or sign language translation for all audio and video with speech.
- Provide a “described” version of a video when description is necessary for unsighted users to understand content. (The described audio track can either be distributed with the video content, or as an audio only file.)
- Be sure that all videos, if they don’t autoplay, have, at the very least, an accessible Play control.
- When text can be rendered just as well by the browser as it can in an image, avoid using images for text. (Image replacement techniques are often an acceptable alternate, but also consider translation requirements when using text in or as images.)
- Avoid CAPTCHAs unless you have no other choice, and even then they should be avoided. However, if you must use them, provide an audio CAPTCHA alternative.
Forms
- Always label all form fields with the
<label> tag. If a form field has no specific text label on the page, add one, and hide it with CSS or use the title attribute.
- Use fieldsets (
<fieldset>) with legends (<legend>) to associate prompts with radio buttons and check boxes. For instance, a form asks “Gender:” and offers radio buttons that say “Male” or “Female”. Then “Gender:” should be enclosed in a <legend> tag, and all three elements (<legend> and the two radio buttons with their labels) should be enclosed in a <fieldset> tag.
- Identify all input errors in text (in addition to any images or icons), and place the error notification either next to the affected field or in a prominent location such as the top of the page with an anchor link to the affected field.
- Provide help links or inline instructions for completing fields when necessary.
- Do not permit users to complete important actions without a confirmation or a way to undo.
- Avoid using HTML elements in nonstandard ways (e.g. form elements for navigation, links for form submission, etc.).
Testing
- Test all pages for markup validation (http://validator.w3.org). If your page does not pass validation, there should be a good reason for it.
- Test all pages for color blindness using simulators or browser plug-ins. (Recommended: http://colororacle.cartography.ch or http://www.vischeck.com)
- Test all pages for accessibility (http://wave.webaim.org), but only after you have done all you can to make sure it is accessible using the recommendations in this document.
- Have your pages reviewed by an accessibility expert.
posted by
cannona
on Friday, Jun 06, 2008
You guessed it, they make their interface accessible. If you are not able to use a mouse or see the screen, you are basically out of luck when it comes to Google Docs. The best you can do is read what others have wrote, and even that is a bit awkward.
Granted, it will not be easy for Google to substantially alter this situation with current popular techniques, but it should be made a lot simpler with the Accessible Rich Internet Applications (WAI-ARIA) standard being worked on by the The World Wide Web Consortium.
For those who are not aware, ARIA is a proposed standard which, among other things, seeks to bridge the gap in communication between the screen reader and dynamic web applications. It allows you to tell a screenreader user, for example, that a particular element on the page is a drop-down menu, add enhanced keyboard functionality, and draw the users attention to elements that change. It is a very promising standard which is already seeing some support in the latest versions of screen readers, and a few of the very recently released browsers.
But getting back to Google, I believe that inaccessibility will very likely hold them back in the market. It is true that the vast majority of users don’t even know what accessibility is, and if they do, they probably don’t pay it much attention. So how could it substantially effect them in the market? There seems to be a growing trend within a few companies, but more within government, to discourage the usage of inaccessible products when accessible alternatives exist. I believe that at least some of the efforts being put forth by companies to make their products more accessible can be directly attributed to these regulations and policies. Of course, I don’t wish to imply that it’s entirely a business decision, as I am sure many companies do it because they care. However, having a little market pressure never hurts.
Right now, Microsoft Office works great with any screenreader worth speaking of, and if you’re the person responsible for deciding what software your organization will use and you have a mandate to consider accessibility in your decision, MS Office has a big advantage that might be difficult to overcome.
Nevertheless, because of the afore mentioned market pressure, and because of Google’s promising history of making virtually all of their other web applications accessible, I am quite optimistic that I too will soon have the opportunity to use Google Docs.
posted by
cannona
on Friday, May 30, 2008
A federal appeals court ruled Tuesday that the U.S. Treasury Department is violating the law by failing to design and issue currency that is readily distinguishable to blind and visually impaired people. (via airbag)
posted by
jason
on Tuesday, May 20, 2008
Aaron Barker sent me a great article on ARIA and how it can be used to make AJAX apps more accessible. I expect that as the standard evolves, it will do great things for improving the accessibility of the richer web applications.
posted by
cannona
on Tuesday, Apr 29, 2008
Ars Technica posted an interesting article on the gaming industry and how they have all but forgotten colorblind gamers. Not surprisingly, folks who are colorblind manage to play anyway. In fact, I my self used to play Mike Tyson’s Punch-Out!!. (I could get all the way up to Bald Bull.) Apparently, based on my conversations with other totally blind people, this is not as unusual as you might imagine. There have always been video games which (probably unintentionally) gave the user enough information to literally play blind.
posted by
cannona
on Thursday, Apr 10, 2008

Accessibility for Currency…
The new US five dollar bill goes into circulation tomorrow. This interactive feature on the US Treasury site touts the design features of the new bill, including a gigantic purple “Low Vision 5” on the back. Nice interactive piece, but does anybody else think that the “5” looks totally out of place on an otherwise beautiful bill? Can’t accessibility be beautiful?
posted by
ted
on Wednesday, Mar 12, 2008
My recent post on the accessibility of Adobe Flex prompted a response from Adam Lehman, an employee of Adobe. His blog post humorously titled “Is Adobe Flex Really Accessible? You bet your robot voice it is!” talks about a few aspects of Adobe Flex which he claims makes it more accessible than the alternatives. Unfortunately, the issues raised in my original post remain, for the most part, unaddressed.
Adam says on his blog:
I think where Aaron had a rough time is that most of the accessibility information on Adobe.com for Flex needs to be updated. It looks like all of the information is based off of Flex 1.5. It’s definitely something that needs to be addressed and our accessibility team is working on it. I’m also willing to bet that all the applications Aaron tested weren’t the best examples of applications designed to be accessible.
I would point out that the applications I tested were those on the above mentioned site that were specifically recommended by Adobe as examples of accessible apps. It is not clear from Adam’s post whether or not those applications are also in need of being updated. It is also not clear if the Jaws scripts (which, as you will recall, I could not get to install on either of two machines) are also slated for update, as they were not mentioned at all.
It is great that Adobe seems to be actively working towards making Adobe Flex accessible. However, “working on it”, and actually being accessible are two very different things.
Again, if I am wrong, I would love to know about it, and I will of course update this blog with any new information. However, at this point, without having actually experienced an accessible Adobe Flex application, I can not recommend it as an accessible solution, though I do hope that that will change.
Sorry for the lack of comments. I’ll keep bugging the admins and hopefully we’ll have them soon. In the meantime, please feel free to email me at cqannqonawq@ldqschuqrchq.org (removing all of the hopefully spam-bot foiling q’s.)
posted by
cannona
on Friday, Feb 08, 2008
Short answer: no, at least not as far as I can tell.
When I first heard that Adobe Flex was accessible, I was naturally quite excited. I had heard about how powerful the technology was for building rich web apps, and I couldn’t wait to try it. Unfortunately, I didn’t get around to taking a closer look until recently, when I was asked to conduct an evaluation by some folks at work.
Adobe has some sample Flex applications available which supposedly show off there accessibility. Unfortunately, they didn’t seem to work that well for me with Jaws 9.0. Almost none of the controls were readable.
Digging around a little more on the adobe site brought me to their page on using Adobe Flex with Jaws where I read:
In order to most effectively use the JAWS screen reader with an Adobe Flex application, users must download and install scripts. These scripts enable some
of the accessibility features of Flex and allow users to utilize the standard JAWS keyboard shortcut to enter Forms mode on a larger set of user interface
controls than would otherwise be possible. It is important to direct users with visual impairments to this page so that they will have the necessary scripts
to use JAWS effectively.
A little background may be in order at this point for those who are less familiar with Jaws for Windows. Jaws is a very powerful screen reading program, and part of its power comes from the ability to use custom scripts. Unfortunately, many users have never installed Jaws scripts, and may not even realize that it is an option.
So, undaunted, I downloaded the Jaws script files to try the demo again. Just one problem. The scripts would not install. I tried on two different computers with a few different versions of Jaws with no luck, and it appears I am not the only one to encounter this problem.
I find this situation to be quite disappointing, as Adobe has done a lot for accessibility in the past. However, as it stands now, the claim that Adobe Flex is accessible seems to be nothing more than marketing hype.
Hopefully, Adobe will put some more time into making Flex truly accessible. It would also be nice if they could get Freedom Scientific (the company which owns and maintains Jaws for Windows) to bundle the scripts with the program as has been done for many other applications. However, until that happens, I can not recommend Adobe Flex.
I would love to be proven wrong, so if you know of a way I can get this to work, please email me at cqannqonawq@ldqschuqrchq.org (removing all of the hopefully spam-bot foiling q’s.)
Update: This post sparked a response from an employee of Adobe. See this post for further details.
posted by
cannona
on Wednesday, Feb 06, 2008
Interestingly enough, the IHam site is surprisingly accessible with Jaws, in spite of the fact that its almost entirely flash. That certainly bodes well for the accessibility of the IHam product.
posted by
cannona
on Tuesday, Feb 05, 2008
“I like to hear my name in print.”
Aaron Cannon in email today, unintentionally helping me “see” again how this medium is experienced so differently by the differently abled
posted by
ted
on Tuesday, Feb 05, 2008
Christopher Philips sent me a link to a very interesting article on accessibility as it relates to large organizations.
posted by
cannona
on Wednesday, Dec 26, 2007
If you’ve been online longer than a day or two, you’ve undoubtedly been confronted with a CAPTCHA: one of those annoying collections of numbers and letters that you have to type into a form before you can continue. A lot of complaints have been made about their inaccessibility, but what are the alternatives? Even more importantly, when are captchas necessary, and when are they overkill?
Before trying to answer the above questions, I would like to define captcha. In short, the definition of a true captcha is a test which can be designed by a computer, but only answered by a human. In addition, each test should be unique with a high degree of probability. If you think about it, this is actually a very difficult problem, and its only going to get more difficult as computer speeds increase and the computer sciences advance. In fact, many captcha schemes currently in use have been broken, although the processing time often makes this impractical for attackers. But again, as time goes on, this will be less of an issue.
When deciding whether a captcha is warranted, at least three factors need to be considered:
- Is your site high traffic or a high value target?
- If an attacker gained access, could they cause a serious problem for you or your users?
- Are there other less intrusive ways to keep out attackers?
If the answer to 1 is no, you should consider the fact that it is probably easier for an attacker to just spam you manually rather than write a script to do so. If 2 is no, then why burden your users needlessly? If 3 is no, then again, think of your users and find an alternative.
If your site is small, you might try a weaker type of captcha which is accessible. For instance, you could create a list of simple questions and answers, and then present your users with a random one from the list. The problem with this is obvious; an attacker can just keep hitting your page until they’re reasonably certain that they’ve seen all of your questions, and then alter their spamming software accordingly. However, if your site is small enough, it probably won’t be worth the effort, and the attacker will either go some where else, or just answer the question manually (which is obviously something which no captcha can protect against, no matter how good).
But what if your site is a high value target, and you definitely need a captcha? There are still a few alternatives. You can setup a standard captcha for most users, and provide an email address or phone number (hopefully with TTY) that disabled users can use to verify that they are in fact a real person. This has the advantage of being accessible to practically everyone, while being hard for an attacker to automatically thwart. The drawbacks are that it would cost money and time to maintain, and, depending on how you had it setup, might require the user to wait for a call back or returned email. Unless the user can gain access in a timely manner, however, I would not consider that they are being given equal access. In addition, (if you provide a phone number) it may not be available to all users, such as those without the ability to make international or long distance calls.
The other option of which I am aware is to set up an audio captcha in addition to a standard visual one. The benefits are that, once it is setup, it would require almost no maintenance, and most disabled users wouldn’t have to wait for a return email. The disadvantages are that it is not accessible to deaf-blind users, and persons who can’t hear the file for what ever reason. It may also not be as secure as a traditional image captcha, although this undoubtedly depends greatly on the implementation.
So how do audio captchas work? Essentially, they work like visual captchas, except that instead of reading a series of numbers (and sometimes letters) you listen to them.
If you do a Google search for audio captcha, you will find a few pre-made solutions. Unfortunately, none that I have found are adequate. They provide a little security, but not much. One problem with all the ones I have seen is that they use synthesized speech to produce the captcha. However, synthesized speech is highly predictable, in addition to being a little hard to understand at times. This means that all an attacker has to do is find out how a computer says each letter, and then match those patterns in the captcha. The other closely related problem is that the program does not introduce any randomness into the captcha, aside from the selection of the characters. This is like having a visual captcha with no variation in how the letters are displayed; it would be very susceptible to analysis by optical character recognition software.
A very few audio captcha generators seek to introduce a little more variability into their captchas by randomizing the voice, pitch, and speed, but I contend that this is still not sufficient to increase the computing cost to the attacker by much. However, it probably does make the captcha more difficult to understand for the user.
So what is the solution? I believe the best and most secure option currently available is to create an audio captcha with human read characters. It must also have a lot of random noise added to it to make pattern recognition more difficult. A good audio captcha generator should do as many of the following as is feasible:
- string together the human read audio characters with randomly varying spaces between them (an exponential distribution works well for this).
- Randomly Vary slightly the speed, pitch, and/or length of each character (A Normal Distribution works well for this).
- If possible, each character should be read by the same person several times varying slightly the manner it is said, and the program should randomize which of the pronunciations it chooses to present to the user.
- Randomly generated noise should be added to the output.
- Random bits of speech from a person of the opposite gender of the reader should be mixed into the audio. (This helps because the human brain is good at distinguishing between different voices and tuning out those of no interest, though reversing the mixed-in speech can help minimize distraction.)
- Each PCM audio sample should be randomized slightly (A Normal Distribution with a low variance is good for this; too large a variance causes too much distortion and makes the speech unintelligible).
- Add random types of echo to the characters.
- Encode the audio into a proprietary format which is not easily converted.
As with visual captchas, care must be taken to insure that your security measures don’t effect the usability of the captcha. However, the above mentioned techniques should make it more difficult to automatically recognize your captcha text, though it is certainly not impossible. Nevertheless, Google, Microsoft, and other companies have been using many of the above techniques for several months; you can make your own conclusions.
I believe that captchas are currently one of the biggest barriers to accessibility. Unfortunately, there appear to be no perfect solutions. Even the last option is pretty secure, but its still probably not as good as the traditional image captcha. Further thought and research is definitely needed, so if you have any ideas, please don’t keep them to your self.
For further information and some history, see the Captcha article from Wikipedia.
posted by
cannona
on Friday, Dec 14, 2007
Christopher Phillips who works for CES (Church Educational System) presented to our team this past week on the “why’s” of designing for accessibility. (Thanks Christopher!) We asked him if he could share some descriptions of people with disabilities so we can understand better. Here’s his roundup: Personas of Persons with Disabilities.
posted by
gilbert
on Thursday, Dec 13, 2007
Two great finds today! The first is this video from Victor Tsaran at Yahoo. He gives a very in depth demonstration of how a blind person uses a screen reader, like the kind I wish I could have done during my presentation if I had had more time.
The other find is a study which is nearly five years old, but still gives some great advice which is as relevant as ever. Basically it’s a government sponsored study which tries to answer the question “what helps and what hinders screen reader users?”
posted by
cannona
on Friday, Dec 07, 2007
A lot has been written on the opening of new browser windows and how you shouldn’t do it because it annoys and confuses just about everyone, especially the blind and visually impaired. However, I feel that, while it can be over used, it definitely has its place.
For instance, if I am filling out a long and complex form, and I click a help button for a field, I don’t want to be whisked off to another part of a page,
or to another page entirely with out an obvious way to get back. I don’t want to have to worry about my form session being preserved.
When a new browser window is opened, I can flip back and forth between the form and the help window as much as needed, and when I’m done, I just close it.
To be honest, I don’t find them to be nearly as annoying as some writers claim, and in fact, they can be quite convenient when used right. Of course,
this is just my opinion, and less experienced users, or users of screen magnification might have a different view. Still, it may bare looking into. My
personal feeling is that whether or not a user will have difficulty with spawned windows is probably less a question of disability and more a question
of experience with the web.
posted by
cannona
on Wednesday, Nov 28, 2007
“In our opinion, disability rights groups, legislators and standards bodies place too much emphasis on adherence to the WCAG cookbook and not enough on creating sites that are accessible in practice. As a result, most businesses are incentivised to just “check the accessibility boxes” rather than to ensure that their sites are actually accessible to real-life disabled users.”
Etre elaborating on Aaron’s cookbook post
posted by
ted
on Tuesday, Nov 13, 2007
To many amateur bakers, making bread is a mysterious and often frightening process. For this reason, it is often avoided. Those who do decide to take the plunge usually are extremely careful not to vary the recipe one bit. In fact, most cookbooks with bread recipes warn strongly against experimentation. Some make the reader feel as though using one more egg than recommended would cause their kitchen to catch fire and their family to die a horribly painful death of bread poisoning. And so, the myth is perpetuated that bread making is a very complex process, the inner-workings of which can only be understood by those bakers with a doctorate in breadology. They forget that our ancestors (a few of whom had to be at least slightly dumber than they are) made bread on a regular basis with no problems.
Fortunately, there are a few enlightened authors who have written books explaining, in essence, how bread works. Many people are surprised to find out that it’s really quite simple. In fact, once they understand the basics, many home bakers find that they no longer need a recipe or even measuring utensils, and they go on to make excellent bread by guess work and intuition alone.
It has been my experience that many people who learn about accessibility are led down a similar path as would-be bread bakers. They are handed a recipe and told, “This is what you are to do, and if you don’t do this exactly, those crazy disability advocates will come after you with their blood-thirsty lawyers.” They are told things like, “mark headings up as such,” and “put skip-to-content links at the top of pages.” What all too often is not mentioned is why. The reader is not told, for example, that most screen readers have a hotkey which, when pressed, will present the user with a list of all of the headings on the page, and that this is often used to “skim”, just as a sighted user might look down the page to see what was typographically emphasized. No mention is made of the fact that persons who must use the keyboard as a result of limited mobility, find skip links a huge time saver, because they don’t have to tab through all those links that one usually finds in abundance at the top of most pages.
What is worse, sometimes advice is given that is just plain wrong. For instance, it is a common misconception that every image on a page should include an alt attribute with a verbose description. In actuality, only images with important information should be provided with descriptions, and those should be as brief as possible. For example, if there was an image which said “50% off this week on all orders over $50”, then that should clearly be provided with alternative text. However, if there was a picture of a man using a particular product, I’m really not interested in hearing “picture of a man looking pleased as punch to be using the new ultra-lite USB hair drier,” or worse, “picture of a man.” I really don’t care about what image the designers chose to use as eye-candy. I can’t see them, and descriptions of meaningless images just waste my time and delay my getting to the information I’m really interested in.
So, what’s a baker to do? Unfortunately, the efficient use of a screen reader takes time to learn, so it is not all that practical to simply install a demo version and try out your site. Your best bet is to learn the accessibility recipe, but then go on to learn why each step is necessary and important. However, in the end, one must ask the question, could a person with no sense of taste learn to make good bread? I believe they could. The real question is, could they do it consistently? Also, how will they know when they’ve botched it. The only real way to know would be to ask someone with a sense of taste, or, in other words, ask a disabled user to test it. As the person suffering from ageusia receives additional feedback on his or her bread, their skills will increase, and they will get it right more of the time.
So, in short, learn all you can about the why of accessibility, and then go do your best. Most of the time, it will probably be good enough, and almost certainly better than if you just blindly follow a recipe.
A great book, which gives a lot of good detail on the why and how of accessibility is Web Accessibility: Web Standards and Regulatory Compliance by Andrew Kirkpatrick, et al.
posted by
cannona
on Friday, Nov 09, 2007
“For some reason, some folks get it into their heads that being blind is really terrible and the only way our lives can be whole is for us to have all the pretty pictures in the world described to us. Where, in actuality, most blind folks couldn’t care less about most of it.”
Aaron Cannon, explaining why many online pictures do not need to be explained in detail to blind users
posted by
ted
on Thursday, Nov 08, 2007
The only way to get accessibility right is to observe users. Maurizio Boscarol’s ALA article explains the difference between what research says and what users are actually doing. User research is apparently lacking in accessibility; even WC3 didn’t do much of it in their published standards according to Maurizio
posted by
todd
on Thursday, Oct 12, 2006