Comment 1 by Animesh.mr on 2013-07-17 15:26
Changes:
Changed title from "n v d a should be axes able with Pidgin" to "Pidgin should be axes able with n v d a"

Comment 2 by Palacee_hun on 2013-07-17 15:54
If you want this or that software to work (better) with NVDA, then please specify in detail what kind of problems you have with that software using NVDA. In this case I suppose you have tried out Pidgin with NVDA. What parts of the software caused accessibility problems and what were they? Without this information developers will have a hard time figuring out your problems and needs. I note that if Pidgin (or any other problematic software) ignores the existence of accessibility APIs or acts in quite non-standard ways (quite common unfortunately, I must say this is rather on the increase) then the core of NVDA can hardly cope with this; in this case the almost only viable solution is to develop an appmodule or an addon for that software.

Changes:
Changed title from "Pidgin should be axes able with n v d a" to "Pidgin should be accessible with NVDA"

Comment 3 by briang1 (in reply to comment 2) on 2013-07-17 17:24
Replying to Palacee_hun:

If you want this or that software to work (better) with NVDA, then please specify in detail what kind of problems you have with that software using NVDA. In this case I suppose you have tried out Pidgin with NVDA. What parts of the software caused accessibility problems and what were they? Without this information developers will have a hard time figuring out your problems and needs. I note that if Pidgin (or any other problematic software) ignores the existence of accessibility APIs or acts in quite non-standard ways (quite common unfortunately, I must say this is rather on the increase) then the core of NVDA can hardly cope with this; in this case the almost only viable solution is to develop an appmodule or an addon for that software.

Also the first port of call is always the writers, who may in fact not realise there is an issue and can thus fix it easily.
As has been said though, ignorance of the accessibility needs of blind users is a disgrace these days.I guess its just not taught to people

Comment 4 by jteh on 2013-07-18 02:27
As far as I know, Pidgin uses GTK+, which is (as far as I know) completely inaccessible in Windows. If I'm correct, there's nothing we can do. Either way, it'd be better to enhance the accessibility of Pidgin, rather than implementing screen reader specific work arounds.

@jcsteh You clearly implied in #3369 (comment) that accessibility should be incorporated into a specific app itself rather than working around in every screen reader separately, which I completely agree with. Does the NeedsExternalFix label suffice in this case or should this ticket be closed too on the same grounds? @ehollig

Closing because there's no chance we can even work around this without GTK implementing Windows accessibility, which is not likely to happen any time soon.