Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LibreOffice Calc: report selected cell coordinates #6897

Open
surfer0627 opened this issue Feb 18, 2017 · 13 comments
Open

LibreOffice Calc: report selected cell coordinates #6897

surfer0627 opened this issue Feb 18, 2017 · 13 comments

Comments

@surfer0627
Copy link
Contributor

@surfer0627 surfer0627 commented Feb 18, 2017

This is a feature request that NVDA report selected cell coordinates.
Steps to reproduce:

  1. Open Calc.
  2. Press shift+downArrow.
    NVDA report: nothing
    expected: a1 through a2 selected
  3. press ctrl+home to move to top.
  4. Press shift+space to select entire row
    NVDA report: space
    expected: a1 through amj1 selected
@zahra21
Copy link

@zahra21 zahra21 commented Jan 16, 2018

hi.
i confirm this issue.
does nvda support reporting of selection in microsoft excel?
if you found solution for this, please inform me.
thanks and God bless all.

@Adriani90
Copy link
Collaborator

@Adriani90 Adriani90 commented Apr 1, 2019

@zahra21 yes in Excel this is supported. In Libre Calc this is still an issue. Right?

@surfer0627
Copy link
Contributor Author

@surfer0627 surfer0627 commented Aug 8, 2019

It seems that LibreOffice developer Tamás Zolnai committed a patch related to this issue (adding selection-changed event).

bug 93825 – Missing accessibility events when selecting/deselecting cells in Calc

cc @leonardder: Could you please check, if this is helpful?

Thanks.

@leonardder
Copy link
Collaborator

@leonardder leonardder commented Aug 8, 2019

@surfer0627
Copy link
Contributor Author

@surfer0627 surfer0627 commented Aug 8, 2019

Yes, developer Tamás Zolnai pointed out that it is available in 5.2.4. @leonardder

@leonardder
Copy link
Collaborator

@leonardder leonardder commented Aug 8, 2019

@surfer0627
Copy link
Contributor Author

@surfer0627 surfer0627 commented Aug 8, 2019

In this case, LibreOffice developer said "selection change event is added."
But, this patch does not fix screen reader NVDA "report selected cell coordinates".
What should we do (Let LibreOffice developer know the gap)?
Or how to use this "selection change event to implement feature "report selected cell coordinates?

@leonardder
Copy link
Collaborator

@leonardder leonardder commented Aug 8, 2019

@nktech1135
Copy link

@nktech1135 nktech1135 commented Oct 14, 2020

Is anyone working on this? It's still an issue in libreoffice 7.0.2 and nvda 2020.3
A fix would be greatly appreciated.

@leonardder
Copy link
Collaborator

@leonardder leonardder commented Oct 14, 2020

Apart from the patch refered to in #6897 (comment), it looks like LibreOffice people aren't that accessibility minded unfortunately.

@nktech1135
Copy link

@nktech1135 nktech1135 commented Oct 14, 2020

it looks like LibreOffice people aren't that accessibility minded unfortunately.

Do we have examples of this? Were the correct bugs ever filed against libreoffice to make them aware of the issue? I'm not a developer so can't file the bugs myself as i wouldn't know what to point at or what the behind the seens tech speak would be.

@feerrenrut
Copy link
Contributor

@feerrenrut feerrenrut commented Oct 14, 2020

A number of accessibility bugs filed, many issues here with the app/libreoffice label have links to bugs on the issue tracker for libreoffice.

I have tried to reach out to a few developers who work on libreoffice, for the record NV Access is willing to work with libreoffice developers to help solve these issues. They can contact us via info@nvaccess.org to start a conversation.

@Qchristensen
Copy link
Contributor

@Qchristensen Qchristensen commented Oct 15, 2020

There is an issue on LibreOfice's bug tracker for this, which goes back to 2016: https://bugs.documentfoundation.org/show_bug.cgi?id=100086 (with references to an older issue again).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
8 participants