On Jun 15, 2020, at 11:21, Shaun Everiss <sm.everiss@gmail.com> wrote:

Hmmm what about contacting sisco on this, sisco do run access courses etc so well they are access concious.

They probably will fix this thing.

On 16/06/2020 4:46 am, Ben J. Bloomgren wrote:
Jabber has been a nightmare to me. I’m glad to know that someone thinks it’s accessible.

On Jun 15, 2020, at 07:23, Marquette, Ed <ed.marquette@kutakrock.com> wrote:

All:

I know at least one other member of this list is a Jabber user. Jabber, a Cisco softphone product, is really wonderful and is mostly accessible. When office phones are not accessible or only marginally accessible, Jabber really helps, and because it is a Cisco product, the IT departments in large companies do not push back--as they do with programs having less recognized pedigrees. Jabber is even more important now that many, if not most, of us are working primarily from our home offices.
NVDA works quite well with Jabber on 95% of the calling features; however, it does not give the "STATUS" of the person being called, and it does not work well with Jabber's live chat feature.
JAWS handles these features fine, but JAWS is so bloated and so slow that our key application, a document management system, nearly chokes with JAWS running.
Once there was a Jabber add-in for NVDA, but it did not help with the above features.
Any assistance would be appreciated.





This E-mail message is confidential, is intended only for the named recipients above and may contain information
that is privileged, attorney work product or otherwise protected by applicable law. If you have received this
message in error, please notify the sender at 402-346-6000 and delete this E-mail message.
Thank you.