Stefan,
>> 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.
>
> I've already changed the links in r18013 (on tuesday) so that they're
> tab stops (i.e., they now have the WS_TABSTOP window style).
I have played with them a bit and the Tab-order situation seems to become
better then before.
Can you please also assign them the accRole property that they are links?
Do you make some of them as disabled when they can not be clicked?
At least I managed to Tab only to the 'All' and 'None' links and suppose
that you are disabling those that can not be activated with g
> Also, I've tried with the Thunder screen reader, and at least this one
> seems to work fine with those links.
Thunder is taken by into account only because this screenreader is totally
free. We should rely on JAWS screenreader in first turn because it takes
about 70% of the market of screen reading software and is one of the most
usable among the blind programmers.
> Does the problem still exist for you in the latest nightly build?
> Because I'd like to keep the links as they are now and not use the
> SysLink control. Because the SysLink control is made for 'real' links
> which open a browser and not for what we use them in the commit dialog.
> While the SysLink control can be programmed to work like that too, it
> requires a lot of tweaking which I'd like to avoid.
The situation is a bit better now and lets try to avoid too much problems
and try to find the most accurate and simple descision here. I believe that
we should move here step by step looking very attentively after every step
and finally we shall solve the problem in the most accurate way.
The first step was done by you and it seems to be very good step.
Lets perform the second step and assign a accRole property to the static
text, Ok and see what the results will be here?
Thank you.
Serge.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2431342
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-12-18 00:41:00 CET