Continuing a discussion from fpc-pascal:

>  >That was my concern too when Fred started with the accessibility options
>> for MSEgui. I suggested to use and extend the "iassistiveclient" and 
>> "iassistiveserver" interfaces of MSEgui in order to connect to standard 
>> screen readers instead to implement own reader functionality.
> Hum, not sure that connect MSEgui assistive interface to a "standard screen
> readers" instead of SAK will solve anything.
> (Even it will be worst, take a look at Lazarus + AT-SPI).

The advantage would be that the users can use the screenreader they are
used to. But maybe - as you write - it is not possible to achieve good
results if the application is not a 100% default Windows application.


mseide-msegui-talk mailing list

Reply via email to