Nabble - Sun - Java-Access

Re: Configuring Java Access Bridge

2008-11-04T01:54:04Z

Hi Marvin,

I'll get back to u on this one as soon as I can... I just have lots of
assignments and tests coming up at school so will probably be delayed
for a week or so...

Thanks for the reply though

Cheers,
Danny

On Mon, Nov 03, 2008 at 06:47:53PM +1100, Marvin Hunkin wrote:

> Hi daniel.
> here's a page from sun java about how to set up the java access bridge from
> hand.
> hope this works.
> cheers Marvin.
>
> JavaTM Access Bridge
> for the Microsoft Windows Operating System
> Version 2.0.1
>
>
> Setup Information Contents
>
> --------------------------------------------------------------------------------
>
> Setting Up the Java Access Bridge
> The Java Access Bridge should only be installed by hand as a last resort.
> The recommended way to install the Java Access Bridge is to use the Java
> Access Bridge installer, which will locate the Java VMs installed on your
> system that support the Java Access Bridge, and then install the Java Access
> Bridge into those Java VMs that you identify. The Java Access Bridge
> installer is a self-extracting executable file called
> AccessBridge-2_0_1.exe.
> The instructions below describe what the Java Access Bridge installer does,
> allowing you to make those modifications by hand if necessary. Please note:
> the Java Access Bridge package includes three editions of the Java
> Accessibility Utilities file 'jaccess.jar', which differs for Java 2 SDK
> 1.2, Java 2 SDK 1.3, and Java 2 SDK 1.4. These files are named
> jaccess-1_2.jar, jaccess-1_3.jar, and jaccess-1_4.jar. Please use the
> jaccess-1_4.jar for Java 2 SDK 5.0.
>
>
> Using JDK 1.1 Environments
> Version 1.0.2 of the Java Access Bridge is required for JDK 1.1
> environments. See the compatibility table for complete information.
> Using Java Environments (Including SDK v1.2.2, v1.3.x, v1.4.x, and v5.0)
>
> To begin the installation, locate your Java platform extensions directory,
> which is the jre\lib\ext subdirectory under the directory in which your JDK
> is installed. Typical locations are:
>
> c:\Program Files\Java\jdk1.5.0\jre\lib\ext
> c:\Program Files\Java\jre1.5.0_05\lib\ext
>
>
> Copy the following files into that directory:
> jaccess-1_2.jar for Java 2 platform edition 1.2.x, or
> jaccess-1_3.jar for Java 2 platform edition 1.3.x, or
> jaccess-1_4.jar for Java 2 platform edition 1.4.x, or
> jaccess-1_4.jar for Java platform edition 1.5.x; and
> access-bridge.jar.
>
> The Java Virtual Machine consults a number of property files as it starts
> up. You will need to modify the c:\Program
> Files\Java\jre1.5.0_05\lib\ext\accessibility.properties file in order to
> enable accessibility. The Java Accessibility Utilities examples
> documentation explains how this all works. Add the following line to the
> accessibility.properties file:
> assistive_technologies=com.sun.java.accessibility.AccessBridge
>
> This line tells the Java VM to load the AccessBridge assistive technology,
> which it finds in the standard extensions directory. In addition, if you are
> using screen magnification technologies such as ZoomText from Ai Squared,
> you must also indicate the presence of screen magnification by adding the
> following line to the accessibility.properties file:
>
> screen_magnifier_present=true
>
>
> Compatibility Information
> In the Java Foundation Classes 1.1 with Swing 1.1, the name of the packages
> containing both the Swing classes and the Java Accessibility API classes
> changed (from com.sun.java.swing and com.sun.java.accessibility to
> javax.swing and javax.accessibility respectively). Java applications and
> applets built with earlier versions of Swing and/or the Java Accessibility
> API will not work with the Java Accessibility Utilities version 1.1 and
> later, nor will they work with the Java Access Bridge. The compatibility
> table details the versions of the Java platform, Java Foundation Classes,
> Java Accessibility Utilities, Java Plugin, and Java Access Bridge that work
> with each other.
>
> Working From a Browser
> The Java Plugin, at http://java.sun.com/products/plugin, provides a browser
> plug-in that contains the Sun Java VM. This VM includes the ability to
> replace the EventQueue in order to load assistive technologies (or, in the
> case of the JDK 1.2 version of the Java Plugin; load assistive technologies
> directly). The Java Plugin (version 1.2.2 and later) includes the Java
> Foundation Classes (and thereby Swing and the Java Accessibility API). The
> Java Plugin is typically installed on your c:\ drive within your Program
> Files directory. It may be a separate, or second Java VM. The Java
> platform extensions directory is typically at:
> c:\Program Files\Java\jre1.5.0_05\lib\ext
>
> which is where you must put the accessbridge.jar and jaccess.jar files. The
> parent lib directory is where the accessibility.properties file is located,
> which must be likewise modified as above.
>
>
>
> --------------------------------------------------------------------------------
> Copyright © 2006 Sun Microsystems, Inc. All Rights Reserved.
>
> Please send comments to: access@...
>
> ===========================================================================
> To unsubscribe, send email to listserv@... and include in the body
> of the message "signoff JAVA-ACCESS". For general help, send email to
> listserv@... and include in the body of the message "help".

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVA-ACCESS". For general help, send email to
listserv@... and include in the body of the message "help".

Configuring Java Access Bridge

2008-11-02T23:47:53Z

Hi daniel.
here's a page from sun java about how to set up the java access bridge from
hand.
hope this works.
cheers Marvin.

JavaTM Access Bridge
for the Microsoft Windows Operating System
Version 2.0.1

Setup Information Contents

--------------------------------------------------------------------------------

Setting Up the Java Access Bridge
The Java Access Bridge should only be installed by hand as a last resort.
The recommended way to install the Java Access Bridge is to use the Java
Access Bridge installer, which will locate the Java VMs installed on your
system that support the Java Access Bridge, and then install the Java Access
Bridge into those Java VMs that you identify. The Java Access Bridge
installer is a self-extracting executable file called
AccessBridge-2_0_1.exe.
The instructions below describe what the Java Access Bridge installer does,
allowing you to make those modifications by hand if necessary. Please note:
the Java Access Bridge package includes three editions of the Java
Accessibility Utilities file 'jaccess.jar', which differs for Java 2 SDK
1.2, Java 2 SDK 1.3, and Java 2 SDK 1.4. These files are named
jaccess-1_2.jar, jaccess-1_3.jar, and jaccess-1_4.jar. Please use the
jaccess-1_4.jar for Java 2 SDK 5.0.

Using JDK 1.1 Environments
Version 1.0.2 of the Java Access Bridge is required for JDK 1.1
environments. See the compatibility table for complete information.
Using Java Environments (Including SDK v1.2.2, v1.3.x, v1.4.x, and v5.0)

To begin the installation, locate your Java platform extensions directory,
which is the jre\lib\ext subdirectory under the directory in which your JDK
is installed. Typical locations are:

c:\Program Files\Java\jdk1.5.0\jre\lib\ext
c:\Program Files\Java\jre1.5.0_05\lib\ext

Copy the following files into that directory:
jaccess-1_2.jar for Java 2 platform edition 1.2.x, or
jaccess-1_3.jar for Java 2 platform edition 1.3.x, or
jaccess-1_4.jar for Java 2 platform edition 1.4.x, or
jaccess-1_4.jar for Java platform edition 1.5.x; and
access-bridge.jar.

The Java Virtual Machine consults a number of property files as it starts
up. You will need to modify the c:\Program
Files\Java\jre1.5.0_05\lib\ext\accessibility.properties file in order to
enable accessibility. The Java Accessibility Utilities examples
documentation explains how this all works. Add the following line to the
accessibility.properties file:
assistive_technologies=com.sun.java.accessibility.AccessBridge

This line tells the Java VM to load the AccessBridge assistive technology,
which it finds in the standard extensions directory. In addition, if you are
using screen magnification technologies such as ZoomText from Ai Squared,
you must also indicate the presence of screen magnification by adding the
following line to the accessibility.properties file:

screen_magnifier_present=true

Compatibility Information
In the Java Foundation Classes 1.1 with Swing 1.1, the name of the packages
containing both the Swing classes and the Java Accessibility API classes
changed (from com.sun.java.swing and com.sun.java.accessibility to
javax.swing and javax.accessibility respectively). Java applications and
applets built with earlier versions of Swing and/or the Java Accessibility
API will not work with the Java Accessibility Utilities version 1.1 and
later, nor will they work with the Java Access Bridge. The compatibility
table details the versions of the Java platform, Java Foundation Classes,
Java Accessibility Utilities, Java Plugin, and Java Access Bridge that work
with each other.

Working From a Browser
The Java Plugin, at http://java.sun.com/products/plugin, provides a browser
plug-in that contains the Sun Java VM. This VM includes the ability to
replace the EventQueue in order to load assistive technologies (or, in the
case of the JDK 1.2 version of the Java Plugin; load assistive technologies
directly). The Java Plugin (version 1.2.2 and later) includes the Java
Foundation Classes (and thereby Swing and the Java Accessibility API). The
Java Plugin is typically installed on your c:\ drive within your Program
Files directory. It may be a separate, or second Java VM. The Java
platform extensions directory is typically at:
c:\Program Files\Java\jre1.5.0_05\lib\ext

which is where you must put the accessbridge.jar and jaccess.jar files. The
parent lib directory is where the accessibility.properties file is located,
which must be likewise modified as above.

--------------------------------------------------------------------------------
Copyright © 2006 Sun Microsystems, Inc. All Rights Reserved.

Please send comments to: access@...

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVA-ACCESS". For general help, send email to
listserv@... and include in the body of the message "help".

configuring access bridge on windows

2008-11-02T18:38:43Z

Hi,

Could someone please explain how to set up the java access bridge on
windows? I've been using linux, so don't know a lot about java or
windows...
I want to be able to use some java applications...

I have jre 6 update 7 or something like that installed already... My
system is dual booting with vista and linux, and I am wanting to do this
to the vista... So what should I do? What are the steps to making java
apps accessible with jaws? How do I configure this access bridge? Or
what should I read to get started?

Thanks for any help,

Danny

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVA-ACCESS". For general help, send email to
listserv@... and include in the body of the message "help".

Re: Announcing AEGIS - a 12.6m investment in open source accessibility

2008-10-20T02:25:28Z

Dear Peter,

Thanks for sharing this fantastic news with us!

I would be interested to know how this project relates to existing projects
such as JAVA accessibility and iAccessible(2), and what the likely future is
for such projects.

