Uncategorized

For quite some time now, I have been dealing with a couple of perplexing, intermittent JAWS issues. First, edit fields in web pages were blank when in forms mode. The text could not be read with the arrow keys, text selection was not spoken and it was impossible to edit using backspace, delete, etc. This problem was becoming critical, as it reared its ugly head in a web based application on which I rely on a daily basis to perform the duties of my job. Second, the message history area of MSN Messenger and Windows Live Messenger was totally blank. Not only was it impossible to read the text using the arrow keys with the PC cursor active, but the text was also absent when reading with the JAWS cursor. These two problems were quickly becoming a source of frustration, so I began a serious effort to resolve or work around them.

After various unsuccessful trial and error procedures, including deactivating my video card’s diagnostic service and enabling “use legacy Internet Explorer support” in the JAWS 7.1 configuration manager, I found the culprit in the way JAWS seems to handle logging in to and out of Windows profiles. Since I telecommute, I use the same desktop computer for both personal and work related activities. I keep these relatively separated through the use of separate Windows profile accounts for home and work use. Switching between these profiles is typically a matter of simply opening the Start menu, choosing Log Off and selecting the desired profile from the list. This seems to work well with JAWS on the surface, except for the presence of these significant caveats. The unfortunate work around is to switch profiles by restarting the computer. Restarting the computer requires a great deal more time than simply logging off one profile and logging on to another.

The question is, what is the root cause of these issues? Is this just one more quirk observed when running JAWS as a service? Is the problem one of transitioning between system and user space? Has anyone else experienced this issue or similar difficulties? I would be interested in your opinions or other potential work arounds.

Many of you may have received three copies of the wedding toast episode. There was a Blogger error last night that caused two copies of the post to publish without appearing in the back end database. When the blog was republished this morning, both posts disappeared, requiring me to post yet a third copy. This copy was published properly. We apologize for the inconvenience and wasted disk space this caused. You may also notice that, despite the lack of any introductory content from us, the wedding toast show was episode 108 of the podcast. All the best to you all on this Saturday.

I thank Kevin McFan for the interview on his Variety Show last night where we discussed everything from accessibility advocacy and visual verification to the philosophy of the National Federation of the Blind. I believe I was rather candid.

Shownotes

Karen’s sister, Tara, presented a wonderful wedding toast. Enjoy.

Download and Listen

Shownotes

Karen and I sit out on the balcony overlooking the Marina chatting on the last night of our San Diego honeymoon. There will be more coverage of this, too. Stay tuned.

Download and Listen

Shownotes

As many of you already know, Karen and I became husband and wife on June 3, 2006. We apologize for the long delay, but we are proud to finally bring to you audio coverage of our wedding ceremony. We were married at approximately 7:00 PM aboard the Odyssey in Boston, Massachusetts. Stay tuned for additional coverage including portions of the wedding reception and our San Diego honeymoon trip.

Download and Listen

We have just learned that Sirius Satellite Radio has implemented an inaccessible CAPTCHA for their online service. This CAPTCHA is required not for initial registration, but for each log in to the service. This CAPTCHA makes the service completely useless to the blind. This action results in a total lock out of blind and visually impaired customers from a service, listening to audio content, they ought to be able to inherently enjoy without barriers. We urge all Sirius Satellite Radio subscribers to call 1-888-539-7474 insisting that the company implement an accessible alternative to CAPTCHA or remove it altogether while seeking a better solution.

I have just discovered that Scott Sigler now requires the passing of an inaccessible visual CAPTCHA in order to post comments to his Infection podcast. This disappointing move means that blind and visually impaired people are no longer allowed to fully participate in the exchange associated with his unique podcast novel experiments. Scott’s podcasts are associated with Adam Curry’s Podshow network. If Podshow provides the blogging platform and the inaccessible CAPTCHA that goes with it, then this “no blind people allowed sign” would represent yet one more area in which the company has not yet delivered on its public pledge of making accessibility a core part of the Podshow DNA going forward from last November’s Portable Media Expo and Podcasting Conference.

Shownotes

Karen survived the Infection! Yay! Is she the only one who will make it? Only Scott Sigler knows. Listen to the previous show for context on that issue. Just a short 30 minute update on our frantic wedding preparations, erands, packing, etc. Check out our Wedding Journal blog for more details mostly in text form. Check out some assorted pics of Karen in her wedding gown and us together outside our apartment. We’ll make sure to get these cleaned up with descriptions added. This link really isn’t intended to be prime time at all. Browse at your own risk…

Download and Listen

I am ecstatic to report that WebBraille has been returned to service! The following information has been provided by Judy Dixon, Consumer Relations Officer at NLS.

The Web-Braille site is now available! Access to Web-Braille was temporarily suspended because NLS became aware of copyright violations. NLS has taken several steps to prevent such problems in the future. Two are noted below.

Users will be required to accept an agreement describing the appropriate use of downloaded material each time a volume of Web-Braille is accessed. In addition, NLS has instituted a monitoring procedure to track all access to the Web-Braille system.

As these enhancements are refined, users may observe some web site behavior that may seem unusual. We very much appreciate your patience while the Web-Braille system is undergoing these necessary modifications.