Created attachment 70443 [details] File that demonstrates the effect when exported as PDF Problem description: In an exported PDF the description of an embedded OLE object is missing. Imported graphics as JPG or PNG view this description, also known as alternative text, are viewing this description. But using an OLE object created e.g. with Draw don't view their description. See attached file for an example. Steps to reproduce: 1. Create new document 2. Insert new Object, OLE Object, choose e.g. Libre Draw 3. Draw an image 4. Close Draw 5. Right mouse click on new image, choose "Description" in context menu 6. Write some description into text field 7. Export document as PDF 8. Open exported PDF with Acrobat reader 9. Focus image with mouse pointer Current behavior: Description of image is not viewed in exported PDF. Expected behavior: Description of image should be viewed as hover text when mouse pointer on it. Platform (if different from the browser): Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17
Created attachment 70444 [details] Exported PDF with missing description of OLE object
reproducible with LO 4.0.2.2 (Win7 Home, 64bit) Note: To reproduce it you need to select TAGGED PDF in the tab GENERAL of the menu FILE -> EXPORT AS PDF.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (4.4.1 or later) https://www.libreoffice.org/download/ *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
Dear funke.holger, 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 http://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 funke.holger, 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
New STR (because OP is ambiguous) 1. New Writer document. 2. Insert - Shape - Basic Shape - Rectangle 3. Insert - Shape - Line - Line 4. Insert - Shape - Line - Freeform Line 5. Insert - Object - Formula Object 6. Insert - Image , then (choose an image) 7. Insert - Chart 8. For each of the inserted objects, select, Format > Description, enter data for "Title" and "Description" 9. File > Export as > Export as PDF 10. Check "Universal Accessibility", then click "Export" 11. View exported PDF file in Adobe Reader Actual: In PDF file, cursor placed over image with mouse shows both Title and Description (OK), but for all Drawing Objects and Formula (OLE Object), Title and Description are not shown (NOK, as indicated in the OP). Tested with: Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 4ea44fdb19e568093ab1e0549c3ffa33296a486b CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: da-DK (da_DK); UI: en-US Calc: CL
*** Bug 149058 has been marked as a duplicate of this bug. ***
The duplicate in comment 7 has an attachment that conducts many of the same tests as described in comment 6, so that bug was made a duplicate of this bug. Meanwhile, the OP is ambiguous, because it seems to refer to Alternative Text and Description as the same thing, but the tests in comment 7 evaluate both Text Alternative and Description. => Bug summary is expanded. The expectation is that both Text Alternative (bug 148941) and Description will be shown in exported PDF (if they are available), for any embedded or linked object. But it seems relevant to ask explicitly if that is the intended/expected behavior.
*** Bug 101800 has been marked as a duplicate of this bug. ***
Armin did some work in this area in 2840352ba56a212d191cc16e08378c87672d7b73
Michael Stahl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/78681cd0829dcb6a73690e1a63ae3808d297677a tdf#57423 drawinglayer: PDF/UA export: more Alt texts for SdrObjects It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Michael Stahl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/122b4264d23df8b11419839ba700b88c4f936a6c tdf#57423 sw: PDF/UA export: Alt texts for SwNoTextNode It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
this should be fixed now in Writer for: * any SdrObject with Default "inventor" - not sure what the others are but they lack a structure element(StructureTagPrimitive2D)... * Writer images, embedded objects - these should obviously have alt text * Writer text frames - less obvious but you can set the alt text via Format->Description, while it's missing in the main properties dialog hopefully SdrObjects in other applications also get Alt text since the StructureTagPrimitive2D should be produced for these with the fix for bug 135638, haven't tested that...
Michael Stahl committed a patch related to this issue. It has been pushed to "libreoffice-7-4": https://git.libreoffice.org/core/commit/2b3fc2a2603f54e60ad16e81d112d30b204e9796 tdf#57423 drawinglayer: PDF/UA export: more Alt texts for SdrObjects It will be available in 7.4.4. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Michael Stahl committed a patch related to this issue. It has been pushed to "libreoffice-7-4": https://git.libreoffice.org/core/commit/0d59eebe858d0d3e5d2260691f245940757deacd tdf#57423 sw: PDF/UA export: Alt texts for SwNoTextNode It will be available in 7.4.4. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Created attachment 184762 [details] The example file exported to PDF in PAC tool Verified in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f1830bff71847a9c17715cff52383956719847fe CPU threads: 14; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: threaded Now there is no more "Alternative text missing for "Figure" structure element" error reported. There is only a warning Possibly inappropriate use of a "Figure" structure element still.
Did this enhancement affect how the alternative text is placed in to the PDF structure. I'm asking, because after upgrading from LO 7.4.3 to version 7.4.4, the Adobe Acrobat Accessibility checker reports "Associated with content" errors with images, in the alternative text check section. In my view, this enhancement is the most relevant alt-text change in the 7.4.4. version. See further details in my bug 155190 report. I would greatly appreciate you looking into this issue.
Thorsten Behrens committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/5351b8789805154219fe57b92b41b17c0e0cd765 related tdf#57423: make a11y checker accept image description too It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
If the last change was a respose to my preceding comment, this change did not unfortunately solve it. I did some more digging and realized that Acrobat tag structure viewer shows a small difference in the tag structure of the exported PDF files. LO 7.4.3 PDF export: <Document> <P> <Div> <Caption> Text: Figure Text: 1 Text: : Picture of apples <Figure> Image (10): w:226 h:226 <-- Missing after upgrade LO 7.4.4 !! LO 7.4.4 and later PDF exports shows the same structure, except the last line is missing!! I also tried the example files with a tool called ngPDF (https://ngpdf.com/loadFile), which can transform tagged pdf documents to html. This tool correctly transformed the LO 7.4.3 exported pdf file to html. However, when I tried it with a LO 7.4.4 exported PDF file, the resulting html file was missing the picture. I think this implies that there is indeed some problem in how the picture is attached to the tag structure and it is not just a problem with Acrobat. See further details in my bug 155190 report
*** Bug 143044 has been marked as a duplicate of this bug. ***