Re: Why isn't Open Office on Windows Accessible?

  • From: "Jay Macarty" <jay.macarty2009@xxxxxxxxx>
  • To: <programmingblind@xxxxxxxxxxxxx>
  • Date: Wed, 18 Aug 2010 16:24:12 -0500

WE4Java can be obtained from the GW Micro Script Central web site. It requires 
Window-Eyes 7.1 or higher and java 1.5 or higher.

I have created a SourceForge project for the Java Accessibility Client (JAC) 
but the source code, which is primarily based on the WE4Java architecture, is 
not yet uploaded as I am making some changes to allow it to run wthout being 
tied to a specific screen reader. 

  ----- Original Message ----- 
  From: Kerneels Roos 
  To: programmingblind@xxxxxxxxxxxxx 
  Sent: Monday, August 16, 2010 1:02 AM
  Subject: Re: Why isn't Open Office on Windows Accessible?

  I would say that with NVDA one has far more than "limited success" with Open 
Office, but it's just not as smooth as I'm positive it could be. Also, some 
dialogs do not voice properly.

  The main point is, OO is not considered to be accessible under windows 
although it might be more accessible than other office suites even, it is known 
as not being accessible. How does one remedy this and also the perception of 
people. Could OO be certified as being as accessible as Java allows or 

  We4java and JAC sounds very interesting. Where can one obtain those from?

  Best regards,

  On Mon, Aug 16, 2010 at 7:28 AM, Jay Macarty <jay.macarty2009@xxxxxxxxx> 

    One of the ideas I have been toying with for the java screen reader (either 
we4java or jac) is providing a set of runtime annotations which could be used 
to enhance an application's accessibility by allowing the app developer to put 
in self voicing annotations. There are differing schools of thought on self 
voicing. Some say it is good because the developer knows the app best and where 
self voicing would be helpful. On the other hand, putting in self voicing 
without providing the user a way of controling it or turning off certain levels 
of it, takes away from the user's control over the accessibility feedback. If 
we put self voicing annotations into the java screen reader, a developer could 
add them in if desired but the base screen reader code base would still have 
control and could provide a common mechanism for allowing the user to adjust 
the self voicing feedback.

      ----- Original Message ----- 
      From: Ken Perry 
      To: programmingblind@xxxxxxxxxxxxx 
      Sent: Friday, August 13, 2010 5:20 PM
      Subject: RE: Why isn't Open Office on Windows Accessible?

      I agree with Chris H.’s answer but I want to point out it’s our fault 
it’s not already accessible.  I wrote a simple talking java screen reader that 
did very little but it made it so I could use  Open Office. Crappily but the 
buttons talked and all and I did this in like 200 lines of code.  I know that 
code got passed around and I have since lost my copy but it  can be done by 
replacing the access bridge with self voicing code.  It just takes someone 
actually doing it. 

      I am interested to see where Open Office goes now that it is Oricals.  I 
am worried about all Java stuff now that Orical is trying to Sew Google into 
stopping Android.  It’s a crazy world.


      From: programmingblind-bounce@xxxxxxxxxxxxx 
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Kerneels Roos
      Sent: Friday, August 13, 2010 3:30 AM
      To: programmingblind
      Subject: Why isn't Open Office on Windows Accessible?

      Hi List,

      Sorry if this question has been raised before and dealt with. Does anyone 
know exactly why the Windows version of Open Office is only partly accessible 
with a screen reader, while the Linux version is streets ahead? Because Open 
Office is written in Java I assume the code base is 98% identical across 
platforms. Is the problem mainly with the JAB (Java Access Bridge) or with the 
screen readers themselves? Could the JAB not be open sourced so it can be 
updated to bridge Java, MSAA, UIA and any other access middle ware standard? 

      NVDA works the best with Open Office, so I would assume it makes the best 
use of the JAB. Is there other Java to access technology middle ware in common 
use today?

      I can remember a really long thread that in part had some info on Java 
accessibility, but I just can't justify going through all that to possibly find 
out more.

      Keep well

      Kerneels Roos
      Cell/SMS: +27 (0)82 309 1998
      Skype: cornelis.roos

      The early bird may get the worm, but the second mouse gets the cheese!

  Kerneels Roos
  Cell/SMS: +27 (0)82 309 1998
  Skype: cornelis.roos

  The early bird may get the worm, but the second mouse gets the cheese!

Other related posts: