Description: Requirement accessebility: Provide hyperlinks with speaking text. PDF export does not recognize the alternative description. Checking tool: Alternative descriptions for annotations - Annotation without alternative description. Steps to Reproduce: 1.Create a hyperlink in a document with a alternate description: Text: "I love Schleswig-Holstein" , Strg K: insert LINK www.schleswig-holstein.de 2.export the document to pdf 3.Check assebility with PAC 3 (Windows): 4. Result: Annotation without alternative description. Actual Results: Check the Assebility wirh PAC 3, Result: red message (error) : Page with one hyperlink with alternative description and one hyperlink without alternative description Expected Results: no error to hyperlink with descriptive text Reproducible: Always User Profile Reset: No Additional Info: the software don't recognize the descriptive text
Thank you for reporting the bug. I can not reproduce the bug in Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nb-NO (en_US); UI: en-US Calc: CL Version: 7.2.0.0.alpha0+ (x64) Build ID: 761a672d62df1891b9f4f367a499b220ab2b33fa CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
Hello Susanne, a new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
I tested in LO 7.0 and 7.4+ and really it was as reported so I put to New. But it's not all clear. How do you create a hyperlink in a document with an alternate description? URL has Text, isn't it enough? If not, LO has no further fields for Alt Text on link.
It seems PAC 3 here is behaving in a silly way and it would be harmful to uncritically follow its advice. See this for one discussion: https://community.adobe.com/t5/acrobat-discussions/alternative-description-missing-for-annotation-table-of-contents/m-p/10217239 Please think of the value that implementing this request would provide. To comply with PAC 3's demands, LibreOffice would have to duplicate the link text by default in the alternative description. It would just be redundant data. World Wide Web Consortium writes: https://www.w3.org/TR/WCAG20-TECHS/PDF13.html "The objective of this technique is to provide replacement link text via the /Alt entry in the property list for a tag. This is usually not necessary, but in some situations, additional information beyond the visible link text is needed, particularly for screen reader users." Pay attention to "usually not necessary".
Well, bug 148934 comment 3 says > The issue is purely about PDF/UA compliance, which requires a text alternative for links. (It's ridiculous, but that's what the standard requires.) So I guess there is no other way.
Code pointers, using alt text for images: vcl/source/gdi/pdfwriter_impl.cxx void PDFWriterImpl::setAlternateText( const OUString& rText ) drawinglayer/source/processor2d/vclmetafileprocessor2d.cxx // Create image alternative description from ObjectInfoPrimitive2D info // for PDF export
(In reply to Buovjaga from comment #6) > Code pointers, using alt text for images: > > vcl/source/gdi/pdfwriter_impl.cxx > void PDFWriterImpl::setAlternateText( const OUString& rText ) > > drawinglayer/source/processor2d/vclmetafileprocessor2d.cxx > // Create image alternative description from ObjectInfoPrimitive2D info > // for PDF export The code is there https://opengrok.libreoffice.org/xref/core/vcl/source/gdi/pdfwriter_impl.cxx?r=e39ea45c#2103 but m_aAltText is always empty
(In reply to Xisco Faulí from comment #7) > but m_aAltText is always empty Sorry, this is not true
As Buovjaga pointed out in Comment 5, this is an issue of PDF/UA compliance. (And Bug 148934 is related to this.) The relevant requirement in ISO 14289-1 (the PDF/UA specification) is section 7.18.5, which says, "Links shall contain an alternate description via their Contents key as described in ISO 32000-1:2008, 14.9.3." Appendix D.2 Hyperlink Titles in ODF 1.3 Part 3 says, "When transforming from another document format to OpenDocument the alt text of hyperlinks, shall be mapped to the office:title attribute of <text:a> 6.1.8 elements or <draw:a> 10.4.12 elements. When exporting OpenDocument documents to HTML, the contents of title text should be mapped to title attribute text on HTML anchor tags. As a minimum, authoring tools should provide a mechanism to provide the hint text." See also subchapter 19.387 office:title, in the ODF spec: "The office:title attribute specifies a short accessible description." Note that the LibreOffice UI currently has no mechanism to set a Hyperlink's alt text or what the ODF spec calls the "hint text". The Hyperlink dialog has a Name field, but that maps to the attribute office:name of the text:a element. "office:name" serves as a target for other hyperlinks, so it is not the right mechanism for the hint text. The goal of implementing this would be to come closer to PDF/UA compliance. Creating PDF/UA-compliant documents is currently almost impossible without expensive additional tools (e.g. Adobe Acrobat Pro, the Axes4 plugins for MS Office or the CommonLook plugins for MS Office), none of which are available for Linux. One way to do this is to add a "Text alternative" field to this Hyperlink dialog which is automatically filled in with the actual link text. This would help both authors who don't know much about accessibility and those who would want to define a different alt text. The Accessibility Checker should check that links have a text alternative that is not simply a full URL. Sidenote: The Hyperlink or Link dialog in Microsoft Word 2016 has a "Tooltip..." button ("QuickInfo..." in the German version) that allows the author to define a tooltip, but this is ignored when the DOCX file is exported to PDF. (It is not obvious whether that mapping would even be correct, but it's all MS Word has to offer in this regard.)
Created attachment 184119 [details] Example file in PAC3 I think we can consider this one fixed - this is attachment 183711 [details] from bug 151826 opened in PAC3 tool - no issue whatsoever, after the fixing of bug 148934.