The AccessCop Network

Now that I have worked a bit more with Window-Eyes, I thought that I would share with you some more of my observations.  Last time, I had mentioned that I planned to look at the performance of Window-Eyes with the Office 2010family of products.  I still have to take a look at every feature of them comparing the two screen readers, but I will, for this entry, focus on my experiences with Window-Eyes and Word 2010.  

One of the more striking things that I have discovered during my time using the two programs together is that some of the features that seem to be available in JAWS don't seem to be available yet to those using Window-Eyes.  a prime example is when an author opens a document in which either they themselves, or someone else has added comments.  Comments are a great way for multiple authors when working on a document to colaborate and give feedback.  I find their  use an integral  part of my own education since my professors use them to provide corrections on essays, scripts, and papers.  The big problem with them that I see when using Window-Eyes and Word 2010 together is that the choices in the right-click context menu pertaining to their manipulation are not read by Window-Eyes, but they are read by JAWS.  (for those who are unfamiliar with what I am talking about, when you have your cursor positioned at the beginning of a line that has a comment in it, and you right-click, two additional choices will appear in the menu that pops up.  They are: delete comment and edit comment.)  I find this rather odd, and I intend to mention it as a support request to GW Micro.  Having this problem could really inhibit the productivity of a blind employee who depends on feedback via this method from their boss and co-workers. 

Another interesting thing that I have found between JAWS and Window-Eyes when working with Word 2010 is the stability of each when working in the spell checker.  With JAWS, the result is   always the same; stability without problems, but with Window-Eyes, it is much different. When a person tries to spell check using Window-Eyes as their screen reader, it may work fine; reading all pertinent information, or it might not, either reading nothing, or reading the information in a very fragmented manner.  Questions have come up a lot on the mailing lists at GW micro regarding this particular topic, and different individuals say different things.  I for one thing, have not had a very good experience with it at all; always switching to JAWS whenever it is time to spell check a document.  Well, till next time, be waiting for my thoughts on another member of the Office 2010 family.   

I cannot say anything for sure yet because I am just getting the experience myself, but for now, just know that I have been doing some comparative reesearch to figure out which screen reader is best for a blind Windows Admin in the increasingly high-tech IT world.  I have been looking right now at two screen readers; JAWS for Windows 12.0 (one version earlier than Freedom Scientific's currently released version 13), and Window-Eyes, from GWMicro.  I have seen some crutial enhancements in the latter  which the former lacks, most of these in the category of application stability on a general scale.  Yet it is very difficult to decide between the two in certain criteria since they have their strengths and weaknesses, advantages and disadvantages.  But what I am most concerned with right now are the uncommon, administrator-only applications most commonly used in corporate environments today such as virtualization technologies, and most other server-side products such as Sharepoint Server 2010, MS SQL Server 2008 R2/2012 (I haven't tried the third CTP since I would rather wait till the final release), and Office 2010. 

I have discovered that in terms of most of the above, Window-Eyes is much more stable, in some cases reading more than what I get with JAWS, and at other times, simply reading an equal amount of information.  The big kicker here though, at least I think, is that with Window-Eyes, one can write their own scripts for any particular application that does not have default support for the screen reader in any programming language including those supported by the .Net Framework.  JAWS allows for this as well, but only for scripts written in a propriotary language that is hard to learn, examples are limited and often silly and unrealistic, and it cannot use Windows .net framework classes or Win32 APIs in the scripts, making for very limited support of anything that falls a bit far from the mark of normal programming practices.  And UIA, you ask?  Well don't.  Because the use of WPF is not one of the strong suits of JAWS for Windows.  In terms of working with virtualization technologies, I have been experimenting a bit with VMware vSphere, yet I haven't gotten Window-Eyes to show a single console to a single VM.  I will be asking the GWMicro community about this since the support staff tell me that they have seen it happen and I do not doubt it in the least since they are very aware of the needs of our community that come with changing technology.  I have not gotten to test out either MSsQL Server 2008 R2, Sharepoint 2010, or microsoft office Access 2010 yet, but I will keep you updated in future blog posts in this series. 

                All those who love Microsoft’s web technologies are aware of their web Platform Installer.  I use it for various things, such as testing to see if certain technologies will work with a particular operating system, installing and configuring different web applications (Mojo Portal is available, just for everyone’s information), or just checking out the available apps to see if any of them will come in handy someday.  This tool was never quite accessible all the way through for screen readers simply due to it’s layout, but upon the update from version 2.0 to 3.0, things have gotten even worse in that regard.  But, no one, whether sighted or not, should worry about anything ... CMD comes to the rescue!  Microsoft has put on their official IIS site (Official Microsoft IIS Site) a blog entry that gives an overview of this tool, and there’s more on MSDN.  And not to mention, in a way, this tool is probably faster since once the commands are entered, things just happen and also in some instances, text without all of the graphical fluff getting in the way really helps folks who want results quickly check their progress.  You can download the tool WebPiCmdLine tool download link.  Good luck to all those who want to have an easier time using Microsoft’s web technologies.

