Date   

Re: Change on Amazon makes buying options less, possibly inaccessible with screenreaders while on product page

Kwork
 

So did I.

----- Original Message -----
From: "Don H" <lmddh50@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, August 14, 2018 2:21 PM
Subject: Re: [nvda] Change on Amazon makes buying options less, possibly
inaccessible with screenreaders while on product page


Just bought items yesterday using NVDA with no issues

On 8/14/2018 4:20 PM, Dennis L wrote:
Everythings fine with latest Jaws 2018

*From:*nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] *On Behalf Of
*Kwork
*Sent:* Tuesday, August 14, 2018 4:57 PM
*To:* nvda@nvda.groups.io
*Subject:* [nvda] Change on Amazon makes buying options less, possibly
inaccessible with screenreaders while on product page

Up through yesterday, I had no trouble buying Kindle books through
Amazon. Things were labeled, and easily findable. Today the area of the
page where the buying options are seems to have changed.

There is now a new heading called "Buying Options." It's the first
heading on the page. The interesting thing about this heading is that
there is no number associated with it. Instead of saying "heading level
1," as the heading below it says, all is says is "heading."

I think the buy and read now links, along with the price that used to be
readily visible are now hidden inside the new "heading" area. Arrowing
down once leads to the "add to list" checkbox.

This has been confirmed both in Firefox 64 and Chrome 64 using Windows 7
64-bit and NVDA 2018.2.1.

If anyone else can confirm, and can have any idea on how to deal with
this, that would be appreciated.

Here's an example. For the US, this book is free at least today, hence
why I chose it, so trying to buy it won't cost anybody any money. And,
yes, the page is the same whether a book is free or not:

https://www.amazon.com/dp/B07FDKPS2C/?tag=bookfreeby-20


Re: Change on Amazon makes buying options less, possibly inaccessible with screenreaders while on product page

bob jutzi <jutzi1@...>
 

No problems using the latest NVDA Alpha along with Firefox 60.
I chose Kindle Store in the dropdown box, entered a title in the Searchbox and clicked Search, and clicked on the link that matched. As expected, the page of the book contained both a Buy Now button and Add to Cart Button. I can also use One Click since I have it enabled.

On 8/14/2018 5:21 PM, Don H wrote:
Just bought items yesterday using NVDA with no issues
On 8/14/2018 4:20 PM, Dennis L wrote:
Everythings fine with latest Jaws 2018

*From:*nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] *On Behalf Of *Kwork
*Sent:* Tuesday, August 14, 2018 4:57 PM
*To:* nvda@nvda.groups.io
*Subject:* [nvda] Change on Amazon makes buying options less, possibly inaccessible with screenreaders while on product page

Up through yesterday, I had no trouble buying Kindle books through Amazon. Things were labeled, and easily findable. Today the area of the page where the buying options are seems to have changed.

There is now a new heading called "Buying Options." It's the first heading on the page. The interesting thing about this heading is that there is no number associated with it. Instead of saying "heading level 1," as the heading below it says, all is says is "heading."

I think the buy and read now links, along with the price that used to be readily visible are now hidden inside the new "heading" area. Arrowing down once leads to the "add to list" checkbox.

This has been confirmed both in Firefox 64 and Chrome 64 using Windows 7 64-bit and NVDA 2018.2.1.

If anyone else can confirm, and can have any idea on how to deal with this, that would be appreciated.

Here's an example. For the US, this book is free at least today, hence why I chose it, so trying to buy it won't cost anybody any money. And, yes, the page is the same whether a book is free or not:

https://www.amazon.com/dp/B07FDKPS2C/?tag=bookfreeby-20


Re: Change on Amazon makes buying options less, possibly inaccessible with screenreaders while on product page

Don H
 

Just bought items yesterday using NVDA with no issues

On 8/14/2018 4:20 PM, Dennis L wrote:
Everythings fine with latest Jaws 2018
*From:*nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] *On Behalf Of *Kwork
*Sent:* Tuesday, August 14, 2018 4:57 PM
*To:* nvda@nvda.groups.io
*Subject:* [nvda] Change on Amazon makes buying options less, possibly inaccessible with screenreaders while on product page
Up through yesterday, I had no trouble buying Kindle books through Amazon. Things were labeled, and easily findable. Today the area of the page where the buying options are seems to have changed.
There is now a new heading called "Buying Options." It's the first heading on the page. The interesting thing about this heading is that there is no number associated with it. Instead of saying "heading level 1," as the heading below it says, all is says is "heading."
I think the buy and read now links, along with the price that used to be readily visible are now hidden inside the new "heading" area. Arrowing down once leads to the "add to list" checkbox.
This has been confirmed both in Firefox 64 and Chrome 64 using Windows 7 64-bit and NVDA 2018.2.1.
If anyone else can confirm, and can have any idea on how to deal with this, that would be appreciated.
Here's an example. For the US, this book is free at least today, hence why I chose it, so trying to buy it won't cost anybody any money. And, yes, the page is the same whether a book is free or not:
https://www.amazon.com/dp/B07FDKPS2C/?tag=bookfreeby-20


Re: Change on Amazon makes buying options less, possibly inaccessible with screenreaders while on product page

Dennis L <dennisl1982@...>
 

Everythings fine with latest Jaws 2018

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Kwork
Sent: Tuesday, August 14, 2018 4:57 PM
To: nvda@nvda.groups.io
Subject: [nvda] Change on Amazon makes buying options less, possibly inaccessible with screenreaders while on product page

 

Up through yesterday, I had no trouble buying Kindle books through Amazon. Things were labeled, and easily findable. Today the area of the page where the buying options are seems to have changed.

There is now a new heading called "Buying Options." It's the first heading on the page. The interesting thing about this heading is that there is no number associated with it. Instead of saying "heading level 1," as the heading below it says, all is says is "heading."

I think the buy and read now links, along with the price that used to be readily visible are now hidden inside the new "heading" area. Arrowing down once leads to the "add to list" checkbox.

This has been confirmed both in Firefox 64 and Chrome 64 using Windows 7 64-bit and NVDA 2018.2.1.

If anyone else can confirm, and can have any idea on how to deal with this, that would be appreciated.

Here's an example. For the US, this book is free at least today, hence why I chose it, so trying to buy it won't cost anybody any money. And, yes, the page is the same whether a book is free or not:

 


Change on Amazon makes buying options less, possibly inaccessible with screenreaders while on product page

Kwork
 

Up through yesterday, I had no trouble buying Kindle books through Amazon. Things were labeled, and easily findable. Today the area of the page where the buying options are seems to have changed.
There is now a new heading called "Buying Options." It's the first heading on the page. The interesting thing about this heading is that there is no number associated with it. Instead of saying "heading level 1," as the heading below it says, all is says is "heading."
I think the buy and read now links, along with the price that used to be readily visible are now hidden inside the new "heading" area. Arrowing down once leads to the "add to list" checkbox.
This has been confirmed both in Firefox 64 and Chrome 64 using Windows 7 64-bit and NVDA 2018.2.1.
If anyone else can confirm, and can have any idea on how to deal with this, that would be appreciated.
Here's an example. For the US, this book is free at least today, hence why I chose it, so trying to buy it won't cost anybody any money. And, yes, the page is the same whether a book is free or not:
 


Re: NVDA + F5 hotkey doing an actual document reload

Gene
 

To test whether NVDA f5 is refreshing the page or just the buffer, you should disconnect from the Internet while a page is in the browser.  If numpad f5 produces a page not found message, then it is refreshing the page itself, which refreshes the buffer, but it is not just refreshing the buffer.  If, on the other hand, NVDA f5 refreshes and starts to read the page when not connected to the Internet, then we know that the command is refreshing the buffer and not the actual page. 
 
Gene

----- Original message -----
From: zahra
Sent: Tuesday, August 14, 2018 11:32 AM
Subject: Re: [nvda] NVDA + F5 hotkey doing an actual document reload

i tried nvda f5 and immediately nvda said refreshed and read the
content very soon at the moment!
i tested with my favorite version of nvda (which is 2017.1) and i dont
see hangs or crashes even i open many many tabs in firefox without
closing for many hours!

