Skip to main content
MelMelMelMel
Participant
May 28, 2026
Question

Acrobat accessibility character encoding fail on certain languages, eg Punjabi, Thai, Khmer

  • May 28, 2026
  • 2 replies
  • 37 views

At the agency where I work, we create a lot of PDFs from Indesign that are in other languages. When I use the accessibility checker on these in Acrobat, I've been having a character encoding fail on several languages. They seem to all be ones where the characters include little flourishes either below or above the character – so like Punjabi, or Thai, or Khmer. Typically we use Noto Sans from Google, so it’s definitely unicode, and of course we are using the world-ready composer, and exporting with the correct language assigned. All that required stuff. It’s not solving this.

Does anyone have any suggestions?

    2 replies

    Meenakshi0101
    Community Manager
    Community Manager
    June 1, 2026

    Hi MelMelMelMel,

     

    Thank you for sharing the information and recording.

    Please allow us some time to check this, and we will share our findings.

     

    Thanks,

    Meenakshi

    Meenakshi0101
    Community Manager
    Community Manager
    May 28, 2026

    Hi MelMelMelMel,


    Thank you for reaching out, and sorry for the trouble caused.


    As mentioned, the issue occurs with specific languages. Could you please share the following information so we can share it with the team to check this further:

    • Share the sample PDF 

    • Acrobat version number.

    • OS used on the machine

    • Share the screen recording of what happens when you run the accessibility checker. 

    Let us know if you have any questions or need help.


    Thanks,

    Meenakshi

    MelMelMelMel
    Participant
    May 31, 2026

    Thanks for reaching out ​@Meenakshi0101 

    I’ve recreated this issue in a separate document, since the original is government work and I can’t share it.

    I’m using InDesign 21.2 to create the source document and exporting as an Interactive PDF (although the same thing happens if I export as a non-interactive PDF).

    I’m on MacOS 26.4

    PDF and screen recording are attached.

     

    Thanks!