Description: Using the Table Heading style for column headers results in those headers being retrievable via the accessible table interface. Unfortunately, using that same style for row headers does not render row headers accessible. Impact: Orca does not present row headers automatically to the user. Steps to Reproduce: 1. Open the attached test case in Writer 2. Launch Accerciser and select Table1-1 in its list of accessible objects 3. In Accerciser's iPython console type the following: t = acc.queryTable() t.getColumnDescription(1) t.getColumnHeader(1).name t.getRowDescription(1) t.getRowHeader(1).name Actual Results: Results: GOOD: t.getColumnHeader(1).name returns "B1" GOOD: t.getColumnDescription(1) returns "Foo" BAD: t.getRowDescription(1) returns "" (should be "A2") BAD: t.getRowHeader(1).name results in an AttributeError because null is returned (should be "Baz") Expected Results: (See above) Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 147955 [details] test case
Hello all, I confirm the issue with LibreOffice on 6.1.4.2 on Debian 9 "Stretch" (GNU/Linux) @Joanie: You've linked the issue to a11y-linux but not the operating system, is it a choice? Best regards, Alex.
(In reply to Alex ARNAUD from comment #2) > @Joanie: You've linked the issue to a11y-linux but not the operating system, > is it a choice? I didn't. See https://bugs.documentfoundation.org/show_activity.cgi?id=122432.
Dear Joanmarie Diggs, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Joanmarie Diggs, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug