Description: Inserted audios & videos cannot be played with the screen reader because the player is not recognised as an object. Steps to Reproduce: 1. Open LibreOffice Writer 2. Insert 3. Media 4. Audio/Video 5. Select the desired audio or video file and insert it into Writer 6. Klick "open" to insert audio/video in Writer 7. A player is displayed in the document, but is not recognised by NVDA and therefore cannot be controlled Actual Results: The player displayed in the document cannot be controlled by NVDA Expected Results: The player is regocnised by NVDA and therefore controllable Reproducible: Always User Profile Reset: No Additional Info: Windows Edition Windows 10 Home Version 1909 Installed on 17.02.2020 Operating system build 18363.1016 LibreOffice Version: 7.0.2.2 (x64) Build ID: 8349ace3c3162073abd90d81fd06dcfb6b36b994 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded
I reproduced this bug using the following components: Libre Office: Version: 7.0.2.2 (x64) Build ID: 8349ace3c3162073abd90d81fd06dcfb6b36b994 Windows: Windows 10 Home Version 2004 Betriebssystembuild: 19041.572
The problem still exists. Even if you select the audio/video object in the document with the mouse, the associated ribbon cannot be operated with the arrow keys. Unfortunately, audio/video objects are not displayed in the navigator either. Windows Edition Windows 10 Home Version 20H2 Installed on 05.02.2021 Operating system build 19042.985 LibreOffice Version: 7.1.3.2 (x64) / LibreOffice Community Build ID: 47f78053abe362b9384784d31a6e56f8511eb1c1 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded
@Jürgen: For your interest, if you add the accessibility meta bug 101912 in the "Blocks" field in Bugzilla when creating accessibility-related tickets, people that are subscribed to the a11y meta bug will be notified automatically and the ticket will also show up when looking at the list of tickets in the meta bug. (There's also an "accessibility" keyword in addition that can be set in the "Keywords" field.)
Dear juergenkohler23, 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