Re: static link announcement in the commit dialogue.

On 16.12.2009 22:23, Serge Tumanyan wrote:
> 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.

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).

Also, I've tried with the Thunder screen reader, and at least this one
seems to work fine with those links.

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.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2431296
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].