Guide
Hebrew PDF accessibility: the three failures that matter
Visual-order storage, wrong document language, and left-to-right column order. All three are invisible to a sighted reviewer and to every mainstream checker.
About 14 minutes · involved
Three failures, all invisible
Hebrew documents fail in ways that Latin-script documents cannot, and all three are invisible to somebody looking at the page.
1. Text stored in visual order
A PDF paints glyphs at coordinates and has no notion of direction. A correct producer stores Hebrew in logical order and paints it right to left. A visual-order producer reverses the characters first and paints them left to right.
The page is identical. The stored text is the sentence backwards.
logical הנגשת מסמכים דיגיטליים היא חובה חוקית בישראל
visual לארשיב תיקוח הבוח איה םיילטיגיד םיכמסמ תשגנהA screen reader applies the bidi algorithm to the second line and reverses it again. The result is neither.
Test it: copy a line and paste it into a plain text editor. Ten seconds. Full explanation →
2. Document language left at en-US
Producers default to English. Nobody changes it, because nothing on screen looks wrong.
An English synthesiser has no phonemes for Hebrew. The reader spells the letters, or falls silent. This is not accented Hebrew — it is nothing.
Test it: File → Properties → Advanced → Reading Options → Language. If it says English on a Hebrew document, that is the bug. Fix →
3. Columns ordered left to right
Auto-tagging tools sweep the page left to right regardless of script. In a Hebrew two-column layout the correct order is right column first, so the document is tagged as two interleaved halves.
Test it: read the document with a screen reader, or open the Tags panel and check which column comes first. Fix →
What you can do free
Detect all three. Copy-paste for visual order, File Properties for language, and the Tags panel for column order. All free, all in Acrobat or any viewer.
Fix the language. File → Properties → Advanced → Reading Options → Language. Thirty seconds.
Fix the column order. Drag tags in the Tags panel. Slow, but free.
Fix visual order. You cannot. There is no setting in Acrobat that converts visual-order storage to logical order, because Acrobat has no notion that the stored order might be wrong. The free options are to re-export from a source document with a modern producer, or — if the file came from a government portal and the source is gone — nothing.
What Taggart does
Detects visual order structurally, by comparing the order glyphs are painted in against their positions on the page, corroborated by Hebrew final-letter morphology, with a confidence and the reasoning attached to every finding.
Repairs it by attaching logical-order /ActualText without touching the content stream, so the page renders pixel-identically.
Sets per-run /Lang at the same time, including for English passages inside a Hebrew document, which fail in exactly the same way in reverse.
Evaluates reading order with the document’s primary script in mind, so a right-to-left two-column page is judged right column first.
And offers IS 5568 as a selectable profile alongside PDF/UA-1 and WCAG 2.1 AA. About IS 5568 →
Frequently asked questions
How do I test a Hebrew PDF in ten seconds?
Select a line of Hebrew, copy it, and paste it into a plain text editor that does not reorder text. If it comes out backwards, the file stores text in visual order. That single test catches the most damaging failure in the Israeli document corpus.
Why does the file pass every checker?
Because checkers ask whether text can be mapped to Unicode, not whether the characters are in the order a human wrote them. PAC, veraPDF and Acrobat all pass a visual-order Hebrew document with clean tagging.
Can this be fixed without changing the page?
Yes. The repair attaches the logical-order string as /ActualText on the structure element, which replaces the content for extraction while the painted glyphs stay exactly as they were. The remediated file renders pixel-identically.
Related failure conditions
- TG-RTL-001 Right-to-left text is stored in visual order Older Israeli government, legal and DTP systems lay out Hebrew by reversing the character order and then rendering left-to-right. The page looks correct, but the stored text is backwards. Extracting it gives you the sentence mirrored, and the bidi algorithm then reverses it a second time.
- TG-RTL-002 A right-to-left run has no language declaration The document declares en-US at the catalog and never overrides it, so Hebrew paragraphs inherit English.
- TG-RTL-004 Reading order is not right-to-left aware Auto-tagging tools order blocks left-to-right, top-to-bottom. In a Hebrew two-column layout the correct order is right column first.
- 11-007 Natural language is not appropriate A language is declared but it is the wrong one — a Hebrew document declared en-US, or an English abstract inside a Hebrew paper inheriting he-IL.
Check your own file. Taggart's validator is free and unlimited — no page cap, no watermark, no account.
Last updated .