Hi!
Hmmmm, maybe, unless each program is done on a different screen. like a DOS
window verses a graphical screen. Like the mixer program I just posted. I added
comments in it from what I discovered and such. Now the cursor locations and
such may work for a text version, but the buttons and such I have yet to try.
They do want a location on the screen and I did notice that tab is suppose to
work, which possibly allows getting back and forth between buttons. Don't know
until I try them. Getting the format right is nine-tenths of the battle. So,
getting the button commands syntax I need to do first. Placing it on the
screen, then seeing what happens is my first goal. The rest may have to be just
using a text screen for sightless and graphical version for the sighted.
In the example I did with the sound it did have graphics icons at the top
for exit/stop and Max/min, the screen reader program can label them, save them,
and call them back up with that screen type...when the program is run again at
a later time.
So, first lets try some examples and see where it goes from there.
Bruce
I think you will find it very difficult to make a pygame application accessible
to people with screenreaders, since it has no concept of "text", "buttons" etc.
There is literally only a collection of pixels in memory.
Regards,
Ulf
--------------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.488 / Virus Database: 269.13.30/1030 - Release Date: 9/25/2007
8:02 AM
