Claire,

         Do you mean when the Version 1803 feature update was applied, literally, or when one of the cumulative updates has been applied subsequently?   Since the latest cumulative update was released as of today, and if that was just applied to your computer, and if you have System Protection turned on you could try using a restore point prior to the latest update to roll back.

          My gut tells me that this is likely a sound card driver related issue and that the latest update has tweaked the device driver in a way that has caused a glitch.
--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

    A little kindness from person to person is better than a vast love for all humankind.

           ~ Richard Dehmel

 

 

Claire,

         Do you mean when the Version 1803 feature update was applied, literally, or when one of the cumulative updates has been applied subsequently?   Since the latest cumulative update was released as of today, and if that was just applied to your computer, and if you have System Protection turned on you could try using a restore point prior to the latest update to roll back.

          My gut tells me that this is likely a sound card driver related issue and that the latest update has tweaked the device driver in a way that has caused a glitch.
--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

    A little kindness from person to person is better than a vast love for all humankind.

           ~ Richard Dehmel

 

 

Just curious, but will NVDA recognize row and column titles if they are defined in the Excel spreadsheet itself, rather than after the fact by telling the screen reader which row is the column titles and which column is the row titles?
I know that JAWS will pick up on row and column titles defined within the spreadsheet without needing to define it to the screen reader.  Of course that means either the creator of the spreadsheet, or you the screen reader user, need to have defined these in Excel itself.
--
Brian *-*Windows 10 Home, 64-Bit, Version 1803, Build 17134
/A little kindness from person to person is better than a vast love for all humankind./
           ~ Richard Dehmel

Do you mean since your  machine updated to  1803?

Hi all, I really hope that someone on this list can help as I am really struggling with this rather  odd issue. I have a word document which I am reading from and I need to select some text to copy and paste elsewhere, however, when using Nvda, all of a sudden I am unable to hear the word or line I have just selected, NVDA completely cuts off. Please can someone help, this has only began to happen since taking the latest Windows update. --

Warm regards, Claire Potter, Check out my brand new website: http://www.pottersplace.me.uk/

Hi all, I really hope that someone on this list can help as I am really struggling with this rather  odd issue. I have a word document which I am reading from and I need to select some text to copy and paste elsewhere, however, when using Nvda, all of a sudden I am unable to hear the word or line I have just selected, NVDA completely cuts off. Please can someone help, this has only began to happen since taking the latest Windows update. --

Warm regards, Claire Potter, Check out my brand new website: http://www.pottersplace.me.uk/

----- Original Message -----

From: Chris via Groups.Io

To: nvda@nvda.groups.io

Sent: Wednesday, August 15, 2018 2:41 AM

Subject: Re: [nvda] codefactory vocalizer

An easy check is to compare the date creation dates of  a older 1.0 and the one that is currently on their website, then tell us what you get

 

 

From: Isaac
Sent: 15 August 2018 08:30
To: nvda@nvda.groups.io
Subject: [nvda] codefactory vocalizer

 

  Hi, just asking has anyone found out why the codefactory addon went badck to 1.0 instead of 1.5 and why we can't get the hq voices?

 

Ok, that works. Thank you. A stupid workaround, but hopefully amazon will
change things back, not holding my breath, or the NVDA developers will
figure out how to work with this kind of change.
Travis
----- Original Message -----
From: "Danni" <luv2ride67@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, August 15, 2018 12:46 PM
Subject: Re: [nvda] Change on Amazon makes buying options less, possibly
inaccessible with screenreaders while on product page


I need to correct 1 thing I said not alt tab but shift tab gets you to the
buy it now button and it works I've been doing it for the last 2 days!

to recap it's check submit queery then spacebar insert then shift tab to buy
now!

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

Thanks all for your messages and thoughts. Maybe it's time to open a
ticket
now that I know it's not me.
Incidentally, I tried it also on the portable ESR Firefox, one still in
the
version 52 series, latest Chrome, and latest IE, and all are showing the
no
numbered heading level. For me, tabbing around didn't work. I'll try
Travis's suggestions in a while.

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


