This is a response to my Blog post about Linux accessibility. I wrote it in response to another comment. It turned into a bit of a long one though and the information is applicable to a lot of things. So, have a read of this:

KDE is based on QT and Gnome is based on GTK. It's important to recognise the differences in these environments from the start. QT doesn't support AT-SPI. It was planned to support this but it never happened. This is down to a decision by the QT developers.
Here's an article that discusses how Gnome communicates with Orca. http://accessibility.kde.org/developer/atk.php

There's information about the accessibility of QT packages at http://doc.trolltech.com/4.5/qt4-accessibility.html

GTK is not the only standard for the graphical desktop manager in Linux. QT is just as much of a player. That's where the problem comes in. Any application that is written for Gnome and follows the Gnome development guidelines will communicate the necessary information to Orca. The problem arises when you launch a QT based application such as Acrobat reader as Orca doesn't get the required information from it.

I understand your point about the limited progress in some areas due to developers not making enough progress with their compliants with the accessibility guidelines but tell me one platform where that isn't an issue. It's nothing to do with communication. It's a problem with bad coding. Simple.

In relation to the problems you have encountered accessing applications that run as root in Ubuntu, there are a number of well documented fixes to this. Basically, Orca, like every other Linux application can not obtain information from a process running as a more privlidged user. This is the reason why Linux is such a secure platform. However, there are work arounds to this as I said earlier. In fact, Listen to one of the recordings in the Linux section of www.lalrecordings.com and you will hear one of the ways of getting around this. In Vinux, the environment is preconfigured for optomal accessibility. Perhaps you should try this out? You might find that with the environment configured to provide the most accessibility, most of your issues are resolved. If nothing else, it will illustrate to you that on most distributions of Linux running Gnome, problems can be ironed out if your willing to spend some time on configuration.

I'd also suggest you read http://live.gnome.org/Orca as I'm almost certain that you'll find an alternative and accessible PDF reader. As for skype, use the plug in for Pidgin. I would bet that you will not find an application that doesn't have a gTK counterpart in LInux. There are very few things in Linux that you will not be able to access if you keep at it. Just like the same can be said in windows or even OSX if your that way inclined.

I really hate talking watches with a passion. Their evil! Their horrible! Their the embodyment of everything that is evil in the world. Why? Well, I'll tell you.

• Their loud. Imagine this. Your sitting in a quiet office. people are typing on their computers around you and you want to find out what time it is. This booming voice shatters the silence by screaming out: "THE TIME IS NOW 6:15 PM!!!!!!!!!" Everyone in the office turns and gasps at this distraction and you go bright red with shame as a result.
• They talk too slowly. You need to know what time it is and you need to know now! You press the button and in it's booming voice, it screams in the slowest voice ever, "THE TIME IS NOW 6:15 PM!!!!!!!!" All you need to know in a hurry was that it was a quarter past 6, but by the time it's finished, it's now twenty past! Ok. that's a huge exageration but you know what I mean.
• Their big and clunky. A talking watch on your arm is like having a huge sign on you saying to people, hay! I'm blind! and I love my talking watch! Listen to it roar!

OK. right. so my hate of talking watches is now known. People, please buy a braille watch. Their much better!

I've been doing a lot with virtual machines this week. Virtual machines are basically computers within a computer. That's really the easiest way of explaining it. The Virtual machine application I chose was VMWare workstation. So, installing the VM was absolutely fine. you'll basically create the VM, decide the virtual machines specifications and when you boot it, it's like booting a normal computer. You'll have to install an operating system and configure it. Fortunately though, installing drivers is usually a non issue as they'll automagically be picked up from the host. The strange things I've come a cross so far are as follows: When installing Jaws, it took two reboots for the mirror driver to be installed. After this, the procedure continued as normal. Authorization etc was as you'd expect on a normal installation of Windows. One non-accessibility odity that I've found is that while in the virtual machine, the power saving settings of the guest still continue to take priority. That means that the machine can suddenly go into stand by even though you have been using the guest continually. OF course, it's not really a problem. Either go to exclusive mode in VMWare or change your power settings. On the first machine I installed this environment on I had huge problems getting the virtual machine to except the installation of Windows XP and then, when I finally got it working, the host couldn't resume from stand by. I think this was as a result of something wrong with that computer though as when I recieved it first, it wouldn't boot until I removed the keyboard and mouse. Some of the windows and reboot issues seemed like ACPI problems too so I switched the disk into a different machine with the same spec and it all worked properly. Interestingly, I would have expected Windows and Jaws to need reactivation when I changed the disk into the alternat PC however both continued working without any changes at all.

