aaron cannon archives
This past weekend, The Church of Jesus Christ of Latter-day Saints held its semi-annual general conference. I had a scheduling conflict with the Saturday morning session, but I still wanted to listen live. The engagement was such that I would be sitting and waiting for most of the time, and so I could listen with very few interuptions. Unfortunately, I was going to be in a place without internet access.
The Church’s General Conference is broadcast over the internet, via C-Band sattelite, and by some local television stations (unfortunately none in my area). It is also shown in chapels around the world, and to Dish Network and Direct TV subscribers. Unfortunately, none of these options would meet my needs.
I of course considered streaming the conference to my Nokia phone, but it only supports RealPlayer, and the AT&T data connection speed around here is too slow and somewhat unreliable. Then it occured to me that if I can’t use my phone as an internet streaming audio device, perhaps I should just use it as a phone.
My final solution was to connect the line-in of my sound card to my Dish Network receiver, and write a brief Python script which caused Skype to call me and play the audio from the conference at the appropriate time. It also called me back if I got disconnected.
The solution was simple, and best of all, it worked flawlessly. The only unfortunate part was that it took me so long to think of it. I’m so used to thinking in terms of internet only solutions that I often forget about the older and sometimes more practicle options like the telephone.
Delivering content via phone is (on a per-user basis) probably never going to be cheaper than doing so via the net, but on the other hand, it is not as expensive as it used to be, nor is it as expensive as most people probably believe. This ironically is due in large part to the internet and Voice over IP, as well as increased competition and free and highly customizable PBX software like Asterisk.
So why am I telling you this? It’s not to sell you on the idea of using the telephone as a content delivery platform, though if it works for your application, go for it. Rather I just wanted to remind us all that as we rush head-long into the future, that we be sure to take full advantage of new technologies when appropriate, but that we also don’t forget the old boring tech that can often complement or even work better than the new. Just because we have AJAX and Flash doesn’t mean that plain HTML and CSS isn’t the better choice for many projects. Even though we can add autocompletion to forms and create flyout menus that look really sweet, that doesn’t necessarily mean that we should.
posted by
cannona
on Wednesday, Apr 08, 2009
WebAIM recently released the results of their screen reader survey, and their are a few surprises. I have no doubt that many people, including my self, will be carefully reavaluating their accessibility doctrines. However, while the results do provide valuable insites, I think we have to be careful and recall that sometimes users don’t necessarily want what they think they want.
posted by
cannona
on Monday, Feb 09, 2009
Sometimes when I work, I like to play a little music in the background. Recently, I’ve been listening to a lot of Jonathan Coulton. However, other times, when I want something a little more relaxing, I put on Solo Piano Radio. What internet stream or artist do you enjoy while working
posted by
cannona
on Tuesday, Oct 28, 2008
case study
In recent months, many web designers have been asking the question, “How can I make my dynamic site accessible?” Unfortunately, good answers have been slow in coming from the accessibility community. While some articles have touched on the problem, not many have gone into details. Here is our first attempt at rectifying this situation.
Why is it so difficult for us to come up with some simple recommendations like we did for web 1.0?
A large part of the problem stems from the complex nature of JavaScript. There are so many things to do with it, and so many ways to do them, that making blanket statements about what works and what doesn’t becomes a challenge. For example, screen readers seem to vary widely in how they support and react to JavaScript events. Nevertheless, if we are to have any hope of ever solving this problem, we have to start somewhere. Hence, this article.
In order to keep this article the size of an article, and not a book, we will only be considering how screen readers interact with various JavaScript events. Screen readers are complex beasts, and understanding why they do what they do can be quite a challenge. We have attempted to explain these concepts as clearly as possible, but you should spend some quality time getting to know screen readers such as Jaws or Window Eyes, or perhaps both.
This article is by no means the final word. We are just beginning to scratch the surface. Much more research is needed.
How Screen Readers Read Web Pages
To understand why screen readers have problems with JavaScript in the first place, we have to understand how screen readers read web pages.
The name screen reader is a misnomer since they do not read the screen. Screen readers load the page content from the browser’s document object model (DOM) into a virtual buffer. The user is then able to review this virtual buffer at will, using numerous hotkeys. Items such as links, form fields, and some other elements are identified when they are read. When the user finds a link or other clickable element that they wish to activate, they simply press Enter, and the screen reader tells the browser where they “clicked”.
Form controls are handled differently. When a user encounters a form control they wish to manipulate, they press Enter, causing the screen reader to enter Forms Mode. When in forms mode, the user is only able to “see” the form control that has focus. They cannot read the page content until they leave Forms Mode and return to Virtual Mode. The user can press tab and shift+tab to iterate through the form controls, and, depending on the control type, use the arrow keys, or enter text to modify the control that has focus. Note however, that just because a particular control has focus in the virtual buffer, it does not necessarily have it in the browser. (This last point will hopefully become clearer in a moment.)
Earlier versions of screen readers would sometimes show the user a page that was out of date, because the page would change, but the virtual buffer wouldn’t get updated. Fortunately, this problem seems to have been resolved in more recent versions, and the virtual buffer is refreshed from the DOM every few seconds.
Alerting the User
When a page refreshes in the browser, or when a new page is loaded, the user usually knows it because the screen reader announces it. However, if JavaScript simply updates the DOM, Jaws remains silent. The user may never realize that something is different. This can pose quite a challenge. How can you notify the user not only that there is a new piece of information, but also where they can find it? A sighted user would probably see that something new popped up, but a screen reader only reads what the user tells it to.
For instance, if the user clicked a help button, and JavaScript dynamically displayed some text, how would the user know it? The screen reader probably won’t say anything. What’s more, even if the user did know it was there, they wouldn’t know where it had popped up within the virtual buffer.
Fortunately, the situation described above isn’t totally hopeless. The user has clicked something, so they are probably expecting something to have changed. Whether their screen reader says anything or not. You can give the user a hand in locating the new or updated information by directing the user’s focus to the help text via an anchor tag, or the text could simply be displayed at the user’s current point of focus. Obviously these solutions aren’t perfect, but they are certainly better than nothing.
Ways to alert the user is an area in need of much more research, and we hope to bring you articles in the future which address this problem in greater depth.
JavaScript Events
The following events were tested with Jaws for Windows 9.0 and Window Eyes 7.0 Beta 1, using Internet Explorer 7. Firefox and other browsers were not tested, as screen reader support for those browsers is quite poor, especially when it comes to JavaScript. As a result, use of “alternative” browsers is much less common among blind users.
click
Jaws and Window Eyes both alert the user when an item on the page is clickable, with one major exception: as all good JavaScript developers know, there are two models for attaching events to HTML elements. There is the traditional model (<span onclick="someFunction()"> or element.onclick = someFunction;) and the advanced model (element.addEventListener(...); or element.attachEvent(...); depending on which browser you are coding for).
Of course, it shouldn’t matter which model is used, right? Wrong. For some reason, both Jaws and Window Eyes will not tell the user that an item is clickable if the click event was registered via the advanced registration model.
In Jaws, if the user happens to press Enter on a part of the page which is not reported as being clickable, a click on that portion of the page is passed to the browser anyway, so if there is a click event attached to that portion of the page, then it will fire. Of course, this is rather improbable, as the user isn’t likely to try to “click” places which aren’t reported as being clickable. Also, in Window Eyes, any press of the Enter key on a portion of the page with no link, form control, or element which is not reported as being clickable is ignored.
Fortunately, there is a simple hack which will force Jaws and Window Eyes to recognize that a given element is clickable when you use the advanced registration model. Simply register an empty click event using the traditional model (onclick="" or element.onclick = "").
It appears that the user can fire traditionally registered click events by pressing Enter on any non-form element in both screen readers. However, in Jaws, only click events attached to checkboxes and radio buttons can fire, and in Window Eyes, it does not seem to be possible to easily fire click events on any form controls.
dblclick
Neither screen reader reports when the dblclick event is attached to any element, and this event is not easily fired in Window Eyes. In Jaws, it is possible, but again, rather improbable. If a user presses Enter twice quickly on a non-form element with this event attached, it will fire. There does not seem to be a way to get it to fire with Jaws when attached to a form control.
mousedown, mouseup
Neither screen reader reports when the mousedown and mouseup events are attached to any element, and these events are not easily fired in Window Eyes. In Jaws, they will fire if the user presses Enter on a non-form element where either of them are attached. There does not seem to be a way to get either to fire with Jaws when attached to a form control.
mouseover
Window Eyes does not support the mouseover event, and there is no way to make it fire with that screen reader. On the other hand, Jaws seems to offer surprisingly good support for this event, though again that support breaks down somewhat when the event is registered via the advanced registration model.
Jaws will alert the user when a mouseover event is attached to an element via the traditional model, and it can be fired by use of the Jaws Mouseover hotkey (Insert+Ctrl+Enter). Here again, if the event is registered via the advanced model, Jaws will not alert the user that they can mouseover that particular element. However, if the user guesses that they can, the hotkey will still work. Pressing Enter on an element with mouseover attached will also cause the event to fire, but will additionally tell the browser that the user clicked there, which may cause other events to fire if attached.
In addition, the same hack that works on the click event also works with the mouseover event. If you attach an event using the advanced model, you can get Jaws to recognize that the mouseover event is attached by adding an empty event to the element via the traditional model.
focus, blur
In Jaws, there are two primary ways to navigate a web page. The first is by reading everything from top to bottom, and the second is by tabbing through all the focusable elements (links and form controls). Confusingly, this results in the user having two cursors, a reading cursor and a mouse cursor. The reading cursor exists only for the screenreader (think of it as the virtual buffer cursor), and it has no effect on the browser. The mouse cursor, of course, is just the mouse pointer. Jaws doesn’t generally move the mouse cursor unless it needs to. If the user reads through a page, and stops on a link or form control, the reading cursor is on the element but the mouse cursor is probably not. When the user presses Enter on that link or control, the mouse is then moved to the same position as the reading cursor, so it can be clicked. On the other hand, if the user tabs through the page, the mouse cursor is moved with the reading cursor, and each element gets focus by both cursors.
The end result is that if a user tabs from form control to form control, the current control gets focus and the preceding control is blurred. However, if the user just reads each control with the reading cursor, then no controls get focus and no controls are blurred.
Like Jaws, Window Eyes also has two cursors, but pressing the tab key or reading through the page will focus the mouse on each link as it is reached, and blur it as it is passed. Form controls, on the other hand, will only receive focus if they are modified or given focus when in forms mode.
With these limitations in mind, the blur and focus work as expected: before a form control is changed and before a link is clicked, it receives focus, so the focus event is fired on the current control, and if applicable, the blur event is fired on the previous control.
change
Works as expected in both Jaws and Window Eyes.
keydown, keyup, keypress
When in forms mode, works as expected in both Jaws and Window Eyes. When not in forms mode, the events can’t be made to fire, because Jaws and Window Eyes capture most keypresses.
select
When in forms mode, works as expected in both Jaws and Window Eyes. When not in forms mode, text can be selected and copied to the clipboard without firing the event. This is likely due to the fact that text is being selected and copied from the virtual buffer, and not directly from the browser.
scroll
In Jaws, this event is fired at seemingly random times, including sometimes on page load.
In Window Eyes, on the other hand, it fires at much more logical times—after the user has read several lines of text. However, keep in mind that all scrolling, as such, is taken care of by the screen reader. From the user’s perspective, there is no such thing as below the fold, as everything on the page is all in one big buffer, and screen readers give no indication to the user when they scroll the screen.
load
Works as expected in both Jaws and Window Eyes.
Compatibility Table
For a nice all in one spot reference, here is a compatibility table after the manner of the great Quirksmode Compatibility Tables by PPK.
| event |
Jaws 9.0 |
Window Eyes 7.0 b1 |
| click |
incomplete |
incomplete |
| dblclick |
minimal |
no |
| mousedown |
minimal |
no |
| mouseup |
minimal |
no |
| mouseover |
incomplete |
no |
| focus |
incomplete * |
yes |
| blur |
incomplete * |
yes |
| change |
yes |
yes |
| keydown |
yes |
yes |
| keyup |
yes |
yes |
| keypress |
yes |
yes |
| select |
incomplete * |
incomplete * |
| scroll |
minimal |
yes |
| load |
yes |
yes |
* = Only works in forms mode
Conclusion
There is no widely adopted solution for helping screen readers interact better with JavaScript, though the W3C is working on one. WAI-ARIA promises to be the next big advancement in web accessibility, and, if implemented, could very well solve many of the issues identified above. Unfortunately, complete and wide-spread adoption of the standard is at least a couple years off.
In the meantime, what users need is more research by the accessibility community into ways to overcome the existing shortcomings of screen readers when interacting with JavaScript, and more work by the screen reader manufacturers to fix some of the issues that have been identified. We must begin to address the concerns of people who are trying to make their dynamic web applications accessible, or we will have no room to complain when the next batch of web applications prove to be unusable by the disabled.
This article was written by both Aaron Cannon and Aaron Barker, but our blog software isn’t that robust, so we had to associate it with just one person.
Thanks to PPK for his permission to let us use the compatibility table design, to Kurt Hills for playing the part of editor and to all the others who gave it a proof-reading.
posted by
cannona
on Tuesday, Oct 07, 2008
“In order to better understand [the elderly’s] experience I have bought a pair of ski gloves and some reading glasses (I don’t need reading glasses). Every now and again, I surf the site I am designing wearing both the glasses and gloves. The glasses make the screen hard to read while the gloves hamper my use of the mouse and the keyboard. There is nothing more frustrating than trying to select something from a drop down menu
wearing ski gloves!”
From Paul Boag in Boagworld podcast episode 130,
and originally found on Web Axe.
posted by
cannona
on Tuesday, Oct 07, 2008
If you follow tech news at all, then you have undoubtedly heard that the National Federation of the Blind filed a class action lawsuit against Target Stores over the inaccessibility of their site. And you have also probably heard that that suit was recently settled. As a result of the agreement, Target will have to pay $6,000,000, legal fees, plus the cost of fixing and maintaining the accessibility of target.com
More important to some, this case failed to answer the question, if a business’s site is not accessible, is it breaking the law? I know many accessibility advocates were hoping for a clear legal precedent, which we did not get. If we had gotten one, my job probably would have gotten a lot easier, but in spite of that, I’m generally pleased with the outcome.
Unfortunately, I believe that this case has been misunderstood by many. Anytime new laws are proposed or legal actions commenced which may have any chance of effecting the internet, the outcry is immediate and often drastic. Along with that outcry, there inevitably come many rumors and incorrect assumptions. It is those false assumptions I would like to address and hopefully put to rest.
Of course, it is not my intention to discourage anyone from making their site accessible. Just because you are not legally required to consider your disabled users, doesn’t mean that there aren’t many good reasons to do so.
Before I go much further, I should mention in the interest of full disclosure that I am an active member of the National Federation of the Blind. Nevertheless, my opinions are my own and don’t necessarily reflect those of the NFB. Also, I am certainly not a lawyer, nor do I claim to be an expert on the ADA, so take my analysis with a very large helping of salt.
Now that that’s out of the way, it is my understanding that the NFB, in its lawsuit was not demanding that all web sites should be made accessible. Rather they were contending that business web sites should be made accessible. In addition, they were suing under a California statute, and under the Americans with Disabilities Act. Before we assume that, were the ADA to be applied to the internet, that it would mean expensive site redesigns and big lawsuits for every site someone considered inaccessible, we would do well to review what the law actually says. Keep in mind that we have to try to apply the statute to a digital domain, even though that’s probably not what the creators of the law were contemplating when they wrote it:
Title III of the ADA prohibits discrimination against persons with disabilities in places of public accommodation and commercial facilities. Places of public accommodation include over 6 million privately owned business establishments of all sizes such as restaurants, hotels, theaters, convention centers, doctors offices, retail stores, museums, libraries, private schools, health spas, and day care centers. Commercial facilities are businesses whose operations affect commerce, such as office buildings, factories, and warehouses. Public accommodations must: provide goods and services in an integrated setting, unless separate or different measures are necessary to ensure equal opportunity; eliminate unnecessary eligibility standards or rules that deny individuals with disabilities an equal opportunity to enjoy the goods and services of a place of public accommodation; and make reasonable modifications in policies, practices and procedures that deny equal access to individuals with disabilities, unless a fundamental alteration would result in the nature of the goods and services provided. They must also ensure effective communication through the use of auxiliary aids and services when necessary, unless an undue burden or fundamental alteration would result. They must remove architectural and structural communication barriers in existing facilities where readily achievable, and provide goods and services through alternative measures when removal of barriers is not readily achievable. When public accommodations or commercial facilities design and construct new facilities, or alter existing facilities, they must do so in accordance with the Standards for Accessible Design. Title III is enforced by the U.S. Department of Justice.
…
If you own or operate a business that serves the public you must remove physical barriers when “readily achievable,” which means easily accomplishable without much difficulty or expense. The “readily achievable” requirement is based on the size and resources of the business. So larger businesses with more resources are expected to take a more active role in removing barriers than small businesses. The ADA also recognizes that economic conditions vary. When a business has resources to remove barriers, it is expected to do so; but when profits are low, barrier removal may be reduced or delayed. Barrier removal is an ongoing obligation—you are expected to remove barriers in the future as resources become available.
(From Introduction to the ADA)
I wish to draw your attention to a couple key phrases from the above quote: “The ‘readily achievable’ requirement is based on the size and resources of the business.” That would seem to mean that if your company makes a lot of money, then it might be held to a higher standard than if it doesn’t. Also, it would appear that personal blogs, sites run as a hobby or just because and the like would not be covered by this. In short, the vast majority of web pages on the internet probably have nothing to worry about.
Second: “ Public accommodations must: provide goods and services in an integrated setting, unless separate or different measures are necessary to ensure equal opportunity; eliminate unnecessary eligibility standards or rules that deny individuals with disabilities an equal opportunity to enjoy the goods and services of a place of public accommodation; and make reasonable modifications in policies, practices and procedures that deny equal access to individuals with disabilities, unless a fundamental alteration would result in the nature of the goods and services provided.” (Emphasis added.)
If I am understanding this correctly, then if your site can’t be made accessible to a particular group, (something by the way which is much less common than you might imagine) then you are probably off the hook, at least as far as access to that group is concerned. However, you would still be responsible for making your site accessible to the rest of the disabled community. Also, for something important like this, you don’t just want to assume that a site feature can’t be made accessible, simply because you can’t think of how it might be done.
Finally, a lot of people have simply wanted to know, “What’s the big deal? Why does it matter if you can’t shop at Target? Just shop somewhere else and be done with it.” However, I dare say that the same people who ask this question would be outraged if Target would not allow them to shop there due to their race, religion, or other personal characteristic.
Most disabled people, in my experience, do not wish to place an undue burden on society, but they also do not wish to be second-class citizens. It may appear that this is all just about convenience, seeing how much money we can get from Target, or just plain stubbornness, but for us it is about the right to full participation in the world.
Is it really too much to ask that a major corporation with billions of dollars of income spend a few thousand on accessibility?
The issue with Target wasn’t that they did it wrong, or that it wasn’t perfectly accessible (something which is virtually impossible to achieve). Target’s problem was that they didn’t even try, and they ignored pleas to change. This is witnessed by the fact that their site lacked alt attributes until after the lawsuit was filed. Of course the missing alt attributes was only one of many accessibility problems with their site.
So, that’s my take on the whole situation. It would be interesting to hear a more official opinion on the legal situation from an attorney. In the meantime, we’ll probably have to wait for the next big lawsuit to find out whether the ADA covers web sites or not.
posted by
cannona
on Monday, Sep 01, 2008
WebAIM has a great new article called Web Accessibility Gone Wild. It gives an overview of frequent accessibility mistakes and how to avoid them.
posted by
cannona
on Monday, Sep 01, 2008
Kiva now has teams. How about a North Temple team?
posted by
cannona
on Friday, Aug 29, 2008
A group of researchers have devised a method which allows people to communicate over a 2G cell phone network using Sign Language. This is a pretty big step for deaf folks, because text messaging is a poor substitute for the expressiveness of Sign Language, and for many who have been deaf since childhood, English is truly a foreign language.
Read more about the project here.
posted by
cannona
on Monday, Aug 25, 2008
There appear to be more scammers in the “business” of search engine optimization than in any other area of web production. I have no idea why that is, but as this fact has become better known, it seems to have discouraged people from paying as much attention to SEO as they used to. This, I feel, is quite unfortunate, as I’m convinced many sites could benefit from a little attention in this area.
I’m certainly no expert on the topic, but in my experience, if you want to help your search rankings, you’ve got to stop asking, “How can I drive more traffic to my site?” and instead ask, “How can I help interested people find my content?” This can be a difficult shift, especially when your site offers little unique information. Nevertheless, I believe that adding fresh and relevant content is unquestionably one of the best things you can do for your site. If you want to improve your search rankings, give the search engine something to find.
Other factors which can effect your ranking to a lesser extent seem to include how many sites link to you (quality is as important as quantity, so no free-for-all link pages), your page title, and of course how well the words in the text of your page match the words that were searched for.
However, like I said, I am no expert on the topic, and I would like to hear from others. What recommendations do you have for search engine optimization? I’m not interested in ways to game the system, just suggestions on how to bring our content to those who are looking for it.
posted by
cannona
on Thursday, Aug 21, 2008
I know image rip-offs are a big concern for many, and now there is a search engine that purports to enable you to scan the web for other copies of an image you provide. It can supposedly recognize the image, even if it has been modified to some extent. The TinEye search engine’s index is not too big, but they say that that will change.
posted by
cannona
on Tuesday, Aug 19, 2008
Cameron Moll sent me an article from A List Apart on Deafness and the User Experience. I found the explanation of the difference between Deaf and deaf quite interesting. However, I think the most valuable piece of advice the author gave is to write clearly.
Font style and size, page layout, graphic choice and placement, and all the other elements which are traditionally the meat of design are useless if your page isn’t written clearly. Good writing all too often is given much too low a priority in the design process. Yet I submit that it is just as important as any other aspect of design, and perhaps even more important.
posted by
cannona
on Friday, Aug 15, 2008
I recently created a couple videos on accessibility. One on specifying the human language of an HTML document, and another on the importance of headings. Please excuse the lack of real video. My purpose was simply to create something that would get the message across.
posted by
cannona
on Monday, Aug 11, 2008
Good catch. Thanks.
posted by cannona on Wednesday, Apr 08, 2009