Community
Participate
Working Groups
UILabel now has getLocalizedLabel and getLocalizedTooltip the same must be available for accessibilityPhrase
I am not at all sure what's the purpose of the accessibilityPhrase. Eric, is it used anywhere?
I think the renderers are going to use this (currently they don't) to implement an IAccessabilityListener. I'm adding Eric to the CC-List ;-)
Yes, the accessibility phrase is a locale oriented string and should be handled accordingly (it's the string passed into the screen reader for visually impaired users).
thanks eric for the confirmation - I've released the change to HEAD >= 20110208
(In reply to comment #3) > Yes, the accessibility phrase is a locale oriented string and should be handled > accordingly (it's the string passed into the screen reader for visually > impaired users). 1) How do you plan to pass it to a screen reader? As far as I know there is no easy way other than exotic hidden widgets or custom implementation of accessible interfaces (which you don't want to do :-)). 2) Even if you manage to do (1) you'll have the "old" way for everything inside parts and the "new" way for the workbench itself.
(In reply to comment #5) > 1) How do you plan to pass it to a screen reader? As far as I know there is no > easy way other than exotic hidden widgets or custom implementation of > accessible interfaces (which you don't want to do :-)). This sounded a bit too strong. The easiest way to implement this is to provide accessible listener override with #getName() returning this new field. That, however, a) will require anybody who actually *needs* to override that accessibility listener to skip our code, and b) will prevent normal SWT accessibility code from working. Both of those are bad. It is possible to supply extra information via IAccessible2 interfaces, but so far it is only used to tie two widgets together. Plus, in practical terms, the support for IA2 is limited at the moment, so this can only be considered as supplemental solution, sort of an extra info is screen reader supports IA2. I'd recommend removing those fields until there is an actual implementation connecting them to a screen reader is available. As it is, it will only clutter the model and cause confusion as clients will expect those fields to do something.
Removing outdated target milestone.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
