|
Hello, everyone. I wrote about this earlier.
I have learned more. Zoom is perfectly accessible with JAWS
16. However, with NVDA, it is not completely so. For example,
when you press alt+a to mute or un-mute audio, JAWS announces
the fact that audio is either muted or un-muted, but, NVDA
says nothing.
In edit fields, JAWS can easily review them
by using arrow keys, it announces what characters you arrow to
or over. With NVDA, review of text in edit fields is not
easy to do. It does not announce what character you are on
when you arrow to or over characters.
These are issues that I believe should be
seriously looked into and fixed. This is a program used in
work environments, and should be used in more places due to
accessibility of the product. Right now, I have to use JAWS 16
to get full access. This should not be so. I hope this one can
be rectified soon.
p.s. I think that the issues, or some of
them, might be related to ARIA. If I can help in any way to
get this working, I will. Let me know how I can help.
|
|
|
JM Casey <crystallogic@...>
Yeah, I just started using this myself, and it does work really well with JAWS 18. I haven’t yet tried it with nVDA, but that’s on the horizon. Now I know what to expect. It’s a hell of a lot better than skype, anyway. *grins*
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Governor staten
Sent: November 10, 2017 2:02 PM
To: nvda@nvda.groups.io
Subject: [nvda] Zoom and NVDA Hello, everyone. I wrote about this earlier. I have learned more. Zoom is perfectly accessible with JAWS 16. However, with NVDA, it is not completely so. For example, when you press alt+a to mute or un-mute audio, JAWS announces the fact that audio is either muted or un-muted, but, NVDA says nothing. In edit fields, JAWS can easily review them by using arrow keys, it announces what characters you arrow to or over. With NVDA, review of text in edit fields is not easy to do. It does not announce what character you are on when you arrow to or over characters. These are issues that I believe should be seriously looked into and fixed. This is a program used in work environments, and should be used in more places due to accessibility of the product. Right now, I have to use JAWS 16 to get full access. This should not be so. I hope this one can be rectified soon. p.s. I think that the issues, or some of them, might be related to ARIA. If I can help in any way to get this working, I will. Let me know how I can help.
|
|
|
Just to provide more info, I"m using the
latest NVDA snapshot in the Next branch. There might be a
version where everything works as expected with Zoom. However,
I don't know what that version of NVDA would be.
On 11/10/2017 4:34 PM, JM Casey wrote:
toggle quoted messageShow quoted text
Yeah,
I just started using this myself, and it does work really
well with JAWS 18. I haven’t yet tried it with nVDA, but
that’s on the horizon. Now I know what to expect.
It’s
a hell of a lot better than skype, anyway. *grins*
Hello, everyone. I wrote
about this earlier. I have learned more. Zoom is perfectly
accessible with JAWS 16. However, with NVDA, it is not
completely so. For example, when you press alt+a to mute
or un-mute audio, JAWS announces the fact that audio is
either muted or un-muted, but, NVDA says nothing.
In edit fields, JAWS can
easily review them by using arrow keys, it announces what
characters you arrow to or over. With NVDA, review of
text in edit fields is not easy to do. It does not
announce what character you are on when you arrow to or
over characters.
These are issues that I
believe should be seriously looked into and fixed. This is
a program used in work environments, and should be used in
more places due to accessibility of the product. Right
now, I have to use JAWS 16 to get full access. This should
not be so. I hope this one can be rectified soon.
p.s. I think that the
issues, or some of them, might be related to ARIA. If I
can help in any way to get this working, I will. Let me
know how I can help.
|
|
|
Hi,
In general, I would say if something doesn't work in Next, it is often worth double checking the latest stable build to make sure it's not a regression. In terms of Zoom, I don't think we've done any work on this recently so I suspect it will be the same between versions.
If you are able to do that Governor Staten, that will ensure you are kept up to date with work done on this issue.
Kind regards
Quentin.
On Sat, Nov 11, 2017 at 8:39 AM, Governor staten <govsta@...> wrote:
Just to provide more info, I"m using the
latest NVDA snapshot in the Next branch. There might be a
version where everything works as expected with Zoom. However,
I don't know what that version of NVDA would be.
On 11/10/2017 4:34 PM, JM Casey wrote:
Yeah,
I just started using this myself, and it does work really
well with JAWS 18. I haven’t yet tried it with nVDA, but
that’s on the horizon. Now I know what to expect.
It’s
a hell of a lot better than skype, anyway. *grins*
Hello, everyone. I wrote
about this earlier. I have learned more. Zoom is perfectly
accessible with JAWS 16. However, with NVDA, it is not
completely so. For example, when you press alt+a to mute
or un-mute audio, JAWS announces the fact that audio is
either muted or un-muted, but, NVDA says nothing.
In edit fields, JAWS can
easily review them by using arrow keys, it announces what
characters you arrow to or over. With NVDA, review of
text in edit fields is not easy to do. It does not
announce what character you are on when you arrow to or
over characters.
These are issues that I
believe should be seriously looked into and fixed. This is
a program used in work environments, and should be used in
more places due to accessibility of the product. Right
now, I have to use JAWS 16 to get full access. This should
not be so. I hope this one can be rectified soon.
p.s. I think that the
issues, or some of them, might be related to ARIA. If I
can help in any way to get this working, I will. Let me
know how I can help.
-- Quentin Christensen
Training and Support Manager
|
|
|
I will do that. Another thing of note is that
no scripts for JAWS are being used.
On 11/12/2017 10:02 PM, Quentin
Christensen wrote:
toggle quoted messageShow quoted text
Hi,
In general, I would say if something doesn't work in Next,
it is often worth double checking the latest stable build to
make sure it's not a regression. In terms of Zoom, I don't
think we've done any work on this recently so I suspect it
will be the same between versions.
If you are able to do that Governor Staten, that will
ensure you are kept up to date with work done on this issue.
Kind regards
Quentin.
|
|
|
I've mentioned this on this list before.
I've also spoken to zoom, and they told me they're talking to
anything that will listen though msaa.
I believe this is so, because not only does zoom notifications
read with JAWS, but they are also read in narrator under windows
10. The rest of the client works reasonably well with it as well.
So it sounds like a tiny piece of something is missing.
If it gets fixed, maybe this would inadvertently improve access
to other apps that we may not be aware of.
On 11/12/2017 10:02 PM, Quentin
Christensen wrote:
toggle quoted messageShow quoted text
Hi,
In general, I would say if something doesn't work in Next,
it is often worth double checking the latest stable build to
make sure it's not a regression. In terms of Zoom, I don't
think we've done any work on this recently so I suspect it
will be the same between versions.
If you are able to do that Governor Staten, that will
ensure you are kept up to date with work done on this issue.
Kind regards
Quentin.
|
|
|
is there an issue on this yet?
if not, I will create it.
Contact me on skype: brian.moore
follow me on twitter:
http://www.twitter.com/bmoore123
On 2017-11-12 10:16 PM, Derek Lane
wrote:
toggle quoted messageShow quoted text
I've mentioned this on this list before.
I've also spoken to zoom, and they told me they're talking to
anything that will listen though msaa.
I believe this is so, because not only does zoom notifications
read with JAWS, but they are also read in narrator under windows
10. The rest of the client works reasonably well with it as
well.
So it sounds like a tiny piece of something is missing.
If it gets fixed, maybe this would inadvertently improve access
to other apps that we may not be aware of.
On 11/12/2017 10:02 PM, Quentin
Christensen wrote:
Hi,
In general, I would say if something doesn't work in
Next, it is often worth double checking the latest stable
build to make sure it's not a regression. In terms of Zoom,
I don't think we've done any work on this recently so I
suspect it will be the same between versions.
If you are able to do that Governor Staten, that will
ensure you are kept up to date with work done on this issue.
Kind regards
Quentin.
|
|
|
I'll put up the ticket shortly.
On 11/13/2017 7:48 AM, Brian Moore
wrote:
toggle quoted messageShow quoted text
is there an issue on this yet?
if not, I will create it.
Contact me on skype: brian.moore
follow me on twitter:
http://www.twitter.com/bmoore123
On 2017-11-12 10:16 PM, Derek Lane
wrote:
I've mentioned this on this list before.
I've also spoken to zoom, and they told me they're talking to
anything that will listen though msaa.
I believe this is so, because not only does zoom
notifications read with JAWS, but they are also read in
narrator under windows 10. The rest of the client works
reasonably well with it as well.
So it sounds like a tiny piece of something is missing.
If it gets fixed, maybe this would inadvertently improve
access to other apps that we may not be aware of.
On 11/12/2017 10:02 PM, Quentin
Christensen wrote:
Hi,
In general, I would say if something doesn't work in
Next, it is often worth double checking the latest stable
build to make sure it's not a regression. In terms of
Zoom, I don't think we've done any work on this recently
so I suspect it will be the same between versions.
If you are able to do that Governor Staten, that will
ensure you are kept up to date with work done on this
issue.
Kind regards
Quentin.
|
|
|
Lino Morales <linomorales001@...>
What's the URL for Zoom? I've been wanting off the Skype train
for a while. If anyone knows email me at:
lino.jr@...
Thanks.
On 11/12/2017 10:16 PM, Derek Lane
wrote:
toggle quoted messageShow quoted text
I've mentioned this on this list before.
I've also spoken to zoom, and they told me they're talking to
anything that will listen though msaa.
I believe this is so, because not only does zoom notifications
read with JAWS, but they are also read in narrator under windows
10. The rest of the client works reasonably well with it as
well.
So it sounds like a tiny piece of something is missing.
If it gets fixed, maybe this would inadvertently improve access
to other apps that we may not be aware of.
On 11/12/2017 10:02 PM, Quentin
Christensen wrote:
Hi,
In general, I would say if something doesn't work in
Next, it is often worth double checking the latest stable
build to make sure it's not a regression. In terms of Zoom,
I don't think we've done any work on this recently so I
suspect it will be the same between versions.
If you are able to do that Governor Staten, that will
ensure you are kept up to date with work done on this issue.
Kind regards
Quentin.
|
|
|
toggle quoted messageShow quoted text
What's the URL for Zoom? I've been wanting off the Skype train
for a while. If anyone knows email me at:
lino.jr@...
Thanks.
On 11/12/2017 10:16 PM, Derek Lane
wrote:
I've mentioned this on this list before.
I've also spoken to zoom, and they told me they're talking to
anything that will listen though msaa.
I believe this is so, because not only does zoom
notifications read with JAWS, but they are also read in
narrator under windows 10. The rest of the client works
reasonably well with it as well.
So it sounds like a tiny piece of something is missing.
If it gets fixed, maybe this would inadvertently improve
access to other apps that we may not be aware of.
On 11/12/2017 10:02 PM, Quentin
Christensen wrote:
Hi,
In general, I would say if something doesn't work in
Next, it is often worth double checking the latest stable
build to make sure it's not a regression. In terms of
Zoom, I don't think we've done any work on this recently
so I suspect it will be the same between versions.
If you are able to do that Governor Staten, that will
ensure you are kept up to date with work done on this
issue.
Kind regards
Quentin.
|
|
|
It is more for business use. However, they
give you a free account that allows you to do some things. So,
you could use it between friends and family.
On 11/13/2017 4:26 PM, Lino Morales
wrote:
toggle quoted messageShow quoted text
What's the URL for Zoom? I've been wanting off the Skype train
for a while. If anyone knows email me at:
lino.jr@...
Thanks.
On 11/12/2017 10:16 PM, Derek Lane
wrote:
I've mentioned this on this list before.
I've also spoken to zoom, and they told me they're talking to
anything that will listen though msaa.
I believe this is so, because not only does zoom
notifications read with JAWS, but they are also read in
narrator under windows 10. The rest of the client works
reasonably well with it as well.
So it sounds like a tiny piece of something is missing.
If it gets fixed, maybe this would inadvertently improve
access to other apps that we may not be aware of.
On 11/12/2017 10:02 PM, Quentin
Christensen wrote:
Hi,
In general, I would say if something doesn't work in
Next, it is often worth double checking the latest stable
build to make sure it's not a regression. In terms of
Zoom, I don't think we've done any work on this recently
so I suspect it will be the same between versions.
If you are able to do that Governor Staten, that will
ensure you are kept up to date with work done on this
issue.
Kind regards
Quentin.
|
|
|
Lino Morales <linomorales001@...>
Well if its meant for business I'm not interested. I wish Viber
was accessible with NVDA.
On 11/13/2017 4:30 PM, Governor staten
wrote:
toggle quoted messageShow quoted text
It is more for business use. However, they
give you a free account that allows you to do some things.
So, you could use it between friends and family.
On 11/13/2017 4:26 PM, Lino Morales
wrote:
What's the URL for Zoom? I've been wanting off the Skype
train for a while. If anyone knows email me at:
lino.jr@...
Thanks.
On 11/12/2017 10:16 PM, Derek Lane
wrote:
I've mentioned this on this list before.
I've also spoken to zoom, and they told me they're talking
to anything that will listen though msaa.
I believe this is so, because not only does zoom
notifications read with JAWS, but they are also read in
narrator under windows 10. The rest of the client works
reasonably well with it as well.
So it sounds like a tiny piece of something is missing.
If it gets fixed, maybe this would inadvertently improve
access to other apps that we may not be aware of.
On 11/12/2017 10:02 PM, Quentin
Christensen wrote:
Hi,
In general, I would say if something doesn't work in
Next, it is often worth double checking the latest
stable build to make sure it's not a regression. In
terms of Zoom, I don't think we've done any work on this
recently so I suspect it will be the same between
versions.
If you are able to do that Governor Staten, that will
ensure you are kept up to date with work done on this
issue.
Kind regards
Quentin.
|
|
|
JM Casey <crystallogic@...>
Well, nothing’s stopping you from using the programme for personal (non-business) use as far as I know. You can still create meetings and so on with a free account. Then someone who has the URL joins you, etc.
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Lino Morales
Sent: November 13, 2017 4:33 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Zoom and NVDA Well if its meant for business I'm not interested. I wish Viber was accessible with NVDA. On 11/13/2017 4:30 PM, Governor staten wrote: It is more for business use. However, they give you a free account that allows you to do some things. So, you could use it between friends and family.
On 11/13/2017 4:26 PM, Lino Morales wrote: What's the URL for Zoom? I've been wanting off the Skype train for a while. If anyone knows email me at: lino.jr@... Thanks. On 11/12/2017 10:16 PM, Derek Lane wrote: I've mentioned this on this list before. I've also spoken to zoom, and they told me they're talking to anything that will listen though msaa. I believe this is so, because not only does zoom notifications read with JAWS, but they are also read in narrator under windows 10. The rest of the client works reasonably well with it as well. So it sounds like a tiny piece of something is missing. If it gets fixed, maybe this would inadvertently improve access to other apps that we may not be aware of. On 11/12/2017 10:02 PM, Quentin Christensen wrote: Hi, In general, I would say if something doesn't work in Next, it is often worth double checking the latest stable build to make sure it's not a regression. In terms of Zoom, I don't think we've done any work on this recently so I suspect it will be the same between versions. If you are able to do that Governor Staten, that will ensure you are kept up to date with work done on this issue. On Sat, Nov 11, 2017 at 8:39 AM, Governor staten <govsta@...> wrote: Just to provide more info, I"m using the latest NVDA snapshot in the Next branch. There might be a version where everything works as expected with Zoom. However, I don't know what that version of NVDA would be.
On 11/10/2017 4:34 PM, JM Casey wrote: Yeah, I just started using this myself, and it does work really well with JAWS 18. I haven’t yet tried it with nVDA, but that’s on the horizon. Now I know what to expect. It’s a hell of a lot better than skype, anyway. *grins* Hello, everyone. I wrote about this earlier. I have learned more. Zoom is perfectly accessible with JAWS 16. However, with NVDA, it is not completely so. For example, when you press alt+a to mute or un-mute audio, JAWS announces the fact that audio is either muted or un-muted, but, NVDA says nothing. In edit fields, JAWS can easily review them by using arrow keys, it announces what characters you arrow to or over. With NVDA, review of text in edit fields is not easy to do. It does not announce what character you are on when you arrow to or over characters. These are issues that I believe should be seriously looked into and fixed. This is a program used in work environments, and should be used in more places due to accessibility of the product. Right now, I have to use JAWS 16 to get full access. This should not be so. I hope this one can be rectified soon. p.s. I think that the issues, or some of them, might be related to ARIA. If I can help in any way to get this working, I will. Let me know how I can help.
-- Quentin Christensen
Training and Support Manager
|
|
|
You get one to one connections unlimited free. One to many (more than one connection) Up to 50 requires a paid account for longer than 40 minute calls. Thanks, Sam
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of JM Casey
Sent: Monday, November 13, 2017 3:30 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Zoom and NVDA Well, nothing’s stopping you from using the programme for personal (non-business) use as far as I know. You can still create meetings and so on with a free account. Then someone who has the URL joins you, etc. Well if its meant for business I'm not interested. I wish Viber was accessible with NVDA. On 11/13/2017 4:30 PM, Governor staten wrote: It is more for business use. However, they give you a free account that allows you to do some things. So, you could use it between friends and family.
On 11/13/2017 4:26 PM, Lino Morales wrote: What's the URL for Zoom? I've been wanting off the Skype train for a while. If anyone knows email me at: lino.jr@... Thanks. On 11/12/2017 10:16 PM, Derek Lane wrote: I've mentioned this on this list before. I've also spoken to zoom, and they told me they're talking to anything that will listen though msaa. I believe this is so, because not only does zoom notifications read with JAWS, but they are also read in narrator under windows 10. The rest of the client works reasonably well with it as well. So it sounds like a tiny piece of something is missing. If it gets fixed, maybe this would inadvertently improve access to other apps that we may not be aware of. On 11/12/2017 10:02 PM, Quentin Christensen wrote: Hi, In general, I would say if something doesn't work in Next, it is often worth double checking the latest stable build to make sure it's not a regression. In terms of Zoom, I don't think we've done any work on this recently so I suspect it will be the same between versions. If you are able to do that Governor Staten, that will ensure you are kept up to date with work done on this issue. On Sat, Nov 11, 2017 at 8:39 AM, Governor staten <govsta@...> wrote: Just to provide more info, I"m using the latest NVDA snapshot in the Next branch. There might be a version where everything works as expected with Zoom. However, I don't know what that version of NVDA would be.
On 11/10/2017 4:34 PM, JM Casey wrote: Yeah, I just started using this myself, and it does work really well with JAWS 18. I haven’t yet tried it with nVDA, but that’s on the horizon. Now I know what to expect. It’s a hell of a lot better than skype, anyway. *grins* Hello, everyone. I wrote about this earlier. I have learned more. Zoom is perfectly accessible with JAWS 16. However, with NVDA, it is not completely so. For example, when you press alt+a to mute or un-mute audio, JAWS announces the fact that audio is either muted or un-muted, but, NVDA says nothing. In edit fields, JAWS can easily review them by using arrow keys, it announces what characters you arrow to or over. With NVDA, review of text in edit fields is not easy to do. It does not announce what character you are on when you arrow to or over characters. These are issues that I believe should be seriously looked into and fixed. This is a program used in work environments, and should be used in more places due to accessibility of the product. Right now, I have to use JAWS 16 to get full access. This should not be so. I hope this one can be rectified soon. p.s. I think that the issues, or some of them, might be related to ARIA. If I can help in any way to get this working, I will. Let me know how I can help.
-- Quentin Christensen
Training and Support Manager
|
|
|
