[Icecast] looking for blind win32 users

[Ross Levis]

Thanks for that oddsock.  There are 3 further issues I just discovered.

1. In the configuration window, the YP Settings and Advanced Settings 
tabs do not work when using the arrow keys.

2. While in the configuration window, after pressing Enter on the OK or 
Cancel buttons, the focus is not returned to the main oddcast window.

3. The new minimize to system tray is less accessible to blind users.  I 
think this will need to be optional so blind users can minimise to the 
taskbar where they can Alt+Tab it visible again.
Alternatively, to save adding an option which needs to be saved 
somewhere, you could minimize to system tray when clicking the [X] Close 
form button, and minimize to taskbar for a normal minimize.  This should 
be much less work.

I think that's about it.  It should be very accessible after these 
changes.

Regards,
Ross.

----- Original Message ----- 
From: "oddsock" <oddsock at oddsock.org>
To: <icecast at xiph.org>
Sent: Wednesday, August 24, 2005 5:41 PM
Subject: Re: [Icecast] looking for blind win32 users


At 11:05 PM 8/23/2005, you wrote:

>Now I know Oddcast is not one of the standard Ogg tools, but I thought 
>I
>would take this opportunity to mention that it is almost unusable by
>blind users.  I believe v3 is much better than v2 since it uses 
>standard
>Windows controls, but it is impossible to tab to the encoder list and
>load an encoder configuration.  If a user manages to click in the
>encoder list and presses enter on a highlighted encoder, the whole
>window closes.  This should work the same as double-click.
>
>These 2 issues should be a simple fix so hopefully Oddsock can have a
>look at it.

fixed and released 3.0.10 (http://www.oddsock.org/tools/oddcastv3).  And
here I thought I had made a pretty darn accessible win32 app... I tend 
not
to get too many reports from blind users (and I know there are quite a 
few
out there in the broadcasting industry)...I guess I figured that "no
reports" meant things were good....

p.s. and to answer Jack's question, yes, it's all about using standard
windows controls, no bitmapped controls, and having keyboard 
accelerators
for everything (oddcast doesn't do a good job at this).  Naming the
controls I believe is also significant (although I cannot confirm this
since I don't have a screen-reader myself).  It's important to not name
your controls IDC_BUTTON1, etc. and to make sure you have static text
fields describing the fields juxtaposed with the fields they refer 
to....

oddsock