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

 

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kwork
Sent: Tuesday, August 14, 2018 5:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Change on Amazon makes buying options less, possibly
inaccessible with screenreaders while on product page

So did I.
----- Original Message -----
From: "Don H" <lmddh50@adams.net>
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

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


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

----- Original Message -----
From: "Don H" <lmddh50@adams.net>
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

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

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

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

----- Original Message -----
From: "Ângelo Abrantes" <ampa4374@gmail.com>
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

----- Original Message -----
From: "Jacob Kruger" <jacob@blindza.co.za>
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@blindza.co.za>
*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..."

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

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

Sent: Tuesday, August 14, 2018 5:45 AM

To: 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..."