Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 100000

Summary: Accessibility:Screen reader unable to read text in the manual test execution application
Product: z_Archived Reporter: Poonam chitale <pchitale>
Component: TPTPAssignee: Bianca Jiang <bjiang>
Status: CLOSED FIXED QA Contact:
Severity: blocker    
Priority: P1    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Java Access Bridge 1.2 for Windows none

Description Poonam chitale CLA 2005-06-14 12:11:26 EDT 
Create new TPTP Manual Test in the java project
Add testcases to the test, test1,test2,test3
From the behaviour tab, add invocation for test1,2 and 3
Run the manual test
Start Window eyes screen reader
It reads the name of the java application that starts, Component Test Manual 
testcase Remote application.
Move the mouse over other fields in the application, test1 invocation; screen 
reader is unable to read this
It is unable to read the test name, the status field, Next button.
Interrupt execution, the Question dialog comes up
Window eyes reads it as Question dialog; the actual question is "Do you want to 
interrupt execution" this question is not read.
Comment 1 Poonam chitale CLA 2005-06-14 13:51:51 EDT 
Conclusion from screen reader testing: The execution of Manual test is not 
screen reader accessible.
Comment 2 Bianca Jiang CLA 2005-06-16 13:09:01 EDT 
As Manual Test Remote App. is implemented in Swing and hasn't been completed
accessibility support before, it'll need tooltip messages thus have PII impact.
Comment 3 Bianca Jiang CLA 2005-06-17 17:01:57 EDT 
No PII changes, worked around by using existing resources.

A note for testing:

Window-Eyes doesn't work for Swing/JFC applications out of the box(maybe needs
some configurations I don't know), tested with IBM accessibility samples that's
implemented in Swing and Sun Swing samples, Window-Eyes doesn't read it out of
the box.

Before Swing app. can be used for accessibility, *Java Access Bridge* needs to
be installed. It can be downloaded from java.sun.com. but I'm attaching it the
lasted 1.2 GA for windows here for conveniency. This is the last releast today
but it only supoort Sun JRE 1.4 or earlier. If you have a 1.5 JRE, this version
of Access Bridge may not work.

To install the Access Bridge, unzip the zip file and run \installer\install.exe.
This installer seems to only able to find JRE that's specified in your system
varialbe "JAVA_HOME", so you need to set it to your 1.X JRE home dir before
install. To verify your install, at least JRE\lib\ext\jaccess.jar should be there.

Make sure manual runner uses this JRE, run RAC's SetConfig.bat and set the
java.exe to be the one from this JRE installed with Access Bridge.

Access Bridge comes with a simple accessibility testing tool called
JavaFerret.exe. It won't read the screen, but it will display AccessibleContext
info of Swing controls in its own window which is used by screen reader. Simply
run it and launch the manual runner to have the two windows next to each other. 

To configure JavaFerret for this testing, at least menu JavaEvents->Track Mouse
Event, and AccessibilityEvents->Track Name Property Events should be checked so
that when mouse click on controls in manual runner, JavaFerret can display
accessibility properties.  In JavaFerret window, Look in "AccessibleContext
Information:" section, every control that can be selected in manual runner
should have a value for either Name or Description or both.
Comment 4 Bianca Jiang CLA 2005-06-17 17:46:44 EDT 
Created attachment 23491 [details]
Java Access Bridge 1.2 for Windows
Comment 5 Paul Slauenwhite CLA 2006-11-16 08:57:56 EST 
ACTION: Please verify/close this defect.
Comment 6 Paul Slauenwhite CLA 2007-02-12 12:57:02 EST 
Closing by default since not closed by the originator in the 7+ months since being resolved.  

Please reopen if the issue is still present in the latest TPTP release or the resolution is not correct.