Darrell Shandrow Hilliker

AxsJAX Brings Accessibility Features to Web 2.0

by

I have just one critical question, my friends. Why haven't the "leading"
screen reader makers incorporated any of this technology into their
products?

Wired.com News
Thursday, November 15, 2007

AxsJAX Brings Accessibility Features to Web 2.0

By Scott Gilbertson

Google Reader's recent makeover wasn't just skin deep. Most people probably
didn't notice it, but the revamped Google Reader also added an accessibility
layer which makes the app screen reader friendly.

LINK:
http://firevox.clcworld.net/

Web 2.0 sites may be slick and easy to use for most people, but such sites
often lack accessibility support, making them difficult, if not impossible,
to use with screen readers and other assistive technologies.

In an effort to improve accessibility on AJAX-heavy websites, Google
recently released the framework behind the new Google Reader tools as an
open source project dubbed AxsJAX. The code has been reworked and most of
the Google-specific features removed, which means it should work for just
about any site that chooses to use it.

LINK:
http://code.google.com/p/google-axsjax/

AxsJAX is designed to enhance the accessibility of AJAX applications.
Charles Chen, who added the accessibility features to Google Reader and
develops Fire Vox, an assistive device friendly add-on for Firefox, writes
on the Google Code Blog:

Based on the experience of access-enabling Reader, we have now refactored
the code to come up with a common JavaScript framework for enhancing the
accessibility of AJAX applications. This framework is called AxsJAX, and it
was refined in the process of access-enabling Web Search.

We're now excited to open-source this framework since we believe that there
is nothing Google-specific in the techniques we have implemented. We invite
the Web developer community to help us collectively define a robust
framework for rapid prototyping of accessibility enhancements to Web 2.0
applications.

LINK:
http://google-code-updates.blogspot.com/2007/11/introducing-axsjax-access-enabling-ajax.html

AxsJAX features can be accessed by users in several ways: as a bookmarklets,
using Greasemonkey or through Fire Vox. The underlying code implements the
W3C's WAI-ARIA spec (Web Accessibility Initiative – Accessible Rich Internet
Applications). Rather than simply providing assistive device users with a
non-AJAX page as is the standard practice, ARIA makes the results of AJAX
calls accessible to screen readers. Check out the ARIA roadmap for more
details.

LINK:
http://www.w3.org/TR/aria-roadmap/

If you'd like to know more about the AxsJAX framework, have a read through
the documentation on the Google Code project page.

LINK:
http://code.google.com/p/google-axsjax/

SOURCE
http://blog.wired.com/monkeybites/2007/11/axsjax-brings-a.html

Visual Verification: Slashdot Adds Accessible CAPTCHA, Allows Blind Readers to Create Accounts and Post Comments

by

We thank Rachel for her report that Slashdot has now enabled full participation by their blind and visually impaired readers by adding an audio CAPTCHA for creating accounts and posting comments. This issue was filed as a priority 5 bug on August 27, and is reported to have been resolved sometime in October. We thank the Slashdot folks for fully opening their doors to the blind and visually impaired.

Watch Your Keys; JAWS Activation Issues Could be a Job Killer!

by

Imagine this nightmare situation! You work nights and/or weekends. One Saturday morning, you start the JAWS-equipped computer on your desk only to find that, for some mysterious reason, JAWS has decided it is no longer authorized. Even worse, since you have JAWS authorized on three computers, you have no additional activations available. It is time to contact Freedom Scientific, right? Wrong! Freedom Scientific is not open during late evenings or on weekends and holidays! You’ll just have to wait till Monday for Freedom Scientific staff to fix the problem! In the meantime, JAWS will run only in 40 minute demonstration mode. It will be necessary to completely reboot your computer 12 times during your eight hour shift. Will your employer find that an acceptable loss of productivity? What if you are an emergency dispatcher, where your ability to correctly and efficiently process each incoming call may be literally a matter of life and death?

It is long past time for Freedom Scientific to come up with a licensing scheme that protects their precious software while ensuring the highest possible availability to its legitimate, paying customers! An excellent example of a reasonably workable scheme would seem to be the new user-centered licensing system recently implemented by Code Factory. Please, Freedom Scientific, if not Code Factory’s model, then come up with a similarly reasonable scheme to protect everyone’s interests. Most users are not going to be highly technical. They’re just not going to be constantly watching FSActivate.com to see if they have an extra key available, just in case the worst happens. Instead, blind employees need reasonable assurances that, barring some sort of catastrophe, their screen reader isn’t going to be the tool that lets them down when they start their work day. Doesn’t JAWS still stand for Job Access with Speech?

Coming up on Main Menu and Main Menu Live for the week of October 24

