https://bugs.documentfoundation.org/show_bug.cgi?id=92389
--- Comment #11 from Christophe Strobbe <c_strobbe-...@yahoo.co.uk> --- I have looked at the bugs that have been marked as a duplicate of this one or that are indirectly linked to it: * Bug 92389 - Writer: Comment text not accessible with screen reader Reported without reference to a specific OS; confirmed both on Linux with Orca (until 2019) and on Windows with NVDA (2017). * Bug 99261 - Calc: Comment not supported with screen reader Reported for Windows (tested with both Jaws and NVDA); confirmed on Linux with Orca * Bug 101002 - Comments in Impress are not accessible (adding/reading) Reported for Linux with Orca; comments mention both keyboard interaction problems and missing accessibility metadata (checked using accerciser). * Bug 102054 - Allow access and modifying of comment with keyboard Reported without reference to a specific OS; bug focuses on keyboard interaction * Bug 102058 - No screen reader notification that there is a comment Reported without reference to a specific OS; confirmed on Linux with Orca (until 2018). * Bug 106180 - No screen reader notification that there is a comment Reported without reference to a specific OS (but split off from bug 102058); confirmed on Linux with Orca (2018). * Bug 135439 - Accessibility: No output from screenreader when adding a comment in Writer Reported for Windows (with unidentified screen reader); confirmed on Linux and repeatedly on Windows. Based on the above reports, the bug seems to be caused by two issues: (1) missing role information in the accessibility API (see issues 92389, 102058, 106180 and 135439) and (2) the absence of keyboard accessibility (originally reported in 99261 and contradicted there, but see my findings below). My findings regarding keyboard access are the following: In LibreOffice Writer, you can indeed insert a comment using either the shortcuts Crtl + Alt + C or through the menu items Insert -> Comment; you can get out of the comment using Esc. However, editing an existing comment later on appears to be impossible: you can browse the list of existing comments in the Navigator, but pressing Enter on a specific comment takes you to the document's text, not to the comment. (In LibreOffice Calc, you can open an existing comment again when you press Shift + F10 to open the cell's context menu and then choosing "Edit comment". This does not work in Writer or Impress. In addition, you exit a comment in Writer or Calc by pressing Esc, whereas this does not seem to work in Impress, where I use F6.) I am not 100% certain what the exposed accessibility role should be; the closest match seems to be IA2_ROLE_NOTE in IAccessible2 and ROLE_COMMENT in ATK/AT-SPI. See the "Role Mapping Table" in "Core Accessibility API Mappings 1.1" at https://www.w3.org/TR/core-aam-1.1/#mapping_role_table Question: Linux, Windows and Mac OS use different accessibility APIs. Should there be just one open bug for this issue in spite of this? Or one for the Windows version and one for Linux (and perhaps another one for Mac OS)? -- You are receiving this mail because: You are the assignee for the bug.
