The “Fire Vox” Firefox extension is a FREE screen reader

Over a month ago I downloaded the Fire Vox Free screen reader extension for Firefox that acts like a screen reader and was created by Charles L. Chen.

I found that it was of great use and I assume it simulates most of the major functions that screen readers like JAWS or Window-Eyes can do, since I have never used either one of those.

Here is a little more information about the two screen readers I mentioned earlier and information about there cost.

  • JAWS – free trial (shuts off machine every 40 minutes) and $900 – $1100 to purchase a full version .
  • Window-Eyes – 60 day trail $39 or $900 to purchase a full version.

Fire Vox does not have all the bells and whistles that the other two have. I have not been able to find how to increase or decrease the speed of the speaking voice.

Some uses for the Fire Vox Firefox screen reader extension.

  • To see how your website will be to someone that uses a regular screen reader for someone with visual issues.
  • Now close your eyes and listen to your website to see if you can navigate and find information. You should be able to, since you created the website.

After awhile of using Fire Vox you might want to turn off the auto speaking function. All of the commands for Fire Vox on at least a PC are done with CTRL + SHIFT + some default key. To get to the list of functions you have to use CTRL +SHIFT + M to get the pop-up menu and un-click the “Speak Events” and “Echo Keys” checkboxes. This will then only allow the screen reader to be activated when you use the following key strokes CTRL +SHIFT + A or when a pop-up window occurs. This allows someone that needs these functions to still be able to get them to work.

For a full explanation please read the post on the Accessify Forum on how to turn off speaking all the time. To get Fire Vox to stop reading/speaking you can hit any key on the keyboard.

Here are some of the functions that Fire Vox does have are their default settings.

  • Auto Read – CTRL + SHIFT + A
  • Read Previous – CTRL + SHIFT + D
  • Read Next – CTRL + SHIFT + F
  • Repeat – CTRL + SHIFT + E
  • Say Selected Text – CTRL + SHIFT + O
  • Spell Out – CTRL + SHIFT + S
  • List of Headings – CTRL + SHIFT + H

There are a great bunch of Fire Vox tutorials on their website that will explain a lot more. There is no point of repeating all that information here.

Here is the links to the exercises from the Fire Vox tutorial page.

  1. Reading Text and Navigating Web Pages
  2. Getting Additional Information
  3. Working With Forms
  4. Working With Live Regions

So please download the Fire Vox free screen reader extension for Firefox and try it out. Tell me what you think.

Long Week in Technology Last Week

It’s been a long week in technology for me this week. I spent about five or six hours on both last Saturday and Sunday working on the website for my accessibility talk for the Refresh DC meet up on Thursday night. This is the prototype for the DC Tech Skills website I’m building so the Washington, DC, technology community can post their skills and then find others that either have the same skills or might need help on projects for skill they need.

Monday was long day at work  with one meeting that ended up needing a few changes and a few other meetings were canceled. The rest of Monday night was spent updating the “Accessibility“ slides I had prepared for “BarCamp DC“ talk back in mid August, 2007.

Tuesday was spent working on getting stuff ready for a move of code to PROD, which never happened. I took a few hours off in the beginning of Tuesday night to go to the “Opportunities & Challenges of the One Laptop Per Child (OLPC) Project” meet up. It was really cool to be able to get to use some of the other features of the OLPC has besides the internet. We had a “Chat” going  and afterwards demonstrated the “Write” and “Memorize” activities to people. Then it was home for about three more hours of presentation work.

Wednesday was filled with meetings and luckily a few were canceled. I’ve had more meeting in the last few days than I normally have in a month. I got approval to move code to PROD for one project. I have like two others that just need user/client review and approval and I’m good to go to PROD.

I got home from work around 5:00 PM and started working on  the final dozen or so slides. Things were going well so I took an hour off to watch the Discovery Channel. I forget what the show was, but it must have been good that i took and hour off to watch it. Once that ended I started back on the presentation. The first thing after the TV show my laptop would not type. There was a problem with the keyboard. I saved things and re-booted.

Around 12:15 AM my keyboard  stopped working a second time. I used the mouse to save everything before re-booting the PC.  The only problem was that it never re-booted. At that point I guess I must have said a few four letters words, since I had not uploaded a copy of my presentation to the server or made a backup in over a day.

After walking into the living room and then the bedroom to try and figure out what I might have to do next. I remembered my friend from Rochester, NY, saying that COMPAQ laptops sometimes won’t re-boot if you have them plugged in all the time and don’t let the battery drain every so often.

So the first thing I did was take the battery out and just used the power cord and that did not work. Next was put the battery back in and unplug the PC and that worked. First thing after twittering about the problem now at like 1:45 AM I put a copy of everything on the server, and two different thumb drives. By 1:00 AM, I was back and finishing the presentation.

I ended up finishing it around 2:15 AM and spent the next bit of time re-copying the updated information to the server, thumb drives, and into another folder on my machine. It was then 2:30 AM and I tried to get to sleep but was to wound up. Finally went to sleep after 3:00 AM. The latest night in five days. All the other nights it had been between 1:00 and 2:00 AM.  I’m getting to old to stay up five night that late.

Thursday morning it started sinking in that close to 100 people were now going to show up to listen to me talk about accessibility. It was just a bit surreal, since when I was at SXSW 2007, I went to most of the accessibility talks and only 50 or 60 people where there to listen to the likes of Derek Featherstone, Ian Lloyd, Patrick Lauke, Glenda Simms (Glenda the Good Witch),  and many others.

These people are proven accessibility experts. I felt like just some guy from Washington, DC consulting for the Army that is really passionate about accessibility.

I had sent the link to two friends to look over early in the morning. I got some feedback from one that I should run the presentation through a spell checker. I said it’s hard when it is done using “S5“, which is HTML based. A guy from the office said paste it into word and run it through, while overriding the code parts. I did this over my lunch. My friend read the whole thing over during his early lunch and liked most of it.  He thought the topic might be to long to get done in the hour I had along with a few other suggestions to improve it some. While on my lunch I made most of his changes along with using a bit of his wording, since it made more sense than what I had first written.

One of the people from work noticed that my accessibility talk was the most popular event on Upcoming for the DC area that day. Once I looked it up I got rid of the DC part and looked and it was the third most popular event  for that day anywhere in the world. The first place event was a  new Flickr feature meet up in San Francisco and then a “MacWorld” meet up in San Francisco. Our event was even about 25 people larger than the London “Pub Standards” meet up. This was just unthinkable to me. It put me in a bit of a panic most of the morning and early afternoon.

After the lunch of updating  my presentation I was much better and the panic slowly went away. The rest of the afternoon flew by because I had to finish some work and move other things to PROD server.

I headed home around 4:30 PM to pickup my computers and get to the Refresh DC meet up early to make sure everything was ready and working correctly. By this time it seemed like everything was okay and I was relaxed on the Metro trip there.

I guess I finally realized I had been thinking about this presentation for the last few months and what I wanted to present. So when it finally came to doing the presentation all the stress, lack of sleep, and everything just went away.

I thought the presentation just flowed out of me. Part way through the presentation I asked the audience if I was going to fast and if they were understanding it. They said no my pace was fine and that yes they understood my talk. I thought I was talking like a million miles a minute. At another point I asked how long it had been and they said like twenty minutes. I was not sure if that meant I had talked for that long or that was how much time I had left.

I got to questions around 8:14 PM (I looked at the computer clock). I guess I had kept the presentation to close to an hour, since we waited a little bit because of the poor weather (snow with rain at rush hour). During the question time I took two photos of the audience of about 50 or 60 people, while someone was answering an audience members question that I had no experience or answer for.

After the talk and then at Cafe Asia everyone I talked to really like the presentation and had only good things to say to me about it and this was other people than my friends.

Now for the general overview of my talk, for those that might have missed it.

  1. Explained a few personal stories of why I’m so passionate about accessibility. One being seeing all the soldiers that come to Pentagon from Walter Reed Medical Center. Meeting Pat Pound at the Knowbility booth in Austin, TX at SXSW 2007. Also having Charles L. Chen show me his great free software, which are two Firefox extensions. One being a page reader called “CLiCk Speak“and the other being “Fire Vox“, which is a paired down screen reader.
  2. The next section was on using “Skip Nav” and “Access Keys” and how useful they are to people that need them.
  3. After that I then talked a bit about the “Color and Contrast” of website and that Text plays an important part of usability for everyone that is sighted.
  4. It was then on to how to build proper data tables by having a “Summary” element to explain what the table contain, along with a “Caption” of the table instead of having header in front of it. The final piece about tables was that you need table headers and then information on you cells to identify what pieces go together.
  5. We got into the longest section of the talk which was about “Forms”. I explained that you need “Fieldsets” and “Legends” to group similar content together and say what it was. The next idea was to put “Labels” and “Input Controls” in either “UL” or “OL”, so screen readers will tell you how many items are there and people will know how many fields they need to fill in. I also explained all the other “Input Controls” in a form and their attributes.
  6. I explained how the “Search” box needs to have the word “SEARCH” in front of it so you can tell what it is, along with using the word “Required” on fields. This is done using the same technique that you used for “Skip Nav”.
  7. The last thing I talked about before questions putting error messages in the label, such as “User name can not contain spaces”.

A lot of the slides have examples of code or links to other articles or my examples of items in use.

The busy technology week did not end with my “Accessibility” talk, no I attended the “DC Adaptive Technology“ talk at the MLK library Saturday afternoon. Because of the issues with Metro maintenance I was not able to stay for the whole talk. The part I did see was about using “Dragon Naturally Speaking“ some scripting code to allow people with visual issues to use Microsoft Word and other products much easier. It was cool watching the guy giving the presentation talk into his microphone and then seeing the words on the screen. By using certain commands he could start, stop, or edit the files that he was in. He could even get software to open and close.

This has been a long week in technology for me and it probably will not be the last one like it. I have also been working on a few different accessibility blog posts to be posted in the next week or so.

Please tell me of similar weeks like this you have had or if you enjoyed my presentation.

CLiCk Speak Firefox Extension

Last year while at SXSW 2007 in Austin, Texas, I spent some time at the Knowbility trade show booth and talked with a young man by the name of Charles L. Chen about his Firefox extension CLiCk Speak. I have found this extension to be every useful to me in that it allows me to listen to what my web pages sound like to a non-sighted individual. It does not have all the features of that the major screen readers like JAWS and Window-Eyes have, but CLiCk Speak at least let’s you hear the information on your pages.

The following text is an overview of CLiCk Speak from their website.

“CLiCk, Speak is designed for sighted users who want text to speech functionality. It doesn’t identify elements or announce events – two features that are very important for visually impaired users but very annoying for sighted users. It also has a simplified, mouse driven interface that is designed to be easy for users familiar with point-and-click graphical user interfaces. Like Fire Vox, CLiCk, Speak works on Windows, Macintosh, and Linux; and Fire Vox has multilingual support, making it great for users who are trying to learn a foreign language and need to hear foreign language web sites read out to them for practice.”

CLiCK Speak buttons in order left to right are 'Speak Selection', 'Auto Speak Mode', and 'Stop Speaking'

The three main features that I have used is the one that just reads down the page from the beginning of your code, so source order does matters, after pressing the “Auto Reading Mode” button. Next it has a “Stop Speaking” button so you can stop it from reading of the page whenever you want to and just push the “Auto Reading Mode” button again to resume from where it left off. The final feature is where you highlight a section of text and click the “Speak Selection” button and  it will only read that part of the page. I could see this as being useful to read a part of the page that you have just updated and wanted to make sure it sounded good. Another advantage to the highlight and read text feature is that if you wanted to go to lets say ESPN.com or CNN.com you could have it read you the article or sport scores, while the browser window is only showing in the toolbar at the bottom of your page. That is if you have headphones on, so no one finds out. It could be used by people that have English as a second language to learn English, since it also highlights each sentence as it reads them.

Charles L. Chen and company have another Firefox extension called Fire Vox. From what I have read this one is more like a normal screen reader.

The following text is a summary from the website.

“Fire Vox is designed to accommodate different users with different needs. For visually impaired users, all Fire Vox commands are keyboard activated. In addition, the keyboard commands can be easily reconfigured in the self Fire Vox Options menu to avoid conflicts with other accessibility software products or to suit personal preferences. For sighted users who need a screen reader, such as web developers interested in testing their webpages or educators who work with visually impaired students, Fire Vox’s highlighting feature makes it easy to keep track of where it is reading from on a page. This highlighting feature is also useful for dyslexic users and partially sighted users.”

While at last weekends DC Adaptive Technology meet up I talked with Patrick Timony about another free screen reader, that is called Thunder, which is free.

I have not tried the Fire Vox Firefox extension or the Thunder screen reader yet, but I plan on trying them out in the next week or so and will report back on what I have found out.

I hope these products are helpful to you in your work and can save you money by not having to get JAWS or other expensive screen readers that cost  hundreds of dollars.

DC Adaptive Technology Meetup

I found another great meetup by using Ross Karchner‘s DC Tech Events website.

This one was the DC Adaptvie Technology meetup that was held at the DC Public Library in Washington, DC. The event was on Saturday December 1st, 2007, from 1:00 PM to 5:00 PM in room 215 at the Martin Luther King Jr. Memorial Library. The Saturday Technology Trainning sessions are usually for users of Adaptive Technology like the JAWS screenreader, the Zoomtext magnifier, and anything else that is technical and useful someone. They are usually held the first and third Saturdays of each month. No, meeting the third Saturday of December because of the holiday season. These meetings are normally run by Patrick Timony.

ICON PDA is a device that allows individulas with visual issues to listen to the web, podcasts, etc.

I was one of only a few sighted people at this meeting, which had about twelve or fifteen people. This meeting included a demonstration of the ICON accessible PDA, a braille reader, and how to use the new Mac OS (Leopard) for better accessibility given by David Poehlman.

David showed everyone how to use the ICON PDA by LevelStar. This device which is the size of an old style manual light meter allows people to use the following tools a calendar, an address book, a music player to listen to music or your favorite pod casts, allows you to take notes yourself with the voice recorder and journal, and stay on top of your world with a word processor, web browser, and email. This device has wifi/wireless and comes with a comprehensive menu of pre-installed applications , 30GB hard drive, and Bluetooth® built-in.

Next, he showed a braille reader that you plug into your computer or I even believe the ICON PDA. Finally, David demonstrated how you can have the new Mac OS be turned on to read everything out loud to you. I forget how he said you turn it on.

ONYX Desktop 17 inch Closed-Circiut TVAfter David got done Jerry Marindin of Freedom Scientific showed everyone how to use the new ONYX Desktop 17 (Closed-circuit television) CCTV. This device allows people with visual issues to magnify papers, books, maps, etc. It also comes in a model that does not have a camera, but plugs into your computer instead. With the remote control that comes with it you can zoom in or out on a document, flip the camera up to point at things in the back of the room and then zoom in on them. This would be great for people at meetings or classrooms that can not see distance. It also allows you to change the color of maps for those that are color blind. You can change the color contrast so if white text on a black background works better for you then you can do that.

pageof text under ONYX CCTV device

I mentioned to Jerry during his presentation that the image under the camera was upside down and he said “I will show you later how to fix that”. He was then able to use the remote to flip the image on the screen to be flipped the proper way that you needed it. He mentioned that when he brought this producted to a meeting a while ago that one of the blind ladies mentioned that the remote when in audible mode said to push the “RED” button. She said what if I can’t see or if I’m color blind. Jerry took that information back with him the company and they fixed that problem. Now the remote says something like “Press the red button in the upper right corner of the remote”. See what happens when you test with really people, you find out things the engineers dont’ think of.

txted zoomed in by the ONYX CCTV device

I learned a bit more after the meeting was over by just sitting and talking with the people that were still there. I asked some questions on what type of things bothered them on the web. It seemed the items that gave them the most grief were forms. Either the form had poor instructions or ones that were to long. They wanted to have short understandable instructions of what the form was for and what type of informtion went in the fields. The other things that bothered them was not telling them that a field was in error until like ten or so fields later or at the end. The one woman said she would like to know as soon as possible when things are incorrect, so she can correct it.

When I left the meeting I asked one of the people still there if they wanted help or they wanted to follow me out to the metro, one woman said sure. I had her grab my arm and follow me out. While getting to the metro I was trying not to tell her to go right or left or whatever, I figured that she would know were to go by where I was leading. She mentioned that at times people will yell “STOP” while she’s out walking somewhere. She was like why should I stop when I don’t know who you are anyway and why should I be stopping. The one other thing she mentioned when we crossed the street was the noise that some of the new crosswalk lights make is really annoying. I asked is it because it does not allow her to hear the traffic and she said “Yes”.

Two other things that I thought was interesting was that Patrick gave out two different agenda lists. One for sighted people that had really big text and one for non-sighted people that was in braille. The other item was that both Patrick and Jerry had business cards that were normal on one side and on the other used big blocky text, one card even had braille on it.

In the end I learned a few things, met some really nice people, and it gave me something more to think about while making my web pages more accessible and 508 compliant by using web standards.

So if you get chance go check out their next meeting, I plan on being there and will post when it is after the holidays.