Bug 249 - [CVS UI] accessibility issues (1GK7A0R)
Summary: [CVS UI] accessibility issues (1GK7A0R)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.0   Edit
Hardware: All Windows NT
: P3 normal (vote)
Target Milestone: 3.0   Edit
Assignee: Platform-VCM-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: investigate, usability
Depends on:
Blocks:
 
Reported: 2001-10-10 21:38 EDT by John Arthorne CLA
Modified: 2004-03-15 21:49 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Arthorne CLA 2001-10-10 21:38:54 EDT
These are some notes JM and I made with regard to VCM accessibility.  See also
	1GK79UB: ITPUI:WINNT - Compare FW accessibility issues

Synchronize view issues:
	* The tree nodes in the synchronize view need to expose their state (i.e., incoming, 
	   outgoing, or conflicting), and their type (file or folder).  Currently this information is 
	   only contained in the icon.  Screen readers don't know how to decode this information.
	* Hotkeys for traversing to next and previous difference are not documented
	* When traversing through changes, an audible beep indicates end of file... 	
		may be a hearing-impaired issue.

File compare/replace dialog:
	* spontaneous focus switching
	* no access to toolbar
	* button actions don't have hotkeys
	* scrolling through version list with keyboard is painful, because for each version 
		selected it invokes a server round-trip.

Merge wizard:
	* no widget has initial focus, can't do anything without first clicking in dialog (same 
		as import/export wizards).


NOTES:
Comment 1 DJ Houghton CLA 2001-10-23 23:48:49 EDT
PRODUCT VERSION:

R0.9

Comment 2 Michael Valenta CLA 2002-09-06 19:27:35 EDT
We should investigate if this is still an issue
Comment 3 Jean-Michel Lemieux CLA 2004-03-15 21:49:59 EST
All of these have been addressed. Sync view can show change type in decorator,
navigation is hooked to standard next/previous commands. Keyboard support is
greatly improved.

If there are additional problems, we should enter separate PRs.

This is a really old bug, I had to clean some dust off it before reading...