Suggestion: allow some pause between the cell content and cell address.

[nvaccessAuto]

Reported by sumandogra on 2013-12-27 09:58 Excel

At present NVDA speaks out the cell address in continuation with the cell content without any pause in between. A small pause between the announcement of the cell content and cell address can help understanding the Excel sheets in a better way.

Suggestion to introduce Blocked by #4877

[nvaccessAuto]

Comment 2 by siddhartha_iitd on 2015-01-23 14:12 A scenario where this issue is relevant: In Banking, BPO and other such sectors, a user has to deal with a lot of customer-data and therefore it becomes imperative that there should be no ambiguity in the presentation of such data by a screen-reader. Presently, NVDA has little gap between speaking MS Excel cell-content and cell-address. This property makes NVDA difficult to use in such scenarios. If we resolve this issue it will be beneficial for visually-impaired users in data-intensive sectors globally.

[bhavyashah]

I believe this suggestion is sufficiently well-defined for this ticket to be marked as a feature. The only remaining consideration may be the length of the pause, because we do not want it to be such that it hinders the efficiency of those extensively working with tables at fast speech rates, still making it noticeably useful for those using slower speech rates. When we get to work on this, I would like to kindly request we tackle #3462 along with this.

[josephsl]

Hi, is this another use case for #4877 instead? CC @JCSTeh

From: bhavyashah [mailto:notifications@github.com] Sent: Saturday, August 26, 2017 9:21 AM To: nvaccess/nvda nvda@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [nvaccess/nvda] Suggestion: allow some pause between the cell content and cell address. (#3736)

I believe this suggestion is sufficiently well-defined for this ticket to be marked as a feature. The only remaining consideration may be the length of the pause, because we do not want it to be such that it hinders the efficiency of those extensively working with tables at fast speech rates, still making it noticeably useful for those using slower speech rates. When we get to work on this, I would like to kindly request we tackle #3462 https://github.com/nvaccess/nvda/issues/3462 along with this.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/3736#issuecomment-325143207 , or mute the thread https://github.com/notifications/unsubscribe-auth/AHgLkEZNyhocOCNMUXSfeTM5QFNUnwfoks5scEXTgaJpZM4PDikC .

[jcsteh]

This depends on #4877, but it won't be implemented directly by that issue.

3642 is not related to this from a design or implementation standpoint, so it should not be handled as part of the same work.

[Adriani90]

@sumandogra, @siddhartha_iitd I am working as financial analyst and am dealing with complex financial models in Excel. I can definitely say that a pause could decrease the probability that someone misinterprets figures. But it would definitely also decrease efficiency because you have to wait longer until the cell coordinate is being reported. Instead of inserting such a pause, I would rather suggest to add a key stroke to NVDA for reporting the current cell. In that case the announcement of cell coordinates could be disabled in document formating settings and we could easily identify the coordinates of the cell by pressing the key stroke when desired.

Another possibility would be to split the reporting of cell coordinate in row and column. Then switch the order (instead of C1 report 1C) and move the reporting of coordinates before cell content while navigating. In this case, NVDA would report i.e. 1A 20, 1B 30, 1C 40 etc.

[Adriani90]

the second option should be optional ofcourse.