Hello all, Sorry to post this here, but I am pretty sure there are a few blind win32 users who frequent the list. I'm looking for a blind win32 user or someone visually impaired enough to depend on assistive technology to use applications. I am doing research related to win32 development and assistive technologies. Essentially I'm trying to make sure a new application will be usable by the differently abled. Please contact me offlist if you are interested in helping. jack.
Jack I am not blind, but the customer that I am using Icecast for is a reading service for the blind and print handicapped. I have a similar interest in possibly developing my systems so that they are compatible with screen readers. I do know that the screen reader that I hear the most about is JAWS. At this point I do not own a copy, so I'm not in a position to do any testing, even for my own use. Some of the services that are similar to ours do have blind staff members, so any development that either you or I do would be enhanced by being accessible. I'm not a lot of help right now, but if you think of something that I could do, please let me know. Regards Dick Trump dtrump1@triadav.com
I'm not blind but I write commercial broadcasting win32 software that a lot of blind users like and use, because it uses standard Windows controls; I always make sure everything can be done using keyboard shortcuts; and navigation is possible using tab. 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. Regards, Ross. ----- Original Message ----- From: "Jack Moffitt" <jack@xiph.org> To: <icecast@xiph.org> Sent: Wednesday, August 24, 2005 2:56 PM Subject: [Icecast] looking for blind win32 users Hello all, Sorry to post this here, but I am pretty sure there are a few blind win32 users who frequent the list. I'm looking for a blind win32 user or someone visually impaired enough to depend on assistive technology to use applications. I am doing research related to win32 development and assistive technologies. Essentially I'm trying to make sure a new application will be usable by the differently abled. Please contact me offlist if you are interested in helping. jack. _______________________________________________ Icecast mailing list Icecast@xiph.org http://lists.xiph.org/mailman/listinfo/icecast
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