Years ago now, I had made an attempt at using iTunes for Windows, when JAWS was only in it's eighth generation.  Now here in 2011, I decided that after Apple shaped up and made their files unprotected, using only the .M4A filetype, which since it is a variant of the AAC format, can easily be converted to regular mp3, WMA, or wav format.  I had to recreate my account considering my former credentials had been long gone for a very long time.  It's difficult all the way through for screen reader users since your normal navigation keys don't work.  You have to make sure that your cursor for no reason whatsoever lands on an edit field unless you have tabbed over to it.  otherwise, the program will throw you back at the desktop, and then you have to find your focus all over again.  Then there is the issue of tackling the comboboxes for your birthday.  You must use your ALT + Space command (as if you were accessing the menubar) to allow for date selection.  Then double click (AKA use enter), on the correct month and date.  just a little issue, and my way for folks using keyboard navigation to get around it.  Hope it helps!

For this entry, I give our very own Ann Seavey credit.  As the Academic Support Center Director at Gordon College in Wenham, Massachusetts,  she made a very good suggestion to me in terms of universal design when it comes to accessibility for blind users.  There are various situations where this concept could work very well, but the two most notable are the fact that Java on the Windows platform is an integral part of the Gordon College network; being used for their support ticket request and tracking system.  This has rendered lots of issues for a few of the blind students who have done their best to work the front desk there.  Most of the time it involves those using the JAWS for Windows or Window-Eyes screen readers.  Ann and I talked about some potential ideas for trying to help solve this problem. 

Another very prominent place where universal design would work great in the Gordon community is in terms of trying to tone down the constant Mac Vs. PC war that never seems to end.  Issues can arise in terms of compatibility, range of support for both opperating systems, as well as accesssibility.  Most of the time professors are trying to work with PC users when they use a Mac, which makes it hard on the user if adequate support is not able to be provided due to the professor's comfort level.  Ann and i also believe that something needs to be done with this.  We have proposed the idea of a system where everyone knows a bit of both to at least help mitigate the support issues.  I'll keep you updated as more comes up on this situation. 

A few weeks ago, I got the opportunity to try out the new Windows Live Essentials 2011 offering from microsoft.  from a feature standpoint, it's one of the best free offerings they've come out with, but accessibility's a very different story.  For those who use System access from Serotek as their primary screen reader, your best bet is either, if you have a subscription to the SA Mobile Network, to use the socializer offered in the package since the new Windows live is completely inaccessible with the software, or to go to messenger.live.com and use the web client that is offered by Microsoft for those who prefer not to download software onto their computers.  But, on the other hand, there is a trick for those who use JAWS to make the new Windows live a bit on the friendly side.  When the program finishes installing, and messenger is the selection made, then you'll be presented with a screen that asks you to connect other services such as facebook, youtube, and myspace to Windows Live.  Connect them if you want by following the prompts, but otherwise, click on social highlights, then tab till you find the button labeled change view.  Default is selected, activate the button to switch to compact view then you'll be able to see all of your contacts.  Be aware that JAWS might struggle a bit to focus on the links and buttons.  I do not know why this occurs, but when I find out, I'll post back with another blog with my findings.  Well, have fun with these new programs!

