aaron cannon archives
Ars Technica has an article today titled Report: Mobile Internet use has reached “critical mass”. “Using the Internet from mobile devices is a lot more popular than some of us realize, and even more surprising is the fact that the US leads the pack when it comes to mobile Internet usage… It should be noted, however, that while the US may lead in mobile Internet use, other countries lead in terms of mobile being the primary way that their population gets online. In Russia, Brazil, and India, mobile lines far outnumber landlines, and as those countries continue to flourish, they will become a greater driving force in mobile Internet use.” The article also talks about which devices are most commonly used to browse the web, and the top device is probably not what you’d guess.
posted by
cannona
on Wednesday, Jul 09, 2008
Could web accessibility become law? Many folks are trying. It will be interesting to see if this effort succeeds, and if so, which sites are covered.
posted by
cannona
on Wednesday, Jul 09, 2008
It is common knowledge that alt attributes should contain image descriptions. Unfortunately this is somewhat of an over simplification when it comes to icons or other images used as pictograms, especially when the icon is only loosely related to the action being represented. This problem can more easily be illustrated by an example:
If your web site contains a delete button represented by a trash can, you might write your alt attribute as alt=”trash can”, and under the simplified “alt = description of image” doctrine, you would be entirely justified. However, I encourage you to give this some careful thought. What is more important, that a visitor know what icon you chose to represent the delete action, or that they know what button to press to delete something? Unless you’re in the business of offering icons, I would assume the latter, and encourage you to use something like alt=”delete” instead.
What’s worse, someone who has been blind for a substantial portion of their life may not have sufficient experience with pictograms to understand what they mean based on their description. For instance, many blind users may have no idea what to make of alt=”a red circle with a line through it”. The user could guess, but do you really want to make the user guess about your interface?
I recently came upon a table which was used to show the status of various tasks. The column titles were something like “pending”, “completed” and “failed”, and the rows had labels like “registered in database”, “confirmed”, “synchronized”, ETC. To determine the status of a particular task, you would find the row for the task you were interested in and then look across the table to see which column had the dot. If The dot was in the “pending” column, it was a blue dot, green for the “completed” column, and red for the “failed” column. The alt attributes were alt=”blue-light”, alt=”green-light”, and alt=”red-light” respectively.
This is of course probably quite simple for most screen reader users to figure out, but it would be simpler still if alt=”pending”, alt=”completed” and alt=”failed” were used instead. Simpler because “looking” at a table is a little more work for a screenreader user. But more importantly, it gets back to the question, what’s more important, the icon or what it represents?
So in short, just remember that alt attributes are primarily not intended for helping the user to “see” the image, but rather for helping them get the information the image conveys.
posted by
cannona
on Monday, Jul 07, 2008
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
Did you know if you link images with out paying a license fee, you are violating a patent? Tis true. I wonder how many companies they’ll sucker into paying them.
posted by
cannona
on Thursday, May 29, 2008
I love to read. Some books I want to keep, but others I only need to read once and then I’m done. Until recently, my books just piled up. But then I discovered a free web site that helps me manage my book piles. PaperBackSwap.com is a site that facilitates the swapping of books (both print and audio) with other people who also read way too much. A very cool site.
In the interest of full disclosure, if you use the above link to sign up, I get credit.
posted by
cannona
on Tuesday, May 13, 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
What lengths would you go to to access the internet if your government restricted its access? Here’s an article on what some Cubans are doing.
posted by
cannona
on Friday, Mar 07, 2008
“Look, we all have something to bring to this discussion. But I think from now on the thing you should bring is silence.”
Arnold Rimmer – Red Dwarf
posted by
cannona
on Wednesday, Feb 27, 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
Ran across a great article on WebAIM titled CSS in Action: Invisible Content Just for Screen Reader Users. It discusses several techniques for “hiding” content so it is only available to screen reader users. The article covers hiding form labels, skip navigation links, and other content just for screen reader users.
posted by
cannona
on Thursday, Jan 03, 2008