Date   

Re: Microsoft Word 2016 stop working.

Pranav Lal
 

Hi Daniele,

You may have sent this before but do you have any logs from the crash?

Pranav


Re: Text selection in Word 2016

Quentin Christensen
 

Hi Claire,

Could you please send me a copy of your NVDA log so I can see if there is anything in there - ideally at log level debug.  See https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps for info on the log.

I am using Windows 10 fast insider build 1803, version 17738.1000 and Office 365 / 2016 version 1807 build 10325.20082
Using either NVDA Alpha 15858.949f0bab or stable 2018.2.1, I am not encountering the issue myself, so it will be interesting to see whether you have different builds of Windows / Office of if it is something that for some other reason isn't affecting everyone across the board.

Someone mentioned the NVDA command to read the current selection - NVDA+shift+up arrow (for laptop layout users, it's NVDA+shift+s).  Does that correctly report the selected text?

Regards

Quentin.

On Thu, Aug 16, 2018 at 10:22 AM, Brian Vogel <britechguy@...> wrote:
On Wed, Aug 15, 2018 at 07:15 PM, Gene wrote:
The update may not be available in your area yet. 
Indeed.   Whether it's a feature update or a cumulative update or a patch Tuesday fix update, none go out to all the world of Win10 computers in a very short time frame.

Feature updates typically take months before phased roll out is complete; cumulative updates between days and weeks, depending on their size and complexity; and small fix updates between several days and a week or so.

It's been that way since the start of Windows 10, with telemetry results guiding speed of the cohorts being pushed out.
 
--

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

 

 




--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: braille stops working

Quentin Christensen
 

Hi Brian,

Not so much a solution, but this issue looks similar to what you've posted in your log.  It might be worth commenting on it to confirm that you are having the problem as well (and prompt those involved previously to have another look): https://github.com/nvaccess/nvda/issues/5754



On Wed, Aug 15, 2018 at 11:37 PM, Brian Tew via Groups.Io <briantew1951@...> wrote:
Hello,
My braille stops working sometimes. restoring saved configuration usually fixes it,
but can you tell me a permanent fix? see line 35 ff. below.
something braillish is going wrong.

INFO - core.main (05:14:26.030):
Config dir: C:\Users\admin\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (05:14:26.030):
Loading config: C:\Users\admin\AppData\Roaming\nvda\nvda.ini
INFO - core.main (05:14:26.108):
NVDA version 2018.2.1
INFO - core.main (05:14:26.108):
Using Windows version 10.0.17134 workstation
INFO - core.main (05:14:26.108):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)]
INFO - core.main (05:14:26.108):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (05:14:26.908):
Loaded synthDriver oneCore
INFO - core.main (05:14:26.924):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (05:14:26.924):
Braille input initialized
INFO - braille.initialize (05:14:26.924):
Using liblouis version 3.5.0
INFO - brailleDisplayDrivers.hims.BrailleDisplayDriver.__init__ (05:14:27.384):
Found Braille Sense connected via USB bulk (\??\USB#VID_045E&PID_930A#00000000-0000-0000-0000-000000000000#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
INFO - braille.BrailleHandler.setDisplayByName (05:14:27.384):
Loaded braille display driver hims, current display has 32 cells.
WARNING - core.main (05:14:27.424):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (05:14:27.434):
UIAutomation: IUIAutomation5
INFO - core.main (05:14:27.625):
NVDA initialized
INFO - config.ConfigManager.save (05:14:32.505):
Base configuration saved
ERROR - scriptHandler.executeScript (05:27:48.190):
error executing script: <bound method GlobalCommands.script_braille_scrollForward of <globalCommands.GlobalCommands object at 0x05824670>> with gesture 'rightSideScrollDown'
Traceback (most recent call last):
 File "scriptHandler.pyo", line 187, in executeScript
 File "globalCommands.pyo", line 1910, in script_braille_scrollForward
 File "braille.pyo", line 1672, in scrollForward
 File "braille.pyo", line 1254, in scrollForward
 File "braille.pyo", line 1021, in nextLine
 File "NVDAObjects\UIA\edge.pyo", line 125, in move
 File "NVDAObjects\UIA\edge.pyo", line 116, in _collapsedMove
 File "NVDAObjects\UIA\edge.pyo", line 93, in _moveToEdgeOfReplacedContent
 File "baseObject.pyo", line 21, in __get__
 File "NVDAObjects\UIA\edge.pyo", line 75, in _get_UIAElementAtStartWithReplacedContent
COMError: (-2147467259, 'Unspecified error', (None, None, None, 0, None))
INFO - core.main (05:32:19.049):
Exiting
INFO - config.ConfigManager.save (05:32:19.072):
Base configuration saved
INFO - __main__ (05:32:20.477):
NVDA exit






--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: Text selection in Word 2016

 

On Wed, Aug 15, 2018 at 07:15 PM, Gene wrote:
The update may not be available in your area yet. 
Indeed.   Whether it's a feature update or a cumulative update or a patch Tuesday fix update, none go out to all the world of Win10 computers in a very short time frame.

Feature updates typically take months before phased roll out is complete; cumulative updates between days and weeks, depending on their size and complexity; and small fix updates between several days and a week or so.

It's been that way since the start of Windows 10, with telemetry results guiding speed of the cohorts being pushed out.
 
--

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

 

 


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

Gene
 

I think they will correct it but those who protest should make clear that changes should be tested before release and not release untested changes and correct the problem after users complain.  They don't treat sighted users this way.  Separate is not equal.
 
Gene

----- Original Message -----
From: Kwork
Sent: Wednesday, August 15, 2018 6:29 PM
Subject: Re: [nvda] Change on Amazon makes buying options less, possibly inaccessible with screenreaders while on product page

Here here! Pretty sad when a simple minded stuffed bear would have more sense than a company supposedly dedicated to accessibility issues.
The Kindle app for iOS was recently broken for Voiceover users. Enough people did complain and the reading issue that plagued many was silently fixed in the next update, so maybe Amazon will listen if enough of us voice our opinions on recent changes to the website. Likely doubtful, but we shouldn't give up.
Travis
----- Original Message -----
From: Gene
Sent: Wednesday, August 15, 2018 2:01 PM
Subject: Re: [nvda] Change on Amazon makes buying options less, possibly inaccessible with screenreaders while on product page

Just one more example of what happens when someone or a corporation, which is bye law a person, so someone, with very little brain, like Winney the Pu (spelling) still doesn't know after years of working with advocacy groups to make their site accessible, that you don't just make changes.  You test them with blind users before implementing them.  This is clearly something a sighted person would see.  A screen-reader wouldn't read it automatically.  the page has changed.  Perhaps this change could be properly coded using Aria or JAVA script, I don't have the technical knowledge to know how best to do it.  The person would be placed on the correct control and the text would be read as well as the control you are on.  But no.  Obviously the changes weren't tested, not even with one or two blind people.  Even Winnie The Pu learns faster.
 
Gene
----- Original Message -----
From: Kwork
Sent: Wednesday, August 15, 2018 3:47 PM
Subject: Re: [nvda] Change on Amazon makes buying options less, possibly inaccessible with screenreaders while on product page

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@...>
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@...>
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@...>
> 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.
>>
>>
>>
>>
>
>
>
>
>
>
>







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

Kwork
 


Here here! Pretty sad when a simple minded stuffed bear would have more sense than a company supposedly dedicated to accessibility issues.
The Kindle app for iOS was recently broken for Voiceover users. Enough people did complain and the reading issue that plagued many was silently fixed in the next update, so maybe Amazon will listen if enough of us voice our opinions on recent changes to the website. Likely doubtful, but we shouldn't give up.
Travis

----- Original Message -----
From: Gene
Sent: Wednesday, August 15, 2018 2:01 PM
Subject: Re: [nvda] Change on Amazon makes buying options less, possibly inaccessible with screenreaders while on product page

Just one more example of what happens when someone or a corporation, which is bye law a person, so someone, with very little brain, like Winney the Pu (spelling) still doesn't know after years of working with advocacy groups to make their site accessible, that you don't just make changes.  You test them with blind users before implementing them.  This is clearly something a sighted person would see.  A screen-reader wouldn't read it automatically.  the page has changed.  Perhaps this change could be properly coded using Aria or JAVA script, I don't have the technical knowledge to know how best to do it.  The person would be placed on the correct control and the text would be read as well as the control you are on.  But no.  Obviously the changes weren't tested, not even with one or two blind people.  Even Winnie The Pu learns faster.
 
Gene
----- Original Message -----
From: Kwork
Sent: Wednesday, August 15, 2018 3:47 PM
Subject: Re: [nvda] Change on Amazon makes buying options less, possibly inaccessible with screenreaders while on product page

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@...>
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@...>
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@...>
> 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.
>>
>>
>>
>>
>
>
>
>
>
>
>







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

Kwork
 

I don't think that would work. Chrome and Internet Explorer are doing the
same thing. In fact, I did try it with the Firefox ESR from the 52 series,
and had the same result. It's definitely a change on Amazon's end. I don't
have any other screenreaders installed here, so can't test. I used to have
the Jaws demo, but got rid of it when it, for some reason, no longer
acknowledged 40 minute mode on this computer, so became a software brick.
Travis

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


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.














Re: Text selection in Word 2016

Gene
 

The update may not be available in your area yet.  According to one report I saw, it was a very large update, the person discussing it said it was the largest he's seen that isn't a six month full update.
 
Gene

----- Original Message -----
Sent: Wednesday, August 15, 2018 6:08 PM
Subject: Re: [nvda] Text selection in Word 2016

Well if its a problem, can others duplicate it.

It should be reported to ms, if its a problem they will fix it.

I havn't looked for updates today for 2016 but if its the latest one
well I am unsure if you can role back or not.

At any rate if you give it to ms and they can fix it, the fix will
probably make the next update role.



On 8/16/2018 10:20 AM, Gene wrote:
> Perhaps the update includes an update to Word 2016 which is somehow causing the problem.
>
> What you might do is select close to what you want, it might be a little over, open a new word window, paste it in, edit it, then copy the edited material to the clipboard again.  Then, paste it wherever you want.  That may be the best thing to do for now until you get a better solution.
>
> Gene
> ----- Original Message -----
>
> From: Claire Potter
> Sent: Wednesday, August 15, 2018 5:08 PM
> To: nvda@nvda.groups.io
> Subject: Re: [nvda] Text selection in Word 2016
>
>
> Hi Brian, yes it was a cuculative update, but the odd thing is that I'm only having the issue in Word 2016.
>
>
> Warm regards, Claire Potter,   Check out my brand new website: www.pottersplace.me.uk
>
> On 15 Aug 2018, at 22:55, Brian Vogel <britechguy@...> wrote:
>
>
>    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
>
>
>
>
>
>
>
>
>



Re: Text selection in Word 2016

 

Well if its a problem, can others duplicate it.

It should be reported to ms, if its a problem they will fix it.

I havn't looked for updates today for 2016 but if its the latest one well I am unsure if you can role back or not.

At any rate if you give it to ms and they can fix it, the fix will probably make the next update role.

On 8/16/2018 10:20 AM, Gene wrote:
Perhaps the update includes an update to Word 2016 which is somehow causing the problem.

What you might do is select close to what you want, it might be a little over, open a new word window, paste it in, edit it, then copy the edited material to the clipboard again. Then, paste it wherever you want. That may be the best thing to do for now until you get a better solution.

Gene
----- Original Message -----

From: Claire Potter
Sent: Wednesday, August 15, 2018 5:08 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Text selection in Word 2016


Hi Brian, yes it was a cuculative update, but the odd thing is that I'm only having the issue in Word 2016.


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

On 15 Aug 2018, at 22:55, Brian Vogel <britechguy@gmail.com> wrote:


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








Muting "selected" on Google Sheets and other grid aria elements?

 

Hello,
Is there any way to mute "selected" on grids? I only want to hear "selected" when I select something. It is too much to hear "selected" when I move between every cell. I love the UX on Google Sheets when Braille support is not checked, but the "selected" when I move between cells drives me crazy.
This is the case on all grid elements.
You can see this behavior both on Google sheets with Braille support checked, as well as:

Is there some way to change it?
Thank you,


Re: NVDA 2018, excel row and column headers

 

Rui,

           Thanks for the confirmation.

--

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

 

 


Re: Text selection in Word 2016

 

Claire,

           I would be very tempted to do a reinstall of NVDA (which is quickest and easiest) to see of that solves the issue, since you say it's only in Word.
 
           The real trick here is all the diagnostic steps required to narrow things down, and when it's really easy to do an uninstall/reinstall, which generally allows you to eliminate issues with the thing uninstalled/reinstalled, its something you can try, particularly since it's easy and fast.
--

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

 

 


Re: Text selection in Word 2016

Gene
 

Perhaps the update includes an update to Word 2016 which is somehow causing the problem. 
 
What you might do is select close to what you want, it might be a little over, open a new word window, paste it in, edit it, then copy the edited material to the clipboard again.  Then, paste it wherever you want.  That may be the best thing to do for now until you get a better solution.
 
Gene

----- Original Message -----
Sent: Wednesday, August 15, 2018 5:08 PM
Subject: Re: [nvda] Text selection in Word 2016

Hi Brian, yes it was a cuculative update, but the odd thing is that I'm only having the issue in Word 2016. 

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

On 15 Aug 2018, at 22:55, Brian Vogel <britechguy@...> wrote:

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

 

 


Re: Text selection in Word 2016

Gene
 

There is an NVDA command to speak selected text.  It is NVDA shift up arrow.  I don't know what the update may have done.  Evidently yesterday, a very large update was released and I've seen two or three reports today from people with this or that problem after the update. 
 
See if that command helps you.  You wouldn't use it to hear every line as you select, but you can use it to hear the whole of what you have selected until you get a better solution.
 
Gene

----- Original Message -----
Sent: Wednesday, August 15, 2018 4:32 PM
Subject: Re: [nvda] Text selection in Word 2016

Yes, that’s right, it is rather hindering now and not great for productivity.

 

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

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Monte Single
Sent: 15 August 2018 22:30
To: nvda@nvda.groups.io
Subject: Re: [nvda] Text selection in Word 2016

 

Do you mean since your  machine updated to  1803?

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Claire Potter
Sent: August-15-18 3:27 PM
To: nvda@nvda.groups.io
Subject: [nvda] Text selection in Word 2016

 

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/


Re: Text selection in Word 2016

Claire Potter <claire.potter99@...>
 

Hi Brian, yes it was a cuculative update, but the odd thing is that I'm only having the issue in Word 2016. 

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

On 15 Aug 2018, at 22:55, Brian Vogel <britechguy@...> wrote:

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

 

 


Re: NVDA 2018, excel row and column headers

Rui Fontes
 

Yes, if you define the names in Excel itself, or using Jaws, NVDA will recognize...

Rui Fontes


Às 21:52 de 15/08/2018, Brian Vogel escreveu:

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


Re: Text selection in Word 2016

 

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

 

 


Re: Text selection in Word 2016

Claire Potter <claire.potter99@...>
 

Yes, that’s right, it is rather hindering now and not great for productivity.

 

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

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Monte Single
Sent: 15 August 2018 22:30
To: nvda@nvda.groups.io
Subject: Re: [nvda] Text selection in Word 2016

 

Do you mean since your  machine updated to  1803?

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Claire Potter
Sent: August-15-18 3:27 PM
To: nvda@nvda.groups.io
Subject: [nvda] Text selection in Word 2016

 

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/


Re: Text selection in Word 2016

Monte Single
 

Do you mean since your  machine updated to  1803?

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Claire Potter
Sent: August-15-18 3:27 PM
To: nvda@nvda.groups.io
Subject: [nvda] Text selection in Word 2016

 

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/


Text selection in Word 2016

Claire Potter <claire.potter99@...>
 

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/