Description: Michel Such, a prominent contributor to the French translation of NVDA, an open source screenreader, has reported to us (via the LibreOfficeFR Twitter account) an issue with the accessibility of the LibreOffice extension manager. Usually when we are in a dialog box, a screen reader like NVDA is reading aloud the name of the control, its type (button, textarea, etc.) and the state of the control (checked, unchecked, radio selected, etc.). This happens each time the user presses the Tab key. The extension manager has different controls: one to check for extensions updates, one control to add an extension and check boxes to choose which type of extension we want to display. The issue we have here is that even if we ask the screen reader to read aloud all controls of this extension manager dialog box, the control corresponding to the list of installed extensions is not found. In practice, this list should be found and we should be able to move up/down in this list using the keyboard arrow to choose a specific extension we want to control (disable/enable/remove). An example we should take inspiration on is the extension manager of the Thunderbird mail client whose accessibility is working nicely. Steps to Reproduce: 1. Install a screenreader like NVDA on Windows 10 2. Open the extension manager 3. Read the controls 4. Realize the extension list is not detected properly. Actual Results: The extension list is not detected properly/read aloud Expected Results: The extension list detected properly/read aloud and being able to navigate using arrows easily. Reproducible: Always User Profile Reset: No Additional Info:
We asked the reported for more clarifications. We want to know whether the extension manager of Thunderbird he was referring to was the one we currently have with the current version of Thunderbird (the web based version) or if he was referring to an old version of Thunderbird using a dedicated dialog box (similar to what we currently have with LibreOffice).
Confimred on Windows 10 Home with NVDA 2019.1 and recent master 6.4.0alpha1 build Version: 6.3.0.4 (x64) Build ID: 057fc023c990d676a43019934386b85b21a9ee99 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded Though the Extension Manager's dialog controls are assigned accessible events and all sound in AT, the list box of extensions is not being assigned accessible events when built. And, unfortunately the list entries are also not exposed to NVDA's object navigation. Suspect it will be the same for ORCA use. Claiming implementation error in that we are omitting accessible events where they are clearly needed for AT. @Caolán, seems similar to the tree view of expert config stanzas (bug 99609)--and of equal impact on UX when dependent on AT. Is there an efficient way to expose elements of these list items to AT?
Created attachment 153719 [details] Thunderbird Extension page What the the bug reporter (Michel) meant by extension page of Thunderbird
Created attachment 153720 [details] Thunderbird activity manager dialog Contrary to the extension page, the activity manager of Thunderbird is what is the most comparable to our extension manager dialogs. The activity manager seems to be properly accessible as well.
Created attachment 153735 [details] LibreOffice dictionary lists For the record, and like specified by Michel on Twitter, the lists we have in the LibreOffice options to choose which dictionary we want to enable and their options, are lists that are properly accessible via screen readers.
What version of LibreOffice was the report against ? Is it a regression against some version where it did work, or is it the case it never worked ?
Hi Caolan, I'm reporting against master, no specific version in mind. According to Michel, this is a problem that has been persistent from the very first moment he tested LibreOffice back in the days of the 5.x release. He assumes this never worked properly actually. But I confirm the importance of such an issue. We had several blind people at the last hackfest organized by the French community and the dialog box of the extension manager has been mentioned several times to have accessibility issues, like this one.
So this isn't a regression IMHO.
[Automated Action] NeedInfo-To-Unconfirmed
Hello, I'm the original reporter of this a11y problem, and I confirm it still exists.
is it related to bug 126935 ?
Hi Xisco, It depends what you mean by related. While this is related to accessibility, this isn't related to the "Area containing context of error" like described at bug 126935. We are speaking of a list area containing items here, not some sort of tooltips like 126935.
I confirm that the issue still exists on: Version: 7.0.0.0.alpha0+ Build ID: e4ee4c5abfbdea48ddcf946f23e3d582ad8e669e CPU threads: 16; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded The screen-reader (orca) only reads "drawing area" for the extensions list.
Dear William Gathoye, 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
Still reproducible in current master, and also on Linux. Looking at the a11y tree in accerciser, there's no a11y representation of the extensions (items in the extension list), just a single unnamed object for the whole pane that contains the items. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1b1a2031140029f6f6d90634edd1e509adc8b1da CPU threads: 12; OS: Linux 6.1; UI render: default; VCL: qt6 (qfont+xcb) Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded
There's also an issue in NVDA's issue tracker: https://github.com/nvaccess/nvda/issues/651 (But this clearly looks like a LO bug.)