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 Message-ID: <4356D520.DE9C3726@dessent.net> Date: Wed, 19 Oct 2005 16:22:08 -0700 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Accessibility and Cygwin setup.exe References: <43555948 DOT 1020103 AT student DOT lu DOT se> <000c01c5d434$d01d5ba0$77ac7682 AT azwaterDOM DOT wr DOT usgs DOT gov> <001301c5d4fc$4e206480$77ac7682 AT azwaterDOM DOT wr DOT usgs DOT gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Sean McMahon wrote: > > Well, getting decent keyboard access is naturally an interest of mine. I'll see > what I can dig up about this from my screen-reader manufacturer. More then > likely your assumption is correct, but if it doesn't work with "standard" > windows controlls, that's also something I need to know. I've not any experience with screen readers, but from what I can tell the main thing is that if we use standard widgets provided by the OS or by the common controls DLL, we should be fine. The current problem is that the package chooser is a custom window that does everything itself, and so it is completely opaque to things like screen readers. That does present a very small problem with the fact that setup has to support all versions of windows back to 95, which means we can't assume any given version of the common controls DLL. (Or maybe we alredy do? I'll have to look.) Some of the neat stuff that MS addded for 2k and XP will not be available in the older versions, but I think there should be enough functionality to implement a package selection screen. Brian -- 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/