Thanks, Travis. I will file this info away because I, too, use Kindle
Unlimited. I used it just the other day to grab a book and it worked
just fine: the correct buttons showed in the correct places and showed
as actual buttons. thank you. I wouldn't have even thought to route the
NVDA cursor to the buttton because I'm not as familiar with that as I
really need to be. I never used the virtual mouse cursor in System
Access when I used it and rarely ever used the JAWS cursor in JAWS when
I used that because I didn't really understand how it worked, but it
sounds like it's time for me to learn to understand it. LOL! Thanks again.

Annette
On 8/14/2018 9:24 PM, Travis Siegel wrote:

The problem exists when using the kindle unlimited program to get a
book. You have to tab to the button (NVDA sees it as a button), but
pressing b doesn't go to it. However, when I was sitting on it (after
finding it via the tab key), I used nvda-F1 to bring up it's
information, and it is clearly labeled as a button, so no clue why b
doesn't navigate to it. I've also discovered the only for me to click
the button is to use the route command (nvda-numpad minus) to route
the nvda cursor to it, then press nvda-shift-numpad enter. (yes, I
need the shift, without it, it activates an entirely different page
which has ne bearing on what I'm trying to do). No idea why the shift
works and w/o the shift doesn't, but there it is. That's the only
I've managed to get my books into the kindle app using the web site.
Interestingly enough, using safari on the Iphone doesn't have this issue.

Someone suggested I roll back to Firefox ESR, but I don't know that that would fix the issue. I think I'll just try what you suggested instead. (Smile).


On 8/15/2018 2:59 PM, Danni wrote:

YW it's much easier but gotta listen for the buy it now or you start over haha I hope they change it back but we know how it goes with change!

----- Original Message ----- From: "Annette Moore" <angelgirl52376@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, August 15, 2018 12:59 PM
Subject: Re: [nvda] Change on Amazon makes buying options less, possibly inaccessible with screenreaders while on product page

Thanks, Danni. I'll try that next time.

Annette


On 8/15/2018 2:46 PM, Danni wrote:

I need to correct 1 thing I said not alt tab but shift tab gets you to the buy it now button and it works I've been doing it for the last 2 days!

to recap it's check submit queery then spacebar insert then shift tab to buy now!

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

Thanks all for your messages and thoughts. Maybe it's time to open a ticket
now that I know it's not me.
Incidentally, I tried it also on the portable ESR Firefox, one still in the
version 52 series, latest Chrome, and latest IE, and all are showing the no
numbered heading level. For me, tabbing around didn't work. I'll try
Travis's suggestions in a while.

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


Thanks, Travis. I will file this info away because I, too, use Kindle
Unlimited. I used it just the other day to grab a book and it worked
just fine: the correct buttons showed in the correct places and showed
as actual buttons. thank you. I wouldn't have even thought to route the
NVDA cursor to the buttton because I'm not as familiar with that as I
really need to be. I never used the virtual mouse cursor in System
Access when I used it and rarely ever used the JAWS cursor in JAWS when
I used that because I didn't really understand how it worked, but it
sounds like it's time for me to learn to understand it. LOL! Thanks again.

Annette
On 8/14/2018 9:24 PM, Travis Siegel wrote:

The problem exists when using the kindle unlimited program to get a
book. You have to tab to the button (NVDA sees it as a button), but
pressing b doesn't go to it. However, when I was sitting on it (after
finding it via the tab key), I used nvda-F1 to bring up it's
information, and it is clearly labeled as a button, so no clue why b
doesn't navigate to it. I've also discovered the only for me to click
the button is to use the route command (nvda-numpad minus) to route
the nvda cursor to it, then press nvda-shift-numpad enter. (yes, I
need the shift, without it, it activates an entirely different page
which has ne bearing on what I'm trying to do). No idea why the shift
works and w/o the shift doesn't, but there it is. That's the only
I've managed to get my books into the kindle app using the web site.
Interestingly enough, using safari on the Iphone doesn't have this issue.

Thanks all for your messages and thoughts. Maybe it's time to open a
ticket
now that I know it's not me.
Incidentally, I tried it also on the portable ESR Firefox, one still in
the
version 52 series, latest Chrome, and latest IE, and all are showing the
no
numbered heading level. For me, tabbing around didn't work. I'll try
Travis's suggestions in a while.

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


Thanks, Travis. I will file this info away because I, too, use Kindle
Unlimited. I used it just the other day to grab a book and it worked
just fine: the correct buttons showed in the correct places and showed
as actual buttons. thank you. I wouldn't have even thought to route the
NVDA cursor to the buttton because I'm not as familiar with that as I
really need to be. I never used the virtual mouse cursor in System
Access when I used it and rarely ever used the JAWS cursor in JAWS when
I used that because I didn't really understand how it worked, but it
sounds like it's time for me to learn to understand it. LOL! Thanks again.

Annette
On 8/14/2018 9:24 PM, Travis Siegel wrote:

The problem exists when using the kindle unlimited program to get a
book. You have to tab to the button (NVDA sees it as a button), but
pressing b doesn't go to it. However, when I was sitting on it (after
finding it via the tab key), I used nvda-F1 to bring up it's
information, and it is clearly labeled as a button, so no clue why b
doesn't navigate to it. I've also discovered the only for me to click
the button is to use the route command (nvda-numpad minus) to route
the nvda cursor to it, then press nvda-shift-numpad enter. (yes, I
need the shift, without it, it activates an entirely different page
which has ne bearing on what I'm trying to do). No idea why the shift
works and w/o the shift doesn't, but there it is. That's the only
I've managed to get my books into the kindle app using the web site.
Interestingly enough, using safari on the Iphone doesn't have this issue.

YW it's much easier but gotta listen for the buy it now or you start over haha I hope they change it back but we know how it goes with change!

----- Original Message ----- From: "Annette Moore" <angelgirl52376@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, August 15, 2018 12:59 PM
Subject: Re: [nvda] Change on Amazon makes buying options less, possibly inaccessible with screenreaders while on product page

Thanks, Danni. I'll try that next time.

Annette


On 8/15/2018 2:46 PM, Danni wrote:

I need to correct 1 thing I said not alt tab but shift tab gets you to the buy it now button and it works I've been doing it for the last 2 days!

to recap it's check submit queery then spacebar insert then shift tab to buy now!

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

Thanks all for your messages and thoughts. Maybe it's time to open a ticket
now that I know it's not me.
Incidentally, I tried it also on the portable ESR Firefox, one still in the
version 52 series, latest Chrome, and latest IE, and all are showing the no
numbered heading level. For me, tabbing around didn't work. I'll try
Travis's suggestions in a while.

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


Thanks, Travis. I will file this info away because I, too, use Kindle
Unlimited. I used it just the other day to grab a book and it worked
just fine: the correct buttons showed in the correct places and showed
as actual buttons. thank you. I wouldn't have even thought to route the
NVDA cursor to the buttton because I'm not as familiar with that as I
really need to be. I never used the virtual mouse cursor in System
Access when I used it and rarely ever used the JAWS cursor in JAWS when
I used that because I didn't really understand how it worked, but it
sounds like it's time for me to learn to understand it. LOL! Thanks again.

Annette
On 8/14/2018 9:24 PM, Travis Siegel wrote:

The problem exists when using the kindle unlimited program to get a
book. You have to tab to the button (NVDA sees it as a button), but
pressing b doesn't go to it. However, when I was sitting on it (after
finding it via the tab key), I used nvda-F1 to bring up it's
information, and it is clearly labeled as a button, so no clue why b
doesn't navigate to it. I've also discovered the only for me to click
the button is to use the route command (nvda-numpad minus) to route
the nvda cursor to it, then press nvda-shift-numpad enter. (yes, I
need the shift, without it, it activates an entirely different page
which has ne bearing on what I'm trying to do). No idea why the shift
works and w/o the shift doesn't, but there it is. That's the only
I've managed to get my books into the kindle app using the web site.
Interestingly enough, using safari on the Iphone doesn't have this issue.

I started a mailing list where I hope to, eventually, have companies and otherwise looking for accessibility testers post to the list from the outside and then users can reply whenever. I am currently building the wiki page, companies that hire people to do accessibility testing and the like. If anybody wants to subscribe, although, there is 0 traffic because I created it 5 minutes ago, send an email to the below. I also will include paid research studies, as well. Paid accessibility surveys too. The wiki is not live yet but should be tomorrow.

a11y+subscribe@groups.io

To have companies and stuff, post to the list, send an email to the below.

a11y@groups.io.