I will admit straight off that these are my findings and opinions after only a brief time of using Fedora 12. You may have different results or find that things work better. But, let's dive straight in. Was the installer accessible? No. Not from what I could tell. The live CD ran for me but obviously, it would require a log out for the gnome accessibility settings to be applied so in a live CD environment, that's out of the question. When trying to make a USB live environment, the system loaded, I applied the gnome accessibility settings however after a restart, the USB key would not boot. It's surprising and currently unexplained, but I'm not sure why it suddenly stopped booting after I made a minor change that shouldn't have anything to do with the boot process at all! I also made sure to leave enough space available so as retaining settings and a limited amount of files was supported. So, to install, I needed to get sighted assistance. Fortunately for me, that's no major problem. After installation, the first thing I did was install ESpeak. That's more prefered for me compared to the default of festival. This was incredibly simple. simply type the following command: yum install espeak gnome-speech-espeak That's all there is too it. Obviously, you need to be logged into the terminal as root for that to work for you. After you've downloaded and installed Espeak, restart Orca and select ESpeak as the synthesizer. I'll probably install TTSynth at a later stage so when I do, I'll write instructions for that here. I've some very interesting things to report in Linux in relation to a comparason with the off screen model used by Windows based screen readers, but again, I'll leave that until I've had more time for testing.

In the previous incarnation of this blog I wrote about the KSonar, a mobility aid for people with visual impairments. This hand held device uses ultrasonic waves similar to Sonar found on boats to detect objects within its range. It then provides an audible notification of these obstructions in a form that relays to the user the distance between the object and the device, the solidity of the object and it’s motion or lack there of.

The KSonar has not been widely adopted by users who are visually impaired as it uses an ear piece to provide this feedback. It is feared by the majority of people that this will obstruct the normal environmental noise that people who have little or no sight depend on to make decisions that assist them in making choices about navigation. This fear is justified! The loss of detection due to an ear piece blocking sound from any direction could cause a person who can not see to misjudge direction or worse, misjudge traffic.

The KSonar comes with a stereo headset that would indeed decrease the volume of external noise. In my opinion, although the sound from this supplied headset is great for differentiating the differences between sounds emanated from the KSonar, it is a poor choice. It is more important to hear external noises than getting feedback from the KSonar. For this reason, I suggest purchasing a different headset.

It is claimed that the KSonar emits sound in stereo. However I did not find that this was the case. Using one ear piece is therefore adequate. Purchasing an ear piece with silicone inserts that fit in to the outside of your ear canal is best in my experience. The ear piece I bought has great clarity and range but it can be worn loosely so that only a minimal change is made to external environmental noise.

Another reason that most people are put off using the KSonar is its learning curve. It is necessary to allot some time to learn what the small changes in output mean. I found that walking around the house and office scanning my surroundings was a great way of determining what each sound meant. When I found something that sounded different, I’d follow the sound and touch it. For example, I found that the internal partition wall sounded different to the bookshelf in this office. The window sounded different to the radiator. The carpet sounded more muffled than my dog’s bed. It took time but slowly I began to build up recognition of different objects. As you become accustom to what each surface sounds like, you become aware that there are hidden noises. For example, if scanning my shoe, I’d hear a secondary noise for the carpet to its left and right. This takes a little more time to learn, or at least, it did in my case, some may find that they catch on much more quickly!

When learning to walk with the KSonar, things felt much different. Not alone did I have to concentrate on listening to everything around me, I had to train my self to stop when something got too close. Unlike walking with a Cain, there’s no tactile, tangible or physical blocker making you immediately aware that there is something in your way. The KSonar will give you the sound but it’s up to you to learn what those sounds mean and to become practise so that the necessary alarm bells go off when you’re too close to something.

It is certainly difficult. There is no escaping that for the first while it takes a lot of concentration and commitment.

After the first learning curve, things started to get much easier. When walking outside, I found my self listening less to what each sound meant and more to the pattern of the audible waves. When the pattern changed, I listened more intently to what it was that I was approaching. When I was coming close to something that was likely to be a barrier, I switched to short range so that the device provided more definition. When walking with the cane, the change in the pattern would cause me to be a bit more careful and slow my pace thus decreasing the extent of the impact between it and the object and allowing me to continue past more efficiently. When walking with the dog, I again used the pattern as a marker for objects around me. With the guide dog, the KSonar is less a mobility aid and more of an information gathering tool. For example, when walking in a new area, I can tell if there is a grass verge on one side. Although my dog isn’t distracted all that much, I know to be aware that grass is around within easy reach so if it has just been raining, there’s going to be more of an attraction for him there to sniff so I can be on my guard. I can also use it to find traffic light poles and other useful land marks.

It’s therefore a pity that the aid is not used by more people. Sure, there is a lot to learn but it’s justified and of major benefit. Just some of the tips that I have are as follows:

• Put the ear piece connection down the right sleeve of your coat. This way, you can easily unplug the KSonar when necessary for storage in your pocket using only one hand. This is perfect when being led by a sighted guide or a guide dog. It also keeps the cable out of the way when using a cane.
• If using the KSonar independently, move your hand in a circular shape scanning more to the left and right as you do so. This will scan ground level, and around head level as well as catching objects on either side of you.
• If using a cane you are restricted to only scanning left and right. However, when navigating steps, I find tilting the cane more than normal gives better differential in the feedback provided by the KSonar for finding steps before the cane does.
• When using the KSonar with a guide dog, use a cross shape as your movement. First go from left to right then in the middle scan from ground to head level. This ensures that your dog is not scanned and saves confusion.

So, why bother with a KSonar? Here are a few of the reasons why I find it handy to have around on a day to day basis:

• When walking in a building with wet paint, it is easy to find lift buttons. Simply scan for the sound associated with the metallic plate and reach for it. This only comes to mind as our office was painted this week.
• When taking my guide dog for his daily walk in the park at lunch time, I like to give him some freedom. He’s been following orders for the entire morning so it’s good to let him have some time to unwind. However, I can’t let him off. It’s just not safe to do so in that area. By using the KSonar, I can put the dog on a flexi lead and follow the path. I can also scan around the area he’s sniffing around.
• My favourite one. This always has people guessing: When in a pub, hold the KSonar just above the bar. IF the bar staff keep passing you, you’ll hear the sound as if you had just passed your hand over the sensor. Wait for the sound and call out in their direction. I don’t know how many times that has worked for me!
• Some of my day to day job involves visiting other buildings and other offices. It’s important to be as independent as possible so when I go to an office, I discretely use the KSonar to pinpoint the desk in the room so I can give my dog the required commands to find it in that general direction. It’s also great for finding chairs in meeting rooms.
• On Busses and trains, it’s incredibly handy for finding free seats.
• For disposing of rubbish in parks etc, it’s really handy for finding bins then the exact opening. Therefore limiting the amount of contact you need to make with the bin. That’s great when some bins are disgusting!
• In hotel rooms, I’m sure you’ve spent time getting to know what’s around you. What’s mounted on walls, what’s in the bathroom etc. The KSonar makes that much easier.

There are more advantages that I could go into but you get what I mean.

The KSonar cost me about €600. Although that’s expensive, in my opinion, it was worth it.

Over the past few days, I’ve learned far more than I ever wanted to learn about Drupal themes. A website that I’m working on needs to conform to W3C web authoring and accessibility guidelines. This has meant that I’ve had to jump through all sorts of hoops to make Drupal, what I thought was a very clean content management system, display content in a very accessible way. I’ll not claim to be a Drupal expert. There are a lot of really smart Drupal people out there who can tell you how everything fits together. But, the problem is, there seems to be very little documentation for those of us who have joined the party late. Up to version 6, I really had no idea how all the parts of Drupal fit together. The last time I used Drupal was 4.7 about three years ago. Back then, I didn’t really need to do anything that involved diving into the code of the application and from what I gather, it’s a lot more complicated now than it was then! Now, when I want to do something, I can never be completely sure what is calling the function I want to use or where the theme is even putting it. Object orientated programming is fantastic and using functions to only call something once is really the only way to develop something properly but when you’re coming at an application as an outsider, it can be very difficult to trace through what’s happening from the top down. Take the read more link for example. That breaks web standard guidelines for accessibility but what the hell generates that link! Where is the function that it’s created in? I’ve no idea! So, as a dirty hack, I have to put a Claus at the top of the template so that if it sees a specific link that contains the read more text, it recreates that link with the read more text as well as the title of the current node. But even with this I have problems. By default, the home page doesn’t set the title variable to anything so I have to have a clause before this that first checks for the existence of the title variable, then checks for text in it. If no text is found, I have to put the title of the home page in it then move onto the next check. The other problem was the Drupal formatting of this read more link. For some reason, it was in a list containing one item at the top and the bottom of news items. This was visually ugly and from the perspective of a screen reader user, it created unnecessary clutter. There is a Drupal module for fixing this actually but when I used it, my little hack for inserting the title into the read more link no longer worked. I did some tweaking but still, although I can change the text, the title variable does not seem to be exposed to the new module. So, I’ve more work to do on this. I may need to request the assistance of the creator of this module if he’s willing. My latest problem is with colours. I’m using a great theme that’s customized extensively to meet the needs of the users of this site. But, although everything is almost finished, to make the site comply to these W3C guidelines, I have to add the option of making the site high contrast. This means that the text would really stand out from the background to make it easier to read. The problem is, there is no clean way of doing this in Drupal. The colour module just doesn’t cut it. After some looking around, I found that another user had successfully used a different style sheet for the same theme to create the high contrast look however these tips were for an earlier version of Drupal and things have changed since then so I couldn’t figure out how to apply his suggestion to the version of Drupal that I’m running. So, my only alternative that would provide this functionality to anonymous users as well as authenticated users was to create an entirely new theme that was modelled on the original one but that had the high contrast colour scheme. After a few hours of work, this is finally done. I’ve got the theme working for authenticated users because Drupal provides the change theme functionality within the user profile page however, it’s not easy enough to use yet. I’m still looking for a better way of changing between themes for both authenticated and anonymous users. I’m looking for something that will sit in a block on every page that has a toggle link for normal or high contrast depending on what is currently running. I think I may have found a solution, but again, it requires more work. I think it’s time I stop working on unpaid projects. Ha! Did I not mention that? All of this is being done for nothing! But, in saying that, I offered. So, there you have it. The joys of working with Drupal.

So, the much anticipated Jaws 11 release is now out and the public beta is over. there's nothing much to say really. I'll have to upgrade because I want to use Windows 7 so I have no choice really as moving to an alternative screen reader isn't a viable alternative. They just don't tick all the boxes Jaws does. Much to my dissapointment by the way. So, Here's the link. http://www.freedomscientific.com/downloads/jaws/JAWS-whats-new.asp

So, the Jaws11 testing fun began today. I've found a few things so far that have already been sent via the bug reporting to FreedomScientific. It would be great if Jaws had an error reporting tool built in similar to that found in Window Eyes by GWMicro... But we can only live in hope. They've boasted that they've fixed a lot and added more features in this most recent version but I'm not impressed. In fact, I'm really unimpressed. Research it... A tool that cant even stand up to Qwitter, a tool made by a few people working in their spare time. No reflection on Qwitter, I think it's a fantastic piece of work and if FS had any sense, they'd snatch up the developers behind it! Qwitter pulls back information via API's and does loads with it. FreedomScientific reads an XML file and gives the information back in the virtual buffer! And even with that, they've only worked on a few feeds that are only of particular interest to their American customers. Utterly Utterly pointless if you ask me and as Stuart Lawler said today, is that really the job of a screen reader anyway? When they cant even provide access to widely used applications should they be thinking of branching out into this type of functionality? Not that I think this took them much time at all. It was probably a small project by one person to tick a box leading up to the release schedule for JFW11. Lets also look at their placemarkers enhancement. They've basically coppied the work done by GWMicro in Window eyes. Their basically searching for text / pointers on the page to find the place you want. So, their not just relying on the line number alone! well, well done FreedomScientific! It only took you two years to think of that? Wow! Next, look at their outlook message list customization. So, they've just rehashed the customize list view tool to provide a bit more customization. And they've released that in an entirely new version? Aren't they great? Shouldn't we be ever so greatful for all the work they've done on this release? OH. Then they actually admit that this is really similar to their customize list view feature. It just gets better and better. Their skype enhancements. Well, from what I can see, their skype enhancements are a load of rubbish. I'm running Skype 4.1 here and when I checked what scripts were running it said 3.x. Now, I don't mind this too much. I know I can go download the version 4.1 scripts from the third party developer who I also must say has done a fantastic job on them but they've written it there on the page that they support version 4.1. Not from what I can see though. Jaws 11 now also supports UIA, the standard that has taken over from Microsoft Active Accessibility. This is something that has been out in the public domain for almost three years if not even longer than that. Microsoft have had that ready for companies like FreedomScientific to start working with since before they released Windows Vista! It's amazing that their only supporting that now. I could go into more but I'm not going to bother at the moment. I'm not entirely annoyed with Jaws 11. There are some good features as well. The multable sound card support has been improved and jaws sounds during jaws tandem was improved also. But, I dont' really understand how it took them an entire year to release what should have been done in the first place. If your interested, You can follow the Twitter updates by a number of Jaws11 users via the following link: http://twitter.com/#search?q=Jaws11 Have fun.

I think it's fair to say that users of screen readers await new versions like a child awaits Christmas. It's always great to see what's going to happen next. What technology will be made accessible this time? What will they think of this year. will they fix the problems that we found in the last version. There are just so many things that can happen. Of course, I for one usually get let down. There have been problems with the support of Lotus notes 7.03 and 8 in Jaws for over three years now. I've also had problems with Jaws while using firefox and it doesnlt look like these two things will be fixed any time soon. However, my gripes aside, I'll still download this Beta of Jaws 11 with the same anticipation and hope as I've done during every other version.

Visit the FreedomScientific.com website to read more and get the download. You can also listen to FSCast with Eric Damery and Jonathan Mosen for a nice overview of the new features you can expect in Jaws 11.

As always, I'll provide updates and problem reports here while the beta is still out there.