Table of Contents

PDF/UA-1 Accessibility Tagging (Preview)

The Report Designer includes early support for tagging generated PDFs as PDF/UA-1 (accessible/tagged PDF, ISO 14289-1) so screen readers and accessibility audits can consume them. This feature is not yet production-ready and its properties are hidden from the Designer property grid by default.

Why it's hidden

The tagging logic still has a known, unresolved compliance issue (a small number of marked-content items are not always linked into the PDF's structure tree correctly), and it has not yet been through a full end-to-end test against a real Business Central report. Until that work is finished, the properties are gated behind a registry setting so they can only be turned on deliberately, for testing.

Enabling the properties for testing

Set the following registry value on the machine running the Report Designer:

Key HKEY_LOCAL_MACHINE\SOFTWARE\ForNAV\Reports ForNAV\Design
Value name EnablePdfUA
Type REG_DWORD
Enabled 1
Disabled (default) 0, or the value not present at all

You can create it with reg add, run as Administrator:

reg add "HKLM\SOFTWARE\ForNAV\Reports ForNAV\Design" /v EnablePdfUA /t REG_DWORD /d 1 /f

To hide the properties again, either delete the value or set it back to 0:

reg delete "HKLM\SOFTWARE\ForNAV\Reports ForNAV\Design" /v EnablePdfUA /f

The Designer reads this value fresh each time the property grid is populated (it is not cached), but the grid itself is only rebuilt on selection changes, so restart the Report Designer after changing the value to be sure it takes effect everywhere.

Properties controlled by this setting

Property Applies to Purpose
PDF/UA Compliant (PdfUA1) Report Enables PDF/UA-1 tagging for the report's output. Values: None (default) / PdfUA1.
PDF/UA Tag (PdfUaTag) Text box / label controls Overrides the automatic heading/paragraph detection for a specific control. Values: Auto (default), Paragraph, H1-H6.
Alternate Description (AlternateDescription) Picture / image controls Alt text applied to the image's tag in the structure tree.

When the registry setting is off, these three properties are simply not shown in the property grid — they are not removed from the report definition, and a report that already has one of them set (for example from earlier testing) still serializes and renders exactly as before. The setting only controls whether they can be newly configured through the Designer UI.

Scope

This setting only affects what's visible in the Report Designer. It does not disable or gate the PDF/UA tagging logic itself at render time — a report XML that already specifies PdfUA1 will still be tagged when rendered, regardless of this registry value.