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

link is not identified as a link by NVDA in Excel sheets, instead it reads it as a simple text. #3042

nvaccessAuto opened this Issue Mar 4, 2013 · 7 comments


None yet
1 participant

Reported by sumandogra on 2013-03-04 11:19
Excel 2010
Link/hyperlink is not recognized as a link by NVDA in an Excel sheet. On moving to a cell that contains a link, no indication is given.
Steps to reproduce:

  1. Write or insert a hyperlink in a cell.
  2. Move to the cell with UP/DOWN ARROW.
  3. NVDA reads the text as a simple text and does not announce it as a link.

Comment 2 by krish on 2013-05-10 06:27
It simply announces "link" before the text, on moving by using keyboard keys into the cell which contains hyperlink.

Attachment hyperlink1.patch added by krish on 2013-05-10 06:27

Comment 3 by vrdhn on 2013-10-11 19:17
Update the code in 2921 ( indicate comments) to indicate links also.
For cell which has formula, comment as well as link, NVDA will speak
'has formula comment link'
This patch is based on the branch mentioned in 2921

Please review this patch:

git repository: ​https://bitbucket.org/manish_agrawal/nvda.git
branch: t3042
base branch: t2921 in same repository


Comment 4 by Michael Curran <mick@... on 2013-10-18 05:07
In [9196608]:

Merge branch 't3042' into next. Incubates #3042

Added labels: incubating

Comment 5 by mdcurran on 2013-10-18 05:10
Sorry - the new implementation is not quite like the provided patch. But we probably should never have used description to indicate formula in the first place.

Comment 6 by Michael Curran <mick@... on 2013-10-31 23:50
In [94cb37f]:

Merge branch 't3042'. Fixes #3042

Removed labels: incubating
State: closed

Comment 7 by mdcurran on 2013-10-31 23:50
Milestone changed from None to 2013.3

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

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