by
Hello Everyone,
 
We have a brand new Main Menu and Main Menu Live for you all this week!
 
During the first hour on Main Menu, Dean Martineau of Top Dot Enterprises demonstrates Jamal Mazrui’s FileDir accessible file management utility.  After that, listen to Matthew Horsepool’s Newsbriefs to catch up on technology news from a blindness perspective.
 
During the second hour of Main Menu Live, join our panel of experts (Jeff Bishop, Darrell Shandrow, Don Barrett, Rick Harmon and Steve Bauer) for an exciting discussion of GoldWave, Studio Recorder, Sound Forge, Total Recorder and possibly other audio editing software applications.  If you are a blind or visually impaired audio engineer, podcaster or otherwise are involved with digital audio production in either a hobby or professional capacity, you’re sure to learn something new by listening to and participating in this show.
 
Here is how to participate in the show:
 
The number to call into the show is 866-400-5333.
You may email your questions to: mainmenu@acbradio.org
You may also interact with the show via MSN (Windows Live) Messenger. The MSN Messenger ID to add is: mainmenu@acbradio.org
 
Would you like to interact with a group of Main Menu listeners about the topics heard on Main Menu and Main Menu Live? You can do this by joining the Main Menu Friends email list. The address to subscribe is: main-menu-subscribe@googlegroups.com. Come join an already lively group of users.
 
Would you like to subscribe to podcast feeds for Main Menu and Main Menu Live? The RSS feeds to add to your podcatching application are:
 
Main Menu -http://www.acbradio.org/podcasts/mainmenu
Main Menu Live -http://www.acbradio.org/podcasts/mainmenulive
 
Main Menu and Main Menu Live can be heard on Tuesday evenings at 9:00 Eastern, 6:00 Pacific, and at 1 universal (GMT) on Wednesday mornings on the ACB Radio Main Stream channel.
 
Follow this link to listen to the show:
 
http://www.acbradio.org/pweb/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=8
 
Jeff Bishop and Darrell Shandrow
The Main Menu Production Team

QVC Asked to Retain Accessibility in Web Site Update

by

Randy from Accessible Devices has informed us that the QVC home shopping network is beta testing a significantly updated web site. While the current site is accessible to blind shoppers, the beta site is apparently not so great. We have just submited a short note to the QVC webmasters asking that they keep in mind the accessibility needs of their blind customers. A response has been explicitly requested, so please stay tuned for any updates. In the meantime, all blind and visually impaired QVC shoppers are asked to immediately complete this contact form asking QVC to continue reasonably accomodating and retaining their blind and visually impaired customers by ensuring the ongoing accessibility of the web site. One quick note from an accessible evangelist is only the very beginning, but it is not even close to sufficient as an ending step. If you are blind or visually impaired, and you shop with QVC, please fill out the form requesting web site accessibility right now.

Freedom Scientific Asked to Reasonably Accomodate Deaf-Blind Customers

by

I just read the article Freedom Scientific says no to access for deaf people on the Access Ability blog, and I must say I am rather dismayed. The issue at hand is the current lack of accessibility of the company’s FSCast to the deaf-blind segment of the blind community.

While Freedom Scientific manufactures products to meet the needs of an underserved, minority population, it also seems to be failing to accomodate a segment of that very community. How can we ask the mainstream technology industry to reasonably accomodate us, when we allow companies in our own blind community to pass on providing accessibility by claiming a lack of resources?

We at Blind Access Journal ask Freedom Scientific to reasonably accomodate its deaf-blind customers by following these steps to incrementally increase the accessibility of their podcast audio content:

  1. Provide a link to an alternative document that delivers similar information. In the case of the most recent podcast episode 10, for instance, posting the JAWS 9.0 release notes at the same time as the audio would have represented a positive step forward.
  2. Provide detailed show notes that cover all the same important information delivered in the audio presentation. This can be a summary, at least in the beginning, so long as the same important information is delivered.
  3. Finally, the ultimate goal should be to supply full text transcripts of each FSCast episode.

We ask Freedom Scientific to do the right thing by moving toward full accomodation of its deaf-blind customers in a way that is inexpensive while ensuring their full inclusion in everything the company has to offer. We believe the largest player in the blindness assistive technology industry ought to be able to show positive movement in this area by the time episode 11 of the FSCast is released. Come on, Freedom Scientific, please step up to the plate, do the right thing and make sure all your blind customers, including those whom also happen to be deaf, are afforded a full and equal opportunity to participate.

JAWS 9.0 Public Beta 1 – First Impressions

by

Although we aim to keep our readers informed, we are also not strictly a news blog. Since the news concerning the impending JAWS 9.0 public beta, and its release yesterday, were broadcast all over the online connected blind community, we elected to hold off for the chance to report some real world first impressions of this new version.

