Gabor Szabo wrote:
Hi,
There was a recent thread on PerlMonks with the above title
where I suggested the use of wxPerl.
http://www.perlmonks.org/?node_id=722367
I wonder what is really the issue?
How can one make sure that the application s/he is writing
has the accessibility features?
As Octavian already wrote, wxWidgets/wxPerl applications
are accessible when you use the widgets that map directly to
native widgets (and obviously the OS is correctly configured,
but that is a separate issue).
The widgets written using wxWidgets but that draw some part of
the interface themselves (wxHTML, wxCalendarCtrl, wxRichTextCtrl, ...)
are not accessible because the accessibility interface only sees
a blank window and has no means to interpret the content.
What is missing in wxPerl (and is only available on wxWidgets
for Win32, anyway) are the APIs to describe custom widgets to
the accessibility support in the OS. [1]
Regards,
Mattia
[1] it more-or-less work this way: te OS asks the application
to describe itself and the application recursively enumerates all
of it controls and subcontrols and the action you can do with them
