Yes, but that is a web application which is a mixture of html and
flash. Michael's complaint or point was stand alone flash apps that
are not web based have accessibility issues. My theory was that the
Flash runtime environment for Windows doesn't always return the
controls or text to the screen reader because its a non-standard API
for Windows applications. Screen readers as a rule rely on core
Windows APIs like the Win32 API and MSAA to gather onscreen
information when and where possible. Java's Swing toolkit, for
example, doesn't use any standard Windows APIs and therefore is
outside the norm and requires a special API, the Java Access Bridge,
to be present in order to communicate onscreen information to the
screen reader assuming the screen reader supports it. This is in large
part why there is accessibility issues with applications, because not
every language, graphics toolkit, etc sticks to a standard and screen
reader developers have to go out of their way to support other
applications using non-standard APIs and toolkits.
On 8/15/11, dark <d...@xgam.org> wrote:
> Hi Tom.
> Interestingly enough, hal actually can interact with flash controls provided
> they use standard text and buttons, so it is possible to for instance use
> the play, rewind etc controls for utube by positioning virtual focus over
> the windows and hitting capslock F to get the flash mode going. Obviously as
> with a windows ap, it helps if there is text involved, but even if not you
> can just hit the buttons.
> I'm not exactly sure how this works, but it does come in handy.
> Beware the grue!
Gamers mailing list __ Gamers@audyssey.org
If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org.
You can make changes or update your subscription via the web, at
All messages are archived and can be searched and read at
If you have any questions or concerns regarding the management of the list,
please send E-mail to gamers-ow...@audyssey.org.