If the existing Java accessibility API (and in particular the windows access
bridge) is to be abandoned, I would be delighted to see the relevant source
code released under a simple and permissive licence. Is there any likelihood
of this happening?

With thanks,
Peter.

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVA-ACCESS". For general help, send email to
listserv@... and include in the body of the message "help".

Re: Announcing AEGIS - a €12.6m investment in open so urce accessibility

2008-10-16T22:36:33Z

Hi Peter,

Congratulations for your role in this project.

I hope it will be a success because I am directly interested in its results.

Octavian

----- Original Message -----
From: "Peter Korn" <Peter.Korn@...>
To: <JAVA-ACCESS@...>
Sent: Friday, October 17, 2008 6:31 AM
Subject: Announcing AEGIS - a €12.6m investment in open source accessibility

>I am *very* pleased to share with you news about the AEGIS project, a
> €12.6m investment in accessibility, with the vast majority of it focused
> on open source solutions.
>
> Rather than repeat here all that I have written about AEGIS already, I
> will instead invite you to read about it in my blog:
> http://blogs.sun.com/korn/ or check out the AEGIS website at:
> http://www.aegis-project.eu/
>
> I have worked in the field of accessibility for nearly 17 years, and on
> open source accessibility almost a dozen of those years. In that time,
> open source accessibility has become a deep and abiding passion.
>
> I'm very proud that the techniques we have pioneered in the open source
> community have since been adopted by Apple with the Macintosh &
> VoiceOver, and are being adopted by Microsoft with UI Automation. These
> same techniques are enshrined in the report a 42 member committee
> delivered to the U.S. Access Board earlier this year (and which at this
> very moment being reviewed by them as they work on their refresh of the
> Section 508 accessibility standard). And these techniques are at the
> core of the AEGIS project.
>
> With AEGIS, over the next 3.5 years we will attempt to bring
> programmatic accessibility more fully to the web, and to the mobile
> world. With AEGIS we will also address a number of issues that still
> remain in accessibility on the open desktop. And while we're at it, we
> will bring a bunch of new and talented people into the open source
> accessibility community (you should start seeing them showing up on our
> mailing lists and wikis in the coming months). We will also fund a
> number of the experts who have already made tremendous open source
> accessibility contributions - to enable to them to continue and to do
> even more. I'm sure they will shortly make their voices heard on these
> lists and in the blogosphere. And we will explicitly fund a number of
> European disability organizations. These organizations and many dozens
> of their members will be providing their expert input on our work, and
> thoughtfully evaluating our prototypes, and perhaps adopting the
> solutions we come up with because they do a great job of meeting their
> needs.
>
> Oh, and we'll also write a bunch of open source accessibility code.
>
>
> By the way - this Sunday the 19th of October marks the 8th anniversary
> of the GNOME Accessibility Project. AEGIS helps bring a fantastic 8th
> year to a close, and also serves to inaugurate the next 3.5 years!
>
>
> Regards,
>
> Peter Korn
> Accessibility Architect & Principal Engineer,
> Sun Microsystems, Inc.
>
> ===========================================================================
> To unsubscribe, send email to listserv@... and include in the body
> of the message "signoff JAVA-ACCESS". For general help, send email to
> listserv@... and include in the body of the message "help".

Announcing AEGIS - a €12.6m investment in open source accessibility

2008-10-16T20:31:35Z

I am *very* pleased to share with you news about the AEGIS project, a
€12.6m investment in accessibility, with the vast majority of it focused
on open source solutions.

Rather than repeat here all that I have written about AEGIS already, I
will instead invite you to read about it in my blog:
http://blogs.sun.com/korn/ or check out the AEGIS website at:
http://www.aegis-project.eu/

I have worked in the field of accessibility for nearly 17 years, and on
open source accessibility almost a dozen of those years. In that time,
open source accessibility has become a deep and abiding passion.

I'm very proud that the techniques we have pioneered in the open source
community have since been adopted by Apple with the Macintosh &
VoiceOver, and are being adopted by Microsoft with UI Automation. These
same techniques are enshrined in the report a 42 member committee
delivered to the U.S. Access Board earlier this year (and which at this
very moment being reviewed by them as they work on their refresh of the
Section 508 accessibility standard). And these techniques are at the
core of the AEGIS project.

With AEGIS, over the next 3.5 years we will attempt to bring
programmatic accessibility more fully to the web, and to the mobile
world. With AEGIS we will also address a number of issues that still
remain in accessibility on the open desktop. And while we're at it, we
will bring a bunch of new and talented people into the open source
accessibility community (you should start seeing them showing up on our
mailing lists and wikis in the coming months). We will also fund a
number of the experts who have already made tremendous open source
accessibility contributions - to enable to them to continue and to do
even more. I'm sure they will shortly make their voices heard on these
lists and in the blogosphere. And we will explicitly fund a number of
European disability organizations. These organizations and many dozens
of their members will be providing their expert input on our work, and
thoughtfully evaluating our prototypes, and perhaps adopting the
solutions we come up with because they do a great job of meeting their
needs.

Oh, and we'll also write a bunch of open source accessibility code.

By the way - this Sunday the 19th of October marks the 8th anniversary
of the GNOME Accessibility Project. AEGIS helps bring a fantastic 8th
year to a close, and also serves to inaugurate the next 3.5 years!

Regards,

Peter Korn
Accessibility Architect & Principal Engineer,
Sun Microsystems, Inc.

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVA-ACCESS". For general help, send email to
listserv@... and include in the body of the message "help".

Re: Java Access Bridge

2008-09-23T21:06:19Z

Hi Marvin,

The latest version of the Java Access Bridge for Windows is 2.0.1, which
can be found at:
http://java.sun.com/javase/technologies/accessibility/accessbridge/ You
can find the Java 6 (sometimes also known as Java 1.6) SDK at:
http://java.sun.com/javase/downloads/index.jsp

Regards,

Peter Korn
Accessibility Architect & Principal Engineer,
Sun Microsystems, Inc.

> Hi.
> where can i get java access bridge for windows vista home Premium?
> and will it work with jaws 9, and the new java a 1.6 sdk.
> cheers Marvin.
>
> ===========================================================================
> To unsubscribe, send email to listserv@... and include in the body
> of the message "signoff JAVA-ACCESS". For general help, send email to
> listserv@... and include in the body of the message "help".
>

Java Access Bridge

2008-09-22T00:41:34Z

Hi.
where can i get java access bridge for windows vista home Premium?
and will it work with jaws 9, and the new java a 1.6 sdk.
cheers Marvin.

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVA-ACCESS". For general help, send email to
listserv@... and include in the body of the message "help".

Re: squiggly markers for errors in Eclipse - anyway to replace them?

2008-07-15T15:17:02Z

There are two proposals being discussed by the IA2 WG.
1) use new text attributes like spelling-error;grammar-error;
or
2) use interfaces/methods to determine if there is an error and if so what kind of error it is.

I'm hoping to get to a consensus on this soon.

BTW, IA2 doesn't have a Collection interface. It was added to ATK/AT-SPI because of its cross process architecture. The Collection interface can be used to cut down on the cross process calls. IA2 ATs tend to be in process, though now we also have NVDA which is mostly out of process due being written in Python.

Pete Brunet

IBM Accessibility Architecture and Development
11501 Burnet Road, MS 9022E004, Austin, TX 78758
Voice: (512) 838-4594, Cell: (512) 689-4155
Ionosphere: WS4G

Peter Korn <Peter.Korn@...>
Sent by: Java Accessibility interest mailing list <JAVA-ACCESS@...>

07/14/2008 07:50 PM

Please respond to
Java Accessibility interest mailing list <JAVA-ACCESS@...>

To	JAVA-ACCESS@...
cc
Subject	Re: squiggly markers for errors in Eclipse - anyway to replace them?

Hi Phill,

A few comments:

...

3. API - Isn't API the preferred method over querying every character and storing information about the text attributes and/or error types? It is usually a big performance hit to the AT to have to query every text and store it attributes and error types. Much more efficient to allow the AT to query the DOM via an API on demand and get the strings of errors.

This is precisely what the new collections interface is about - allowing an AT to make queries and get back a list of the objects/places that meet the query (the collection of things meeting the query if you will). This kind of approach is much more generic than application-specific DOMs, and much easier to implement broadly than trying to generify a DOM across a spectrum of very different applications (a word processed document DOM likely looks quite different from a spreadsheet DOM, and those different from a vector graphics editor DOM).

Regards,

Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.
=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".
=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

Re: squiggly markers for errors in Eclipse - anyway to replace them?

2008-07-14T17:50:34Z

Hi Phill,

A few comments:

...

3. API - Isn't API the preferred method over querying every character and storing information about the text attributes and/or error types? It is usually a big performance hit to the AT to have to query every text and store it attributes and error types. Much more efficient to allow the AT to query the DOM via an API on demand and get the strings of errors.

This is precisely what the new collections interface is about - allowing an AT to make queries and get back a list of the objects/places that meet the query (the collection of things meeting the query if you will). This kind of approach is much more generic than application-specific DOMs, and much easier to implement broadly than trying to generify a DOM across a spectrum of very different applications (a word processed document DOM likely looks quite different from a spreadsheet DOM, and those different from a vector graphics editor DOM).

Regards,

Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.
=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

Re: squiggly markers for errors in Eclipse - anyway to replace them?

2008-07-14T12:36:57Z

A few comments:

1. Text attributes - knowing the text attributes is (should be) independent of the semantics that an error is also being represented. The fundamental principle that presentation should be separated from semantics comes into play here. Some may prefer and/or need it presented as a yellow box, or larger font with different contrast, or the red squiggly line - but the user/AT/agent still needs to know the semantics - spelling, grammatical, syntax, or what-ever error.

2. Extensible error type: It would be useful for the error types to be extendable. Start off with the common ones today, such as spelling, grammar, syntax,etc. But allow the API to be extended to include additional ones yet to be defined.

3. API - Isn't API the preferred method over querying every character and storing information about the text attributes and/or error types? It is usually a big performance hit to the AT to have to query every text and store it attributes and error types. Much more efficient to allow the AT to query the DOM via an API on demand and get the strings of errors.

Regards,
Phill Jenkins
IBM Research - Human Ability & Accessibility Center
http://www.ibm.com/able
=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

Re: squiggly markers for errors in Eclipse - anyway to replace them?

2008-07-14T11:33:04Z

Jeff, We've been discussing this matter (along with grammar errors) in the IAccessible2 group for some time now and the discussion is at a point where I'm waiting for some input from the OpenOffice team. In Lotus Symphony the red wavy underlines are exposed using IA2's IAccessibleText::attributes indicating that there is an underline, that it is wavy, and that it is red. However, what is really needed is to expose that there is an error of a certain sort, e.g. spelling or grammar, not that there is an underline with particular attributes. There are two ways to expose the error, either as a text attribute, e.g. ...;spelling-error:true;grammar-error:true;... or an interface (or a pair of interfaces) that returns the error information. If you have any input regarding this issue the IA2 site is at http://www.linuxfoundation.org/en/Accessibility/IAccessible2 and the mailing list info is at https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2.

Thanks,
Pete Brunet

IBM Accessibility Architecture and Development
11501 Burnet Road, MS 9022E004, Austin, TX 78758
Voice: (512) 838-4594, Cell: (512) 689-4155
Ionosphere: WS4G

Jeff Bishop <jeff.bishop@...>
Sent by: Java Accessibility interest mailing list <JAVA-ACCESS@...>

07/14/2008 12:20 PM

Please respond to
Jeff Bishop <jeff.bishop@...>

To	JAVA-ACCESS@...
cc
Subject	Re: squiggly markers for errors in Eclipse - anyway to replace them?

Peter,

Do you know if Eclipse has a com way of getting at that information?

Jeff

----- Original Message -----
From: Peter Korn
To: JAVA-ACCESS@...
Sent: Monday, July 14, 2008 9:55 AM
Subject: Re: squiggly markers for errors in Eclipse - anyway to replace them?

Dear Phill,

I think the first question to ask is *how* does an AT like JAWS determine that a portion of text has a a squiggly line underneath it (or any other attribute/styling). I believe JAWS & WindowEyes do this with Microsoft Word by using the proprietary COM APIs that Word exposes - essentially by "going to the DOM" to determine this.

In applications using a uniform accessibility API (e.g. iAccessible2) and not providing a unique-to-them DOM/COM interface, the question becomes "how should one expose this information via iAccessible2" (or whatever is the appropriate accessibility API in question). A first choice might be via text attributes, though this can be challenging to implement because the information is typically stored and even sometimes rendered in a very different part of the application from the part that knows about boldface/underlining, etc.

Apropos of this, a very similar issue is being worked on right now in the Linux Foundation's Open Accessibility working group, where IBM's Pete Brunet is working through a proposal conveying change tracking information via iAccessible2 and the UNIX ATK/AT-SPI interfaces.

So I think the actual answer is: JAWS isn't given enough information today to do this in Eclipse, but hopefully in not too long the accessibility APIs will be exposed to allow JAWS (or someone writing a script for JAWS) to do so.

Regards,

Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.

If one gets an error when typing inside of Eclipse you see a squiggly line
near the error. However, for a screen reader it will not designate such an
error.

Isn't that really an opportunity for writing a script? Doesn't JAWS & WindowEyes see the squiggly line character - if so, then it is the AT that needs to be customized to react to it correctly - just as it has been done for Microsoft Word or any other application that uses special characters to identify misspellings, etc.

Regards,
Phill Jenkins
IBM Research - Human Ability & Accessibility Center
http://www.ibm.com/able =========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

Re: squiggly markers for errors in Eclipse - anyway to replace them?

2008-07-14T10:20:11Z

Peter,

Do you know if Eclipse has a com way of getting at that information?

Jeff

----- Original Message -----

From: Peter.Korn@...

To: JAVA-ACCESS@...

Sent: Monday, July 14, 2008 9:55 AM

Subject: Re: squiggly markers for errors in Eclipse - anyway to replace them?

Dear Phill,

I think the first question to ask is *how* does an AT like JAWS determine that a portion of text has a a squiggly line underneath it (or any other attribute/styling). I believe JAWS & WindowEyes do this with Microsoft Word by using the proprietary COM APIs that Word exposes - essentially by "going to the DOM" to determine this.

In applications using a uniform accessibility API (e.g. iAccessible2) and not providing a unique-to-them DOM/COM interface, the question becomes "how should one expose this information via iAccessible2" (or whatever is the appropriate accessibility API in question). A first choice might be via text attributes, though this can be challenging to implement because the information is typically stored and even sometimes rendered in a very different part of the application from the part that knows about boldface/underlining, etc.

Apropos of this, a very similar issue is being worked on right now in the Linux Foundation's Open Accessibility working group, where IBM's Pete Brunet is working through a proposal conveying change tracking information via iAccessible2 and the UNIX ATK/AT-SPI interfaces.

So I think the actual answer is: JAWS isn't given enough information today to do this in Eclipse, but hopefully in not too long the accessibility APIs will be exposed to allow JAWS (or someone writing a script for JAWS) to do so.

Regards,

Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.

If one gets an error when typing inside of Eclipse you see a squiggly line
near the error. However, for a screen reader it will not designate such an
error.

Isn't that really an opportunity for writing a script? Doesn't JAWS & WindowEyes see the squiggly line character - if so, then it is the AT that needs to be customized to react to it correctly - just as it has been done for Microsoft Word or any other application that uses special characters to identify misspellings, etc.

Regards,
Phill Jenkins
IBM Research - Human Ability & Accessibility Center
http://www.ibm.com/able =========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

Re: squiggly markers for errors in Eclipse - anyway to replace them?

2008-07-14T09:55:06Z

Dear Phill,

