Mira
On Fri, 25 Jul 2003 09:48:00 -0400 GMT(7/25/2003, 9:48 AM -0500 GMT), Steve M. Sawczyn
wrote:
I got this in a RITLAB group thought you might be interested! I
remember you talking about accessibility.
,----- [<[EMAIL PROTECTED]>]
'| In addition, if anyone is looking for someone to test
'| applications for accessibility, I'd be willing to do that as it'll
'| pave the way for other blind folks in the future.
`-----
SMS> Hello all,
SMS> My name is Steve Sawczyn and I am a totally blind computer user. I
SMS> access Windows with the help of a screen program called Window Eyes.
SMS> Essentially, Window Eyes uses a number of methods to verbalize
SMS> relevant information appearing on the screen.
SMS> Recently, I decided to switch to The Bat! from OUtlook. As I receive
SMS> around 800 messages daily from various lists,I feel the Bat! will
SMS> assist me with efficiently managing everything.
SMS> I've encountered some accessibility issues with the current release
SMS> version of the Bat! and have posted the following to the TBUDL list.
SMS> Although I'm not a programmer, I'd like to work with all of you on the
SMS> Beta list in an effort to make future versions of the Bat! more
SMS> accessible.
SMS> Again, my name is Steve and I'm glad to be on this list.
SMS> -- pasted message below
SMS> This is a forwarded message
SMS> From: Steve M. Sawczyn <[EMAIL PROTECTED]>
SMS> To: [EMAIL PROTECTED]
SMS> Date: Monday, July 21, 2003, 11:13:55 AM
SMS> Subject: Making the bat more accessible to screen readers
SMS> ===8<==============Original message text===============
SMS> Hello all,
SMS> As all of you know, I'm on a quest to make the Bat as accessible to
SMS> blind folks like myself who depend on screen reading technology. I'm not a
SMS> programmer, or developer, so if this post seems a bit vague, it's
SMS> probably due to my lack of understanding about programming.
SMS> Screen readers rely heavily on the way controls within an application
SMS> are classed. For example, when i encounter a list box, edit field,
SMS> radio button, etc..., the screen reader allows me to interact with
SMS> that control and, because it knows how these standard controls
SMS> operate, I get relevant feedback i.e. what is checked, what is
SMS> selected, etc... In those instances where an application does not
SMS> use standard classes, I have the option to reclass, that is I can tell
SMS> the screen reader to treat a control as a standard control essentially
SMS> overriding what the programmer intended. THe problem arises when the
SMS> control doesn't behave like a standard control and this is the main
SMS> access issue when it comes to the Bat.
SMS> According to the screen reader, the main message list, i.e. when
SMS> opening a folder, is classified as a MessageListview. Since this is
SMS> not a standard class, the screen reader isn't really sure how to
SMS> interact with this control. Fortunately, as standard highlighting is
SMS> used, the screen reader is able to read which message is highlighted.
SMS> UNfortunately, this precludes the graphics displayed to the left of
SMS> the message columns. Also, when a message is deleted, the screen
SMS> reader doesn't look for the next highlight as it doesn't think I need
SMS> that information. I tried reclassing this as a listview, but then
SMS> nothing is spoken. I'm not sure why this is -- the only feedback
SMS> I've gotten from the screen reader developers is that the control
SMS> doesn't emulate a standard listview.
SMS> Accessible applications seem to do one of three things:
SMS> #1 incorporate standard controls as defined by Microsoft.
SMS> #2 Support MSAA, Microsoft's Active Accessibility.
SMS> #3 Use their own controls, but emulate standard controls.
SMS> For more information on this in general, I would suggest the
SMS> following URL
SMS> http://www.microsoft.com/enable
SMS> In addition, the developers of the specific screen reading product
SMS> i'm using, Window Eyes, can be contacted in the US at (260) 489-3671.
SMS> They can be Emailed at:
SMS> [EMAIL PROTECTED]
SMS> or
SMS> http://www.gwmicro.com
SMS> Jaws is another popular screen reader. I've found that the same
SMS> access issues exist with Jaws -- presumably due to the issues
SMS> mentioned above.
SMS> I hope this information clarifies some of the access issues faced by
SMS> blind users using the Bat. If anyone can help me get this
SMS> information to the Bat development folks, I know I'd certainly
SMS> appreciate it. In addition, if anyone islooking for someone to test
SMS> applications for accessibility, I'd be willing to do that as it'll
SMS> pave the way for other blind folks in the future.
--
Love,
Jim
Using SecureBat! v1.62s on Windows 2000 5.0 Build 2195 Service Pack 3
________________________________________________________
Current beta is 1.63b11 | "Using TBBETA" information:
http://www.silverstones.com/thebat/TBUDLInfo.html