Freedom Scientific released JAWS 9.0 Public Beta 1 yesterday, October 1. The enhancements and new features of this version were demonstrated last week in episode 10 of the company’s FSCast podcast. The release notes were posted last Friday and the JAWS for Windows 9.0 Public Beta was made available on Monday.

As an advanced blind computer user who depends on reliable screen access in order to perform my day job, among other tasks, I believe it essential to take every opportunity to test new public beta versions and releases of all the assistive technology in my toolbox. This includes, of course, this JAWS 9.0 public beta. In this regard, the ability to install and run new versions of JAWS while retaining previous versions remains a significant advantage. In the event of a crash, instability or a new feature with which I simply can’t live at the moment, I am able to quickly return to a previous version and get on with the business at hand.

Though I’ve spent less than a day with the JAWS 9 public beta, my first impressions are quite positive. The most significant improvement I have experienced thus far is increased overall responsiveness across the board. Though I have not yet taken the opportunity to experience the new features of this public beta, the following seem to be the most significant:

  • Improved support of Microsoft Office 2007 and Windows Vista.
  • The ability to copy and paste content from the virtual buffer (such as virtual PC cursor mode in Internet Explorer) into a Microsoft Word document or HTML e-mail while retaining live links and visual formatting. Though I do not necessarily consider this a “break through” feature, it is, nevertheless, a potentially useful tool for working more effectively with sighted colleagues.
  • Initial support for the standard Gmail web user interface, possibly without the need to use the basic HTML view. I haven’t yet had a chance to test this functionality, but would certainly consider this significant, especially if it really makes that view accessible now. Are we finally starting to see JAWS seriously tackling an AJAX enabled web site?

Other JAWS users, including Rick Harmon are reporting Windows Vista enhancements not currently listed in the release notes, along with some new issues. I also note that the improvements made to the blank virtual buffer issue and FSBraille crashes in the limited release build 2178 were not listed in the JAWS 9.0 What’s New write up. All the same, I have yet to experience either issue so far. It is absolutely critical that we use the Beta Report Form to provide thorough feedback regarding any issues encountered while using this public beta. The programmers at Freedom Scientific can fix problems only when they are made aware of their existence.

Though JAWS 9.0 will add some new functionality to our overall computing experience, I do not feel it warrants a 9.0 version designation that results in a reduction of our SMA count or an additional financial cost for those who are not part of Freedom Scientific’s SMA program. Instead, it seems a version number such as 8.5 may have been more in line with the feature set being offered. As always, comments are quite welcome.

GoldWave Developer Seeks Accessibility Feedback from Blind Users

by

The developer of the GoldWave audio editing software has expressed an interest in learning how blind and visually impaired people use the software and taking feedback regarding ways in which it may be made more accessible in future releases. All blind and visually impaired GoldWave customers are encouraged to contact Chris, the developer of this popular application in the blind community, with constructive feedback. Given the numerous issues with Sound Forge 9.0, and the apparent lack of communications between Sony and its customers on accessibility and many other concerns, I may consider switching to GoldWave. All thoughts on this are welcome.

Visual Verification: Six Apart Continues to Lock Out the Blind with Inaccessible CAPTCHA

by

We continue to be locked out of full and equal participation by Six Apart, developers of the TypePad blogging platform, due to an inaccessible CAPTCHA used for account creation and posting comments to blogs. In the past, numerous attempts to contact the company have gone ignored. Now that it has come to our attention that various members of the disability community use TypePad as their blogging platform, despite its inaccessible CAPTCHA, it would seem to be time for another attempt at getting this issue properly addressed by Six Apart. All blind and visually impaired Internet users, along with those sighted people who care about what happens to us, are urged to use the Contact Us page on the Six Apart web site to ask the company to finally do the right thing by making their CAPTCHA accessible. I have already contacted Jane Anderson, Six Apart’s Media Contact, asking for her assistance in resolving this issue or devising a plan for doing so in preparation for another article in the works concerning TypePad bloggers in the disability community. It has been proven over and over again that, if we keep on publicly and privately discussing this issue of the inaccessible CAPTCHA lockout, it often does eventually get resolved. Let’s all keep the lights shining clearly on this challenge as we move toward more positive results.

Visual Verification: Mike Tech Show Covers Yahoo! Accessibility Improvement Petition

by

Thanks to Mike Smith of the Mike Tech Show podcast for discussing and urging his listeners to sign the Yahoo! Accessibility Improvement Petition asking the company to make their CAPTCHA accessible to the blind and visually impaired. Let’s all continue our efforts to reach out on this and all other critical technology access issues.