Comment 1 by jteh on 2013-02-24 01:06
This is a help message. While I understand the desire for it for newer users, NVDA doesn't currently support help messages at all, so this would need to be implemented first.

Comment 2 by rameshwar.nagar on 2013-05-02 09:19
Now User reach on last cell using Tab or Ctrl+Alt+Arrow(Key) then NVDA announce that Last Cell of Table. I atteched patch file for review.

Attachment 3018_Last_Cell_of_Table_bugfix1.patch added by rameshwar.nagar on 2013-05-02 09:53
Description:
NVDA report when user reach in last cell of table using Tab or Ctrl+Alt+ArrowKey
Update:
File added from Trac
3018_Last_Cell_of_Table_bugfix1.patch.txt

Comment 3 by bhavyashah on 2015-01-17 12:08
Hi,
Please add the keywords 'needs code review' to this ticket since a patch seems to have been provided.
ONe more question, is the provided patch specifically for Microsoft Office Word 2010, or will it work on other versions of MS Word?
Thanks.

@jcsteh mentions in #3018 (comment) that NVDA currently does not support help messages. While I am unaware of the technical meaning of 'help messages', could someone please cite the ticket which covers the general support of help messages, if one exists? Also, the NeedsCodeReview label needs to be added and the attachment needs to be restored. @ehollig

Hi,

Find attached some examples and bug and improvement lists to fix related with tables.
It is very important since it happens in various Ms office versions.
Sorry for uploading it like this.

Thanks
TableExamplesNVDA.docx

Actually a table should not be read by pressing tab or shift+tab. Users should be encouraged to use ctrl+alt+arrow keys because this fives you a much better orientation within the table. And you hear the borders of the table as well.
I suggest instead of investing so much work in implementing such a function, we should add some practical recomendations in the user guide which gives the user some tools to work productively with.

In forms for example you do not get announced that the next tab press will bring you back to the first field. And in my opinion we can find lots of such logical navigation paths where users are not desoriented even though NVDA does not announce what will happen next. For example pressing tab when editing an excel cell brings you to the next cell but your text will be saved in the previous cell. This is also not announced but it is known by every ecxel user and thus, this behavior does not desorientate users.

I suggest closing this issue and adding some recommendations in the user guide.

@rameshwar.nagar could you please raise a Pull request for this issue?

@jcsteh, @michaelDCurran, the author of the patch uploaded above seems not to be available on Github anymore. In my view we do not need this extra verbosity because the table borders are reported by NVDA when navigating with ctrl+alt+arrow keys. Are there any plans to implement this though?

After thinking more about this, I think for braille display users would be beneficial to have such a feature like a notification which can appear for five seconds or so. But in my view this would not be needed for speech.

After thinking more about this, the fact that pressing tab in the last cell creates a new row, is valid also for sighted people and there is no message for them which displays that a new row is created, at least according to my knowledge.
So I think this should be covered by basic knowledge of the application and not by adding a custom message in NVDA.
@lukaszgo1, @Qchristensen what do you think? Especially Quentin, can you confirm there is no message displayed for sighted people when focusing the last cell with tab?

Currently, at least in the Microsoft Word in Office 365, when pressing TAB in the last cell of a table NVDA announces that the table size has changed, and that caret has moved to the new cell, along with its coordinates.
This however covers only the part of the issue, that is blind user is aware that new row was added. There is however, no announcement that the cell in which user is positioned currently is the last one, which is pretty apparent to a sighted person. I don't have a clear idea in which way this can be communicated, as not to be overly verbose, but the original problem, is IMHO, valid to some extend.

For NVDA to report the new added row properly, "tables" must be enabled in document formating settings. Even though cell coorinates are enabled, these work only together with the tables option. This bug, at least for browse mode, how ever is already covered in #8583.

I think this issue would be solved if there was the possibility to switch into a table mode where you can use arrow keys to navigate the cells. We could introduce gesture layers, wher i.e. you press nvda+shift+t to enable table mode and then use arrow keys or other commands to navigate the table without leaving it.