On 8/14/18, Brian's Mail list account via Groups.Io
<bglists@...> wrote:
> I suggest you ask this question as an issue on github. I to was under the
> same impression as you.
>  Brian
>
> bglists@...
> Sent via blueyonder.
> Please address personal E-mail to:-
> briang1@..., putting 'Brian Gaff'
> in the display name field.
> ----- Original Message -----
> From: "Jacob Kruger" <jacob@...>
> To: <nvda@nvda.groups.io>
> Sent: Tuesday, August 14, 2018 1:22 PM
> Subject: Re: [nvda] NVDA + F5 hotkey doing an actual document reload
>
>
>> Problem with standard F5 keystroke is that almost every single browser
>> will then just reload the page from scratch, losing all DHTML content
>> changes.
>>
>>
>> I do also know that NVDA key + number row 5 is meant to turn on
>> reporting of dynamic content changes, but, it won't always work, partly
>> since, at times, the webpages document-object-model will be rather
>> extensive.
>>
>>
>> Either way, I had just thought/assumed that it was offering/implementing
>> a form of virtual page buffer refresh, but anyway - will play around
>> with other keystrokes, alt+tabbing away from window, and back to it,
>> etc. etc.
>>
>>
>> Stay well
>>
>>
>> Jacob Kruger
>> Blind Biker
>> Skype: BlindZA
>> "Resistance is futile...but, acceptance is versatile..."
>>
>> On 8/14/2018 1:59 PM, Gene wrote:
>>> I believe it does reload the document, because, as I recall, I think
>>> it takes too long than to just refresh the buffer. If so, it is doing
>>> the same thing as just f5. Of course, if you reload the document, you
>>> are reloading the buffer. But try turning browse mode off and then on
>>> with NVDA key space. This may just refresh the buffer.
>>> If NVDA key f5 is explained in the manual, I don't know where. It
>>> isn't discussed in the browse mode section. It is probably mentioned
>>> in the quick reference guide, but it may well not clarify what it does.
>>> Gene
>>> ----- Original Message -----
>>> *From:* Jacob Kruger <mailto:jacob@...>
>>> *Sent:* Tuesday, August 14, 2018 5:45 AM
>>> *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
>>> *Subject:* [nvda] NVDA + F5 hotkey doing an actual document reload
>>>
>>> This is something I think has been going on across a few versions of
>>> NVDA now, and, just wanted to confirm that it's not me that's confused.
>>>
>>>
>>> I am currently making use of Version: alpha-15854,a8bda064, FWIW.
>>>
>>>
>>> Anyway, I was under the impression that, for example, in a web browser,
>>> the hotkey combination of NVDA + F5 should repopulate the virtual buffer
>>> rendition of the page contents - I do need this at times since I work
>>> with dynamic web contents - but, it seems to, literally, just reload the
>>> page as if you'd clicked on something like the browsers own refresh
>>> button, or as if you'd in fact told NVDA that the next keypress should
>>> be passed directly through to the operating system?
>>>
>>>
>>> Or am I incorrect in having thought it only repopulated a form of
>>> virtual buffer for the webpage?
>>>
>>>
>>> TIA
>>>
>>>
>>> Jacob Kruger
>>> 082 413 4791
>>> Skype: BlindZA
>>> "Resistance is futile...but, acceptance is versatile..."
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
>
>
>


--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali



ConfigObj 5.1.0: different import paths causes some add-ons to fail to initialize

 

Hi all,

 

The second of a series of advisories regarding what’s happening with NVDA 2018.4:

 

As of today’s alpha build, ConfigObj has been upgraded to 5.1.0. The biggest change, apart from ConfigObj being source-compatible with Python 3, is the new import path for validate module. Unfortunately, the module that is supposed to be part of NVDA wasn’t added, which causes Remote Support, Vocalizer and other add-ons that rely on validate routines to fail to initialize. NVDA developers are aware of this and plans to fix this as soon as possible.

 

Cheers,

Joseph


Re: NVDA + F5 hotkey doing an actual document reload

 

i tried nvda f5 and immediately nvda said refreshed and read the
content very soon at the moment!
i tested with my favorite version of nvda (which is 2017.1) and i dont
see hangs or crashes even i open many many tabs in firefox without
closing for many hours!

On 8/14/18, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:
I suggest you ask this question as an issue on github. I to was under the
same impression as you.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Jacob Kruger" <jacob@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, August 14, 2018 1:22 PM
Subject: Re: [nvda] NVDA + F5 hotkey doing an actual document reload


Problem with standard F5 keystroke is that almost every single browser
will then just reload the page from scratch, losing all DHTML content
changes.


I do also know that NVDA key + number row 5 is meant to turn on
reporting of dynamic content changes, but, it won't always work, partly
since, at times, the webpages document-object-model will be rather
extensive.


Either way, I had just thought/assumed that it was offering/implementing
a form of virtual page buffer refresh, but anyway - will play around
with other keystrokes, alt+tabbing away from window, and back to it,
etc. etc.


Stay well


Jacob Kruger
Blind Biker
Skype: BlindZA
"Resistance is futile...but, acceptance is versatile..."

On 8/14/2018 1:59 PM, Gene wrote:
I believe it does reload the document, because, as I recall, I think
it takes too long than to just refresh the buffer. If so, it is doing
the same thing as just f5. Of course, if you reload the document, you
are reloading the buffer. But try turning browse mode off and then on
with NVDA key space. This may just refresh the buffer.
If NVDA key f5 is explained in the manual, I don't know where. It
isn't discussed in the browse mode section. It is probably mentioned
in the quick reference guide, but it may well not clarify what it does.
Gene
----- Original Message -----
*From:* Jacob Kruger <mailto:jacob@...>
*Sent:* Tuesday, August 14, 2018 5:45 AM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* [nvda] NVDA + F5 hotkey doing an actual document reload

This is something I think has been going on across a few versions of
NVDA now, and, just wanted to confirm that it's not me that's confused.


I am currently making use of Version: alpha-15854,a8bda064, FWIW.


Anyway, I was under the impression that, for example, in a web browser,
the hotkey combination of NVDA + F5 should repopulate the virtual buffer
rendition of the page contents - I do need this at times since I work
with dynamic web contents - but, it seems to, literally, just reload the
page as if you'd clicked on something like the browsers own refresh
button, or as if you'd in fact told NVDA that the next keypress should
be passed directly through to the operating system?


Or am I incorrect in having thought it only repopulated a form of
virtual buffer for the webpage?


TIA


Jacob Kruger
082 413 4791
Skype: BlindZA
"Resistance is futile...but, acceptance is versatile..."










--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali


Re: NVDA remote not working with last alpha: alpha-15854,a8bda064

Brian's Mail list account <bglists@...>
 

I'm sure there is a temporary fixed version somewhere, that Joseph made while waiting for the bigger changes that a new version of Python will require from this add on. the original redevelopers, or at least one of them have showed interest, but I doubt they will do much while its only wx4 which is the issue if a complete rewrite might be needed a couple of months on.

Just what i gathered from the discussions I've witnessed on mail lists. Sorry if I have the wrong stick end.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Ângelo Abrantes" <ampa4374@...>
To: <nvda-addons@nvda-addons.groups.io>; <nvda@nvda.groups.io>; <devlearning@nvda.groups.io>
Sent: Tuesday, August 14, 2018 4:38 PM
Subject: [nvda] NVDA remote not working with last alpha: alpha-15854,a8bda064


Here's my ".log":


ERROR - globalPluginHandler.listPlugins (16:33:54.717):
Error importing global plugin remoteClient
Traceback (most recent call last):
File "globalPluginHandler.pyc", line 22, in listPlugins
File "C:\Users\Angelo\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\__init__.py", line 17, in <module>
File "C:\Users\Angelo\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\configuration.py", line 5, in <module>
ImportError: No module named validate
DEBUG - addonHandler.Addon.__init__ (16:33:54.746):
Using manifest translation from C:\Users\Angelo\AppData\Roaming\nvda\addons\poeditMadeEasy\locale\en\manifest.ini
DEBUG - addonHandler.Addon.__init__ (16:33:54.766):
Using manifest translation from C:\Users\Angelo\AppData\Roaming\nvda\addons\instantTranslate\locale\pt_PT\manifest.ini
ERROR - globalPluginHandler.listPlugins (16:33:54.786):
Error importing global plugin clock
Traceback (most recent call last):
File "globalPluginHandler.pyc", line 22, in listPlugins
File "C:\Users\Angelo\AppData\Roaming\nvda\addons\clock\globalPlugins\clock\__init__.py", line 19, in <module>
ImportError: No module named validate
DEBUG - core.main (16:33:54.806):
Initializing core pump
DEBUG - core.main (16:33:54.806):
Initializing watchdog

Thanks for your attention.

Ângelo Abrantes


---
Este e-mail foi verificado em termos de vírus pelo software antivírus Avast.
https://www.avast.com/antivirus



Re: NVDA + F5 hotkey doing an actual document reload

Brian's Mail list account <bglists@...>
 

I suggest you ask this question as an issue on github. I to was under the same impression as you.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Jacob Kruger" <jacob@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, August 14, 2018 1:22 PM
Subject: Re: [nvda] NVDA + F5 hotkey doing an actual document reload


Problem with standard F5 keystroke is that almost every single browser
will then just reload the page from scratch, losing all DHTML content
changes.


I do also know that NVDA key + number row 5 is meant to turn on
reporting of dynamic content changes, but, it won't always work, partly
since, at times, the webpages document-object-model will be rather
extensive.


Either way, I had just thought/assumed that it was offering/implementing
a form of virtual page buffer refresh, but anyway - will play around
with other keystrokes, alt+tabbing away from window, and back to it,
etc. etc.


Stay well


Jacob Kruger
Blind Biker
Skype: BlindZA
"Resistance is futile...but, acceptance is versatile..."

On 8/14/2018 1:59 PM, Gene wrote:
I believe it does reload the document, because, as I recall, I think
it takes too long than to just refresh the buffer. If so, it is doing
the same thing as just f5. Of course, if you reload the document, you
are reloading the buffer. But try turning browse mode off and then on
with NVDA key space. This may just refresh the buffer.
If NVDA key f5 is explained in the manual, I don't know where. It
isn't discussed in the browse mode section. It is probably mentioned
in the quick reference guide, but it may well not clarify what it does.
Gene
----- Original Message -----
*From:* Jacob Kruger <mailto:jacob@...>
*Sent:* Tuesday, August 14, 2018 5:45 AM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* [nvda] NVDA + F5 hotkey doing an actual document reload

This is something I think has been going on across a few versions of
NVDA now, and, just wanted to confirm that it's not me that's confused.


I am currently making use of Version: alpha-15854,a8bda064, FWIW.


Anyway, I was under the impression that, for example, in a web browser,
the hotkey combination of NVDA + F5 should repopulate the virtual buffer
rendition of the page contents - I do need this at times since I work
with dynamic web contents - but, it seems to, literally, just reload the
page as if you'd clicked on something like the browsers own refresh
button, or as if you'd in fact told NVDA that the next keypress should
be passed directly through to the operating system?


Or am I incorrect in having thought it only repopulated a form of
virtual buffer for the webpage?


TIA


Jacob Kruger
082 413 4791
Skype: BlindZA
"Resistance is futile...but, acceptance is versatile..."






NVDA remote not working with last alpha: alpha-15854,a8bda064

Ângelo Abrantes
 

Here's my ".log":


ERROR - globalPluginHandler.listPlugins (16:33:54.717):
Error importing global plugin remoteClient
Traceback (most recent call last):
  File "globalPluginHandler.pyc", line 22, in listPlugins
  File "C:\Users\Angelo\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\__init__.py", line 17, in <module>
  File "C:\Users\Angelo\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\configuration.py", line 5, in <module>
ImportError: No module named validate
DEBUG - addonHandler.Addon.__init__ (16:33:54.746):
Using manifest translation from C:\Users\Angelo\AppData\Roaming\nvda\addons\poeditMadeEasy\locale\en\manifest.ini
DEBUG - addonHandler.Addon.__init__ (16:33:54.766):
Using manifest translation from C:\Users\Angelo\AppData\Roaming\nvda\addons\instantTranslate\locale\pt_PT\manifest.ini
ERROR - globalPluginHandler.listPlugins (16:33:54.786):
Error importing global plugin clock
Traceback (most recent call last):
  File "globalPluginHandler.pyc", line 22, in listPlugins
  File "C:\Users\Angelo\AppData\Roaming\nvda\addons\clock\globalPlugins\clock\__init__.py", line 19, in <module>
ImportError: No module named validate
DEBUG - core.main (16:33:54.806):
Initializing core pump
DEBUG - core.main (16:33:54.806):
Initializing watchdog

Thanks for your attention.

Ângelo Abrantes


---
Este e-mail foi verificado em termos de vírus pelo software antivírus Avast.
https://www.avast.com/antivirus


Checkable list boxes comes to NVDA, it will make its debut as early as end of this year

 

Hi everyone,

 

This is first of a series of two advisories regarding changes coming in NVDA 2018.4 that’ll affect everyone (the second advisory, which is more important than this one, is next):

 

Checkable list boxes comes to NVDA. A checkable list box is a list of checkboxes laid out vertically so you can select one or more items by checking checkboxes. The best known example of this control is Disk Cleanup where you can select items to delete once cleanup scan results are returned.

 

Prior to this, NVDA users and developers could not use this control due to accessibility issues. A combination of MSAA events and a property server implementation resolves this (developed by a third-party contributor,. Not me). At the moment this new control has scaling issues with high DPI (dots per inch) displays, but it doesn’t affect how it works. A corresponding scaling problem was filed on wxPython GitHub repo at:

https://github.com/wxWidgets/Phoenix/issues/963

 

As a result of introduction of checkable list boxes, the following changes has been made or under planning phase:

 

Changed:

  • In keyboard settings panel, you might be familiar with a series of checkboxes for selecting NVDA modifier keys. This is now a checkable list box.

 

Planned:

  • It may one day be possible to select which add-ons you’d like to copy to secure screens when copying NVDA user settings.

 

Thank you.

Cheers,

Joseph


Re- NVDA, Firefox, and PDF Documents

Abbie Taylor <abbietaylor945@...>
 

That's DocuScan Plus, not DocuScan Pus. Sorry about that.

Abbie Johnson Taylor, Author http://abbiescorner.wordpress.com
http://www.abbiejohnsontaylor.com
abbietaylor945@...
Order my new memoir at http://www.abbiejohnsontaylor.com/memoir.htm

--
Abbie Johnson Taylor, Author
http://www.abbiejohnsontaylor.com
http://abbiescorner.wordpress.com
abbietaylor945@...


Patreon accessibility input

 

Since Patreon has denied our requests to consider accessibility, for years, mind you, by the way, this page does a good job of explaining what Patreon is, Our lawyer wants to hear from disabled users who want to either donate to others but can't, or who had issues with the service in general, as a disabled person, not just the blind and the visually impaired. He  wants to hear from creators too. Share the below contact info widely! Thanks.


MATTHEW K. HANDLEY
HANDLEY & ANDERSON PLLC
718 7th Street, NW Washington, DC  20001
202-559-2411
mhandley@...
hajustice.com


Hi Robert,

Yes, input from others would be very helpful. My contact info should be directly below.

Thanks,

Matt

MATTHEW K. HANDLEY
HANDLEY & ANDERSON PLLC
718 7th Street, NW Washington, DC  20001
202-559-2411
mhandley@...
hajustice.com


Re: NVDA and AMD processors

Travis Siegel <tsiegel@...>
 

NVDA makes no distinction between intel or amd processors, it's written (mainly) in python, which is an interpreted language, and it doesn't care if it's an intel, AMD, arm processor, or something entirely different, as long as the interpreter works, python doesn't care, as a result, NVDA shouldn't care either.

On 8/13/2018 6:37 PM, JM Casey wrote:
I have an AMD also, but haven't had any issues.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: August 13, 2018 6:22 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA and AMD processors

Just purchased a HP Envy 13z laptop that has AMD Ryzen™ 5 processor and AMD Radeon™ Vega 8 Graphics.
I have installed the latest released version of NVDA. I am having a issue where NVDA stops talking and has to be restarted to get speech back.
Are there any known issues with NVDA on a AMD system? Any hints in how to figure out what is going on?
Thanks







Re: NVDA + F5 hotkey doing an actual document reload

Jacob Kruger
 

Problem with standard F5 keystroke is that almost every single browser will then just reload the page from scratch, losing all DHTML content changes.


I do also know that NVDA key + number row 5 is meant to turn on reporting of dynamic content changes, but, it won't always work, partly since, at times, the webpages document-object-model will be rather extensive.


Either way, I had just thought/assumed that it was offering/implementing a form of virtual page buffer refresh, but anyway - will play around with other keystrokes, alt+tabbing away from window, and back to it, etc. etc.


Stay well


Jacob Kruger
Blind Biker
Skype: BlindZA
"Resistance is futile...but, acceptance is versatile..."

On 8/14/2018 1:59 PM, Gene wrote:
I believe it does reload the document, because, as I recall,  I think it takes too long than to just refresh the buffer.  If so, it is doing the same thing as just f5.  Of course, if you reload the document, you are reloading the buffer.  But try turning browse mode off and then on with NVDA key space.  This may just refresh the buffer. 
 
If NVDA key f5 is explained in the manual, I don't know where.  It isn't discussed in the browse mode section.  It is probably mentioned in the quick reference guide, but it may well not clarify what it does.
 
Gene
----- Original Message -----
Sent: Tuesday, August 14, 2018 5:45 AM
Subject: [nvda] NVDA + F5 hotkey doing an actual document reload

This is something I think has been going on across a few versions of
NVDA now, and, just wanted to confirm that it's not me that's confused.


I am currently making use of Version: alpha-15854,a8bda064, FWIW.


Anyway, I was under the impression that, for example, in a web browser,
the hotkey combination of NVDA + F5 should repopulate the virtual buffer
rendition of the page contents - I do need this at times since I work
with dynamic web contents - but, it seems to, literally, just reload the
page as if you'd clicked on something like the browsers own refresh
button, or as if you'd in fact told NVDA that the next keypress should
be passed directly through to the operating system?


Or am I incorrect in having thought it only repopulated a form of
virtual buffer for the webpage?


TIA


Jacob Kruger
082 413 4791
Skype: BlindZA
"Resistance is futile...but, acceptance is versatile..."





Re: NVDA + F5 hotkey doing an actual document reload

Gene
 

I believe it does reload the document, because, as I recall,  I think it takes too long than to just refresh the buffer.  If so, it is doing the same thing as just f5.  Of course, if you reload the document, you are reloading the buffer.  But try turning browse mode off and then on with NVDA key space.  This may just refresh the buffer. 
 
If NVDA key f5 is explained in the manual, I don't know where.  It isn't discussed in the browse mode section.  It is probably mentioned in the quick reference guide, but it may well not clarify what it does.
 
Gene

----- Original Message -----
Sent: Tuesday, August 14, 2018 5:45 AM
Subject: [nvda] NVDA + F5 hotkey doing an actual document reload

This is something I think has been going on across a few versions of
NVDA now, and, just wanted to confirm that it's not me that's confused.


I am currently making use of Version: alpha-15854,a8bda064, FWIW.


Anyway, I was under the impression that, for example, in a web browser,
the hotkey combination of NVDA + F5 should repopulate the virtual buffer
rendition of the page contents - I do need this at times since I work
with dynamic web contents - but, it seems to, literally, just reload the
page as if you'd clicked on something like the browsers own refresh
button, or as if you'd in fact told NVDA that the next keypress should
be passed directly through to the operating system?


Or am I incorrect in having thought it only repopulated a form of
virtual buffer for the webpage?


TIA


Jacob Kruger
082 413 4791
Skype: BlindZA
"Resistance is futile...but, acceptance is versatile..."




Re: NVDA FireFox and PDF Incompatibility

Gene
 

Since Docuscan is an OCR program, it sounds to me as though you are performing OCR on every PDF document you open.  This takes extra time; it may take a good deal of extra time.  There are times, I don't work with PDF documents enough to know how often, that this will correct or reduce decolumnization problems.  That is, at times, just reading a PDF document that is in columns  misplaces text significantly.  OCR can at times, correct or mostly eliminate the problem.  but it also introduces errors and is not the original document, if you need the original document for some reason, such as for legal reasons. 
 
In short, instead of having an OCR program recognize every PDF document, you might to better to have an actual PDF reader display files, then decide if you want to perform OCR on them.  Your newspaper may or may not display properly without OCR.  If it doesn't need OCR, you will eliminate errors in recognition and you will have the document ready faster, perhaps much faster.
 
If it does need OCR, it may be most efficient to have it recognized by Docuscan rather than by downloading it first.  But there may be times when you would be better served temporarily changing the setting to work with another program.
 
Gene

----- Original Message -----
> Did you know that Firefox can be set to open pdf files in another program
> such as Adobe Acrobat Reader? I don't remember exactly how I set it up, but
> now, when I download my local newspaper, which is in pdf format, I just
> click on the link to the issue I want, and after okaying a dialog box that
> confirms that I want to open the document in DocuScan Pus, a program I use
> to read pdf files, voilla! Until the issue with Firefox and pdf files is
> resolved, this might be a good work-around.
>
> Abbie Johnson Taylor, Author http://abbiescorner.wordpress.com
> http://www.abbiejohnsontaylor.com
> abbietaylor945@...
> Order my new memoir at http://www.abbiejohnsontaylor.com/memoir.htm
>
> --
> Abbie Johnson Taylor, Author
> http://www.abbiejohnsontaylor.com
> http://abbiescorner.wordpress.com
> abbietaylor945@...
>
>
>


--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali



NVDA + F5 hotkey doing an actual document reload

Jacob Kruger
 

This is something I think has been going on across a few versions of NVDA now, and, just wanted to confirm that it's not me that's confused.


I am currently making use of Version: alpha-15854,a8bda064, FWIW.


Anyway, I was under the impression that, for example, in a web browser, the hotkey combination of NVDA + F5 should repopulate the virtual buffer rendition of the page contents - I do need this at times since I work with dynamic web contents - but, it seems to, literally, just reload the page as if you'd clicked on something like the browsers own refresh button, or as if you'd in fact told NVDA that the next keypress should be passed directly through to the operating system?


Or am I incorrect in having thought it only repopulated a form of virtual buffer for the webpage?


TIA


Jacob Kruger
082 413 4791
Skype: BlindZA
"Resistance is futile...but, acceptance is versatile..."


Re: NVDA FireFox and PDF Incompatibility

Brian's Mail list account <bglists@...>
 

Yes indeed, its a mess. I always use a reader whis is not part of any browser.

Of course this can have issues for those still on xp as the adobe product which is current cannot run on xp.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "zahra" <nasrinkhaksar3@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, August 14, 2018 7:51 AM
Subject: Re: [nvda] NVDA FireFox and PDF Incompatibility


hi.
this issue remain and is not be resolved.
because firefox does not support npapi plugings in the version 52 and later.
you can open your pdf files with firefox directly, but cant use npapi
pluging acrobot reader.

On 8/14/18, Abbie Taylor <abbietaylor945@...> wrote:
Did you know that Firefox can be set to open pdf files in another program
such as Adobe Acrobat Reader? I don't remember exactly how I set it up, but
now, when I download my local newspaper, which is in pdf format, I just
click on the link to the issue I want, and after okaying a dialog box that
confirms that I want to open the document in DocuScan Pus, a program I use
to read pdf files, voilla! Until the issue with Firefox and pdf files is
resolved, this might be a good work-around.

Abbie Johnson Taylor, Author http://abbiescorner.wordpress.com
http://www.abbiejohnsontaylor.com
abbietaylor945@...
Order my new memoir at http://www.abbiejohnsontaylor.com/memoir.htm

--
Abbie Johnson Taylor, Author
http://www.abbiejohnsontaylor.com
http://abbiescorner.wordpress.com
abbietaylor945@...



--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali