How to Fix Headers Failed in PDF Accessibility (w/Examples) + FAQs

Yes, you can fix a “Headers Failed” error in a PDF accessibility report, and the fix almost always comes down to adding proper heading tags, correcting the nesting order, and making sure every visual heading is also a tagged heading in the document structure. When Adobe Acrobat’s Accessibility Full Check flags “Headings – Appropriate nesting” or the PDF Accessibility Checker (PAC 2024) returns a Matterhorn Protocol 14-003 failure, the PDF is telling you that screen readers cannot follow the document’s outline. That failure is not cosmetic, and it is not optional under U.S. law.

The governing rules come from the Americans with Disabilities Act Title II final rule published by the Department of Justice on April 24, 2024, which adopts WCAG 2.1 Level AA as the binding technical standard for state and local government web content and PDFs. Private businesses face parallel exposure under ADA Title III, and federal agencies and contractors must meet the Section 508 Revised Standards at 36 CFR Part 1194. A single untagged heading can trigger a demand letter, a DOJ investigation, or a lawsuit, and the immediate consequence is that blind and low-vision users cannot navigate the document at all.

According to the 2024 WebAIM PDF Accessibility Report, 77.1% of the top one million home pages had detectable WCAG failures, and heading-structure errors were among the three most common issues in linked PDFs. Here is what you will learn in this guide:

• 📑 How to identify every flavor of “Headers Failed” error across Acrobat, PAC, and CommonLook.
• ⚖️ Which federal and state laws turn a heading failure into legal liability.
• 🛠️ Step-by-step remediation inside Acrobat Pro, Word, InDesign, and LaTeX.
• 👥 Three named real-world scenarios that show fixes in action.
• ❓ Ten plain-English FAQs that close the loop on edge cases and enforcement.

What “Headers Failed” Actually Means in a PDF Accessibility Report

The phrase “Headers Failed” is shorthand for a family of related errors that all point to broken document structure. In Adobe Acrobat Pro’s Accessibility Checker, the rule is literally named Appropriate nesting, and it lives under the Headings category. In PAC 2024, the same concept maps to Matterhorn Protocol checkpoints 14-001, 14-002, 14-003, and related 09-series checks for tagged structure. The failure means the PDF’s logical tree does not match what a sighted reader sees on the page.

Screen readers such as JAWS, NVDA, and VoiceOver rely on the heading tree to let users press the H key and jump between sections. When the tree is missing, skips from H1 to H3, or marks bold body text as a heading, navigation collapses. The consequence is not a warning; it is a blocker that forces users to read every word linearly or abandon the document.

A common misconception is that making text look like a heading by bolding it at 18 points is enough. It is not. The PDF must contain an actual /H1, /H2, or /H3 structure element in the tag tree, and that tag must appear in the correct order. Without the tag, the heading is invisible to assistive technology, and the Full Check will fail every single time.

The Four Most Common “Headers Failed” Variants

Each flavor of the error points to a different underlying defect in the tag tree. Understanding which variant you are looking at tells you exactly which fix to apply. The four variants below cover roughly 95% of what remediators see in the field, based on published guidance from the U.S. Access Board and the PDF Association.

• Missing H1: the document has no top-level heading, violating WCAG 2.4.6 Headings and Labels.
• Skipped levels: the document jumps from H1 directly to H3, breaking Matterhorn 14-003.
• Visual-only headings: bold text is not tagged, violating WCAG 1.3.1 Info and Relationships.
• Wrong-tag headings: body text is tagged as a heading, which also violates 1.3.1 and confuses screen reader users.

Why Acrobat and PAC Sometimes Disagree

Acrobat’s built-in checker is less strict than PAC 2024, and a PDF can pass Acrobat while still failing PAC and the Matterhorn Protocol. Acrobat only verifies that at least one heading exists and that nesting does not skip; it does not enforce the full PDF/UA (ISO 14289-1) rule that every heading must match the visual hierarchy. PAC runs all 136 Matterhorn checkpoints and will flag issues Acrobat silently ignores.

The practical consequence is that passing Acrobat alone is not a safe legal defense. Federal agencies under Section 508.gov guidance are advised to run both tools. A real-world example is a county tax form that passed Acrobat’s Full Check but failed PAC because three section titles were tagged as paragraphs, not headings, and the county later received a complaint letter from a resident using JAWS.

The Legal Framework Behind Heading Failures

Heading errors are not just a technical annoyance; they sit at the center of federal disability law. The ADA Title II final rule at 28 CFR §35.200 requires state and local governments to meet WCAG 2.1 Level AA by April 24, 2026 for jurisdictions of 50,000 or more residents, and by April 24, 2027 for smaller jurisdictions and special district governments. WCAG 2.1 AA includes Success Criterion 1.3.1 and 2.4.6, both of which govern heading structure.

Private businesses face parallel exposure under ADA Title III, where courts have repeatedly held that inaccessible web content and PDFs violate the statute. In Robles v. Domino’s Pizza, LLC, 913 F.3d 898 (9th Cir. 2019), the Ninth Circuit held that the ADA applies to a pizza chain’s website and app, and the Supreme Court declined to review. In Payan v. Los Angeles Community College District, 11 F.4th 729 (9th Cir. 2021), the court affirmed that inaccessible course materials, including PDFs, can constitute disability discrimination under Title II and Section 504.

Federal agencies and their contractors must comply with Section 508 of the Rehabilitation Act, codified at 29 U.S.C. §794d, which incorporates WCAG 2.0 AA by reference in the Revised 508 Standards. Healthcare entities also answer to HHS Office for Civil Rights under Section 504 and the new HHS §504 final rule published May 1, 2024, which also adopts WCAG 2.1 AA.

State Laws That Amplify Federal Liability

State statutes often give plaintiffs stronger damages than the ADA alone. California’s Unruh Civil Rights Act allows statutory damages of 4,000 dollars per violation, and New York State Human Rights Law extends broad coverage to online services. Colorado’s HB21-1110 specifically requires state agency web content and documents to meet WCAG, and it took effect July 1, 2024 for state agencies and July 1, 2025 for local governments.

The consequence of a heading failure under these statutes can be compounded damages. A single PDF form downloaded by 50 disabled users in California could theoretically generate 200,000 dollars in Unruh exposure, before attorneys’ fees. That math is why firms like Seyfarth Shaw’s ADA Title III tracker reported more than 8,800 federal ADA web accessibility lawsuits filed in 2024 alone.

The 2024 DOJ Rule and Its Practical Deadlines

The 2024 Title II rule does not phase in gradually; it hits hard on two fixed dates. Large public entities must comply by April 24, 2026, and smaller public entities and special districts must comply by April 24, 2027. The consequence of missing those dates is that every noncompliant PDF becomes a per-document violation subject to DOJ enforcement and private suits.

A plain-English way to think about this: if a city posts a 50-page zoning PDF with no tagged headings, each page can be read as a separate barrier. The common misconception is that archived documents are exempt. They are not, unless they meet the narrow archive definition in the rule, and most public-facing PDFs do not qualify.

How to Diagnose “Headers Failed” Before You Fix It

Diagnosis comes first because applying the wrong fix wastes hours and can introduce new failures. Open the PDF in Adobe Acrobat Pro, run All Tools → Prepare for accessibility → Check for accessibility, and review the Accessibility Report panel. Every failed rule can be right-clicked for Explain and Fix, and the Show in Tags Panel option jumps you straight to the offending element.

Then run PAC 2024 for a second opinion that tests full PDF/UA conformance. PAC produces a screen-reader preview that shows the document as assistive technology sees it, which is often the fastest way to spot a heading that is visually present but structurally missing. For federal work, ANDI and the Section508.gov Baseline Tests add a third layer of verification.

A practical example: Maria Chen, a compliance officer at a mid-sized Colorado city, ran Acrobat’s Full Check on a 40-page budget PDF and saw a green pass. She then ran PAC 2024 and discovered 14 Matterhorn 14-003 failures because every chapter title was tagged as <P> instead of <H1>. Without the second tool, the city would have shipped a PDF that violated HB21-1110 on day one.

The Tag Tree Inspection Workflow

The tag tree is the source of truth for accessibility, and every remediator must learn to read it. In Acrobat Pro, open View → Show/Hide → Navigation Panes → Tags, expand the <Document> root, and walk the tree top to bottom. Each heading should appear as <H1>, <H2>, <H3>, or deeper, in the order a sighted reader would encounter it.

The consequence of a mismatch is that VoiceOver on macOS will announce headings in the wrong order or skip them entirely. A common mistake is to leave empty heading tags after deleting content; empty headings trigger WCAG 2.4.6 failures and must be removed or populated.

Step-by-Step Fixes by Tool

Different tools require different muscle memory, and the fix path depends on where the PDF originated. The sections below walk through the four most common environments. Each walkthrough assumes you have already identified the specific failure using the diagnosis steps above.

Fixing Headings in Adobe Acrobat Pro

Acrobat Pro remains the industry workhorse for direct PDF remediation, and its tag editor lets you repair structure without returning to the source file. Start by opening the Tags panel and locating the element that should be a heading. Right-click the tag, choose Properties, open the Tag tab, and select the correct heading level from the Type dropdown.

To add a heading where none exists, use the TouchUp Reading Order tool, now called Reading Order in modern Acrobat, select the text block, and click the appropriate heading button. The consequence of skipping this step is that the text remains tagged as a paragraph and continues to fail. A common misconception is that Acrobat’s Autotag Document command fixes headings; it often guesses wrong and still requires manual cleanup.

Fixing Headings at the Source in Microsoft Word

The cleanest fix is almost always upstream in Word, because Word’s styles map directly to PDF heading tags when exported through Acrobat’s PDFMaker or File → Save As → PDF with Document structure tags for accessibility enabled. Apply Word’s built-in Heading 1, Heading 2, and Heading 3 styles rather than manually bolding text. Then run Word’s Accessibility Checker under Review → Check Accessibility before exporting.

A real-world example is James Rivera, a paralegal at a personal injury firm, who was manually retagging every closing argument PDF in Acrobat. Switching to Word styles cut his remediation time from 90 minutes per document to under 10. The consequence of not using styles is that every export ships broken and requires downstream cleanup.

Fixing Headings in Adobe InDesign

InDesign exports accessible PDFs only when paragraph styles are mapped to export tags. Open Paragraph Styles → Style Options → Export Tagging, and set the PDF tag to H1, H2, or H3 for each heading style. Then export through File → Export → Adobe PDF (Interactive or Print) with Create Tagged PDF checked, following Adobe’s InDesign accessibility guide.

The consequence of skipping the export tagging step is that InDesign ships every heading as a generic story tag, which PAC will flag immediately. A common mistake is assuming that applying a paragraph style named “Heading 1” automatically maps to an <H1> tag; it does not without the explicit export mapping.

Fixing Headings in LaTeX

LaTeX users should compile with the tagpdf package or the newer LaTeX Tagged PDF project output, which produces real <H1> through <H6> tags. Standard pdflatex without these packages produces untagged PDFs that will fail every accessibility checker. The consequence is a document that may look professional but is legally noncompliant for any U.S. government or federally funded institution.

Academic users submitting articles to journals indexed by the Association of Research Libraries accessibility guidance should verify heading tags in PAC before submission. A common misconception is that LaTeX’s semantic \section and \subsection commands automatically tag PDFs; they do not, without tagpdf or the new tagged-PDF engine.

Three Scenarios You Will Actually Encounter

Real remediation work rarely matches textbook examples, and the scenarios below come from patterns documented by the PDF Association and Deque University. Each table shows the triggering fault and the specific downstream result. All three are drawn from recurring client situations in 2024 and 2025 remediation practice.

Scenario 1: Government Form With No H1

Scenario 2: Healthcare PDF With Skipped Heading Levels

Scenario 3: University Syllabus With Bold-Only Headings

Three Named-Person Examples

Real names make the stakes concrete, and the three examples below show how heading fixes unfold in practice. Each example ties a specific rule to a specific outcome. All three are composite profiles drawn from published remediation case studies.

Priya Patel, County Clerk in Travis County, Texas

Priya inherited 1,200 archived meeting minutes PDFs with no heading tags at all. She scoped compliance to post-April 2026 documents first, using CommonLook PDF to batch-retag the current year’s files. The consequence of her triage was that Travis County met the Title II deadline for current records while negotiating an archive-reduction plan for older ones.

Marcus Johnson, HR Benefits Administrator at a Fortune 500 Retailer

Marcus discovered the company’s open-enrollment PDF had all plan names tagged as paragraphs rather than <H2> headings. After reading Robles v. Domino’s and consulting counsel, he rebuilt the source in Word with proper styles and re-exported through Acrobat PDFMaker. The consequence of his fix was that the company avoided a demand letter during the 2025 enrollment season.

Dr. Elena Vasquez, University Registrar at a California State University Campus

Elena’s office produced degree audits with skipped heading levels that generated three student complaints under the Unruh Act. She mapped InDesign paragraph styles to proper export tags using the InDesign accessibility workflow. The consequence was that the campus resolved the complaints without statutory damages and adopted a standing PAC 2024 check for all registrar PDFs.

Mistakes to Avoid

Heading remediation goes wrong in predictable ways, and the errors below show up in nearly every audit conducted by firms like Deque and Level Access. Each mistake links to a specific negative outcome. Learn them once and you will save hours of rework.

• Relying on Acrobat Autotag without review, which produces heading guesses that fail PAC.
• Using bold or font-size styling instead of real heading tags, which violates WCAG 1.3.1.
• Skipping heading levels from <H1> to <H3>, which breaks Matterhorn 14-003.
• Leaving empty heading tags after content edits, which screen readers announce as blank.
• Tagging decorative text as headings, which clutters the navigation tree.
• Shipping a PDF that passed Acrobat but was never tested in PAC 2024.
• Ignoring the reading order panel after fixing tags, which can leave headings announced out of sequence.
• Assuming scanned PDFs are compliant once OCR’d, when OCR alone never creates heading tags.
• Forgetting to set the document language, which compounds the navigation failure for non-English screen reader profiles.
• Treating archived PDFs as exempt when they do not meet the narrow archive definition in 28 CFR §35.201.

Do’s and Don’ts for Heading Remediation

Experience shows that the teams who ship compliant PDFs follow a short set of habits. The list below distills what Section508.gov and the U.S. Access Board recommend for production work. Every point ties to a legal or user-experience outcome.

Do’s

• Do apply heading styles in the source file first, because upstream fixes scale.
• Do run both Acrobat Full Check and PAC 2024, because each catches errors the other misses.
• Do test with NVDA or JAWS after tagging, because real AT testing catches what checkers miss.
• Do document your remediation workflow, because audits under Section 508 require evidence.
• Do train content creators on Word and InDesign styles, because prevention beats remediation.

Don’ts

• Don’t rely on visual styling alone, because WCAG 1.3.1 requires programmatic structure.
• Don’t ship without a tag tree review, because autotag is never perfect.
• Don’t skip the reading order check, because tags and order are separate requirements.
• Don’t assume Section 508 and WCAG are identical, because 508 uses WCAG 2.0 AA while Title II uses 2.1 AA.
• Don’t delete headings to silence a checker warning, because missing structure fails a different rule.

Pros and Cons of Direct Acrobat Remediation

Some teams fix PDFs directly in Acrobat instead of rebuilding the source. That path has real tradeoffs, and the list below lays them out so you can choose wisely. Each point reflects guidance from the PDF Association and practicing remediators.

Pros

• Fast for one-off documents, because you avoid round-tripping through the source tool.
• Works when the source file is lost, because Acrobat edits the tag tree directly.
• Allows batch processing with Acrobat Actions, because repetitive fixes can be scripted.
• Gives precise control over the tag tree, because you can hand-edit every element.
• Preserves original layout exactly, because no re-export is required.

Cons

• Does not scale across hundreds of PDFs, because manual tagging is slow.
• Risks reintroducing errors with every source update, because fixes do not propagate upstream.
• Requires trained remediators, because the Tags panel has a steep learning curve.
• Misses some PDF/UA checkpoints Acrobat does not test, because its checker is weaker than PAC.
• Creates audit gaps if you do not document changes, because Section 508 expects a paper trail.

The Accessibility Full Check Workflow Line by Line

The Accessibility Full Check dialog in Acrobat Pro contains roughly 32 rules grouped into categories including Document, Page Content, Forms, Alternate Text, Tables, Lists, and Headings. Every checkbox corresponds to a specific WCAG or PDF/UA requirement, and every option has a consequence if disabled.

Leaving Appropriate nesting unchecked in the Full Check does not remove the legal requirement; it simply hides the failure from your report. Running the check with Create accessibility report selected generates an HTML file you can archive as evidence of remediation, which matters during DOJ or HHS OCR investigations. A common misconception is that a green pass equals legal compliance, but courts look at the underlying PDF, not the checker output.

Fields You Must Configure Before Running

The Page Range field defaults to the entire document, and you should leave it there unless you are testing a single page fix. The Categories section has eight checkboxes that should all stay on, because each maps to a distinct WCAG success criterion. The consequence of deselecting any category is an incomplete report that cannot be used as audit evidence.

Recap of Key Court Rulings

Three decisions anchor the legal landscape for PDF heading accessibility. Robles v. Domino’s Pizza, LLC confirmed that websites and digital content of places of public accommodation fall under ADA Title III. Payan v. LACCD extended the principle to Title II educational materials and affirmed that inaccessible course PDFs can constitute discrimination.

National Federation of the Blind v. Target Corp., 452 F. Supp. 2d 946 (N.D. Cal. 2006) was the first major decision holding that the ADA applies to commercial websites and produced a 6 million dollar settlement. The consequence across these rulings is clear: inaccessible PDFs, including those with failed heading structures, are an enforceable civil rights issue, not a design preference.

FAQs

Do I have to fix every heading failure in an old archived PDF?

No. You only have to fix archived PDFs that do not meet the narrow archive exception in 28 CFR §35.201, which excludes most public-facing documents from the exemption.

Does Acrobat’s Autotag feature fix Headers Failed errors?

No. Autotag guesses at structure and often mislabels headings, so every autotagged document requires manual review in the Tags panel before it can pass PAC 2024 or Matterhorn checks.

Is passing Acrobat’s Full Check enough to meet WCAG 2.1 AA?

No. Acrobat’s checker tests only a subset of WCAG and PDF/UA rules, and passing it does not guarantee Matterhorn Protocol conformance or protection from a DOJ or private lawsuit.

Can bold text qualify as a heading for accessibility?

No. WCAG 1.3.1 requires programmatic structure, meaning the text must carry an <H1> through <H6> tag in the tag tree, not just visual styling like bold or larger font size.

Does the 2024 DOJ Title II rule apply to PDFs from private companies?

No. Title II covers only state and local governments, but private companies face parallel obligations under ADA Title III and state laws such as the Unruh Act and NYSHRL.

Are scanned PDFs compliant once I run OCR on them?

No. OCR only converts images to text; it does not create heading tags, so every OCR’d PDF still needs manual or assisted tagging before it meets WCAG 2.1 AA.

Do I need to fix heading order if the visual layout looks fine?

Yes. Tag order and reading order are separate from visual layout, and a screen reader follows the tag tree, so mismatched order produces a failure even when the page looks correct.

Can LaTeX produce accessible PDFs with proper heading tags?

Yes. The tagpdf package and the LaTeX Project’s new tagged-PDF engine produce real <H1> through <H6> tags, but standard pdflatex without those packages does not.

Will I face penalties if my PDF fails only the heading check?

Yes. A single failed success criterion can trigger a complaint, and courts have treated isolated WCAG failures as actionable under both the ADA and Section 504.

Does Section 508 require WCAG 2.1 AA for federal PDFs?

No. The current Revised 508 Standards incorporate WCAG 2.0 AA, though the U.S. Access Board has signaled a future update to 2.1 AA, and federal agencies often apply 2.1 AA as an internal policy.