Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Order of speaking cell position and cell contet in MS Excel must be configurable #320

nvaccessAuto opened this Issue Jan 1, 2010 · 13 comments


None yet
1 participant

Reported by aleksey_s on 2009-05-21 05:40
Currently, NVDA announces cell position previously to actual cell content which can be nasty in many situations. So there must be a option to change this order or (at least) disable cell position announcement at all. Therefore, script to read current cell's position is required as well.

Comment 1 by aleksey_s on 2010-02-06 15:37
Any chances this be implementent in the mean time? I've seen users request for this also for oo.o calc in NVDA mailing list. This will really improve user experience in table editing software.

Comment 2 by heikofolkerts on 2010-02-10 20:49
The order also results in misleading spoken text. When in a1 there is the value 500 the speach (in german) says a1500 instead of a1 500. At first I searched for the error in my formula that I tried until I understood, that it was just the join of position and value.

IMHO is this effect blocking the work with apps like excel without a brailledisplay. A fix would really help very much. Maybe it is enough to make a break between position and value.

Comment 3 by jteh on 2010-02-10 21:40
I agree this new issue is major priority, but it is a separate issue and should be filed as such.

Comment by coffeekingms on 2010-02-11 16:55
(In #555) Replying to heikofolkerts:

When using NVDA in Excel 2003 using the german default settings, the cell position and values are pulled together, so that it sounds wrong.


a1 = 300

a2 = 500

will be read like

a 1300

a 2500

It irritated me so much, that I first thought my formula was wrong.

The speach has to tread the cell position and the value separately.

This deffect makes excel allmost unusable without a braille display.

I believe that this is a duplicate of #320. jamie, what do you think? I have closed this temporarily as duplicate of 320. please reopen if I'm incorrect.

Comment 6 by linda on 2011-01-02 19:22

I’m a very new user of NVDA and enjoy ist quality very much.

As a excel-user I have the same problem that is reported here.
Does anyone have a solution for it now? Is there any way to make NVDA speak content of cell first and cell position last?

Would be very glade to get an answer!

Kind regards!

Changed title from "Order of speaking cell position and cell contet in MS Excel must be configurable" to "Solution for Order of speaking cell position and cell content in MS Excel"

Comment 7 by jteh on 2011-01-02 22:06
No, there is no solution yet.
Changed title from "Solution for Order of speaking cell position and cell content in MS Excel" to "Order of speaking cell position and cell contet in MS Excel must be configurable"

Comment 9 by Shaimaa on 2011-04-20 22:16
Changing the order of the cell announcement to speak the cell name before the content slows down work especially when user deals with many confusing numbers. This is making my work more difficult than it should be, I would be grateful when this is implemented

Comment 10 by Shaimaa on 2011-06-01 07:27
Hi, I have talked to some blind people recently about nvda and they also raised to me the issue of the necessity of speaking the content before the cell coordinates, they just don't have good English to give comments etc. The problem exists in Microsoft office 2003 and 2007.
We will be grateful if this is fixed soon to make life easy at work.

Comment 11 by fatma.mehanna on 2011-06-16 10:21
excel is used by most of the companies that employ the blind in call centres and data organizing.
we note many fixes for many problems we face in excel like moving between the active sheats and reinstating the f2 cell editor dialogue.
we will be more gratefull if you have time to let nvda speak the cell content before the cell reference.
it will make work easier.

Comment 12 by Shaimaa on 2012-04-11 16:23
Hey Guys,
for more than a year now, some people and I strongly needed that this ticket to be fixed urgently because it affects our work and it is really irritating for the user who deals with thousands of cells daily but nothing has been done yet. I recently donated $50 for this ticket and another $50 for another Excel related ticket hoping they get fixed very soon.
I highly appreciate your great work and the pressure you experience from time to time. I also don't know how you guys set your priorities for each release but if the user doesn't feel that his program doesn't meet his / her needs at work or studies, he / she may leave very quickly to a commercial program.
Thank you

Comment 13 by orcauser on 2012-04-30 09:55
Shaimaa/Fatma, can you check if a recent snapshot gives the desired output?
Mick committed a possible fix in 0e42030.

Comment 14 by fatma.mehanna (in reply to comment 13) on 2012-04-30 12:36
Replying to orcauser:

Shaimaa/Fatma, can you check if a recent snapshot gives the desired output?

yes it has been fixed as the cell content is being reported before the cell coordinate.

Mick committed a possible fix in 0e42030.



State: closed

Comment 15 by jteh on 2012-04-30 22:35
Milestone changed from None to 2012.2

@nvaccessAuto nvaccessAuto added this to the 2012.2 milestone Nov 10, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment