ncda 2016.1:
Kenny Peyattt jr.
Hi will nvda 2016.2.1 work with the anaversary update? Kenny Peyatt jr.
Sent from Mail for Windows 10
|
|
!
mistydbradley@...
|
|
OT: Progressive sound add-on/extension for firefox
Jacob Kruger
Sorry, just reinstalled latest version of firefox, to give it another go, and can't remember what the name was for the extension that offers a form of progress bar beeps for page loading?
TIA Jacob Kruger Blind Biker Skype: BlindZA "Resistance is futile, but, acceptance is versatile..."
|
|
Re: Some issues coming between Google Chrome and NVDA
Gene
I believe that Chrome usually fixes things as
well. But my impression is that problems get to production versions that
should have been corrected during beta testing more often and that are more
serious than Firefox problems that may crop up from time to time. Proper
testing and correction would get rid of such problems long before the production
versions are released. What I'm saying about Firefox versus Chrome is an
impression. it may be wrong and others may wish to comment. But
that's my impression from trying both programs as updated for many months.
Gene
----- Original Message -----
From: Brian's Mail list account Sent: Thursday, August 11, 2016 10:26 AM
Subject: Re: [nvda] Some issues coming between Google Chrome and
NVDA moment is all this now it workds now it won't stuff. They obviously do not test their new versions very well from what i can tell. At least firefox do fix things like they fixed the navigation sounds not working in 47, and its fine in the later versions, aand lists work properly in web pages as well. Btrian bglists@... Sent via blueyonder. Please address personal email to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message ----- From: "Jacob Kruger" <jacob@...> To: <nvda@nvda.groups.io> Sent: Thursday, August 11, 2016 1:44 PM Subject: Re: [nvda] Some issues coming between Google Chrome and NVDA > Not sure if this message is going to make it through to list, since seem > to have mail server issues, but, also, just make sure you try using > different review modes - document review mode should be default when > browsing web contents, but, also try object review and screen review > mode - or at least, just make sure you have tried the navigation keys > while in document review mode, and while you are focused on some element > which is specifically in the document contents - my one, ongoing issue > with chrome is just getting NVDA to focus on webpage contents, at times, > but, it works fine after figure out a work-around for that each time. > > > Stay well > > > Jacob Kruger > Blind Biker > Skype: BlindZA > "Resistance is futile, but, acceptance is versatile..." > > On 2016-08-11 2:13 PM, Gene wrote: >> I'd have to update my Chrome and find out. I almost never use >> Chrome. Since I have seen not one complaint other than yours, and >> since many list members use Chrome, at this time, I suspect that you >> are having problems that others, at least in general, aren't having. >> I may experiment with Chrome later today, depending on what others say. >> Gene >> ----- Original Message ----- >> *From:* Simone Dal Maso <mailto:simone.dalmaso@...> >> *Sent:* Thursday, August 11, 2016 4:11 AM >> *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> >> *Subject:* Re: [nvda] Some issues coming between Google Chrome and NVDA >> >> Il 11/08/2016 10:43, Gene ha scritto: >> > Failure of Chrome to remain accessible with two Google apps does not >> > render it unsupported by NVDA. >> >> Gene, if you read my ticket, you will discover that Chrome is not able >> to read headings, some links, and there are xml parsing error and really >> ttones of errors. >> What I'd like to know is if I am the only one that can't use Chrome. >> If you open www.yahoo.it <http://www.yahoo.it> with chrome, can you >> surf it? >> >> >> >> >> >> > >
|
|
Re: Twitter any help or addons?
Roger Stewart
Only problem is the Qube hasn't been supported for a long time now. I've removed it here but keep using TW Blue.
toggle quoted messageShow quoted text
Roger
On 8/11/2016 12:37 PM, Olcay AŞCI wrote:
Hi
|
|
Re: Twitter any help or addons?
Olcay AŞCI
Hi
toggle quoted messageShow quoted text
the qube Twitter client coded in Python. I think him a Twitter client with RSS reader plugin can be written to a logic nvda like.
-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Lino Morales Sent: Thursday, August 11, 2016 8:14 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Twitter any help or addons? Nope but you can use an number of 3rd party clients I.E. TW Blue, Chicken Nugget and others I've missed. On 8/11/2016 3:57 AM, John from Woodside Apps wrote: Hello
|
|
Re: Twitter any help or addons?
Lino Morales <linomorales001@...>
Nope but you can use an number of 3rd party clients I.E. TW Blue, Chicken Nugget and others I've missed.
toggle quoted messageShow quoted text
On 8/11/2016 3:57 AM, John from Woodside Apps wrote:
Hello
|
|
Re: Some issues coming between Google Chrome and NVDA
Dejan Ristic
Set Facebook aside. Test the language lists in Google Translate
by Chrome, and compare their pronounciation with the one tested by
Mozilla Firefox. I hope that you will face the difference as to
the pronounciation of the language lists. Let me know what you
have faced. On 8/11/2016 6:58 PM, Dejan Ristic
wrote:
|
|
Re: Some issues coming between Google Chrome and NVDA
Dejan Ristic
I do it, friend, but how to handle both the source and target
list of the languages in Google Translate by using Chrome when
they are not pronounced? I do not care for Facebook when I
translate, but I am crestfallen when I experience what I did not
experience before as to Chrome and Google Translate. QTranslate is
good, but not so good as Google Translate when it comes down to
examples and terms explained On 8/11/2016 2:44 PM, Jacob Kruger
wrote:
|
|
Re: Some issues coming between Google Chrome and NVDA
Dejan Ristic
I also use Chrome. The only thing is that I have been
experiencing the mentioned problems only in these two instances.
Note that I mentioned that the Opera browser behaved in the same
way. I also tested Avast! Safe Zone Browser, and it also did
behave in the same way. Mozilla firefox and Internet explorer are
good to use in these cases, but they slow down. That's why I like
Chrome and Opera so much, and that's why I use them as much as the
accessibility features allow me to do so. On 8/11/2016 2:13 PM, Gene wrote:
|
|
Re: Some issues coming between Google Chrome and NVDA
Brian's Mail list account
One of the main reasons I'm not using anything else but firefox at the moment is all this now it workds now it won't stuff. They obviously do not test their new versions very well from what i can tell. At least firefox do fix things like they fixed the navigation sounds not working in 47, and its fine in the later versions, aand lists work properly in web pages as well.
toggle quoted messageShow quoted text
Btrian bglists@... Sent via blueyonder. Please address personal email to:- briang1@..., putting 'Brian Gaff' in the display name field.
----- Original Message -----
From: "Jacob Kruger" <jacob@...> To: <nvda@nvda.groups.io> Sent: Thursday, August 11, 2016 1:44 PM Subject: Re: [nvda] Some issues coming between Google Chrome and NVDA Not sure if this message is going to make it through to list, since seem
|
|
Re: Some issues coming between Google Chrome and NVDA
Jacob Kruger
Not sure if this message is going to make it through to list, since seem to have mail server issues, but, also, just make sure you try using different review modes - document review mode should be default when browsing web contents, but, also try object review and screen review mode - or at least, just make sure you have tried the navigation keys while in document review mode, and while you are focused on some element which is specifically in the document contents - my one, ongoing issue with chrome is just getting NVDA to focus on webpage contents, at times, but, it works fine after figure out a work-around for that each time.
Stay well
Jacob Kruger Blind Biker Skype: BlindZA "Resistance is futile, but, acceptance is versatile..." On 2016-08-11 2:13 PM, Gene wrote:
|
|
Re: Some issues coming between Google Chrome and NVDA
mk360
I've many problems too, but I use next for NVDA. the thing is Chrome sometimes works fine, sometimes it doesn't. So, I think one thing is supported, other thing is partially supported or supported when Chromium team doesn't change things. Note that the evaluations of how accessible is the product depends of the user... I use chrome because my chromecast need it and well, because I know many programs that are less usable than chrome, but I can't say it works correctly, only that it is usable. Is something similar to the accessibility of windows 10
aniversary... the insiders are happy with the accessibility
provided, I think it works fine, but many end users think that
some things don't work.
Regards, mk. El 11-08-2016 a las 8:13, Gene
escribió:
|
|
Re: Some issues coming between Google Chrome and NVDA
Gene
I'd have to update my Chrome and find out. I
almost never use Chrome. Since I have seen not one complaint other than
yours, and since many list members use Chrome, at this time, I suspect that you
are having problems that others, at least in general, aren't having. I may
experiment with Chrome later today, depending on what others say.
Gene
----- Original Message -----
From: Simone Dal Maso
Sent: Thursday, August 11, 2016 4:11 AM
Subject: Re: [nvda] Some issues coming between Google Chrome and
NVDA > Failure of Chrome to remain accessible with two Google apps does not > render it unsupported by NVDA. Gene, if you read my ticket, you will discover that Chrome is not able to read headings, some links, and there are xml parsing error and really ttones of errors. What I'd like to know is if I am the only one that can't use Chrome. If you open www.yahoo.it with chrome, can you surf it?
|
|
Re: Some issues coming between Google Chrome and NVDA
Dejan Ristic
Thank you for doing so.
toggle quoted messageShow quoted text
But, let's consider that these issues did not exist before. Do you agree with the fact that some major changes in Chrome can be done, so that the relation between NVDA and Chrome may be improved as far as the instance of accessibility is concerned?
On 8/11/2016 10:25 AM, Simone Dal Maso wrote:
Google Chrome on my opinion should be removed from supported NVDA browser.
|
|
Re: Some issues coming between Google Chrome and NVDA
Simone Dal Maso
Il 11/08/2016 11:27, Jacob Kruger ha scritto:
Quick test, and it worked fine here with chrome 52 and latest NVDAOh... thank you! So this is only a problem of mine. Thank you very much, I will try to reinstall chrome.
|
|
Re: Some issues coming between Google Chrome and NVDA
Jacob Kruger
Quick test, and it worked fine here with chrome 52 and latest NVDA master snapshot?
toggle quoted messageShow quoted text
Jacob Kruger Blind Biker Skype: BlindZA "Resistance is futile, but, acceptance is versatile..."
On 2016-08-11 11:11 AM, Simone Dal Maso wrote:
Il 11/08/2016 10:43, Gene ha scritto:Failure of Chrome to remain accessible with two Google apps does notGene, if you read my ticket, you will discover that Chrome is not able to read headings, some links, and there are xml parsing error and really ttones of errors.
|
|
Re: Some issues coming between Google Chrome and NVDA
Simone Dal Maso
Il 11/08/2016 10:43, Gene ha scritto:
Failure of Chrome to remain accessible with two Google apps does notGene, if you read my ticket, you will discover that Chrome is not able to read headings, some links, and there are xml parsing error and really ttones of errors. What I'd like to know is if I am the only one that can't use Chrome. If you open www.yahoo.it with chrome, can you surf it?
|
|
Re: Some issues coming between Google Chrome and NVDA
Gene
Failure of Chrome to remain accessible with two
Google apps does not render it unsupported by NVDA. This may be more of
Googles routine breaking of things. They seem to break something about
every six months in production versions. Here we are, somewhere between
four and six months since the last thing that was broken.
This routine breaking of things and not correcting
the problem or problems until after they reach production versions is hardly a
demonstration of a proper commitment. That's one reason I don't use Chrome
as my main browser. I've seen too many completely unnecessary problems in
production versions over time. That the problems are usually corrected
doesn't mitigate the fact that they reach production versions.
Gene
----- Original Message -----
From: Simone Dal Maso
Sent: Thursday, August 11, 2016 3:25 AM
Subject: Re: [nvda] Some issues coming between Google Chrome and
NVDA It is absolutely not usable, at least on my three pc. I opened a ticket about this: https://github.com/nvaccess/nvda/issues/6249 Il 10/08/2016 21:02, Dejan Ristic ha scritto: > Both the previous and the current version of Chrome have decreased some > accessibility features as far as Facebook and Google Translate are > concerned. > > > When I type in the search field what I wish to find on Facebook, I am no > longer able to hear the list of the items found when I use the up and > down arrows to go through them after I have typed my search term. NVDA > only pronounces my search term when I up and down, but does not show the > list of the items found as it did before. Compare Mozilla Firefox with > Chrome, and all will be clear. The same goes for the Opera browser. > > > As for Google Translate, it is impossible for me to choose between the > list of the source and target languages. The only NVDA-output > pronounciation is: "list submenu expanded" and "list submenu collapsed". > The same goes for the Opera browser. > > When I handle it by Mozilla Firefox, I succeed in choosing between the > desired source and target languages. It means that both lists are spoken > correctly. > > > I use the latest version of NVDA, and the latest version of both Chrome > and Opera. > > > My operating system is: Windows 7 Ultimate, 64bit. > > > Allow me to ask you whether you shake hands with the same issues? > > > Thankful in advance, > > Dejan > > > > >
|
|
Re: Some issues coming between Google Chrome and NVDA
Simone Dal Maso
Google Chrome on my opinion should be removed from supported NVDA browser.
toggle quoted messageShow quoted text
It is absolutely not usable, at least on my three pc. I opened a ticket about this: https://github.com/nvaccess/nvda/issues/6249
Il 10/08/2016 21:02, Dejan Ristic ha scritto:
Both the previous and the current version of Chrome have decreased some
|
|