Description John Arthorne 2001-10-10 22:39:40 EDT

Over a month ago we had an accessibility expert come in to help us evaluate
the accessibility issues in Eclipse.  Here were some notes that Jean-Michel
and I made about the compare framework:

arrows distinguising change direction are very small (visibility issue).
within a text file, incoming, outgoing and conflicting changes are represented in either red, 
blue, or black.  This may be a colour/low visibility issue.  Even blue vs. black may be difficult 
to distinguish

compare editors don't even read the text to you using MS Narrator.  I would like to 
try this with JAWS to see if it can read it.  It is doubtful that it will work because it's 
a custom widget.

GDA> Jaws cannot read it in a meaningful way. It reads a line at the left, line at the right, 
	line at the left, back to a line at the right. So multi line changes are brutal.

changes are represented graphically with lines and arrows, which doesn't translate to speech.
all compare actions are in toolbars only.  As far as we know there is no way to access these 
toolbars without a mouse.  This issue is actually pretty complex, because a compare view is 
composed of panes that may be contributed by different plugins, and they don't know about 
each other.  Not trivial to just add all these actions to the context menu.

compare FW sometimes spontaneously changes focus between tree and editor.  
This messes with screen readers and magnifiers, which rely heavily on widget focus.


NOTES: