Re: [pygame] Tutorial... GUI

["RR4CLB" <chester_lab@xxxxxxxxxxxx>]

Marcus,

    Correct, for I finally got the scoop on that. When getting my son back what I was reading was the graphic symbol for Python, a snake, then the title bar, then the 3 standard buttons, min, Max, and close. I have programmed them in a set file and it calls there labels with text up every time I load the Python screen. When going to that screen, alt tab, it focuses on the Python symbol. Verbalizing it every time.

    Nothing else is readable until we go back to the console page. But I guess the title bar could be used to send the message as well, to keep it within the same window. I will try it and see.

    But the tab feature works, the message gets printed in the console window. I tried triggering that message and it failed so I will have to ask WE for the reason for that. Probably sequence is in error on that. For the screen reader can be in different windows and respond to changes, but the console seems to not respond as of yet to that. When sensing changes in the Python window, it does say window is triggered. So it does know that something has changed, but what? is the issue.

    So there is always a way around things, not the standard print window, can things be located on the screen using positioning? Then setting up tables to run from there? I mean the console window.

    I will check it out, but the more I read and run and test, the faster I learn the language. I am not one for just reading, I like to test and change...

    Thanks, I wish it could be faster in release. This would give a lot of possibilities for us, I mean the sightless to play with.

    Thanks again, I appreciate you taking the time.

        Bruce



This sounds like it identifies the menu button of the window as button.
The title, min, max and close controls are native Windows controls,
which it places on the window created for the pygame display.  I guess,
that it provides you only those information and the size, the window
occupies on your screen.

So you can minimize, maximize or close the window, read its title bar
and access the window menu button (which provides information in a menu
like "properties, "minimize", "maximize", "close").

All those items are part of the native window layout, Win32 applications
use, not of the pygame window itself.

It does not sound to me like it would identify anything which is shown
within the pygame window (such as the both test buttons). This leads us
once more to the assumption, that the screen reader can not identify
anything on the pygame window, which would make it necessary to provide
additional information using the offered accessibility technologies such
as MSAA and ATK/AT-SPI.

Regards
Marcus

No. The user interface controls of OcempGUI currently do not support
ATK/AT-SPI, but it is planned in a later version (possibly around
version 0.3.0).

What I meant was, that the screen readers I tried so far were only able
to support MSAA (or ATK/AT-SPI) enabled applications and the console,
thus leaving applications, which do not implement those features, aside
and inaccessible for users of assistive technologies. They were not
capable of distinguishing between colors or something like that but
merely relied upon those accessibility libraries to provide the
necessary information.