PDF Association logo

Discover pdfa.org

Key resources

Get involved

How do you find the right PDF technology vendor?
Use the Solution Agent to ask the entire PDF communuity!
The PDF Association celebrates its members’ public statements
of support
for ISO-standardized PDF technology.

Member Area

What Does a Failed PDF Check Mean?

Passing a PDF accessibility check does not guarantee compliance, nor does failing one confirm non-compliance. Learn the limits of automated testing, the importance of manual checks, and best practices for accessibility testing and remediation.

Member NewsNovember 18, 2026
Person using a laptop with floating PDF and document icons representing digital document management.
What Does a Failed PDF Check Mean?
Person using a laptop with floating PDF and document icons representing digital document management.

Passing a PDF accessibility check does not guarantee compliance, nor does failing one confirm non-compliance. Learn the limits of automated testing, the importance of manual checks, and best practices for accessibility testing and remediation.

Member NewsNovember 18, 2026

Vijayshree Vethantham

About Vijayshree Vethantham, Continual Engine

DISCLAIMER
The views expressed in this article are those of the author(s) and do not reflect the policies or positions of the PDF Association.

What Do PDF Checker Results Actually Tell You?

A PDF checker evaluates a document against a set of technical rules. When it reports a failure, it means that a specific test condition was not met or that the tool found a possible accessibility issue.

Most checkers use different result categories, but the following terms explain some common outcomes:

  • Failed: The document did not meet a specific test condition. The issue needs to be investigated and corrected where necessary.
  • Passed: The document met the conditions tested by the tool. However, this does not confirm that every accessibility requirement has been met.
  • Needs Manual Verification: The tool cannot determine whether the content meets the requirement on its own. A person must review it.
  • Not Applicable: The test does not apply to that particular document or element.

These results should be treated as findings rather than a final judgment on compliance. A failed test identifies something to investigate, while a passed test only confirms what the checker was designed to evaluate.

What Can Automated PDF Checkers Find?

Depending on the tool and the standard or rules it checks, an automated checker may identify:

  • Missing document tags
  • Incorrect document structure
  • Missing alt text
  • Reading-order issues
  • Missing document language
  • Missing titles or metadata
  • Table structure issues
  • Link and annotation issues

Automated checkers can also test other technical properties, depending on their capabilities. However, their coverage varies.

What Automated PDF Checkers Cannot Fully Evaluate?

Although automated tools can detect many technical problems, they cannot reliably judge every part of a document. Some accessibility issues depend on meaning, context, and the experience of the person using the PDF.

Here are some scenarios that PDF checkers can’t fully evaluate:

  • Whether the Content Makes Sense

A checker may confirm that an image has alternative text, but it cannot always determine whether that description accurately explains the image's purpose.

  • Whether the Reading Order Is Logical

An automated tool can tell if the reading order is present or not, but it cannot fully evaluate whether it’s logical.

  • Whether Tables Are Easy to Understand

A checker may identify table tags and structural elements, but that does not guarantee that users can understand the information.

  • Whether Real Users Can Access the Document

Some accessibility issues become clear only when real users interact with the PDF. Manual evaluation can help determine whether users can navigate and understand the document.

Some aspect of accessibility checking requires human judgment. This includes:

  • Reviewing the document manually to check whether its content is meaningful and well organized.
  • Testing keyboard navigation to confirm that interactive elements can be reached and used.
  • Using screen readers to check how the document's content is announced.
  • Testing with relevant assistive technology to identify practical barriers.

Does a Failed PDF Check Mean the Document Is Non-Compliant?

No. A failed PDF checker does not automatically mean that a document is non-compliant with every applicable accessibility requirement.

Accessibility compliance is assessed against the specific laws, standards, and technical requirements that apply to the document and its use, not just a simple accessibility score.

Different tools may also test different criteria. Therefore, a score or pass/fail result from one tool should not be treated as a universal compliance verdict.

Can a PDF Pass an Automated Checker & Still Be Inaccessible?

Yes. A PDF can pass automated checks and still create barriers for people with disabilities because some accessibility problems require human judgment.

For example:

  • Meaningless alternative text: An image may have alt text, but the description may not explain the information it communicates.
  • Confusing reading order: The PDF may contain reading-order information, but a screen reader may still announce its content in an unclear sequence.
  • Difficult tables: A complex table may pass structural checks but remain hard to understand because its headings do not clearly explain the data.
  • Missing visual context: A chart or diagram may be tagged, but users who cannot see it may not receive enough information to understand its meaning.

This is why passing an automated PDF accessibility checker should not be treated as proof that a document is fully accessible. Organizations need to check both technical requirements and the experience of people who use the document.

Steps to Take After a PDF Accessibility Check Fails

A failed result should lead to a clear review and remediation process.  A practical workflow follows five steps:

  • Detect the issue

Identify the specific test that failed and note the affected page, element, or document feature.

  • Understand the result

Determine what the failure means and whether it indicates an actual accessibility barrier or requires manual verification.

  • Correct the problem

Remediate the underlying issue, such as missing tags, incorrect reading order, or missing alternative text.

  • Run the checker again

Repeat automated testing to confirm that the identified technical issue has been addressed.

  • Validate the document manually

Review the final PDF and use keyboard and screen reader testing where appropriate to check whether people can access and understand its content.

Automated PDF Testing vs. Human Accessibility Review

Automated Testing Manual Review
Identifies technical issues that software can detect. Evaluates whether the content is meaningful and easy to understand.
Processes documents quickly. Examines the document with greater attention to context.
Applies the same test rules consistently. Uses human judgment to assess usability.
Can support testing across large volumes of documents. Helps validate the experience of people using assistive technology.

 

Neither method should replace the other. Automated testing helps find technical issues efficiently, while human review helps determine whether the document is genuinely usable.

What Does a Reliable PDF Accessibility Process Look Like?

A strong PDF accessibility process combines automated checks with human judgment at different stages. Organizations should build a workflow that identifies issues, corrects them, and verifies the final document before publication.

A practical process looks like this:

Automated checks to identify technical accessibility issues.

↓

Issue review to understand the failed results and their impact.

↓

Remediation process to correct the identified accessibility barriers.

↓

Automated retesting to check whether the technical issues have been resolved.

↓

Manual validation to review the document using human evaluation and assistive technology.

↓

Compliance assessment to evaluate the document against the applicable accessibility requirements.

For organizations managing large document libraries, solutions such as Continual Engine's PDF and Document Remediation Services can support the process of identifying and addressing accessibility issues.


Continual Engine solves the core challenges of digital accessibility by transforming PDFs, documents, images, multimedia, and STEM materials into fully accessible and compliant formats. As an award-winning provider of AI-powered accessibility solutions, we deliver comprehensive, end-to-end services that help institutions meet and exceed WCAG 2.1/2.2 Level AA, Section 508, and…

Read more

WordPress Cookie Notice by Real Cookie Banner