As is our mission, we will do what we can to get companies, organizations, as well as individual developers to make their programs accessible to all parties using them.  I've seen so much of this, and still it often seems like folks don't care one bit once they've decided on a development plan for their programs.  It is clear that often times, the blind folks are not thought of at all.  This has been the case for many years.  Though things have improved greatly since the 1990's, there is still much work to be done in terms of accessibility standards.  Though there is the ADA, as well as 508 compliance for web sites, it seems that too many folks are getting away with not following such simple rules.  I can understand that some folks, like big corporations, they might not have time to deal with that, but if the smaller companies could, it would be a step in the right direction. 

One problem, or misconception, I should say, that most people have is that it takes a lot more money to make programs accessible out of the box.  In some situations, yes, indeed that might be true, but for those who develop in .net and use the tools that microsoft has kindly offered for this purpose, they are all set, and no extra money needs to be paid.  Visual Studio 2010, both the free express version as well as the paid-for professional version, has beautiful property dialogues where one can edit the labels of buttons, menu items, and toolbars.  The really fascinating thing about this is the fact that no code needs to be typed into the code edeitor window to make these changes take effect.  For those of you who prefer to code everything by hand, which is quite a few of us these days, you do have to worry about the code behind the formatting.  I want to tell you that I am most experienced (with what little experience i yet have), in .net, so most of my programming comments will be based on those languages.  This is just an example of how easy accessibility is to implement in programs.  There are even ways to make custom controls accessible and natively readable by screen readers, and as I learn more, I'll blog more about that in the future.  Keep an eye out! 

For those who don't know me this is Ashley here, one of the original founders of the Raeder24 Network. This entry is just the first as an introduction to the random crazy stuff that goes on in my life.

I had recorded a few things for someone on the Braille+, whitch, although it has its glitches is a pretty decent device. The other day I was trying to take those folders and put them on my computer so that I could send them over skype to the person they were intended for. Sounds easy, doesn't it? I mean how hard could moving files be? If you operate a computer but can't move a file, then... I really don't know what to tell you.

The device comes with this cable so that you can either charge it in a wall charger or plug it into USB and charge using your computer. I was going that route, because if you plugged the device into the computer it would show you it's files just like any other device. This time however, it charged fine but it wasn't showing up what so ever in my list of drives. So then I decided, fine, I'd set up my FTP server and upload them to my computer that way. But, fail once again, because I couldn't figure out how to FTP on the braille+. If anyone knows, please do tell.

Finally I realized that the very same cable I was using also had another port on it. To me it looked like you could plug a thumb drive into it and use that as another drive for the braille+. I plugged the drive in, and thankfully everything recognized. So I took the files, put them on the drive, took the drive and put that in my computer, and then sent them. Three and a half hours later, I finally had my files.

We must apologize for the delay in content being added to the site in the past month.  as all of us are very busy seeing that 2010 has almost come to a close, I am now glad to announce that Mojo Portal has been updated to the latest version, therefore, the security vulnerability affecting logins has now been mitigated.  Everyone can now log in and feel secure again. 

 Remember how I said that there are musicians in this group?  Well, I'll tell you about my very nice experience on August 1st.  I had gone to a church service with some folks, and I was invited to play the piano for the entire congregation.  I was so embarrassed since it seems like years since I've gotten the appropriate amount of practice since school has been so busy, and not to mention, I've been away from a piano for a while now.  I played anyway, despite this, and though I'll will tell you that my performance was nowhere near perfect, everyone was just happy to hear me play again.  So my point?  You can still make folks happy even without perfection.  Community is not concerned with that.  Or, I should say, at least not in that environment.  Keep that in mind. 

As a person who loves technology, loves windows and all of the other microsoft offerings, I am also one who loves to tinker and fiddle with everything I can get my hands on.  just a few days ago, I noticed an obvious mistake, and so I figured I'd mention it here for those also having this same issue.  I was testing out mySQL to see it's performance on my aging, but still revving, Dell desktop.  It works great!  Only problem?  For a long time, I couldn't connect as a different user other than root.  Well, seeing that most of my tinkering seemed to happen at the most ungodly hours of the morning, I'm not at all surprised that it wasn't working.  Well, figures!  Easy fix. All I had to do was prior to opening the command line client, I just used the run dialog to connect.  Works like a charm.  My point, make sure to use the run dialog to connect to the MySQl server!  People seem to get confused when the term "command line" is  stated to be used.  Most people think command Prompt when they hear that.  Word of advice, always try run first.   Just thought I'd share that little tip with all of you.