Stefan,
I have performed a lot of investigations and comparisons along with some
test dialogue creating to understand why the static labels that you use as
links are announced on opening the commit dialogue and here are the results:
1. The screen readers do prefer to announce the dialogue message text once
at the session - when the dialogue appears and when you have Alt+Tabbed to
it.
2. Microsoft recommends to make such text with the ControlID=0 and the first
in the order.
3. Nearly noone utilizes Microsoft recommendations.
As a result the screenreader authors try to catch all possible situations
and take all the text contained in static window class as a dialogue text
and this results in announcing the static lables that are used by you as
pseudo-links.
Here is the options I can suggest:
1. The best way here is to create real links that are handled as links, can
be placed in the Tab-order and can be assigned a hotkey.
2. To use the buttons as pseudo-links - you can create the buttons looking
as you like - links for example.
3. To use a toolbar for that - then you need to place only the whole toolbar
control into Tab-order - the navigation inside the toolbar is easily
performed with arrow keys if needed or to assign a special keystroke to land
focus in a toolbar without placing it into Tab-order.
4. The worst possible workaround can be to place all the labels that are
assumed to be as links to a separate wrapper window and this will stop
screenreaders from taking their text as a dialogue text and to assign the
ROLE_LINK to accRole property of every static text label. May be if you will
use the WS_TABSTOP window style the labels will be placed in Tab order.
Thank you.
Serge.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2430928
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-12-16 22:25:14 CET