I think the first question to ask is *how* does an AT like JAWS determine that a portion of text has a a squiggly line underneath it (or any other attribute/styling). I believe JAWS & WindowEyes do this with Microsoft Word by using the proprietary COM APIs that Word exposes - essentially by "going to the DOM" to determine this.

In applications using a uniform accessibility API (e.g. iAccessible2) and not providing a unique-to-them DOM/COM interface, the question becomes "how should one expose this information via iAccessible2" (or whatever is the appropriate accessibility API in question). A first choice might be via text attributes, though this can be challenging to implement because the information is typically stored and even sometimes rendered in a very different part of the application from the part that knows about boldface/underlining, etc.

Apropos of this, a very similar issue is being worked on right now in the Linux Foundation's Open Accessibility working group, where IBM's Pete Brunet is working through a proposal conveying change tracking information via iAccessible2 and the UNIX ATK/AT-SPI interfaces.

So I think the actual answer is: JAWS isn't given enough information today to do this in Eclipse, but hopefully in not too long the accessibility APIs will be exposed to allow JAWS (or someone writing a script for JAWS) to do so.

Regards,

Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.

If one gets an error when typing inside of Eclipse you see a squiggly line
near the error. However, for a screen reader it will not designate such an
error.

Isn't that really an opportunity for writing a script? Doesn't JAWS & WindowEyes see the squiggly line character - if so, then it is the AT that needs to be customized to react to it correctly - just as it has been done for Microsoft Word or any other application that uses special characters to identify misspellings, etc.

Regards,
Phill Jenkins
IBM Research - Human Ability & Accessibility Center
http://www.ibm.com/able =========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

Re: squiggly markers for errors in Eclipse - anyway to replace them?

2008-07-14T09:26:45Z

I believe in the case of Word this information is obtained via the object model of that application. Do you know if a COM interface exists within Eclipse to gain access to that information?

Jeff

----- Original Message -----

From: pjenkins@...

To: JAVA-ACCESS@...

Sent: Monday, July 14, 2008 9:06 AM

Subject: Re: squiggly markers for errors in Eclipse - anyway to replace them?

If one gets an error when typing inside of Eclipse you see a squiggly line
near the error. However, for a screen reader it will not designate such an
error.

Isn't that really an opportunity for writing a script? Doesn't JAWS & WindowEyes see the squiggly line character - if so, then it is the AT that needs to be customized to react to it correctly - just as it has been done for Microsoft Word or any other application that uses special characters to identify misspellings, etc.

Regards,
Phill Jenkins
IBM Research - Human Ability & Accessibility Center
http://www.ibm.com/able =========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

Re: squiggly markers for errors in Eclipse - anyway to replace them?

2008-07-14T09:06:44Z

If one gets an error when typing inside of Eclipse you see a squiggly line
near the error. However, for a screen reader it will not designate such an
error.

Isn't that really an opportunity for writing a script? Doesn't JAWS & WindowEyes see the squiggly line character - if so, then it is the AT that needs to be customized to react to it correctly - just as it has been done for Microsoft Word or any other application that uses special characters to identify misspellings, etc.

Regards,
Phill Jenkins
IBM Research - Human Ability & Accessibility Center
http://www.ibm.com/able =========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

squiggly markers for errors in Eclipse - anyway to replace them?

2008-07-12T12:17:33Z

Hello Everyone,

If one gets an error when typing inside of Eclipse you see a squiggly line
near the error. However, for a screen reader it will not designate such an
error.

Is there a way or a plugin to get a popup window or a sound alert if an
error takes place that anyone is aware of?

Jeff

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

Eclipse question ...

2008-04-17T20:06:42Z

Hello,

Has anyone gotten Eclipse intellesense to work inside of Eclipse with a screen reader?

If so, how?

Jeff

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

Re: MyEclipse - is it accessible

2008-04-14T23:26:33Z

Hi Jeff,

Not sure if I am really qualified to comment on MyEclipse. I was
asked to install and use it for my previous job. My impression is that
it was basically Eclipse with pre-selected/packaged plug-ins and add-ons
installed together with Eclipse (e.g. Hibernate support, SQL support,
Subclipse...). I had not played with their latest version (V6?) but when
I used the previous one I didn't find it that much better than Eclipse
with a few FOSS plug-ins installed. Since I installed it after Eclipse,
it used a different directory to install its plug-ins while Eclipse's
installer will install plug-ins at a default location. Sooner or later I
got conflicting versions of plug-ins/libraries installed inside one
runtime. At the end, I just removed the duplicates inside MyEclipse'
default folder and more or less restored to basic Eclipse. Personally, I
prefer using just Eclipse and extend it with the downloadable plug-ins.

Alvin
> Hello,
>
> Has anyone played with MyEclipse and if so is it accessible?
>
> It is found at:
>
> http://www.myeclipseide.com/
>
> Jeff

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVA-ACCESS". For general help, send email to
listserv@... and include in the body of the message "help".

Re: Accessibility of Eclipse and pointers

2008-04-14T10:22:39Z

Another useful shortcut that I didn't mention and that I use a lot is ctrl+shift+p. Place the cursor after a { or after a } and press ctrl+shift+p. Eclipse will move the cursor to the matching brace.
It also can be used to find a matching left or right paren or a left or right bracket.

Shelton, Robert O. (JSC-AE) wrote:

Wow -- thanks, I'll have to try that.

