Re: NVDA and office 365

Timothy VD Berg


I know that I am in the table.

When I navigate I use tab, or alt + control and arrows keys.

It tells me not in a table.





From: <> On Behalf Of Quentin Christensen
Sent: Wednesday, 02 November 2022 22:35
Subject: Re: [nvda] NVDA and office 365


When you say NVDA is not reading the table, how are you trying to read it?  (say all, pressing down arrow, using table navigation keys)?  And are you getting any feedback from NVDA?


Which version of NVDA?

Which version of Office?

Which build of Windows 11?


Just trying here with NVDA 2022.4 Beta 2 (We've added some new table commands etc, in this version, which is handy, but I don't think we've changed anything around the core functionality of being able to read tables in general - certainly our belief is that tables in Word should have been reading fine for some years now).


I also tried the current stable version, NVDA 2022.3.1.


Windows 11 (64-bit) Version: 22H2, Build: 22621.755
Office 365 (64-bit) Version: 16.0.15629.20204


With both mentioned versions of NVDA, I just created a new document, added a table with two columns and rows (alt+n, t, down arrow, right arrow, enter), moved through and added content to each cell and I can read it with say all (NVDA+down arrow or NVDA+a), using arrows, control+alt+arrows, etc.


The other thing I'd suggest, if you have recently updated anything - Windows, NVDA, Office, etc - please restart the PC and see if it still happens.  Also are you using any NVDA add-ons?  And if so, if you press NVDA+q, then down arrow to "Restart with add-ons disabled" and enter, does it still happen.


Kind regards




On Thu, Nov 3, 2022 at 2:48 AM Timothy VD Berg <timothyvandenberg51@...> wrote:

Hi I just opened the document

Which worked all the time

Can It be a update on windows 11




From: <> On Behalf Of Brian Vogel
Sent: Wednesday, 02 November 2022 17:41
Subject: Re: [nvda] NVDA and office 365


On Wed, Nov 2, 2022 at 10:54 AM, Sarah k Alawami wrote:

We cannot help you without these steps, also what have you done to produce the problem

I'll also add, when possible, it is really, really helpful to have a copy of the actual file that is causing the issue if that is something that can be shared.  It lets all assistants be "on the same page(s)" literally when doing their own troubleshooting.

This group, like most of them, does not allow attachments.  But using Google Drive, OneDrive, Dropbox, or similar when possible to share an example of a file that's giving issues is very helpful.

It really is essential, these days, that at a minimum whe know what version of Windows and NVDA you're using.  Office 365 is generally enough, initially, as far as that goes.  If heavy duty digging becomes necessary, then the long version number for the program in the office suite you're using (Word, in this case) might be asked for.

As Sarah has noted, too, knowing what it is you're trying to do and how you went about doing it allows others to try the same techniques to see if they can replicate the problem you're having.
These kinds of issues really don't get solved in the abstract, but in the very, very specific.

Brian Virginia, USA  Windows 10, 64-Bit, Version 22H2, Build 19045  

There are many people who can only make themselves feel better about themselves by making themselves feel better than others.

    ~ Commenter Looking_in on the Washington Post, 7/10/2014



Quentin Christensen
Training and Support Manager


Join { to automatically receive all group messages.