Re: [pygame] Tutorial... GUI

["RR4CLB" <chester_lab@xxxxxxxxxxxx>]

Marcus,

"needs accessibility awareness through the MSAA library (or ATK/AT-SPI"

    I think that the MSAA library is exactly what we are talking about. I have not tried the new one yet, but I suspect that this is the issue. I can try and teach the screen reader to read a screen that is produced all the time and that may also work. But one step at a time is what I have to do in order to learn this. But the MSAA library is probably the issue. For all Window Eyes stuff is to focus on it. Even has a special key to get into and out of that mode. 


    So on to testing and I will get back with you.

    Thanks, Bruce

On, Thu Sep 27, 2007, RR4CLB wrote:

> 
>     I noticed just only one graphic symbol present. I labeled it and
> the ladle stayed the same for both, that means they are the same
> color/image. So when tabbing back and forth the first screen said
> button 1 or button 2 but the screen reader only read the same
> label. Also when tabbing I got no text, which means no text label
> in the button itself.

Which label did the screen reader read? Does it receive the button
information or only the title text of the pygame window?

I think, the screen reader cannot receive any information from the AT
software, because pygame (and SDL in general) simply does not support
such accessibility features.

However, I attached a slightly modified version of the button example,
in which the first button now receives a red background colour, the
second one a green background colour. If you could give it a try, it'd
be helpful for me to figure out on what I have to focus for the
accessibility systems.

> 
>     So, I guess there has to be a different color or image I would
>  have to use for each button. Also, text label for the button, is
>  that in this or forced to be in first screen window? For when it
>  said which was focused I had to go to the other screen by alt
>  tab. Control tab went back to the first button but the text label
>  I placed on it with the screen reader still read Button 2, because
>  of button color/image.

The visual representation of the buttons displays a textual label on
them as done in the code. I simply added a print function (which goes to
the other console window) for the focus so you can distinguish between
both buttons in case the screen reader cannot deal with them correctly.

I hope, the screen reader can recognize the changed example correctly
now. If not, we have to think of another solution as it is likely that
the screen reader won't be able to deal with any content displayed on
the pygame window then. This would mean that each object to be shown
needs accessibility awareness through the MSAA library (or ATK/AT-SPI
for unix).

Regards
Marcus