From: Java Accessibility interest mailing list [JAVA-ACCESS@...] On Behalf Of José Vilmar Estácio de Souza
Sent: Monday, April 14, 2008 10:27 AM
To: JAVA-ACCESS@...
Subject: Re: Accessibility of Eclipse and pointers

Hi,
Shift+f2 launches a browser that tries to access the documentation in html format.
f2 extracts the documentation directly from the source file, if available. Depending on the desired information it is more efficient and quick.

Shelton, Robert O. (JSC-AE) wrote:

>f2 - shows the documentation of a method, variable or class

Isn't this shift+F2?

Very cool. Some of the other shortcuts are new to me, so we all learn something.

From: Java Accessibility interest mailing list [JAVA-ACCESS@...] On Behalf Of José Vilmar Estácio de Souza
Sent: Monday, April 14, 2008 4:55 AM
To: JAVA-ACCESS@...
Subject: Re: Accessibility of Eclipse and pointers

Hi Jeff,
Eclipse is very accessible with jaws. I can not comment about eclipse and window-eyes because I have no experience with window-eyes.

I work with java and eclipse every day but the applications that I'm developing are in general batch applications. I could create my applications using a simple text editor but using eclipse save me much time.

My favorites hot keys are:
f2 - shows the documentation of a method, variable or class. The cursor must be in the desired name before you press the f2 key.
f3 - move to the declaration of a method, variable or class where the cursor is.
ctrl+f6 or ctrl+shift+f6 - cycle between files that are being edited.
ctrl+spacebar - activate the content assist.
ctrl+shift+o - opens a dialog in which a can type a string. Eclipse will show all elements that starts with what i typed so that i can jump to the element quickly.
ctrl+shift+e - brings a list with all files that are being edit so that I can jump to a file quickly.

And much much much more!
Jeff Bishop wrote:

Hello Everyone,

I have an opportunity to move into a position at the University of Arizona as a Java developer working on the Kuali project. I have 21 years of programming background but none of that in Java. I am studying like mad to learn the language and utilizing the JDK command line tools to accomplish that effort.

The Kuali project utilizes Eclipse as its IDE of choice and from some very limited looking it appears to be very accessible.

I noticed that it was written with the SWT framework. Does this mean that Eclipse is using all standard windows controls? Would it be safe to assume that both Window-Eyes and JAWS should work with Eclipse in all areas? I just wanted to find out what others experience has been.

Can anyone suggest any pointers on Eclipse usage or settings that are beneficial with the use of a screen reader in Eclipse?

Thanks for any help you may be able to provide.

Jeff

avast! Antivirus: Inbound message clean.
Virus Database (VPS): 080414-0, 04/14/2008
Tested on: 4/14/2008 4:36:33 AM
avast! - copyright (c) 1988-2008 ALWIL Software.

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

avast! Antivirus: Inbound message clean.
Virus Database (VPS): 080414-0, 04/14/2008
Tested on: 4/14/2008 10:38:42 AM
avast! - copyright (c) 1988-2008 ALWIL Software.

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

avast! Antivirus: Inbound message clean.
Virus Database (VPS): 080414-0, 04/14/2008
Tested on: 4/14/2008 1:47:05 PM
avast! - copyright (c) 1988-2008 ALWIL Software.

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

Re: Accessibility of Eclipse and pointers

2008-04-14T09:31:11Z

Wow -- thanks, I'll have to try that.

From: Java Accessibility interest mailing list [mailto:JAVA-ACCESS@...] On Behalf Of José Vilmar Estácio de Souza
Sent: Monday, April 14, 2008 10:27 AM
To: JAVA-ACCESS@...
Subject: Re: Accessibility of Eclipse and pointers

Hi,
Shift+f2 launches a browser that tries to access the documentation in html format.
f2 extracts the documentation directly from the source file, if available. Depending on the desired information it is more efficient and quick.

Shelton, Robert O. (JSC-AE) wrote:

>f2 - shows the documentation of a method, variable or class

Isn't this shift+F2?

Very cool. Some of the other shortcuts are new to me, so we all learn something.

From: Java Accessibility interest mailing list [JAVA-ACCESS@...] On Behalf Of José Vilmar Estácio de Souza
Sent: Monday, April 14, 2008 4:55 AM
To: JAVA-ACCESS@...
Subject: Re: Accessibility of Eclipse and pointers

Hi Jeff,
Eclipse is very accessible with jaws. I can not comment about eclipse and window-eyes because I have no experience with window-eyes.

I work with java and eclipse every day but the applications that I'm developing are in general batch applications. I could create my applications using a simple text editor but using eclipse save me much time.

My favorites hot keys are:
f2 - shows the documentation of a method, variable or class. The cursor must be in the desired name before you press the f2 key.
f3 - move to the declaration of a method, variable or class where the cursor is.
ctrl+f6 or ctrl+shift+f6 - cycle between files that are being edited.
ctrl+spacebar - activate the content assist.
ctrl+shift+o - opens a dialog in which a can type a string. Eclipse will show all elements that starts with what i typed so that i can jump to the element quickly.
ctrl+shift+e - brings a list with all files that are being edit so that I can jump to a file quickly.

And much much much more!
Jeff Bishop wrote:

Hello Everyone,

