Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 19 Oct 2005 17:08:37 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Sean McMahon cc: cygwin AT cygwin DOT com Subject: Re: Accessibility and Cygwin setup.exe In-Reply-To: <000c01c5d434$d01d5ba0$77ac7682@azwaterDOM.wr.usgs.gov> Message-ID: References: <43555948 DOT 1020103 AT student DOT lu DOT se> <000c01c5d434$d01d5ba0$77ac7682 AT azwaterDOM DOT wr DOT usgs DOT gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Ugh, top-posting... Reformatted. On Tue, 18 Oct 2005, Sean McMahon wrote: > ----- Original Message ----- > From: "Igor Pechtchanski" > To: "Lennart Borgman" > Cc: . Thanks. > Sent: Tuesday, October 18, 2005 1:45 PM > Subject: Re: Accessibility and Cygwin setup.exe > > > On Tue, 18 Oct 2005, Lennart Borgman wrote: > > > > > I read in the archives that there has been some discussions about > > > accessibility and Cygwin setup.exe. Are there any plans to improve > > > this? Keyboard support was not mentioned there but is also an > > > important accessibility feature for many people. Are there any plans > > > for keyboard support? > > > > I don't believe anyone has voiced plans for adding accessibility > > features to the current implementation of the setup package chooser. > > There are a couple of people (including me) working (slowly) on > > re-implementing the chooser completely using standard Windows > > controls, which will support keyboard interaction, screen readers, > > etc, automatically. > > > > Igor > > Igor, have you been able to get any documentation from screen reader and > screen magnification makers reguarding what are and are not accessible > window controlls? Glad to hear this is being worked on. > > Sean No, I have not tested my code with screen readers or any other accessibility software, as that's not my primary goal here. What I'd like to do is essentially decouple the logic from the GUI in setup, and have setup use standard Windows controls. The accessibility and keyboard interaction come as nice side benefits resulting from the use of standard controls. I'm assuming that the controls I'm planning to use (e.g., ListView) have sufficient accessibility support built-in. If and when I have some working code, I will request that people interested in accessibility test that code for the features they need. One thing I forgot to mention in my previous reply is that while using the standard Windows controls is my choice, nothing prevents others from submitting patches with alternate approaches (including patching the current code for accessibility). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. /DA -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/