Guide
PAC 2024 errors explained: every failure and its fix
What each failing line in a PAC 2024 report means, the PDF/UA condition behind it, and how to fix it, from “Pages with annots have tab order S” to role maps.
About 8 minutes · quick
The whole table is also open data: JSON and CSV, every condition with its PAC 2024 and Acrobat names, free to reuse with attribution.
How to use this page
Find the line from your PAC 2024 report in the tables further down this page. Each row names the PDF/UA condition behind the line and links to its page: what is wrong in the file, what a screen reader does with it, and how to fix it free in Acrobat Pro. The last column says whether Taggart repairs it automatically, proposes a repair for your decision, or leaves it to you.
PAC’s detailed messages are taken from axes4’s help articles; its summary lines are written as people search for them and have not yet been compared with PAC itself. If the line in your report reads differently, search the tables for its key words — a role map, a tab order, a heading level — and tell us what it said, so the page can be corrected.
Only the lines this site already explains are here, which is a part of the 136 conditions in the Matterhorn Protocol. The list of every condition gives Taggart’s plain-language title for each of the rest.
What PAC passes that still fails people
A clean PAC report means the conditions software can decide have passed. Two kinds of failure get through it.
Text stored in visual order. Hebrew and Arabic PDFs from older systems often store each line reversed. The page looks right, and PAC accepts it, because no Matterhorn condition tests the order text is stored in. A screen reader then reads the line backwards. Right-to-left text stored in visual order explains the failure and how to find it with nothing but copy and paste.
The conditions only a person can decide. Forty-seven of the protocol’s conditions need human judgement: whether the tags are in the order a person reads the page (09-001), whether a custom tag is mapped to the right standard one (02-002), whether alt text says what an image is there for. PAC’s screen-reader preview helps a person judge the first. No checker can pass or fail any of them for you, and that includes Taggart.
When PAC and Acrobat disagree
They are different lists. Acrobat’s Full Check runs 32 rules of its own, tests some things PDF/UA does not require, and misses many of the Matterhorn conditions PAC tests. When a line appears in one report and not in the other, look up both: Acrobat’s accessibility checker, rule by rule does for Acrobat what this page does for PAC.
We have not yet cross-checked Taggart against PAC either. Where the two disagree about a file, read both findings, and tell us — that is how the comparison gets done.
Then fix the file
Taggart checks the same file free, with no account needed up to 60 pages, and with a free account it runs its repairs on your file so you can see what they change: check a PDF free.
PAC 2024: PDF/UA › Alternative text
| The line in the report | Condition | What it means | Taggart’s fix |
|---|---|---|---|
| Form field has TU key | 28-005: A form field has neither a TU entry nor an alternative description | The /TU tooltip is the accessible name of a PDF form field. Without it the field has no name at all — the visible label printed next to it is not connected to the control. | Proposed for your decision |
PAC 2024: PDF/UA › Annotations
| The line in the report | Condition | What it means | Taggart’s fix |
|---|---|---|---|
| Widget annotations in Form tag | 28-010: A widget annotation is not nested within a Form tag | Every form control must sit inside a Form structure element. | Applied automatically |
| Link annotations in Link tag | 28-011: A link annotation is not nested within a Link tag | A link annotation must be a child of a Link structure element containing the link's text, joined by an object reference (/OBJR). | Proposed for your decision |
PAC 2024: PDF/UA › Content
| The line in the report | Condition | What it means | Taggart’s fix |
|---|---|---|---|
| No tagged content in artifact | 01-004: Tagged content is present inside content marked as Artifact | A marked-content sequence for real content has been opened inside an open artifact sequence. The artifact swallows the real content. | Applied automatically |
PAC 2024: PDF/UA › Document settings
| The line in the report | Condition | What it means | Taggart’s fix |
|---|---|---|---|
| Pages with annots have tab order S | 28-008: A page containing an annotation does not contain a Tabs entry | Any page carrying annotations must declare a tab order. PDF/UA-1 requires /Tabs /S — tab order follows the structure tree. | Applied automatically |
| Pages with annots have tab order S | 28-009: A page containing an annotation has a Tabs entry with a value other than S | /Tabs is present but set to /R (row order) or /C (column order) rather than /S (structure order). | Applied automatically |
PAC 2024: PDF/UA › Headings
| The line in the report | Condition | What it means | Taggart’s fix |
|---|---|---|---|
| First heading is H1 | 14-002: First heading tag is not H1 | The document uses numbered headings (H1–H6) but the first one encountered in the structure tree is not an H1. | Applied automatically |
| No headings skipped | 14-003: Numbered heading levels in descending sequence are skipped | The heading hierarchy jumps a level going down — H1 straight to H3. Going back up any number of levels is fine; going down must be one level at a time. | Applied automatically |
PAC 2024: PDF/UA › Metadata
| The line in the report | Condition | What it means | Taggart’s fix |
|---|---|---|---|
| Document contains title | 06-003: XMP metadata stream does not contain dc:title | The Dublin Core title property is missing from the XMP packet. | Proposed for your decision |
PAC 2024: PDF/UA › Role map
| The line in the report | Condition | What it means | Taggart’s fix |
|---|---|---|---|
| Non-standard structure type is remapped | 02-001: Non-standard tag mapping does not terminate with a standard type | A custom tag name is present in the role map but the chain of mappings never arrives at a structure type defined in ISO 32000-1, 14.8.4. Mapping may be indirect — a custom type may map to another custom type — but it must eventually terminate. | Applied automatically |
PAC 2024: Detailed results
| The line in the report | Condition | What it means | Taggart’s fix |
|---|---|---|---|
| Artifact present inside tagged content | 01-003: Content marked as Artifact is present inside tagged content | A BMC/BDC artifact sequence has been opened while a marked-content sequence for real content is still open. Artifacts and real content may not be nested inside one another. | Applied automatically |
| Tagged content present inside an Artifact | 01-004: Tagged content is present inside content marked as Artifact | A marked-content sequence for real content has been opened inside an open artifact sequence. The artifact swallows the real content. | Applied automatically |
| Non-standard structure type "…" is neither mapped to a standard structure type nor to another non-standard structure type | 02-001: Non-standard tag mapping does not terminate with a standard type | A custom tag name is present in the role map but the chain of mappings never arrives at a structure type defined in ISO 32000-1, 14.8.4. Mapping may be indirect — a custom type may map to another custom type — but it must eventually terminate. | Applied automatically |
| Structure type "…" is mapped in a circular fashion | 02-003: A circular mapping exists | The role map contains a cycle: A maps to B, B maps back to A. Resolution never terminates. | Applied automatically |
| Standard structure type "…" is remapped to "…" | 02-004: One or more standard types are remapped | A standard structure type appears as a key in the role map — for example /P mapped to /Span. Standard types must never be remapped; doing so redefines the vocabulary the whole file depends on. | Applied automatically |
| First heading is not on the first level | 14-002: First heading tag is not H1 | The document uses numbered headings (H1–H6) but the first one encountered in the structure tree is not an H1. | Applied automatically |
| Numbered heading skips one or more heading levels | 14-003: Numbered heading levels in descending sequence are skipped | The heading hierarchy jumps a level going down — H1 straight to H3. Going back up any number of levels is fine; going down must be one level at a time. | Applied automatically |
| Alternate field name entry missing in form field | 28-005: A form field has neither a TU entry nor an alternative description | The /TU tooltip is the accessible name of a PDF form field. Without it the field has no name at all — the visible label printed next to it is not connected to the control. | Proposed for your decision |
| Tab order entry in page with annotations not set to S | 28-008: A page containing an annotation does not contain a Tabs entry | Any page carrying annotations must declare a tab order. PDF/UA-1 requires /Tabs /S — tab order follows the structure tree. | Applied automatically |
| Tab order entry in page with annotations not set to S | 28-009: A page containing an annotation has a Tabs entry with a value other than S | /Tabs is present but set to /R (row order) or /C (column order) rather than /S (structure order). | Applied automatically |
| Widget annotation not nested inside a Form structure element | 28-010: A widget annotation is not nested within a Form tag | Every form control must sit inside a Form structure element. | Applied automatically |
| Link annotation is not nested inside a Link structure element | 28-011: A link annotation is not nested within a Link tag | A link annotation must be a child of a Link structure element containing the link's text, joined by an object reference (/OBJR). | Proposed for your decision |
Frequently asked questions
Is PAC 2024 free?
Yes. PAC 2024 is free of charge, from axes4. It checks and fixes nothing, and its screen-reader preview, which shows the text in the order a reader would announce it, is the part most worth opening.
Does PAC run on a Mac?
No, PAC is Windows-only. On a Mac, axesCheck, the free browser checker from PAC's makers, runs the same kind of checks; veraPDF is cross-platform, free and open source, and covers the same PDF/UA-1 clauses; and Taggart's validator runs in any browser. Between them you can get an independent second opinion without a virtual machine.
Related guides
- Acrobat accessibility checker: every rule explainedWhat each of the 32 rules in Acrobat's Full Check means, which PDF/UA condition it matches, and how to fix it — from Tab order failed to Logical Reading Order.
- How to check if a PDF is accessible: four free checkersCheck PDF accessibility free, online or on your own machine: four checkers against PDF/UA and WCAG, what each catches, and the failures none of them see.
- How to fix PDF reading orderA working method for finding and repairing reading order, free in Acrobat and faster in Taggart, including the two-column case that costs the most time.
Related failure conditions
- 01-003 Content marked as Artifact is present inside tagged contentA BMC/BDC artifact sequence has been opened while a marked-content sequence for real content is still open. Artifacts and real content may not be nested inside one another.
- 01-004 Tagged content is present inside content marked as ArtifactA marked-content sequence for real content has been opened inside an open artifact sequence. The artifact swallows the real content.
- 02-001 Non-standard tag mapping does not terminate with a standard typeA custom tag name is present in the role map but the chain of mappings never arrives at a structure type defined in ISO 32000-1, 14.8.4. Mapping may be indirect — a custom type may map to another custom type — but it must eventually terminate.
- 02-003 A circular mapping existsThe role map contains a cycle: A maps to B, B maps back to A. Resolution never terminates.
- 02-004 One or more standard types are remappedA standard structure type appears as a key in the role map — for example /P mapped to /Span. Standard types must never be remapped; doing so redefines the vocabulary the whole file depends on.
- 06-003 XMP metadata stream does not contain dc:titleThe Dublin Core title property is missing from the XMP packet.
- 14-002 First heading tag is not H1The document uses numbered headings (H1–H6) but the first one encountered in the structure tree is not an H1.
- 14-003 Numbered heading levels in descending sequence are skippedThe heading hierarchy jumps a level going down — H1 straight to H3. Going back up any number of levels is fine; going down must be one level at a time.
- 28-005 A form field has neither a TU entry nor an alternative descriptionThe /TU tooltip is the accessible name of a PDF form field. Without it the field has no name at all — the visible label printed next to it is not connected to the control.
- 28-008 A page containing an annotation does not contain a Tabs entryAny page carrying annotations must declare a tab order. PDF/UA-1 requires /Tabs /S — tab order follows the structure tree.
- 28-009 A page containing an annotation has a Tabs entry with a value other than S/Tabs is present but set to /R (row order) or /C (column order) rather than /S (structure order).
- 28-010 A widget annotation is not nested within a Form tagEvery form control must sit inside a Form structure element.
- 28-011 A link annotation is not nested within a Link tagA link annotation must be a child of a Link structure element containing the link's text, joined by an object reference (/OBJR).
Check your own file. Taggart's validator is free and unlimited — no page cap, no watermark, and no account at all up to 60 pages. To repair a file rather than check it, see how Taggart’s repairs work.
Last updated .