I have an opportunity to move into a position at the University of Arizona as a Java developer working on the Kuali project. I have 21 years of programming background but none of that in Java. I am studying like mad to learn the language and utilizing the JDK command line tools to accomplish that effort.

The Kuali project utilizes Eclipse as its IDE of choice and from some very limited looking it appears to be very accessible.

I noticed that it was written with the SWT framework. Does this mean that Eclipse is using all standard windows controls? Would it be safe to assume that both Window-Eyes and JAWS should work with Eclipse in all areas? I just wanted to find out what others experience has been.

Can anyone suggest any pointers on Eclipse usage or settings that are beneficial with the use of a screen reader in Eclipse?

Thanks for any help you may be able to provide.

Jeff

avast! Antivirus: Inbound message clean.
Virus Database (VPS): 080414-0, 04/14/2008
Tested on: 4/14/2008 4:36:33 AM
avast! - copyright (c) 1988-2008 ALWIL Software.

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

avast! Antivirus: Inbound message clean.
Virus Database (VPS): 080414-0, 04/14/2008
Tested on: 4/14/2008 10:38:42 AM
avast! - copyright (c) 1988-2008 ALWIL Software.

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

Re: Accessibility of Eclipse and pointers

2008-04-14T08:27:06Z

>f2 - shows the documentation of a method, variable or class

Isn't this shift+F2?

Very cool. Some of the other shortcuts are new to me, so we all learn something.

From: Java Accessibility interest mailing list [JAVA-ACCESS@...] On Behalf Of José Vilmar Estácio de Souza
Sent: Monday, April 14, 2008 4:55 AM
To: JAVA-ACCESS@...
Subject: Re: Accessibility of Eclipse and pointers

Hi Jeff,
Eclipse is very accessible with jaws. I can not comment about eclipse and window-eyes because I have no experience with window-eyes.

I work with java and eclipse every day but the applications that I'm developing are in general batch applications. I could create my applications using a simple text editor but using eclipse save me much time.

My favorites hot keys are:
f2 - shows the documentation of a method, variable or class. The cursor must be in the desired name before you press the f2 key.
f3 - move to the declaration of a method, variable or class where the cursor is.
ctrl+f6 or ctrl+shift+f6 - cycle between files that are being edited.
ctrl+spacebar - activate the content assist.
ctrl+shift+o - opens a dialog in which a can type a string. Eclipse will show all elements that starts with what i typed so that i can jump to the element quickly.
ctrl+shift+e - brings a list with all files that are being edit so that I can jump to a file quickly.

And much much much more!
Jeff Bishop wrote:

Hello Everyone,

I have an opportunity to move into a position at the University of Arizona as a Java developer working on the Kuali project. I have 21 years of programming background but none of that in Java. I am studying like mad to learn the language and utilizing the JDK command line tools to accomplish that effort.

The Kuali project utilizes Eclipse as its IDE of choice and from some very limited looking it appears to be very accessible.

I noticed that it was written with the SWT framework. Does this mean that Eclipse is using all standard windows controls? Would it be safe to assume that both Window-Eyes and JAWS should work with Eclipse in all areas? I just wanted to find out what others experience has been.

Can anyone suggest any pointers on Eclipse usage or settings that are beneficial with the use of a screen reader in Eclipse?

Thanks for any help you may be able to provide.

Jeff

avast! Antivirus: Inbound message clean.
Virus Database (VPS): 080414-0, 04/14/2008
Tested on: 4/14/2008 4:36:33 AM
avast! - copyright (c) 1988-2008 ALWIL Software.

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

avast! Antivirus: Inbound message clean.
Virus Database (VPS): 080414-0, 04/14/2008
Tested on: 4/14/2008 10:38:42 AM
avast! - copyright (c) 1988-2008 ALWIL Software.

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

accessing the toolbar for buttons that don't h ave menu items ...

2008-04-14T06:59:34Z

Hello,

MyEclipse has a Run Server button on the toolbar. What is the best strategy to gain access to these buttons on the toolbars?

Jeff

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVA-ACCESS". For general help, send email to listserv@... and include in the body of the message "help".

Nabble - Sun - Java-Access

Re: Configuring Java Access Bridge

Configuring Java Access Bridge

configuring access bridge on windows

Re: Announcing AEGIS - a 12.6m investment in open source accessibility

Re: Announcing AEGIS - a €12.6m investment in open so urce accessibility

Announcing AEGIS - a €12.6m investment in open source accessibility

Re: Java Access Bridge

Java Access Bridge

Re: squiggly markers for errors in Eclipse - anyway to replace them?

Re: squiggly markers for errors in Eclipse - anyway to replace them?

Re: squiggly markers for errors in Eclipse - anyway to replace them?

Re: squiggly markers for errors in Eclipse - anyway to replace them?

Re: squiggly markers for errors in Eclipse - anyway to replace them?

Re: squiggly markers for errors in Eclipse - anyway to replace them?

Re: squiggly markers for errors in Eclipse - anyway to replace them?

Re: squiggly markers for errors in Eclipse - anyway to replace them?

squiggly markers for errors in Eclipse - anyway to replace them?

Eclipse question ...

Re: MyEclipse - is it accessible

Re: Accessibility of Eclipse and pointers

Re: Accessibility of Eclipse and pointers

Re: Accessibility of Eclipse and pointers

accessing the toolbar for buttons that don't h ave menu items ...

Re: Announcing AEGIS - a 12.6m investment in open source accessibility