|
Sean is absolutely correct here. Just upgrading to the latest version is not an answer.
In an organization with enterprise applications and stringent data security policies, ordinary users--even senior partners in large law firms--almost never have administrative privileges.
One has to schedule time with a member of the IT Department to install updates. In fact, I'm waiting right now to get the latest 2020 version of NVDA (I'm still on 2019.3).
Then, there is the question of whether the enterprise is ready to upgrade an enterprise application. Typically, an application will go through a testing phase, and at that, the version will be at least one (and usually two) releases back, the hope being that patches and bug fixes will have solved problems that almost inevitably accompany new releases.
Being a part of a large organization has its advantages, but there are disadvantages too.
toggle quoted message
Show quoted text
-----Original Message----- From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss via groups.io Sent: Tuesday, June 16, 2020 1:42 PM To: nvda@nvda.groups.io Subject: Re: [nvda] NVDA and Jabber [ CAUTION - EXTERNAL SENDER ] Well obviously you couldn't do it yourself in a work place, you need to ask for it. I found that out the hard way when updating my isp controled router last year I had to ask for it and was used to doing my own updates. On 16/06/2020 10:42 pm, Sean Murphy wrote: Shawn
when I used to work for Cisco, I supported the jabber application for accessibility. The last version I worked on was 12.7. Hence I have a far deeper knowledge than yourself and most people on this list. You just can’t upgrade such an application without your IT department support. Your comment on just upgrade to the latest version is very misplaced and clearly indicates you don’t have a full understanding on how enterprise applications work
Cisco‘s long-term is to remove the requirement of having any form of scripts or plug-ins for Windows screen readers.
Sean
My experience is the part
On 16 Jun 2020, at 8:13 pm, Shaun Everiss <sm.everiss@...> wrote:
Hmmm well obviously first you should get the latest update and try again if you are not updated.
On 16/06/2020 10:10 pm, Sean Murphy wrote:
I used to work for Cisco Systems in the accessibility team. Jabber version 12.1 and 4.0 support NVDA JabbJabber version 12.5 and later does not really supportnvda Jabber 12.7 and later I suspect the level of support has improved. Jabber 12.7 has a major uplift where you do not require Jaws scrips There are still some gaps here as well. I do not know about any later versions. My suggestion is send your complaints tMy suggestion is send your complaints to Cisco Be vebe very loud about it. The accessibility team will do their best but the ownership relies on the product teamThe accessibility team will do their best but the ownership relies on the product team.
My experience is the part
On 16 Jun 2020, at 12:23 am, Marquette, Ed <ed.marquette@...> 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.
|
|
|
Well obviously you couldn't do it yourself in a work place, you need to ask for it.
I found that out the hard way when updating my isp controled router last year I had to ask for it and was used to doing my own updates.
toggle quoted message
Show quoted text
On 16/06/2020 10:42 pm, Sean Murphy wrote: Shawn
when I used to work for Cisco, I supported the jabber application for accessibility. The last version I worked on was 12.7. Hence I have a far deeper knowledge than yourself and most people on this list. You just can’t upgrade such an application without your IT department support. Your comment on just upgrade to the latest version is very misplaced and clearly indicates you don’t have a full understanding on how enterprise applications work
Cisco‘s long-term is to remove the requirement of having any form of scripts or plug-ins for Windows screen readers.
Sean
My experience is the part
On 16 Jun 2020, at 8:13 pm, Shaun Everiss <sm.everiss@...> wrote:
Hmmm well obviously first you should get the latest update and try again if you are not updated.
On 16/06/2020 10:10 pm, Sean Murphy wrote:
I used to work for Cisco Systems in the accessibility team. Jabber version 12.1 and 4.0 support NVDA JabbJabber version 12.5 and later does not really supportnvda Jabber 12.7 and later I suspect the level of support has improved. Jabber 12.7 has a major uplift where you do not require Jaws scrips There are still some gaps here as well. I do not know about any later versions. My suggestion is send your complaints tMy suggestion is send your complaints to Cisco Be vebe very loud about it. The accessibility team will do their best but the ownership relies on the product teamThe accessibility team will do their best but the ownership relies on the product team.
My experience is the part
On 16 Jun 2020, at 12:23 am, Marquette, Ed <ed.marquette@...> 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.
|
|
|
Shawn
when I used to work for Cisco, I supported the jabber application for accessibility. The last version I worked on was 12.7. Hence I have a far deeper knowledge than yourself and most people on this list. You just can’t upgrade such an application without your IT department support. Your comment on just upgrade to the latest version is very misplaced and clearly indicates you don’t have a full understanding on how enterprise applications work
Cisco‘s long-term is to remove the requirement of having any form of scripts or plug-ins for Windows screen readers.
Sean
My experience is the part
toggle quoted message
Show quoted text
On 16 Jun 2020, at 8:13 pm, Shaun Everiss <sm.everiss@...> wrote:
Hmmm well obviously first you should get the latest update and try again if you are not updated.
On 16/06/2020 10:10 pm, Sean Murphy wrote:
I used to work for Cisco Systems in the accessibility team. Jabber version 12.1 and 4.0 support NVDA JabbJabber version 12.5 and later does not really supportnvda Jabber 12.7 and later I suspect the level of support has improved. Jabber 12.7 has a major uplift where you do not require Jaws scrips There are still some gaps here as well. I do not know about any later versions. My suggestion is send your complaints tMy suggestion is send your complaints to Cisco Be vebe very loud about it. The accessibility team will do their best but the ownership relies on the product teamThe accessibility team will do their best but the ownership relies on the product team.
My experience is the part
On 16 Jun 2020, at 12:23 am, Marquette, Ed <ed.marquette@...> 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.
|
|
|
Hmmm well obviously first you should get the latest update and try again if you are not updated.
toggle quoted message
Show quoted text
On 16/06/2020 10:10 pm, Sean Murphy wrote: I used to work for Cisco Systems in the accessibility team. Jabber version 12.1 and 4.0 support NVDA JabbJabber version 12.5 and later does not really supportnvda Jabber 12.7 and later I suspect the level of support has improved. Jabber 12.7 has a major uplift where you do not require Jaws scrips There are still some gaps here as well. I do not know about any later versions. My suggestion is send your complaints tMy suggestion is send your complaints to Cisco Be vebe very loud about it. The accessibility team will do their best but the ownership relies on the product teamThe accessibility team will do their best but the ownership relies on the product team.
My experience is the part
On 16 Jun 2020, at 12:23 am, Marquette, Ed <ed.marquette@...> 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.
|
|
|
I used to work for Cisco Systems in the accessibility team. Jabber version 12.1 and 4.0 support NVDA JabbJabber version 12.5 and later does not really supportnvda Jabber 12.7 and later I suspect the level of support has improved. Jabber 12.7 has a major uplift where you do not require Jaws scrips There are still some gaps here as well. I do not know about any later versions. My suggestion is send your complaints tMy suggestion is send your complaints to Cisco Be vebe very loud about it. The accessibility team will do their best but the ownership relies on the product teamThe accessibility team will do their best but the ownership relies on the product team.
My experience is the part
toggle quoted message
Show quoted text
On 16 Jun 2020, at 12:23 am, Marquette, Ed <ed.marquette@...> 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.
|
|
|
I should have mentioned I use Jabber 12.6.
The phone works pretty well, but the IM doesn't.
As I and others have mentioned JAWS is so slow that it isn't worth using.
I'll see if I can get 12.8.
toggle quoted message
Show quoted text
-----Original Message----- From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ben J. Bloomgren via groups.io Sent: Monday, June 15, 2020 1:35 PM To: nvda@nvda.groups.io Subject: Re: [nvda] NVDA and Jabber [ CAUTION - EXTERNAL SENDER ] Okay, that's good to know. My employer uses it for IM and soft phone, and I've not found that it works all that well. Thanks, Ben On Jun 15, 2020, at 11:21, Shaun Everiss <sm.everiss@...> 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@...> 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.
|
|
|
HI. this is very dependant on which version you have. 12.8 and later are pretty good for accessibility. However, we use 12.5 and it is very difficult with NVDa. The jaws scripts work but are so slow as to be almost not worth using. Brian. Contact me on skype: brian.moore follow me on twitter: http://www.twitter.com/bmoore123
On 6/15/2020 2:21 PM, Shaun Everiss 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@...> 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.
|
|
|
Ben J. Bloomgren
Okay, that's good to know. My employer uses it for IM and soft phone, and I've not found that it works all that well.
Thanks,
Ben
toggle quoted message
Show quoted text
On Jun 15, 2020, at 11:21, Shaun Everiss <sm.everiss@...> 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@...> 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.
|
|
|
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.
toggle quoted message
Show quoted text
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@...> 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.
|
|
|
Ben J. Bloomgren
Jabber has been a nightmare to me. I’m glad to know that someone thinks it’s accessible.
toggle quoted message
Show quoted text
On Jun 15, 2020, at 07:23, Marquette, Ed <ed.marquette@...> 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.
|
|
|
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.
|
|
|
