Other PDF Issues

How to Fix Character Encoding Errors in Accessible ArcGIS PDFs

Aamir Naveed AkramAamir Naveed Akram Nov 3, 2026 869 views

Question details

The user needs to resolve character encoding errors flagged by PDF accessibility checkers in documents generated from ESRI ArcGIS.

How to Fix Character Encoding Errors in Accessible ArcGIS PDFs
Product
PDF / ESRI ArcGIS
Device & OS
not provided
Scenario
Running an accessibility check on a PDF document containing maps or graphics exported from ESRI ArcGIS.
Observed behavior
The accessibility checker reports character encoding errors due to missing embedded fonts, non-Unicode fonts, or incorrect glyph mappings.
Before you start

Ensure you have access to the original ESRI ArcGIS source files or can contact the map creation team, as these encoding errors must primarily be resolved during the initial export phase.

Solution 1Recommended

Adjust ESRI ArcGIS PDF Export Settings

Fix the encoding issue at the source by ensuring all fonts are embedded and utilize Unicode formatting during the ArcGIS export process.

PDF/UA compliance requires Unicode fonts so that glyphs can be accurately interpreted by assistive technologies. If standard or non-Unicode fonts are used without embedding, the accessibility checker will report encoding errors.

1
Verify Font Usage in ArcGIS

Open the map project in ESRI ArcGIS and ensure that Unicode or OpenType fonts are applied to all map text and symbols.

2
Access Export Settings

Navigate to the export or share menu within ArcGIS to generate the PDF.

3
Enable Font Embedding

Locate the font settings within the export dialog and check the option to 'Embed All Fonts' or 'Embed subsetted fonts'.

4
Export Directly to PDF

Complete the export process directly through the software's native PDF export tool rather than using a 'Print to PDF' virtual printer, which typically strips out accessibility structures.

Adjust ESRI ArcGIS PDF Export Settings
Direct Export Required: Always use the native export function. Virtual PDF printers create flattened files intended solely for physical printing and remove the tagging structure necessary for accessibility.

Manage and Combine PDFs Securely with WPS Office

While source encoding errors must be fixed within the ArcGIS application, WPS Office provides robust PDF management tools to combine your compliant files securely without losing document structure, tags, or embedded fonts.

  1. 1. Open WPS Office PDF: Launch WPS Office and navigate to the PDF module from the main dashboard.
  2. 2. Select Merge PDF: Click on the 'Merge PDF' tool under the 'Edit' or 'Tools' tab.
  3. 3. Combine Compliant Files: Add your pre-checked, accessible ArcGIS PDF files and click 'Merge' to generate a unified document that retains the original embedded fonts and structural layouts.
Merge multiple PDF documents while preserving original tags and formattingFully compatible with standard PDF structures and Microsoft Office formats (Word, Excel, PowerPoint)Lightweight, intuitive interface for fast PDF editing and readingComprehensive PDF toolkit available in a free, easy-to-use alternative
microsoft office alternative - wps office

Frequently Asked Questions

Why do character encoding errors occur in accessible PDFs?

These errors typically happen when a PDF is exported using standard or non-Unicode fonts, or when the fonts used in the document are not embedded during the creation process. Assistive technologies require embedded Unicode fonts to correctly map and read the document's characters.

Why shouldn't I use a virtual PDF printer to create accessible PDFs?

Virtual PDF printers (such as the 'Print to PDF' function) generate flattened files that are optimized strictly for physical printing. This process removes structural metadata, reading order tags, and formatting elements that are strictly required for PDF/UA accessibility compliance.

What does subsetting fonts mean during PDF export?

Font subsetting is a process where only the specific characters (glyphs) used within the document are embedded into the PDF file, rather than attaching the entire font family. This practice ensures exact text rendering and full accessibility compliance while keeping the overall file size manageable.