Bug 163272 - LibreOffice Writer -> Export As -> Export as PDF -> Universal Accessibility (PDF/UA) Tagging issue
Summary: LibreOffice Writer -> Export As -> Export as PDF -> Universal Accessibility (...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
24.8.2.1 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: PDF-Export
  Show dependency tree / graph
 
Reported: 2024-10-03 15:19 UTC by Poornachandra
Modified: 2025-02-27 06:15 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Poornachandra 2024-10-03 15:19:35 UTC 
Description:
1.Footer and Header data should be tagged with corresponding tags instead of artifacts
2.Tagging the single link with data spanning across the lines as a single link instead of multiple link tags
3.Though Nirmala UI and Khmer UI are Unicode fonts, they are not being encoded properly, which may result in data loss.
4.Tagging the language of the paragraph in the <p> tag instead of <span> tag
5.Require additional languages such as Samoan, Ilocano, Chinese etc. to be added in the Languages for Proofing in LibreOffice Writer.


Steps to Reproduce:
1.Create an accessible .docx file with all the header, footer, letter body with accessible links and phone numbers.
2.Open the above created .docx file with LibreOffice Writer and in File -> Export As -> Export as PDF -> Check Universal Accessibility (PDF/UA) -> Export
3.An accesible PDF file would be generated with the above reported issues, which can be verified through Adobe accessibility check and accessibility tags 

Actual Results:
Accessible PDF produced does not have the Footer and Header tagged.
Any accessible link with data spanning across the lines are getting tagged twice.
Any content using Nirmala UI and Khmer UI fonts which are Unicode fonts are not being encoded properly, which results in data loss.
language of the paragraph gets tagged in the <span> tag instead of <p> tag.
No languages such as Samoan, Ilocano, Chinese etc are available in language proofing.

Expected Results:
Accessible PDF produced should have the Footer and Header tagged with Footer and Header tags.
Any accessible link with data spanning across the lines should be getting tagged only once in a single link tag.
Any content using Nirmala UI and Khmer UI fonts which are Unicode fonts should be encoded properly, which results in data loss.
language of the paragraph should get tagged in the <p> tag instead of <span> tag.
languages such as Samoan, Ilocano, Chinese etc should be available in language proofing.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 24.8.2.1 (X86_64) / LibreOffice Community

Build ID: 0f794b6e29741098670a3b95d60478a65d05ef13

CPU threads: 2; OS: Windows 10 X86_64 (10.0 build 14393); UI render: Skia/Raster; VCL: win

Locale: en-US (en_US); UI: en-US

Calc: threaded