Frequently Asked Questions (FAQ)

Yes. That figure does contain alternate text – it’s predefined directly in the tagging template, so it’s applied automatically whenever the template runs. PDFix has additional webinars planned specifically covering templates in more depth for anyone who wants to go further into how these rules are built.

The PDFix SDK works on existing PDF documents – meaning once a document has been created, you set up a workflow that modifies it to bring it into compliance with either PDF/UA or WCAG, depending on your requirements. The advantage of this approach is that it doesn’t require changing your existing document-creation workflow at all. If you already have a process set up for generating and distributing documents, you simply add one additional step to that workflow and apply the changes to the documents before distribution.

Ideally, clients learn to build their own templates, and most end up doing exactly that. For the first few templates, PDFix typically provides direct assistance or builds them together with the client, along with documentation and guidance. Once someone has been through that process a couple of times, most users find template-building isn’t as difficult as it looks and start creating new templates independently going forward.

Both – as long as you validate against the right profile. PDFix uses veraPDF for validation, and if a document passes PDF/UA validation, it will also pass WCAG. The recommended validation profile is WCAG 2.2 Complete, which tests not only against WCAG 2.2 but also against PDF/UA (ISO 14289). You can set WCAG 2.2 Complete as your default validation profile, and then you’re covered for both standards in one pass.

No. PDFix Desktop provides a user interface for creating templates – the template can be displayed in a tree view, and all the rules and properties in it can be presented in a more user-friendly way. The JSON is written in the background, but you build your own rules for element creation – based on position, anchors in the document, font color, size, and so on – through that interface rather than writing JSON by hand.

Screen reader support comes from natively reading the tagging structure of the PDF document. By making a PDF compliant with PDF/UA or WCAG, you automatically get support from all screen readers that support those accessibility standards, and you should get the right user experience in those viewers.

The template is ideal for documents that were created from the same source or same database – documents that typically have the same layout and formatting but just use different data in the content. For this purpose, the template works very well, and you can set up rules that are universal and flexible enough to capture the changing content. Templates can be set up more generally too, but the more variable the documents are, the fewer common rules you can write, and the results can move away from what’s expected. If you really have documents made from the same source – like the form used in this demo, where only the data changes – you can achieve almost 100% accuracy, and the template is highly customizable. Follow-up from the presenters: To be clear, this was a very specific document layout that the team took time to template out precisely. If you don’t have that experience or bandwidth yet, or you’re still learning, PDFix’s built-in Make Accessible action (using the generic pre-flight template, without a custom template loaded) is a solid, more generic option. It won’t get the most precise tagging that a fully custom template would, but for well-structured general documents it does a solid job of tagging plus the other Make Accessible remediation steps – getting you most of the way there, if not all the way, so even without a custom template you’re not left without solutions.

The difference is significant. With a template prepared in advance, you’ll probably get the expected results, and you can fine-tune outcomes based on the tagging structure generated by that particular template – down to things like controlling line spacing and word spacing, building relationships between words or segments, and building anchors that positionally define elements even if they shift position between documents. So the layout template is a set of human-defined, controlled rules applied to a document. AI auto-tagging, on the other hand, can do a very good job on layouts where content variability is much larger and a single template can’t be used – but results can be somewhat unexpected depending on which model you choose for auto-tagging. Performance is also a factor: the layout template is just a JSON file with no dependency on any external resource, so the operation can be fully controlled in an offline environment.

Ideally, authors should be making sure they’re meeting contrast requirements while creating the documents in the first place – that’s the best way to go about it. But PDFix does have functionality to correct color contrast issues for text and its background. From within the document view, under Content Actions, there’s a Set Content Color option – you can select text to see its RGB value, then go to Set Content Color, target objects with that specific color, and specify the new fill color you want. That action can be run across one document or in batch/SDK across multiple documents, and wherever that color comes up, it gets changed. One thing to be clear on: veraPDF itself does not test for color contrast – that’s something you’d want to be diligent about yourself – but PDFix does allow you to fix it, in one document or many at once.

This can be handled a few ways: running an action to add alt text, using AI to generate it, or – if templating – setting it directly in the template. Ideally the issue is fixed at the source (real text instead of an image). If the content is already an image and can’t be modified, tag it as a Figure with meaningful alt text describing what the image conveys. If the document can be modified, OCR can create a text layer to retag properly – but OCR output should always be reviewed, since accuracy depends on the source image quality and OCR engine.

No – the JSON itself wasn’t demonstrated being written from scratch, but the webinar did show some of the high-level pieces that go into building a template.

Yes – PDFix has documentation on templates and actions, a Knowledge Base with help articles (some including downloadable JSON action files), GitHub resources, and direct email support. If more hands-on help is needed, or someone wants PDFix to build the templates for them, that’s available too.

Important distinction: OCR converts a scanned image of a document into searchable text so it can be tagged – it’s not the same as alt text. Alt text describes images (a logo, a graph, etc.) that you wouldn’t OCR in the first place; you’d keep it as an image, tag it as a Figure, and write alt text describing what it conveys.

The Enfocus Switch application, just published in the Enfocus App Store, runs on the same principles as the command-line execution demoed earlier. The only arguments you need to fill in are your input file, output file, and the path to your JSON file containing the configuration for running the Make Accessible batch command. It’s the same way of using the SDK, just in a different environment – so Enfocus Switch users can take advantage of the same approach.

Yes! We have made available the sample documents that we showed and the Make Accessible, with the tagging template. pdfix_sdk_example_templates/summary_of_benefits at main · pdfix/pdfix_sdk_example_templates Please try it with the latest version of PDFix Desktop.

Two so far: Make Accessible (remediation) and Validation (conformance checking). This page is updated each time a new one ships.

The app is free to download. You’ll need a valid PDFix SDK license to run it.

Yes, entirely – unlike Make Accessible, Validation needs no PDFix SDK license. It runs on the bundled veraPDF CLI.

No. Make Accessible ships the PDFix SDK command-line runtime inside the app; Validation ships the veraPDF CLI and PDFix Desktop-compatible profiles the same way.

No tool can. Make Accessible automates tagging, structure, and metadata; Validation automates the conformance check. Both still need human review and interpretation before you call a document fully compliant.

PDF/UA-1 by default, with PDF/UA-2, PDF/A-1A, WCAG 2.2, and ISO 32000-1 Tagged PDF also available.

Yes. PDFix lets you fix a single issue across multiple documents at once with a single Action, or fix many issues at once across many documents with a pre-loaded sequence of actions – such as the “Make Accessible” sequence, which runs about 37 individual steps in one click.

Out of the box, Actions can set or add a document title (using the file name, the first H1, or a custom title), embed fonts, fix Unicode issues, and provide Alt text for Figure tags – including AI-generated Alt text.

For one-off documents, Actions and action sequences still help. For documents that share a similar layout, you can build a tagging template that automatically and accurately tags them – and combine it with the “Make Accessible” sequence to handle most of the remediation for you.

Yes. Actions, action sequences, and custom actions built in PDFix Desktop can all be exported and used in the PDFix SDK.

Yes, the PDFix SDK supports multiple programming languages including Python, C++, Java, .NET, and JavaScript. It is cross-platform and runs on Windows, Linux, and macOS.

You can explore the list of Batch Actions available under documentation. While we currently don’t link PDF standard clause numbers directly to actions, we’re working on adding this mapping. For now, feel free to contact us for guidance on addressing specific issues.

There is no hard limit. We’ve successfully processed PDF files with over 12,000 pages. Performance may depend on system resources, but generally, the SDK can handle large documents efficiently. For monitoring long operations like auto-tagging, progress monitoring can be implemented – contact us for an example.

Yes! Use the Create Bookmarks action in the PDFix Actions. If your PDF has headings in its structure, this action will auto-generate bookmarks. Check our documentation for implementation details.

PDFix SDK doesn’t support PDF reconstruction from XML. Instead, it provides direct PDF editing functions – modifying content, links, page assembly. For specific needs, review our GitHub examples or email us for guidance.

Accessibility features, including auto-tagging, require the PDFix SDK Enterprise license.

The auto-tag function removes the entire existing structure by default. However, for fixing pre-tagged documents – for example those from InDesign – refer to our webinar, which covers custom remediation workflows.

Absolutely! Modify the script to iterate through all files in a directory—it can handle any number of PDFs.

PDFix tagging templates are reusable rule sets that define how document elements should be tagged for accessibility. You configure rules based on text size, position, and layout patterns — PDFix then applies those rules automatically across any PDF with the same structure.

Templates work best for document families with consistent structure – invoices, financial reports, government forms, newsletters, and Office-based documents. Any document type where layout and formatting follows a predictable pattern is ideal for template-based auto-tagging.

Yes. Once a template is created, it can be applied across entire folders of similarly structured PDFs in one batch run — delivering consistent PDF/UA-compliant tagging without opening each document individually.

Yes – PDFix templates are designed to produce PDF/UA-1 and PDF/UA-2 compliant output. After batch tagging, you can validate results using the built-in veraPDF integration in PDFix Desktop.

There isn’t one universal “best” AI model – accuracy depends on the document type and layout. All supported models (Amazon Textract, Docling, and Paddle) perform well in layout recognition, table detection, and heading structure identification. However, none consistently outperforms the others across all business documents. We recommend testing each model on your specific document set to see which fits best. If you find an AI model that performs exceptionally well, contact us – we can guide you on how to integrate it and convert its output into a compatible PDFix Layout Template.

Yes. You can integrate your own AI layout model into the PDFix workflow.Each layout action in the PDFix Marketplace links to our open-source Docker implementation on GitHub. Using this reference, you can implement your own AI model and gain competitive technical or business advantages.

It depends on the AI model you choose. Cloud-based models such as Amazon Textract require an internet connection.However, many models – including Docling or other locally deployed AI models — can run fully offline inside a Docker container.Keep in mind that some of these models are large (e.g., 4–5 GB) and require local disk space, but once set up, they work entirely offline.

You can freely modify or merge AI-generated templates with your own.The AI template is a standard JSON file that you can edit to: Add or adjust element properties (for example, marking an element as a heading) Modify tagging rules Apply heuristics or logic to improve structure recognition You can do this manually or programmatically – for instance, by adding custom properties such as alternate text, role mappings, or structural adjustments to enhance accessibility and accuracy.

Creating templates manually is possible but not necessary — PDFix Desktop includes a visual template editor.With PDFix Desktop, you can: Visually design and test layout templates Tag elements directly on the page Export the JSON template for SDK automation For a step-by-step demonstration, see our PDFix Layout Templates webinar, linked in this video’s description and on our webinar page.

Yes. PDFix SDK supports integrating PDF/UA validation (e.g., with veraPDF) directly in your automated workflow.You can perform auto-tagging, apply fixes for accessibility issues, and then validate results – all programmatically. This topic will be covered in an upcoming webinar, and you can also refer to our earlier webinars on automated validation and fixing accessibility issues with PDFix SDK.

Absolutely. You can assign alternate text (alt text) to any element directly in your template – without AI.For example: Mark an element as a figure and define its alternate_text property. Identify images based on page number, position (bounding box), or object ID. Use template functions to automatically assign descriptive alt text to each image. This allows complete control over accessibility tagging within a purely rule-based (non-AI) template workflow.

A typical end-to-end workflow looks like this: Document Intake Detect whether documents already include tags or are PDF/UA-compliant Validation StepRun a compliance check (e.g., with veraPDF) to determine the tagging quality Auto-Tagging & Accessibility FixesUse PDFix SDK to perform layout recognition, auto-tagging, and automated fixing of accessibility issues. Re-ValidationValidate the processed files to confirm PDF/UA conformance. Manual Review (if needed)Send any remaining files for manual remediation to ensure full accessibility compliance. This hybrid automation-plus-review approach ensures accuracy and reliability across large document volumes.

You can find all our past and upcoming webinars in the Webinar category on pdfix.net. More recorded sessions are also available on our YouTube channel: Team PDFix

Absolutely! You can follow along and experiment using the same materials. All the documents and JSON template files are available for download on our GitHub: Weekly Market Sample

Yep, everything you see in this webinar is replicable in the SDK. See a separate webinar for auto-tagging with PDFix SDK.

Templates can be created with the Preflight function in PDFix Desktop, using an AI model, or manually. Template examples are available on GitHub.

Yes, it’s possible. If you need help creating one, just contact us — we can assist with multi-page and repeating layouts.

Yes, that’s correct. Templates can be generated automatically using AI. PDFix Desktop then applies them to fix and enhance the tagging structure.

Some AI models require credentials, some don’t. PDFix Desktop offers a free AI layout models such as Paddle.

PDFix Desktop offers a free AI layout models such as Paddle which does not require credentials.

Yep! You can train and prepare your own model, then integrate it easily into PDFix.

We continuously work on imtegration of new LLM models into PDFix Desktop, including Microsoft Azure. Please check for PDFix Marketplace updates.

Yes! We offer an external OCR action that can be applied before auto-tagging. It automatically adds an OCR text layer to scanned PDF files. Learn more here: OCR Tesseract Action

Yes, we have an external Table Summary mode that improves table readability for LLMs: Generate Table Summary with OpenAI

We support both OpenAI and Paddle for MathML detection.

Tagging PDF Forms is challenging, but possible. Each form field is properly tagged based on PDF/UA standard. The form field descriptions can be auto-generated from field names or tooltips.

Manually created templates can handle auto-tagging of complex layouts. If you need help creating one, just contact us — we can assist with complex layouts.

Not completely. PDFix relies on the open-source veraPDF tool for PDF/UA validation. You can learn more here: PDF Accessibility Validators

Yep! Check our related blog and webinar here: How to automate fixes in InDesign created PDFs

Yes, exactly! You can use the free BLIP or paid OpenAI model for automatic Alternate Text generation.

Constantly. External actions are updated whenever new versions are released. PDFix SDK and Desktop are updated at least quarterly — or more often if needed.

Yes, it is possible to use Podman instead of Docker Desktop for running external actions integrated with PDFix Desktop.PDFix Desktop supports actions that can be distributed through the PDFix Marketplace or installed manually using an action configuration file (JSON).Each action configuration file defines: Action metadata — such as name, category, and subtype, enabling integration into specific workflows (e.g., template creation or tag editing). Program execution pattern — including the command-line call and its arguments. Argument definitions — allowing customization of how the action runs and interacts with PDFix Desktop. Because the action system executes external programs through command-line calls, Podman can be used in the same way as Docker Desktop or any other CLI-based container runtime.Example: Executing the Action with Docker docker run -v $(pwd):/data -w /data –rm pdfix/autotag-textract:latest \ tag –aws_id ${AWS_ID} –aws_secret ${AWS_SECRET} –aws_region ${AWS_REGION} \ -i /data/input.pdf -o /data/output.pdf Example: Executing the Same Action with Podman podman run -v $(pwd):/data -w /data –rm pdfix/autotag-textract:latest \ tag –aws_id ${AWS_ID} –aws_secret ${AWS_SECRET} –aws_region ${AWS_REGION} \ -i /data/input.pdf -o /data/output.pdf Since Podman provides a Docker-compatible command-line interface, no additional configuration changes are required in the PDFix action definition.Simply replace docker with podman in the execution command. For detailed guidance on creating or installing custom actions, please contact us.

Create or sign in to your AWS account (console). Create an IAM user (or use an existing one) and enable Programmatic access so it can get access keys. When you create the access key pair, save the secret — AWS shows the secret only once. AWS Documentation Attach Textract permissions to that user/role. For testing you can attach the managed policy AmazonTextractFullAccess; for production prefer least-privilege (grant only the textract:* actions you need). AWS Documentation Create the access key for that IAM user (Access Key ID + Secret Access Key) via the IAM → Users → Security credentials → Create access key UI. Store those credentials securely (see storage below). AWS Documentation

Paddle is currently supported only for layout recognition in auto-tagging and template workflows. It does not include OCR functionality.At the moment, Tesseract is the only OCR engine supported in the PDFix Marketplace. Please check for future updates that may add OCR support for Paddle or other engines.

veraPDF is an open-source PDF validator covering all parts of the PDF/A and PDF/UA (Matterhorn Protocol Machine failure conditions) standards. Originally funded by the PREFORMA project, veraPDF has been sustained and maintained by the Open Preservation Foundation since 2017. Dual Lab provides active user support and carries out maintenance and bug fixes. The PDF Association’s PDF/A Technical Working Group continues its role in resolving ambiguities arising from veraPDF’s usage in the field.

Yes. It is industry supported open-source standard with active maintenance and PDF community governance. It validates PDF/UA requirements, highlights common tagging and structure errors, and produces validation reports you can trust. See the full list of PDF/UA validation profiles.

veraPDF outputs HTML, XML, or JSON with detailed findings, errors, and fail summaries.

Use the veraPDF Web Demonstrator or the PDFix online validator (pdfix.io) to run PDF/UA checks directly in your browse.

Yes. veraPDFis free and open-source – you can download it, use it, and modify it to meet your needs.

If you encounter a validation result that appears incorrect, we encourage you to report it on the veraPDF GitHub issue tracker or reach out to the Open Preservation Foundation. Community feedback is essential to improving veraPDF. You can also volunteer your time and expertise by contributing to the software and documentation via GitHub (https://github.com/veraPDF)

veraPDF desktop is a great validator, but PDFix Desktop Lite makes the results practical to work with. PDFix Desktop Lite: Integrates the same veraPDF validation engine directly into a PDF viewer/editor. Shows validation results in a dedicated panel. Groups issues by type (e.g., natural language, images, structure). Lets you click an issue and jump directly to the problematic object on the page or in the structure tree. Supports batch validation across many files, with a combined view of issues. So if you not only want to check conformance but also understand and work with the problematic content, Desktop Lite offers a much more usable wo

Yes. This means the validation results in PDFix match what you would get from the official veraPDF distribution (for the same profile and version). PDFix uses the latest official veraPDF engine. When PDFix needs improvements or bug fixes, they contribute changes upstream to the veraPDF open-source project.

Yes, this kind of structural fix is possible in PDFix. PDFix provides a “Delete Tags” action that: Deletes selected tag types (e.g., <P>) based on rules. Lets you decide what happens to nested content: Leave content in place, Move nested tags up to the parent level, or Mark the content as artifact. You can define a custom template that targets only the structures you want.Example from the webinar: Delete <P> tags whose parent is <TR>, and move nested tags up one level. Applied to your case, you can: Target <P> tags that contain figures/tables/formulas. Use the “move nested tags to parent” option. This effectively lifts the figure/table/formula out of the paragraph and places it as a sibling tag. If needed, PDFix support can help define the exact template logic for your layout.

Key points: veraPDF: The default PDF/UA profile does not include color contrast checks. A more complete / WCAG-oriented profile does contain a color contrast test. The contrast algorithm and thresholds in veraPDF may differ from other tools. You can inspect and even adjust the color contrast check in the profile XML if you have specific criteria. PAC and other tools: PAC is still widely used for color contrast validation. Different tools may report different results because they use different algorithms or interpretation rules. Recommended approach: For critical workflows, review or customize the veraPDF contrast check to match your internal requirements. Use multiple validators (e.g., PAC + veraPDF with a profile that includes color contrast checks).

Yes, you can generate veraPDF validation reports directly from PDFix Desktop Lite. The UI lets you: Run validation with a chosen profile. Generate a veraPDF report as: HTML, XML Open the report inside PDFix and then save it (e.g., as HTML or convert to PDF for sharing). JSON: CLI / Docker / SDK integration → HTML / XML / JSON, depending on how you call veraPDF. veraPDF itself can output JSON via its command-line usage. JSON is typically accessed in automation/SDK or Docker-based workflows, rather than through the basic Lite UI. So: Desktop Lite UI → HTML / XML reports

There is no fixed hard limit in the SDK itself. Throughput and “efficient volume” depend on: Your hardware (CPU cores, RAM, disk/IO). Parallelization strategy (how many processes/threads you run). Complexity and size of the PDFs. What actions you perform (validation only vs. validation + fixing + conversions). Real capacity is determined by how you architect your batch/queue system, not by a built-in limit in SDK. PDFix SDK can be used: In continuous workflows, processing thousands to millions of documents. In parallel processes (e.g., multiple CLI or worker instances).

NVDA is Windows-only, so it’s not an option on Mac. The main native screen reader on macOS is VoiceOver: Use VoiceOver together with Adobe Acrobat Reader DC or Acrobat Pro for realistic PDF testing. Built-in viewers (like Preview) generally don’t expose full tag/structure information the way screen readers need. Alternative / complementary method: Use PDFix conversion to HTML as a proxy for reading order: PDFix can convert tagged PDFs to HTML using the document structure (tag tree) as the reading order. You can then review: Heading levels (H1, H2…), Reading order, Grouping of content. This is not a replacement for an actual screen reader, but it’s a very useful additional check based on the same tag structure that assistive tech relies on. Recommended practice: Optionally, combine this with PDF → HTML conversion via PDFix to visually inspect reading order and tag structure. On Mac: Use VoiceOver + Acrobat Reader/Pro for hands-on accessibility testing.

Yes – all PDFix webinars are free and available on demand. No registration required to watch recorded sessions. New live webinars are announced on pdfix.net and open to everyone.

PDFix webinars cover PDF/UA-1 (ISO 14289-1), PDF/UA-2 (ISO 14289-2), WCAG 2.1 and 2.2, and EU Accessibility Act (EAA) requirements for digital documents. Sessions also cover veraPDF validation, common PDF/UA error remediation, and automated tagging workflows.

Yes. PDFix Desktop supports batch validation and batch remediation across large document sets. PDFix SDK and tagging templates are built specifically for high-volume workflows – processing thousands or millions of PDFs automatically without manual intervention.

PDFix Desktop lets you run batch validation across multiple PDFs, identify PDF/UA errors by type, and apply custom remediation actions automatically – without manually fixing each document. Watch our veraPDF webinar to learn more about validation and automated PDF/UA error fixes.

veraPDF is the open-source gold standard for PDF/UA-1 and PDF/UA-2 validation, maintained by the Open Preservation Foundation and aligned with the PDF Association. Our webinar covers installation, validation profiles, interpreting results, and fixing errors using the PDFix integration.

For very simple documents with basic headings and paragraphs, some auto-taggers may do a decent job. However, as soon as any complexity is introduced – tables, nested lists, tables of contents, or documents that used invisible layout tables – success rates drop significantly. PDFix addresses this through auto-tagging templates, which let you define the exact structure of a repeating document type so that auto-tagging produces correct, fully compliant output every time.

PDF auto-tagging is the process of automatically adding accessibility tags to a PDF document – tags that define structure (headings, paragraphs, lists, tables) so that screen readers and assistive technologies can read the document correctly. Most auto-taggers use algorithms or AI to detect content structure. Quality varies widely depending on the tool and the complexity of the document.

Most auto-taggers rely on generic algorithms that struggle with complexity. Common failure points include tables used for layout instead of data, nested lists, numbered headings misidentified as lists, complex data tables, and tables of contents. Additionally, most auto-taggers only handle tagging – they ignore other accessibility requirements such as embedded fonts, Unicode character mapping, annotation Contents, tooltip assignment, and metadata.

PDFix Actions are automated operations that can be run against one document or batches of hundreds of documents at once. Examples include adding Contents entries to link annotations, setting the document title in metadata, automatically detecting and setting document language, tagging untagged annotations, and assigning tooltips to form widgets. In PDFix Desktop a user runs the action; in the PDFix SDK, actions run fully automatically without any human trigger.

PDFix layout templates let you define the exact tag structure for a specific document type. Once you build a template for a recurring document – an annual report, a form series, a policy document – you can run it against hundreds or thousands of similar documents and get correct, fully compliant tags and reading order automatically, with no additional manual work. Unlike other tools, PDFix lets you create, own, and edit your own templates, so if your organization’s style guide changes, you simply update the template.

PDFix handles scale through Actions – a single automated operations run across hundreds of documents, and layout templates – document-type-specific tag maps applied to thousands of similar files. The PDFix SDK removes the need for any human trigger – everything runs automatically in your IT infrastructure or cloud environment.

You currently need a custom External Action that connects your AI workflow to PDFix.

Yes. PDFix provides free examples and integration samples for developers.

Yes. PDFix can prepare custom AI integrations as tailored solutions.

Potentially any remediation-related step, including OCR, tagging, alt text, structure analysis, validation workflows, and custom remediation logic.

Not currently. AI integrations today are implemented through dedicated External Actions designed for structured remediation workflows.

It means the PDF is missing a valid language tag (Lang entry) at the document, structure element, or content level. The fix is to set a correct language identifier in the document metadata or the affected structure element. Covered under clause 7.2-34.

Each validator implements ISO 14289-1 independently and applies different logic, heuristics, and rule coverage. In our study of 155 PDF test files, the four leading validators produced inconsistent results in 50.3% of cases – meaning the same file passed one tool and failed another. This does not mean one tool is wrong. It reflects genuine differences in how each tool interprets ambiguous clauses, which errors it prioritizes, and how it handles edge cases. The practical consequence: relying on a single validator can produce incomplete compliance conclusions. Cross-checking with at least two tools is strongly recommended for any document requiring formal compliance. See also: PDF/UA Validator Comparison (155 files tested).

Many can. Automated tools – including PDFix Desktop’s Auto-Fix – resolve all machine-checkable errors: missing metadata, font embedding, DisplayDocTitle, language tags, and role mapping. However, approximately one third of PDF/UA criteria require human verification and cannot be automated. Errors that need manual judgment include whether alt text meaningfully describes an image, whether reading order reflects the document’s logical structure, and whether heading levels match the actual content hierarchy. A document can pass every automated check and still fail real-world accessibility testing. Best practice is to run automated fixes first, revalidate, then manually review remaining errors.

The fix depends on whether the image carries meaning – and no automated tool can decide this for you. – Informational image – add meaningful Alt text describing what the image communicates, not just what it looks like. – Decorative image – do not add empty alt text. Mark it as an Artifact instead. An artifacted element is excluded from the tag tree and ignored by screen readers. Adding empty alt text to a decorative image is itself a PDF/UA error. In PDFix Desktop, use the Tags panel to set the Alt text or change the element type to Artifact depending on which applies.

Related but not the same. Both are font errors that frequently appear together – but they describe different problems. “Font not embedded” (clause 7.21.4.1-1) means the PDF references a font that is not included in the file itself. Screen readers cannot reliably read text when the font is missing, which makes the document inaccessible and causes it to fail PDF/UA validation. “Character cannot be mapped to Unicode” (clause 7.21.7-1) means the font is present but lacks the data needed to translate its characters into readable text. The document may look correct on screen but fails when a screen reader, search tool, or copy-paste tries to extract the text. In PDFix Desktop, use Embed Fonts to fix the first error and Add Missing Unicodes for the second. For complex cases – such as broken encoding tables or CID font errors – PDFix also offers an automated Font Fix action that detects and repairs both issues in one step.

For state and local government agencies facing the 2026 ADA Title II deadline, PDFix-US offers the most complete automated PDF accessibility platform available in the U.S. market. PDFix SDK 9.0 handles batch remediation across legacy document libraries of any size, with built-in verification for Section 508, WCAG 2.2 AA, and PDF/UA. Unlike manual remediation services billed per page, PDFix uses volume-based licensing – keeping costs predictable regardless of document volume. A U.S.-based team led by David Herr (PMP, CPACC) provides local implementation support and training, with on-premise deployment available for agencies with strict data residency requirements. Get a free evaluation license

PDFix is the Slovakia-based PDF technology company that has built automated PDF accessibility tools since 2017, proven with business enterprises, state agencies, and top universities. PDFix-US is its newly established exclusive U.S. distributor, launched in 2026 specifically to serve the American market. The practical difference: PDFix-US provides U.S.-based sales, customer support, training, and implementation services – with a local team that operates in American business hours, understands U.S. compliance frameworks (ADA Title II, Section 508, state mandates), and can engage directly with procurement and legal teams. Both offer the same PDFix SDK and PDFix Desktop product suite. Learn more at pdfix-us.com or pdfix.net.

Yes – PDF accessibility can be fully automated for both Section 508 and ADA Title II compliance. PDFix SDK 9.0 applies AI-assisted auto-tagging and structural analysis to generate PDF/UA-conformant output that satisfies Section 508 (federal), WCAG 2.1 AA and WCAG 2.2 AA (ADA Title II state and local requirements), and the PDF/UA ISO standard. Automated remediation handles document structure, reading order, alt text, table tagging, and language declarations at enterprise scale. Every output includes an integrated VeraPDF verification report – the audit documentation compliance officers and procurement auditors need. Manual review is still recommended for complex layouts, but automation handles the volume that manual workflows cannot. Read more in Deutsche Bank case study.

Universities with high-volume PDF remediation needs – course catalogs, syllabi, research outputs, scanned lecture slides – are moving to automated remediation platforms rather than expanding accessibility teams. PDFix-US enables higher education institutions to process entire document repositories using AI-assisted auto-tagging and batch processing. PDFix Desktop integrates easily into document management workflows. The result: sustainable compliance at scale, with consistent VeraPDF-verified output and a clear audit trail.

With PDFix Desktop 3.0, drag the folder into the Application Dashboard, run batch validation, and click Fix Error to remediate all affected documents in a single pass – no need to open files individually.

PDFix Desktop 3.0 is the only tool on the market that combines batch PDF/UA validation, AI-powered accessibility fix actions, and veraPDF integration in a single dashboard. You can validate hundreds of PDFs at once, see errors with their exact location in each document, and apply fixes across the entire batch without opening files individually.

Adobe Acrobat is built around single-document workflows – you open one PDF, run the Accessibility Checker, and fix issues manually. PDFix Desktop is built for automated PDF remediation and high-volume batch operations: drop in a folder, validate every PDF at once, and remediate errors across the whole batch. PDFix also integrates veraPDF directly in the preview and supports automated AI tagging through AI models (Docling), which Acrobat doesn’t offer natively.

Yes. PDFix SDK 9.0 is a production-ready SDK for embedding PDF/UA validation and remediation into custom applications, document factories, and CI/CD pipelines. It supports external AI actions through the PDFix Actions Marketplace, includes built-in actions like Fix Table, Fix Fonts, Fix Headings, and Fix Metadata, and ships veraPDF-style object identification.

PDFix Desktop 3.0 integrates veraPDF directly into the document preview, highlighting validation issues at the page, annotation, or content level. PDFix SDK 9.0 adds PdfObjectInfo, which resolves veraPDF-style object paths to real PDF locations (page number, MCID, content stream, bounding box) – making PDFix one of the few tools that closes the validate → locate → fix loop programmatically. Read more.

Yes. SDK 9.0 adds external action support to batch processing, so you can apply accessibility actions across thousands of files in a single CLI command.

Full release notes are available for both PDFix Desktop and PDFix SDK.

PDF/UA compliance means making sure that a PDF adheres to the rules outlined in the PDF accessibility standard. “UA” stands for Universal Accessibility. The specific ISO standard for PDF/UA is ISO 14289 – and PDF/UA is a sub-standard of ISO 32000, which is the core “how to make a PDF” specification. In short: ISO 32000 defines how to build a PDF; PDF/UA defines how to make that PDF accessible to everyone.

PDF/UA stands for PDF Universal Accessibility. It is the ISO standard (ISO 14289) that defines the rules for making PDF documents accessible to people who use assistive technologies such as screen readers, braille displays, and other accessibility tools.

PDF/UA (ISO 14289) is the accessibility standard specifically written for PDF documents, covering how content must be tagged, structured, and ordered so that assistive technology can read it correctly. WCAG (Web Content Accessibility Guidelines) is a broader standard written primarily for web content. The two standards complement each other – a PDF/UA-compliant document also goes a long way toward WCAG conformance for PDF-based content, but they are separate specifications with different scopes.

Yes. PDF/UA is the informal name for ISO 14289, the international standard for accessible PDF documents. The current widely-supported version is PDF/UA-1 (ISO 14289-1). A newer version, PDF/UA-2 (ISO 14289-2), exists but does not yet have broad tool or software support – though that is expected to change.

No – and this surprises many people. PDF/UA does not require headings to be present in a document at all. However, there is an important condition: if a document does contain headings, they must be tagged correctly as heading elements, and numbered heading levels must be sequential — you cannot skip from H1 directly to H3, for example. The same logic applies to tables of contents, hyperlinks, and fillable form fields: PDF/UA does not require them to exist, but if they do exist, they must be handled correctly.

You can check PDF/UA compliance using validation tools. Some checks – such as whether the document is tagged, whether heading levels are in sequence, and whether the document language is declared – can be done automatically by software. Other checks, such as whether the reading order makes logical sense or whether image alt text is meaningful rather than just present, require human verification. A useful reference for understanding which checks are automatic versus manual is the Matterhorn Protocol, published by the PDF Association. PDFix offers both an online validator and a desktop validation tool that covers both automatic and manual checks.

The Matterhorn Protocol is a reference document published by the PDF Association that lists all of the ways a PDF document can fail PDF/UA-1 compliance. It is an essential companion to the PDF/UA standard itself. The Matterhorn Protocol is especially useful because it clearly separates which compliance checks can be performed automatically by validation software from those that require human review. Anyone working on PDF/UA compliance – whether checking documents manually or building automated validation into a workflow – should be familiar with it.

Fixing a PDF that fails PDF/UA validation is called remediation. The process involves identifying which specific rules the document violates – using a validator – and then correcting those issues, such as adding or correcting tags, fixing reading order, or adding meaningful alternative text to images. For a small number of documents this can be done manually. For larger volumes of documents, tools like PDFix Desktop or PDFix SDK allow you to remediate documents in batches, automating much or all of the remediation work rather than fixing each file one at a time.

Most PDF/UA validation tools can only test one document at a time. PDFix is an exception – even the free PDFix Lite allows you to run batch validation across multiple documents simultaneously. This makes it possible to quickly assess a large document library: how many documents pass, how many fail, and what types of issues are most common. That information lets you plan remediation efficiently rather than discovering issues one file at a time. For batch remediation a quick fixes – not just batch validation – PDFix Desktop and PDFix SDK can automate the fixing process across large volumes of documents.

AI handles the heavy lifting – structural tagging, reading order, headings, lists, and links – and the best automated pipelines can process 70–98% of document elements without human intervention. But certain elements genuinely require human judgment: whether alt text is meaningful in context, whether heading levels reflect the actual document logic, and whether complex tables are structured so a screen reader user can follow them. The honest answer is that AI is an extremely powerful first pass, but human review on the subjective elements is still what separates a tagged PDF from a truly compliant one.

Yes, and it is happening at scale. ADA accessibility lawsuits surged 37% in the first half of 2025 alone, with over 2,000 cases filed. Under the DOJ’s revised ADA Title II rule, larger public entities (serving populations over 50,000) faced a compliance deadline of April 2026. The European Accessibility Act similarly requires accessible documents for consumer-facing services across EU member states. Organizations with inaccessible PDF backlogs face real legal exposure – and manual remediation at $3–$20 per page makes the cost of inaction compound fast.

Manual remediation by an outside vendor typically runs $3–$20 per page depending on document complexity – Ohio State University estimated $3–$4 per page just for their backlog. Cloud-based AI tools charge $1–$4 per page on a per-page model, which sounds cheaper but becomes prohibitive at scale: a 50,000-page archive can run $50,000–$200,000. The most cost-effective approach for high-volume organizations is on-premises automation with unlimited page licensing – which is exactly how PDFix is structured.

You need both, and they cover different ground. PDF/UA (ISO 14289) defines the technical structure of an accessible PDF – proper tagging, logical reading order, correct tag hierarchy. WCAG covers broader perceivability and usability criteria, including color contrast, link descriptions, and language identification. Regulators, courts, and procurement offices increasingly require conformance with both. An automated tool that only validates against one standard will leave you exposed on the other.

For organizations in healthcare, finance, legal, or government – probably not without careful review. Uploading documents to a third-party cloud platform means your content transits and resides on infrastructure you do not control, which can conflict with internal data governance requirements. On-premises or private-cloud deployment keeps sensitive documents inside your own infrastructure. This is a significant reason why enterprise organizations choose tools like PDFix that install inside your own environment rather than SaaS platforms that process your files on shared cloud infrastructure.

Because tagging and compliance are not the same thing. An AI model can attach structural tags to a PDF – headings, paragraphs, tables – but a tag existing does not mean it is correct. A heading tagged as H2 may be semantically wrong. Alt text generated by AI may describe an image literally without capturing its purpose in context. Table headers may be tagged without defining scope, breaking screen reader navigation. The PDF/UA and WCAG standards require semantic accuracy, not just structural presence. This is why validation against a tool like veraPDF after auto-tagging is not optional – it is how you find out what the AI actually got wrong.

Yes – batch processing is one of the areas where AI genuinely delivers. Modern pipelines can process entire document archives automatically, applying auto-tagging, OCR for scanned content, alt-text generation, language detection, and validation in a single scripted workflow. PDFix customers routinely automate 70–98% of processing across large backlogs, reserving human review only for edge cases and subjective elements like alt text accuracy. The key requirement is that the automation runs validation as part of the pipeline – not as an afterthought – so compliance issues are caught at processing time, not discovered later during an audit.

PDFix Desktop Pro & Enterprise and PDFix SDK API. Enterprise and volume licensing available for all.

We respond to all quote requests within 1-2 business days.

PDF/UA (ISO 14289) is the international standard for accessible PDFs. It is required for Section 508 (US federal), EN 301 549 (EU), and WCAG 2.1 compliance.

Yes. PDFix Enterprise and the SDK support automated batch workflows for tens of thousands of documents, with server-side deployment and API integration.

PDF/UA (ISO 14289) is the international standard for universally accessible PDF documents. It ensures PDFs are fully readable by assistive technologies including screen readers, Braille displays, and voice controls. Non-compliant PDFs can create legal liability under ADA, Section 508, and the European Accessibility Act. PDFix automates the remediation process to make PDFs PDF/UA compliant efficiently.

PDFix uses AI-driven layout recognition to automatically detect document structure, reading order, tables, lists, headings, and annotations. It then generates the correct PDF/UA tag structure, drastically reducing the time needed for manual accessibility remediation – cutting effort by up to 80% on most document types.

PDFix supports PDF/UA (ISO 14289), WCAG 2.1 AA, ADA Title II (including 2026 deadline requirements), Section 508 for federal agencies, and the European Accessibility Act (EAA). Both Desktop and SDK products cover all four major standards.

Yes. PDFix Desktop Pro includes batch processing for bulk PDF remediation. The PDFix SDK enables enterprise-scale automation by integrating directly into existing document workflows, CMSes, and document generation pipelines — processing thousands of documents automatically.

Yes – you can download PDFix Desktop and PDFix SDK for free and use all features without any time limit or registration. The only limitation in the free trial is that saved documents carry a watermark. This lets you fully evaluate auto-tagging, batch processing, validation, and every other feature before purchasing a license. PDFix Desktop Lite is a permanently free PDF accessibility checker – no purchase needed. It includes the industry-supported veraPDF validator, which is the standard engine used across the PDF accessibility community. It supports all major accessibility standards and profiles including PDF/UA, WCAG 2.1, WCAG 2.2, Section 508, and the European Accessibility Act, and lets you navigate directly to each detected issue in your document.

Under the updated ADA Title II rule, state and local government entities and public universities must meet WCAG 2.1 Level AA standards for digital content, including PDFs. Most compliance deadlines fall in 2026. PDFix provides specific workflows designed to help organizations meet these deadlines efficiently and at scale.

In 2026, PDFix Desktop is the most capable tool for automated PDF accessibility remediation. It is the only product on the market that combines automated AI-powered tagging with fully customizable batch processing scripts, allowing organizations to remediate thousands of PDF documents at once. Unlike first-generation manual tools such as CommonLook PDF or Axes4, or second-generation cloud tools like Equidox and Continual Engine that rely on fixed auto-tagging algorithms, PDFix Desktop Pro Enterprise lets users build their own workflow “recipe” using a modular Marketplace of AI integrations – including IBM Docling, Amazon Textract, OpenAI, and much more. It runs on Win, Mac, and Linux, supports true VeraPDF validation against PDF/UA and WCAG standards, and starts at $599 per year — making it the most cost-effective enterprise-grade solution available.

Batch processing PDFs for accessibility compliance requires a tool that can automate the remediation workflow across large document volumes without requiring manual intervention for every file. PDFix Desktop solves this with a one-to-many remediation approach: a remediator manually tags one document to establish the correct workflow, exports that workflow as a JSON script, and then runs the script to automatically remediate thousands of similar files in a batch. The exported JSON scripts can be updated at any time to incorporate the latest AI models and tools, so organizations always benefit from the newest technology without restarting their process. For developers and enterprise systems requiring backend integration, PDFix SDK — a high-performance C++ PDF library — enables automated PDF accessibility and document processing at scale across millions of pages. This is the only approach on the market that combines customizable automation with enterprise-grade volume processing.

PDF accessibility tools have evolved through three distinct generations, each solving limitations of the previous: First generation tools (e.g., CommonLook PDF, Axes4) were designed to help manual remediators work faster. They are desktop-based, PC-only applications that speed up the process of manually tagging documents but still require skilled human operators for every file. Second generation tools (e.g., Equidox, Continual Engine) are cloud-based platforms that use AI auto-tagging algorithms to reduce manual work. They are designed for non-technical teams but rely on fixed remediation models, offer no customization, and do not support third-party AI integrations. Tools like Streamline attempt to sidestep the problem entirely by converting PDFs to HTML, but downloaded files remain untagged and inaccessible. Third generation tools — led by PDFix Desktop — expand on both previous generations by enabling users to build fully customizable, scriptable automation workflows. These tools integrate a modular ecosystem of AI models, run on Windows, Mac, and Linux, support true batch processing of thousands of documents, and are continuously updated with new AI capabilities through an expanding Marketplace. In 2026, only third generation tools provide the flexibility, compliance accuracy, and volume capacity required by government agencies, enterprises, and organizations facing mandatory PDF accessibility regulations worldwide.

Most PDF accessibility remediation tools in 2026 are still limited to Windows PC only. CommonLook PDF and AxesPDF are PC-only applications, leaving Mac users without a native solution for professional remediation work. Cloud-based tools like Equidox, Continual Engine, and Streamline operate through a web browser and are therefore platform-agnostic, but they offer no customization, limited validation, and no true batch processing capability. PDFix Desktop is the only professional-grade PDF accessibility remediation tool that runs natively on PC, Mac, and Linux. This cross-platform support makes it the only choice for organizations with mixed-OS environments, Mac-based creative or publishing teams, and Linux-based enterprise or government infrastructure. The full feature set — including AI-powered batch processing, VeraPDF validation, and the modular Marketplace of integrations — is available across all three platforms with no functionality compromises.

No. While auto-tagging handles the structural framework, human verification is mandatory for semantic accuracy. Automated tools cannot reliably determine the intent of an image (Alt Text) or the logical flow of complex nested tables.

Templates allow you to remediate once, apply everywhere. By saving the tagging rules of a master document as a JSON file, PDFix applies those exact structural rules to thousands of similar files (like monthly invoices) instantly, eliminating repetitive manual work.

Missing Header Scope. Visually, a table looks correct, but without the TH (Table Header) tag and a defined Scope (Column or Row), assistive technology cannot associate data cells with their headers, making the table unreadable.

Yes – using a desktop-based Batch Processing workflow like the “Make Accessible” command allows for enterprise-scale remediation on local folders. This ensures data privacy and security because the files never leave your internal environment.

Not quite. A tool like veraPDF confirms the document meets technical machine-check requirements (tags exist, fonts are embedded). However, a manual check of the Logical Reading Order is still necessary to ensure the document makes sense when read aloud.

While 90–95% of technical tagging can be automated using PDFix layout templates, human review is still required for “semantic” elements like the accuracy of Alt-Text or complex graphs and reading orders that require subjective judgment.

The PDFix SDK is designed for high-performance enterprise environments, capable of processing tens of pages per second per CPU core, making it ideal for millions of documents.

Automated tools like veraPDF catch all machine-verifiable requirements (tags, metadata, structure). However, they cannot verify if a description actually matches an image – that remains a human task.

Build layout templates for your recurring document types in PDFix Desktop, then run batch process via PDFix Desktop Enterprise or PDFix SDK. Every output is automatically validated against PDF/UA and WCAG using integrated veraPDF. The entire process — template application, tagging, validation — runs without manual intervention per document.

PDFix SDK integrates into any workflow via Python, C++, Java, .NET, or Node.js APIs, and runs in Docker for cloud or on-premises deployment. Documents can be made accessible at the moment they are generated — with no post-production remediation required.

Yes – alongside Unicode-mapping errors (7.21.7), it repairs “font not embedded” errors (7.21.4.1-1).

ISO 14289-1 Clause 7.21.7 and 7.21.4.1, plus WCAG 2.1 Success Criterion 1.4.5.

Yes, 100% free and runs entirely on your local machine via Docker.

Yes. The PDF/UA (ISO 14289) standard explicitly requires all fonts to be embedded to ensure consistent rendering and accessibility across assistive technologies.

PDF accessibility failures are commonly caused by missing fonts, partial font embedding, broken font encoding, or non-standard Type 3 fonts. These issues prevent screen readers from accurately interpreting text and violate PDF/UA requirements.

Improperly embedded or encoded fonts prevent screen readers from correctly mapping characters to speech output. This results in unreadable or skipped content for users with visual disabilities.

Yes. Font fixing using callas technology is free for PDFix Desktop users, providing font repair at no additional cost.

PDFix automatically fixes: Glyph mapping errors Missing or unembedded fonts Partial font embedding Broken font encoding

Yes. The PDFix SDK allows developers and enterprises to integrate automated font fixing into large-scale PDF processing pipelines.

No. Proper font embedding ensures visual consistency across devices, printers, and assistive technologies without altering layout or design.

After running the Fix Fonts action in PDFix Desktop, you can run built-in PDF validation to confirm that all PDF/UA font requirements are satisfied.

Section 508 PDF compliance means ensuring PDF documents used by federal agencies, contractors, or funding recipients are accessible to people with disabilities, following WCAG 2.0 Level A and AA success criteria.

All U.S. federal agencies, federal contractors, and organizations receiving federal funding must comply with Section 508 when creating, publishing, or procuring electronic documents, including PDFs.

Section 508 requires PDFs to conform to WCAG 2.0 Level A and AA and align with PDF/UA technical requirements to ensure screen reader compatibility and proper document structure.

No. Section 508 applies to federal agencies and contractors, while ADA Title II applies to state and local governments. Both require accessible PDFs but follow different legal frameworks and WCAG versions.

Federal agencies can automate Section 508 compliance using tools like PDFix that provide AI-powered auto-tagging, WCAG and PDF/UA validation, intelligent error fixing, and batch processing.

While Section 508 references WCAG 2.0, PDF/UA is widely used as the technical standard to ensure PDFs meet structural and assistive technology requirements necessary for compliance.

Section 508 compliance is an ongoing requirement. Federal agencies must ensure all newly created, updated, and procured PDFs are accessible at all times, including ahead of the 2026 compliance enforcement focus.

ADA Title II digital accessibility requires public universities, colleges, and other state or local public education institutions to ensure all digital content, including PDFs and course materials, is accessible to people with disabilities under WCAG 2.1 Level A and AA.

ADA Title II applies to public universities, state colleges, community colleges, public graduate schools, multi-campus state systems, and public online education programs operated by state or local governments.

Public educational institutions serving populations of 50,000 or more must comply by April 24, 2027. Institutions serving fewer than 50,000 people must comply by April 26, 2028.

ADA Title II requires academic PDFs to meet WCAG 2.1 Level A and AA success criteria, including proper document structure, logical reading order, alternative text, accessible tables, forms, metadata, and language specification.

ADA Title II references WCAG 2.1, but PDF/UA is widely used as the technical standard to ensure PDFs meet structural and assistive technology requirements necessary for WCAG conformance in academic documents.

STEM PDFs containing equations, formulas, diagrams, graphs, and tables must be made accessible using proper tagging, structure, alternative text, and assistive technology compatibility to meet WCAG 2.1 requirements.

Common failures include untagged or scanned PDFs, missing alternative text, poor reading order, inaccessible tables and forms, missing document titles, undefined language, and inaccessible mathematical content.

Universities can automate compliance using tools like PDFix that provide AI-powered auto-tagging, WCAG and PDF/UA validation, intelligent remediation, batch processing, and centralized compliance reporting.

ADA Title II digital accessibility requires state and local governments to ensure that all digital content, including PDF documents, is accessible to people with disabilities in accordance with WCAG 2.1 Level A and AA standards.

ADA Title II applies to state and local government public entities, including agencies, courts, municipalities, counties, public libraries, public universities, and special district governments that provide services, programs, or activities to the public.

Public entities serving populations of 50,000 or more must comply by April 24, 2026. Public entities serving fewer than 50,000 people and special district governments must comply by April 26, 2027.

ADA Title II requires PDFs and other digital documents to conform to WCAG 2.1 Level A and AA success criteria, including proper structure, reading order, alternative text, accessible forms, and metadata.

No. ADA Title II applies to state and local governments, while Section 508 applies to federal agencies and federal contractors. Both require accessible PDFs but follow different legal frameworks and standards.

All digital content used in government services, programs, or activities must be accessible, including PDFs, forms, court documents, reports, notices, spreadsheets, and presentations.

Common failures include missing or incorrect tags, improper reading order, missing alternative text, inaccessible forms, missing document titles, undefined language, and improperly structured tables.

Governments can automate compliance using tools like PDFix that provide AI-powered auto-tagging, WCAG and PDF/UA validation, intelligent error fixing, batch processing, and audit-ready reporting.

PDF compliance means ensuring PDF documents meet technical accessibility standards and legal accessibility requirements so they are usable by people with disabilities and meet regulatory obligations such as ADA, Section 508, WCAG, PDF/UA, and the European Accessibility Act.

PDF compliance reduces legal risk, supports procurement requirements, improves access for people using assistive technologies, and ensures organizations meet mandatory accessibility laws while scaling document accessibility efficiently.

PDF accessibility compliance is defined by WCAG 2.1 and 2.2 success criteria for content accessibility and PDF/UA (ISO 14289), which specifies the technical structure required for accessible PDF documents.

Key laws and regulations requiring PDF compliance include ADA Title II for state and local governments, Section 508 for federal agencies, and the European Accessibility Act (Directive 2019/882) for digital products and services in the EU.

WCAG defines accessibility requirements for content, while PDF/UA defines how a PDF must be technically structured to support that content. Both are required for fully accessible and regulation-ready PDF documents.

Organizations check PDF compliance using accessibility validation tools that test PDFs against WCAG and PDF/UA standards, identify specific failures, and generate detailed compliance reports.

Government agencies, educational institutions, healthcare providers, financial institutions, legal organizations, and public-sector vendors rely on PDF compliance software to meet accessibility laws and procurement requirements.

The April 24, 2026 ADA deadline requires public entities serving 50,000+ people – including state governments, counties, cities, and public universities – to ensure all digital content, including PDF documents, complies with WCAG 2.1 Level AA. This includes proper tagging, reading order, alternative text, form accessibility, and logical structure.

WCAG 2.1 Level AA is the middle conformance level, including all Level A and AA requirements, and represents what many organizations strive to meet as it balances accessibility with practical implementation. For PDF documents, this means: Proper semantic structure Alternative text Correct reading order Color contrast Document language Keyboard accessibility Form field labels Federal data shows that among government PDF downloads, 77% were PDFs, but only 20% of those PDFs were compliant with Section 508 standards.

Manual PDF remediation doesn’t scale to meet the volume demands most government agencies face. Automation through tools like PDFix provides a more efficient solution: Key automation capabilities: Auto-fix features: Automatically correct common accessibility errors while experts focus on complex issues Auto-tagging: Automatically analyzes document layout and applies semantic tags Batch processing: Process thousands of PDFs securely on-premises at tens of pages per second per core Built-in validation: Real-time compliance checking against Section 508, WCAG 2.1/2.2, and PDF/UA standards

PDFs are often complex, high-volume, and sourced from Word, InDesign, scanned documents, or third-party systems – making them inconsistent and difficult to remediate manually. Tagging tables, forms, multi-column layouts, charts, and long documents can take 15–30 minutes per page. PDFix eliminates this strain by automatically generating structure, detecting layout elements, adding alt text, and validating compliance instantly.

USCIS uses PDFix Desktop for auto-tagging, WCAG validation, and on-premises batch remediation of millions of immigration documents. The Federal Reserve integrates PDFix SDK into its internal systems to process thousands of long, scanned financial PDFs securely, using OCR, intelligent tagging, and per-core parallel processing. Both agencies achieve Section 508 and WCAG compliance without exposing sensitive data to external vendors.

PDFix provides fully local, on-premises accessibility automation – ideal for agencies handling confidential or regulated content. Features include AI auto-tagging, batch processing, document templates, built-in veraPDF validation, and customizable SDK workflows. This ensures fast, consistent, and secure compliance across high-volume PDF collections, reducing cost, eliminating outsourcing risks, and enabling sustainable accessibility ahead of the 2026 ADA deadline.

In PDFix Desktop, select the Figure, Table, or Formula tags in the Tag panel, then run the matching AI action – Set Alternate Description for images, Generate Table Summary for tables, or Generate Formula MathML for equations. Each action connects to a chosen AI model (OpenAI or BLIP) and writes the result directly into the tag. The same actions are available programmatically through PDFix SDK for batch processing.

It means the validator found a Link or other annotation missing a Contents entry, which PDF/UA and WCAG require so screen readers can announce the annotation’s purpose. Fix it with the Set Annotation Contents action, or manually add the Contents key in the Annotation Properties panel.

It flags a <Figure> tag with no Alt entry. You can resolve it through manual tagging, a layout template with predefined Alt values, or an AI action such as Set Alternate Description (OpenAI/BLIP).

Yes. PDFix SDK exposes the same alt text, table summary, and MathML actions available in PDFix Desktop programmatically, so you can generate and apply alternate descriptions across hundreds of PDFs in a server or pipeline environment.

Font Fix (callas software) repairs four categories of font compliance failures: missing font embeddings (fonts referenced in the PDF but not included in the file), CID font errors (broken character identifier structures), encoding table failures (incorrect or missing tables that cause garbled text extraction), and glyph structure problems (malformed glyph definitions that cause rendering or validation errors). It also applies controlled font substitution where original font embedding is not possible.

Font Fix (callas software) addresses compliance requirements for both PDF/UA-1 (ISO 14289-1) and PDF/A (ISO 19005). PDF/UA requires that all fonts used in an accessible PDF are properly embedded and have complete encoding data. PDF/A additionally requires that fonts be fully embedded for long-term archival fidelity. This action is the only PDFix Marketplace font repair action that covers both standards.

Use in PDFix Desktop is free and unlimited. Building Font Fix (callas) into an automated workflow using PDFix SDK requires a callas software license for commercial deployment. For licensing information, contact the PDFix sales team.

No. The action runs entirely on your local machine inside a Docker container. No document data is transmitted to callas software, PDFix, or any third party during processing.

Both actions repair PDF font accessibility issues, but they use different engines and address different problem depths. Font Fix (PDFix) uses OCR to recover missing Unicode mappings – it is 100% free, fully open-source, and ideal for documents where glyphs display correctly but lack machine-readable character data. Font Fix (callas software) uses the professional callas pdfToolbox engine and handles a broader range of structural font failures including missing font embeddings, CID errors, encoding table failures, and glyph structure problems. It also supports PDF/A compliance in addition to PDF/UA. If your documents fail validation due to Unicode mapping gaps only, Font Fix (PDFix) is sufficient. If your validation reports missing embeddings, CID errors, or encoding failures, Font Fix (callas software) is the appropriate tool. For the most complex documents, running both actions in sequence is also a valid approach.

Yes. PDFix integrates Docling as a free AI action with no per-document fees, so you can batch-process unlimited PDFs at no extra cost beyond PDFix Desktop and Docker.

No. Once the Docker container is pulled during setup, Docling runs entirely on your own machine — documents never leave your network and no cloud upload is required.

It’s built to produce PDF/UA- and WCAG-compatible output: heading hierarchy (H1–H6), correct reading order, tagged tables (including merged cells), lists, and figures.

Yes. PDFix also integrates PaddlePaddle AI and Amazon Textract as alternative auto-tagging engines, so you can pick the best fit for a given document type or workflow (local vs. cloud).

Docling is an open-source AI toolkit developed by IBM Research for document understanding and analysis. It uses the RT-DETR object detection architecture to analyze PDF page layouts, identifying structural elements such as headings, paragraphs, tables, figures, and lists. The PDFix integration uses the Docling model to drive automatic PDF accessibility tagging.

PDF tagging is the process of adding a logical structure tree to a PDF document that describes the type and reading order of each content element. Tags allow screen readers, braille displays, and other assistive technologies to correctly interpret document content. Without tags, a PDF is effectively inaccessible. PDF/UA (ISO 14289) requires that all PDFs intended for public use be fully tagged.

No. After the initial Docker image download, the action runs entirely offline on your local machine. No document data is transmitted to IBM, PDFix, or any third party.

AutoTag (Docling) processes the PDF and writes a complete accessibility tag structure directly to the file in a single step. Use this for one-off documents or when immediate output is the priority. Create Layout Template (Docling) takes a different approach: instead of tagging the PDF directly, it analyzes the document layout and generates a reusable JSON template file describing the page structure – heading regions, table boundaries, body text areas, footer zones. You can review and adjust this template in PDFix Desktop before applying it. The key advantage is reusability: once a template exists for a given document format, the same template can be applied to every future version of that document automatically, with no repeated work. This makes Create Layout Template the right choice for recurring documents such as monthly reports, standardized forms, or any document series where the layout is consistent across versions. Learn more about PDFix Layout Templates →

Both actions auto-tag PDFs, but they differ in cost, privacy, and use case. Docling is 100% free, open-source, and runs entirely locally – making it suitable for sensitive or regulated documents with no per-document cost. Amazon Textract is a cloud-based service that requires an AWS account, sends documents to Amazon’s servers for processing, and is billed per page. Textract can offer advantages for scanned or low-quality documents where cloud OCR accuracy is a priority.

You use your own OpenAI account and API key. OpenAI usage is not included in the PDFix license. PDFix simply connects to your OpenAI API key, so: You need your own OpenAI subscription/account. You can limit and monitor your own usage and costs. All billing for OpenAI runs through your own OpenAI account, not PDFix.

Processing time depends on which method you use: Template-based methods: These run purely on the machine using PDFix’s own layout rules. They are very fast – typically, you can process many pages per second and large batches of files efficiently. Local AI models: Speed depends on the performance of your machine and the specific model. BLIP, as integrated in PDFix Desktop, is quite fast and provides good results, but it’s still naturally slower than pure template processing because each image is actually sent to and processed by the AI model. Cloud AI models: Speed depends on your internet connection, the chosen model, and the AI’s response time.

Right now, Docker is the primary way to integrate External Actions (including AI models like Docling) with PDFix Desktop. Why Docker: You only need to get approval for one application (Docker) instead of many separate tools. It simplifies the installation of complex AI tools that have many dependencies. It lets you run multiple different AI models on the same machine without managing conflicting dependencies manually.

Yes. This is exactly what the local AI models are for. You can use offline AI actions, such as BLIP (for image descriptions) or Paddle (for math formulas and other tasks) and other local models available as External Actions. These run completely locally on your machine, even without an internet connection, so: No document data or images are sent to the cloud. You keep all content on-premise, which is ideal for confidential or regulated data. If you choose to use OpenAI or other cloud-based AI, your data will be sent to that provider’s servers.

Yes – this is already possible. The AI models and External Actions demonstrated (via Docker) can also be run as command-line processes. Docker is used as a CLI tool, not a continuously running service. You can design a workflow where: You run PDFix CLI to process PDFs You run Docker-based AI actions as additional command-line steps You chain these commands in scripts/batch jobs to automate full pipelines If you need help setting this up, PDFix can provide examples, resources, and guidance on integrating AI actions with your PDFix CLI workflows.

At the moment, there is no built-in, ready-to-use feature in PDFix Desktop that automatically detects repeated identical images, and reuses a single AI result for all occurrences. However, this scenario can be handled with a custom solution: A separate application or script that identifies duplicate images That custom tool then calls the AI once per unique image and applies the same alt text to all duplicates In some workflows, if repeated images are purely decorative, you might choose to artifact the duplicates and describe only one instance – but that depends on accessibility requirements and document semantics. So: no automatic duplicate-detection/reuse yet, but it’s technically feasible via a custom integration.

Yes, this is fully supported and is often the recommended approach. Example workflow: First pass – template/basic actions Use template-based functions like Set Alternate Description or Set Actual Text to automatically set alt text for images you can clearly define with rules and target specific images by size, position, page number, or other template rules. AI actions After the first pass, some images still won’t have alt text. Then you run an AI action (e.g., BLIP, OpenAI) on the remaining images. Let AI generate descriptions only where templates didn’t already set alt text. You can also bundle this into a single custom workflow/action in PDFix: Action step 1: Set Alternate Description (template-based). Action step 2: Set Alternate Description (OpenAI) or another AI model. This combined workflow can then be run on a single document, or in batch mode across many PDFs, so the mixed strategy is fully automated.

Yes. PDFix Desktop’s point-and-click interface auto-tags PDFs using basic detection, Preflight-generated templates, AI-generated templates, or pre-defined JSON templates — no programming required. Developers who need code-level or CI/CD integration should use PDFix SDK instead.

For complex, non-standard layouts, use an AI-generated layout template (via external AI actions like Amazon Textract). For repeated layouts — invoices, bank statements, standardized reports — build a pre-defined JSON template once and reuse it for consistent, predictable tagging across the whole batch.

PDFix Desktop suits accessibility specialists and non-developers doing visual, batch, or manual-review tagging. PDFix SDK suits developers building auto-tagging into code (Python, C++, Java, .NET) for CI/CD pipelines or processing millions of documents.

Yes – with PDFix SDK developers can integrate the same auto-tagging logic directly into workflow pipelines, document management systems, or automated PDF generation processes.

PDF/UA (Universal Accessibility), defined by ISO 14289-1, is the standard for making PDF documents fully accessible for people using assistive technologies (e.g. screen readers). It ensures that the document’s structure (tags, reading order, semantics) is correctly defined so that users can navigate, read, and interact with content. Without PDF/UA compliance, a PDF might appear visually correct but remain inaccessible in practice.

Different validators can interpret the PDF/UA or WCAG rules differently, implement distinct logic, or cover different subsets of validation rules. Each tool may apply different heuristics or fallback logic for complex cases. Some rules require human judgment, which can’t be fully automated. Rule coverage, severity thresholds, and error reporting formats differ. As a result, it’s common for one validator to flag an issue another overlooks. The inconsistencies don’t mean one is wrong — they reflect variation in implementation.

No. Automated tools can detect many structural, tagging, and rule-based issues, but they cannot fully assess context, meaning, or design intent (e.g. whether alt text conveys the right meaning, or whether the reading order truly matches human expectations). Thus, best practice is to combine automated validation with manual review and human expert checks.

There is no one-size-fits-all best validator. Popular tools include veraPDF, PAC, Adobe Preflight PDF/UA, or CommonLook PDF Validator — each with its own strengths and trade-offs in rule coverage and reporting depth. Using multiple validators in tandem is often recommended to cross-check results, compare error reports, and complement them with manual review.

When reading a validation report, consider: Re-test — after remediation, re-run validators and compare reports to ensure improvements. Severity & context — not all flagged issues are equally critical. Focus first on errors (not just warnings). Rule descriptions vs. tool-specific explanations — understand the underlying standard (e.g. ISO 14289, WCAG) rather than relying solely on the tool’s wording. Prioritize fixes — address structural, tagging, and navigation issues first. Then refine alt text, reading order, metadata, etc.

BLIP – Bootstrapping Language-Image Pretraining – is an open-source vision-language model developed by Salesforce Research. It is trained to understand and describe image content in natural language. The PDFix action uses the BLIP-large variant, which offers higher description accuracy than the base model.

No. The BLIP model runs entirely on your local machine inside a Docker container. No image data is transmitted to Salesforce, PDFix, or any third-party service. This makes it suitable for use with confidential or regulated documents.

BLIP-large produces accurate descriptions for photographs, diagrams, and general figures. For highly specialized technical images – such as engineering schematics, medical scans, or complex charts – the generated descriptions should be reviewed by a human before finalizing. PDFix Desktop allows you to edit any generated alt text before saving.

Both actions generate alt text for PDF images, but they differ in cost and data handling. The Salesforce BLIP action is 100% free and runs entirely on your local machine with no data leaving your environment. The OpenAI action connects to the OpenAI API, requires an API key, and is billed per use – but can produce more nuanced descriptions for complex or context-dependent images.

PDFix services are priced per project based on scope, document complexity, and volume. There is no standard rate card – every engagement is different. Submit a brief via the contact form below and our EU or US team will provide a tailored quote, typically within hours. There is no obligation with a quote request.

A PDF auto-tagging template is a reusable configuration that teaches the PDFix engine how to recognize and correctly tag specific document structures – column layouts, header hierarchies, table patterns, footnotes, figure captions – for a particular document family. Once built, the template enables fully automated PDF/UA-compliant tagging for every document of that type, with no manual tagging per document. For organizations with thousands of similar PDFs (government forms, bank statements, academic papers), this is the highest-ROI service PDFix offers – typically reducing per-document effort by 80% or more.

Yes. ADA Title II 2026 deadline preparation is one of the most common consulting engagements. PDFix helps US government agencies and public universities assess their document backlog, prioritize remediation, build automated workflows for recurring document types, and implement validation processes — specifically targeting WCAG 2.1 Level AA compliance required by the April 2026 deadline. Learn more about ADA Title II →

Yes. PDFix has a European headquarters in Slovakia and provides development services specifically for EAA (EN 301 549) requirements. Our EU team understands both the technical PDF/UA standard and the regulatory context for European organizations. A single PDFix engagement can cover both EU and US compliance requirements simultaneously.

PDFix Desktop and SDK are software that your team uses independently to check and remediate PDFs. PDFix Services is when our expert team works directly with you – building templates for your document types, integrating the SDK into your systems, reviewing your implementation, or training your staff. Services complement the software for organizations that need specialist knowledge or custom development rather than (or in addition to) a self-service tool.

Not necessarily. Consulting engagements can be standalone – we can review your existing accessibility workflow regardless of tooling. However, template creation produces templates that work with PDFix Desktop or SDK, so those products are required to use the deliverables. Custom development is typically built on PDFix SDK. In most cases, the software cost is a small fraction of the efficiency gains from the service.

PDFix SDK is an enterprise-grade PDF accessibility library that lets developers automate PDF/UA compliance, WCAG 2.2 remediation, auto-tagging, and structured content extraction. It runs fully on-premises, integrates into existing document management systems and CI/CD pipelines, and supports Python, C#, Java, C++, and Node.js.

PDFix SDK Lite is permanently free – no registration, no time limit. It includes PDF rendering, reading PDF objects, content extraction, and metadata reading. Commercial tiers (Basic, Professional, Enterprise) are priced by instance count – request a quote for exact pricing tailored to your deployment scale.

Fix SDK officially supports Python, C# (.NET), Java, C++, and Node.js. Complete code examples and documentation for all five languages are available on GitHub. The SDK also supports command-line integration for shell-based automation and CI/CD pipelines.

PDFix SDK is fully on-premises – no document data is transmitted to PDFix servers or any cloud service. All processing happens locally within your infrastructure. This is a core architectural principle, which is why federal agencies including USCIS and the Judicial Council of California trust PDFix SDK for sensitive document processing under strict data residency requirements.

Yes. PDFix SDK is designed for enterprise batch processing at scale. Customers process millions of PDFs monthly using PDFix SDK integrated into their document management workflows. The SDK’s architecture supports multi-threaded batch processing, worker queue integration, and deployment in containerized environments (Docker/Kubernetes). See the PDFix Actions Marketplace for pre-built automation actions.

Yes. PDFix Desktop Lite is permanently free – no time limit, no registration, no credit card required. It includes a full PDF accessibility checker powered by veraPDF, supporting WCAG 2.1, WCAG 2.2, PDF/UA (ISO 14289), Section 508, and the European Accessibility Act. Download it now for Windows, macOS, or Linux. PDFix Desktop is fully featured in the free download – no time limit, no registration, no credit card required. Desktop Pro and Enterprise feature works immediately: auto-tagging, batch processing, full remediation, PDF conversion, veraPDF validation – all accessibility features. The only limitation is that documents saved with the free version carry a watermark. Purchase a license to remove the watermark for production use.

PDFix Desktop Pro costs €350 per user per year or $599 per user per year for US customers. It includes everything in Lite plus: AI-powered auto-tagging, full PDF remediation and accessibility fixes, table and list structure editing, reading order management, PDF conversion, layout template configuration, and custom commands. It is designed for accessibility specialists and compliance teams who need to remediate PDFs automatically and efficiently.

The key difference is batch processing. Enterprise adds the ability to process hundreds or thousands of PDFs automatically – no manual file-by-file work. If your team remediates more than ~50 documents per week, Enterprise typically pays for itself quickly.

Yes. PDFix Desktop runs natively on Windows, macOS, and Linux – all three platforms at no extra cost. This makes PDFix unique: most PDF accessibility tools are Windows-only or web-based SaaS. If your team uses mixed operating systems or requires a Linux server environment, PDFix is the only desktop solution that covers all three.

Adobe Acrobat Pro is a general PDF editor with accessibility tools added on. PDFix Desktop is purpose-built for PDF accessibility remediation, with AI-powered auto-tagging that significantly reduces manual effort. Key PDFix advantages: cross-platform (Mac/Linux support), fully on-premises (no cloud), batch processing in Enterprise tier, and lower per-user cost for dedicated compliance teams. Adobe is better for general document creation; PDFix is better for systematic, standards-driven remediation workflows.

No. PDFix Desktop is fully on-premises – your documents never leave your computer or network. There is no cloud upload, no SaaS processing, and no telemetry on document content. This is why agencies like USCIS and the Judicial Council of California trust PDFix for sensitive and classified documents. For GDPR, FISMA, and HIPAA-constrained environments, PDFix is the correct choice.

Under the updated ADA Title II rule, most US state and local government entities and public universities must achieve WCAG 2.1 Level AA compliance for digital content – including PDFs – by April 24, 2026 (large entities) or April 26, 2027 (smaller entities). PDFix Desktop’s batch processing and auto-tagging capabilities are designed specifically to help organizations remediate large legacy document repositories before this deadline.

PDFix SDK auto-tags PDFs with a single call – doc.AddTags(PdfTagsParams()) in Python, or pdfix_app add-tags from the command line. For better structure, generate a layout template first (via Preflight, an AI model, or a pre-defined JSON file) and load it before tagging.

Yes. PDFix SDK exposes auto-tagging programmatically through Python, C++, Java, and .NET bindings, plus a Command-Line Tool, so you can integrate it into scripts, CI/CD pipelines, or backend services rather than tagging documents by hand.

A PDF accessibility SDK is a developer toolkit for adding the structure tags, reading order, and metadata a PDF needs to meet PDF/UA and WCAG standards. PDFix SDK covers auto-tagging, alt text, table summaries, and MathML generation, and integrates with validators like veraPDF to check the result.

Yes. All four auto-tagging methods in this guide include a Python code example using the pdfixsdk package, alongside an equivalent Command-Line Tool command.

It means a validator checked whether a <Figure> tag has an Alt entry describing its content. Charts, graphs, photos, and scanned images all need this — without it, screen readers skip the figure entirely, which fails PDF/UA and WCAG checks.

A Figure tag marks an image, chart, or graphic as a distinct structural element in a tagged PDF, separate from surrounding text. PDF/UA requires every Figure tag to carry an Alt (alternate description) attribute so assistive technology can convey its content or meaning.

In PDFix, open the figure’s Tag Properties and either type a custom description, reuse text from a nearby caption or heading, or extract text from behind the figure’s bounding box. For images without obvious source text, an external AI action (OpenAI or BLIP) can generate a description automatically.

Yes. PDFix’s external AI actions analyze a figure’s visual content and suggest an alt text description — you can run this on a single figure or across an entire batch of files, then review and refine the results before finalizing.

PDF/UA (PDF/Universal Accessibility) is the ISO standard (ISO 14289) that defines how PDFs must be structured to be accessible to people using assistive technologies such as screen readers. PDFix Desktop includes a built-in PDF/UA validator to ensure every document meets both PDF/UA and WCAG requirements, helping organizations achieve accessibility compliance faster.

Desktop Pro (350 €): Designed for professionals and small teams. Includes AI-powered auto-tagging, remediation tools, layout template mapping for complex documents, PDF conversion, and custom accessibility commands. Desktop Enterprise (1 000 €): Includes all Pro features, plus advanced tools for high-volume document processing with batch automation – ideal for organizations handling large numbers of PDFs every week.

Yes. Both Pro and Enterprise editions of PDFix Desktop include all minor updates and improvements. This ensures you always have the latest features and compliance checks without extra costs.

Yes. You can download a free trial of PDFix Desktop to explore auto-tagging, OCR for image-based or scanned PDFs, AI-driven remediation features, and PDF/UA compliance validation before upgrading to the full license.

Amazon Textract is a machine learning service developed by Amazon Web Services that automatically extracts text, tables, forms, and document structure from PDFs and images. Unlike basic OCR, Textract identifies the logical structure of a document – understanding which text is a heading, which is a table cell, and what the reading order should be. PDFix converts this structural output into a conforming PDF accessibility tag tree.

Yes. This is Textract’s primary advantage over local auto-tagging models. Amazon Textract processes both native digital PDFs and scanned image-only documents, applying AWS’s cloud OCR models to extract text and structure even from low-quality or photographed pages. For scanned document archives that local tools struggle to process reliably, Textract is the recommended auto-tagging action.

Amazon Textract pricing is based on the number of pages processed and the features used. Pricing varies by AWS region and document type. New AWS accounts receive limited Free Tier access each month for initial testing. For production volume pricing, refer to the Amazon Textract pricing page on AWS. There is no additional PDFix fee for using this action beyond standard PDFix Desktop or SDK licensing.

Yes. This is a cloud-based action. Documents are transmitted to Amazon Web Services infrastructure in your selected AWS region for processing. If your documents contain sensitive or regulated data, review AWS’s data handling and compliance policies before use. For workflows where data cannot leave your local environment, use the Auto-Tag PDF (Docling IBM) action instead, which runs entirely on your machine.

Both actions auto-tag PDFs for accessibility but are designed for different scenarios. Docling IBM is 100% free, open-source, and runs entirely on your local machine – no data leaves your environment and there is no per-page cost. It is the right choice for most native digital PDFs, privacy-sensitive documents, and workflows where cost control is a priority. Amazon Textract is a paid cloud service that excels where Docling is limited: scanned or image-based PDFs, documents with degraded quality, and high-volume enterprise environments where cloud scalability and zero local compute are requirements. For organizations already using AWS infrastructure, Textract also integrates naturally into existing cloud workflows. When in doubt, test both actions on a sample document and compare output quality for your specific document type.

Accessible reports ensure that employees, clients, and partners with disabilities can use the information. Beyond inclusivity, it also protects companies from compliance risks under PDF/UA, WCAG, and Section 508.

Use a layout template that tags headings, tables, and reading order once, then apply it to every budget report your system generates. This keeps you aligned with Section 508 and WCAG without manually retagging each PDF.

Standardize on one accessibility-tagged template for all outgoing reports – financial, project, or KPI – so every version distributed to staff works with screen readers from the moment it’s generated, not after a manual fix.

Define your accessibility rules once in a layout template (headings, table headers, alt text for charts), then apply that template automatically to each new export. PDFix uses fixed properties, floating anchors, or AI-powered recognition to detect and tag elements consistently.

Yes — the cost driver is manual, per-file remediation, not accessibility itself. A single reusable template removes the need for one-off fixes or dedicated accessibility staff, cutting both the cost and the turnaround time.

Not at all. Templates work for client-facing business reviews, weekly sales reports, high-volume invoices, bank statements, annual sales reports, and annual financial statements.

PDF/UA requires heading levels to descend in order – H1, then H2, then H3, with nothing skipped (e.g., H1 straight to H3 fails). In PDFix, this usually means your template or AI-detected rules mis-assigned a level. Review the generated heading tree after Auto-Tag and correct any gaps before publishing.

PDF/UA-1 requires the very first heading in the document’s structure to be tagged H1, even if it’s styled smaller than other text. If your template or Preflight rule tagged the opening heading as H2 or lower, fix that mapping first — everything downstream depends on it.

This means the document uses both numbered heading tags (H1–H6) and generic H tags in the same file — PDF/UA doesn’t allow mixing the two conventions. Pick one approach (numbered is the standard PDFix uses) and make sure every template rule, Preflight pass, and AI-generated tag applies it consistently.

n PDFix, you can add headings manually (select text, right-click, “Add to Template,” assign H1/H2/etc.), automatically via the Preflight tool (detects levels from font size, style, and frequency), or with AI-powered recognition using PaddleOCR, Amazon Textract, or an LLM. All three feed into the same Auto-Tag step.

Yes. Each page is first rendered as an image before Textract analyzes it, so the workflow handles scanned and image-based documents the same way it handles native PDFs.

Page images are sent to Amazon Textract’s cloud servers for analysis, so this workflow relies on AWS’s security and compliance posture rather than running fully offline. If 100% local processing is a requirement, PDFix’s Docling AI integration is the local alternative.

Yes. Once PDFix generates a JSON template from Textract’s output, it can be reused across similar documents, which is what makes batch tagging thousands of files practical.

All three are valid paths in PDFix — the built-in engine needs no external service, Textract is a strong cloud-based OCR option for complex forms and tables, and PaddlePaddle is a multilingual, open alternative. Which one fits best depends on your document types and whether cloud processing is acceptable for your workflow.

Open the PDF in PDFix Desktop. Go to Actions → Make Accessible (includes Auto-Tag, sets Language & Title, creates Bookmarks, embeds Fonts for PDF/UA compliance). Open the Validation side panel and click Validate (PDF/UA-1). Apply Auto-Fix or Quick Fix, use manual edits if needed, then validate again until status is Passed.

Make Accessible is an automated one-click workflow that clears old structure, runs Auto-Tag (or Auto-Tag with Paddle AI), sets Document Language and Title, creates Bookmarks, embeds Fonts, and prepares the file for PDF/UA validation and fixes.

Auto-Tag quickly builds a semantic tag tree. Make Accessible runs Auto-Tag plus key metadata and font embedding steps — making it the best starting point for fast PDF/UA results.

In the Template side panel you can define rules for headings, tables, figures, reading order, and artifacts. Templates standardize recognition and boost accuracy on complex layouts. Use them to fine-tune detection when Auto-Tag alone isn’t perfect.

Open the Validation side panel. Click Validate (PDF/UA-1) or Validate With to select a profile. Review results, apply Auto-Fix or Quick Fix, and re-validate until Passed.

Yes. In the document view, choose Run Action → Accessibility → AutoTag( Paddle), or AutoTag(AmazonTextract) to try an alternative AI-powered engine that can improve detection on certain layouts. We’re constantly adding new models, which you can find in our marketplace.

Auto-Fix provides one-click repairs for frequent problems. Quick Fix offers targeted commands for specific issues such as missing language or bad list structure. Manual Fix can be used for complex issues via the Tag Tree, Bookmarks, Content, or Annotations panels.

After Auto-Tag or Make Accessible, open the Tag Tree and Content panels to verify order from top to bottom. You can even convert PDFs to HTML to preview the reflowable layout and verify the correct reading order.

PDFix detects many decorative items and marks them as artifacts automatically. If something is missed, select the object in the Content panel and mark it as Artifact.

If an image is decorative, mark it as an Artifact instead of adding alt text. In the Tag Tree, select the Figure tag and add concise, meaningful Alt text. You can also run an action to automatically add alt text to images using PDFix, OpenAI, or Saleforce BLIP. We’re constantly adding new models, which you can find in our marketplace.

It means a validator checked whether a PDF annotation (link, highlight, comment, etc.) has a Contents entry that assistive technology can read. If it’s missing, empty, or generic, the annotation fails PDF/UA and WCAG checks — fix it by setting real descriptive text via the Set Annotation Contents action.

Form field widgets use a TU (tool tip / user name) key instead of a Contents key for their accessible description — e.g., “Enter your email address” for a text field, or “Click to Submit” for a button. PDFix Desktop sets this automatically from custom text or layout-based content.

The annotation technically has a Contents key, but it contains only spaces or blank characters — which validators treat the same as missing alt text, since a screen reader has nothing meaningful to announce. Fix it by re-running Set Annotation Contents with Overwrite enabled so the blank value gets replaced with real text.

Use the Set Annotation Contents action’s “Text from annotation bounding box” option to pull the visible text for highlights and underlines, or “Action destination” for links, which describes where the link goes (e.g., “Go to Page 4” or “Open external URL”).

The most scalable way to auto-tag structured PDFs is by using a template-based layout recognition system like PDFix. You define a single JSON file that tells the engine what to tag and where, then apply it across thousands of files without manual editing.

Yes. PDFix supports automatic PDF/UA-compliant tagging using semantic elements (<h1>, <p>, <table>, etc.). With the right JSON template, you can generate accessible documents that pass compliance checks without manual tagging. Read more about PDFix Template logic – a rule based layout engine defined in JSON.

The template is a JSON configuration file that defines elements by position, text pattern, style, or anchors. PDFix SDK uses this file to recognize and tag structures like headers, tables, and footers across any number of PDF files. Read more about Layout Template.

Yes, it’s ideal. Bank statements and invoices usually follow a predictable layout. PDFix templates are perfect for batch-tagging structured documents like monthly financial reports, utility bills, or receipts.

Absolutely. The PDFix SDK can be embedded into any document automation pipeline (Windows, Linux, or cloud-based). Deutsche Bank, for example, integrated it without disrupting their existing workflow.

You can use PDFix Desktop for visual layout analysis and template creation, then run batch operations using the PDFix SDK CLI or your own script. No coding is needed to start.

You’ll find all working examples on GitHub under PDFix_SDK_Example_Templates.

You can use Set Content Color action in PDFix Desktop to automatically adjust fill and stroke colors of PDF objects. This helps improve readability and meet accessibility standards without manual editing.

Yes. With PDFix Desktop, you can define rules to change colors across text, paths, and shapes in bulk using a JSON template. This is ideal for correcting entire documents quickly.

It’s a new PDFix action that lets you apply custom color filters to content based on type, fill, stroke, or other properties. Also, you can selectively target and change colors using the object_update.

Use the Set Content Color feature to ensure proper color contrast (as defined by WCAG guidelines). This is a critical step for creating WCAG and PDF/UA-compliant documents that support screen readers and low-vision users.

Yes. You can define filter rules in JSON to match only specific fill and stroke color values (e.g., red 255,0,0) and update them to new colors (e.g., black 0,0,0), ensuring accurate and consistent adjustments.

PDFix supports updates to any page object – including text, paths, and vector graphics – defined via the object_types parameter in your template. You can match based on color, object type, or custom filters.

Absolutely. PDFix’s Set Content Color is designed to integrate with PDF remediation pipelines. It’s especially useful for organizations working on accessibility at scale – such as banks, finance, government agencies, and digital publishers.

The U.S. Department of Justice (DOJ) has finalized new ADA Title II web accessibility rules. Smaller entities and special districts: must comply by April 26, 2027.These deadlines apply to websites, mobile apps, and digital documents — including PDFs. Large entities (50,000 + population): must comply by April 24, 2026.

Yes. The DOJ explicitly includes PDF documents under ADA Title II. Any downloadable or online PDF must be accessible to screen readers and follow WCAG 2.1 criteria, such as proper tags, alt text, and logical reading order.

Use PDFix Desktop to auto-tag and repair existing PDFs, or PDFix SDK to integrate accessibility directly into your workflow.. The tools analyze document structure, detect headings and tables, and apply accessibility tags automatically – reducing manual remediation time while ensuring PDF/UA and WCAG compliance. Explore real-world results to see how Board of Governors of the Federal Reserve System and U.S. Citizenship and Immigration Services use PDFix to automate compliance at scale.

Educational institutions can use PDFix Desktop to tag syllabi, course materials, and administrative forms. For large volumes, PDFix SDK allows automated remediation directly in existing learning management systems (LMS) and campus workflows — helping schools meet WCAG compliance faster. Read more in our University Case Study to see how PDFix streamlines accessibility at scale.

PDFix actions are designed to meet PDF/UA (ISO 14289-1), WCAG 2.1 and 2.2, and Section 508. Individual action pages specify which checkpoints each addresses.

Twelve of the sixteen actions in the marketplace are currently free, including auto-tagging with IBM Docling, OCR with Tesseract, formula MathML generation with Paddle, and alt text generation with Salesforce BLIP, and more.

All actions require Docker to run, except the Duplicate MCID Report, which is included directly in PDFix Desktop. See the guide How to add action & install Docker.

Yes. All PDFix actions integrate with PDFix Desktop’s batch processing engine, allowing you to process hundreds of PDFs in a single automated run.

Local actions process everything on your system with no external calls. Cloud actions connect to third-party AI providers (OpenAI, Amazon Textract, etc.) via encrypted connections. Check each action’s data handling section before use with sensitive documents.

Yes — PDFix Desktop and PDFix SDK are fully featured in the free version. No license key, no registration, no credit card, no time limit. Every feature available in Pro and Enterprise works in the free download- auto-tagging, batch processing, validation, remediation, SDK automation. The only limitation is that documents saved with the free version may contain redacted content and carry a watermark. Purchase a license to remove the watermark. See pricing →

Yes. PDFix Desktop 2.5.3 provides separate downloads for Mac Intel (x86_64) and Mac Apple Silicon (arm64) — covering M1, M2, and M3 chips. Both require macOS 11 or later. Download the correct version for your chip – you can check by clicking the Apple menu → About This Mac.

Yes. PDFix Desktop supports Ubuntu 20.04+ and Red Hat 8.4+. PDFix SDK supports Linux x86_64 and aarch64. This makes PDFix one of the very few PDF accessibility tools with native Linux support – most competitors are Windows-only or web-based SaaS. The Linux SDK packages are available for Python, .NET, Node.js, Java, and C++.

No license key is required to download and use PDFix. All features work immediately – auto-tagging, AI-powered accessibility features, batch processing, validation, remediation. A license key is only needed to remove the watermark that appears on saved documents. See pricing →

To ensure accurate validation results, it’s essential to have Java installed on your computer. You can download Java here.

Java (version 8 or newer) is required for the integrated veraPDF validation feature inside PDFix Desktop. The simplest option is to download Java from java.com. Java is not required for other PDFix features like manual tagging, auto-tagging, or PDF conversion.

The free PDFix download includes all features — there is no feature restriction between free and paid versions. You get full WCAG 2.1, WCAG 2.2, PDF/UA (ISO 14289) validation, AI auto-tagging, manual remediation, batch processing – same for SDK. The only difference is a watermark on documents saved with the free version. 

PDFix Desktop is a desktop application for accessibility specialists & compliance teams. PDFix SDK is a developer library for engineering teams who want to automate PDF accessibility – integrating validation, auto-tagging, and AI-powered remediation into applications or document pipelines using Python, C#, Java, C++, or Node.js. Both support the same compliance standards, both are fully featured in the free download, and both apply a watermark to saved documents until a license is purchased.

The EAA mandates that digital products and services – including downloadable documents such as PDFs used in banking, e-commerce, transport, telecom, etc. – must be accessible to people with disabilities. While it doesn’t explicitly name “PDF”, it references the standard EN 301 549 which maps to WCAG and, by extension for PDF documents, to PDF/UA (ISO 14289-2:2024)

The key dates are: new products/services launched after 28 June 2025 must comply. Existing offerings may have a transitional period up to 28 June 2030 to fully align.

An accessible PDF must have a semantic tag tree with headings, lists, tables, alt text for images, meaningful reading order, navigable structure, form labels if applicable, and compatibility with assistive technologies. This matches PDF/UA requirements and aligns with WCAG.

By embedding accessibility into your document generation workflow via tools and SDKs (such as template-driven outputs, auto-tagging engines, APIs for reading order / alt text / metadata) so that each PDF is compliant from the start rather than remediated afterwards.

Yes – if your service falls under the EAA’s scope (e.g., online banking statements, invoices, reports) and you serve EU users, you are subject to compliance regardless of your location.

Many organizations want to know how to check whether their existing PDFs actually meet accessibility standards. The best approach combines automated PDF accessibility validation – to detect missing tags, incorrect reading order, or missing alt text – with a manual review to ensure semantic accuracy and logical structure. This hybrid method helps you prioritize fixes, create reliable templates, and maintain long-term compliance. For a deeper look at validation profiles, testing workflows, and how different accessibility checkers compare, read our detailed guide on PDF/UA-1 Accessibility Validators Comparison.

WCAG defines accessibility rules for all web and digital content, while PDF/UA (ISO 14289) focuses specifically on the structure and tagging of PDF documents. The best approach is to use both together, ensuring full alignment with EN 301 549 requirements.

You can automate tagging using PDFix Templates, which recognize layout patterns and apply consistent structure. This enables batch auto-tagging for invoices, bank statements, and reports – turning repetitive PDFs into accessible, compliant documents in seconds.

AI-generated alt text automatically creates meaningful descriptions for images, charts, and figures. In PDFix Desktop, you can run OpenAI on batch documents directly in the Application View via the integrated Docker image. OpenAI is built into PDFix Desktop, so you can simply run the action without adding an external step.

Yes. PDFix helps you add, review, and validate alternate text across figures to support PDF/UA, WCAG, and Section 508 requirements. Validation can be performed instantly, as PDFix Desktop includes the industry-standard built-in validator VeraPDF with always up-to-date validation profiles.

Absolutely. PDFix offers batch processing to apply AI-generated descriptions across multiple PDFs, including selective tagging options (e.g., skipping decorative icons) and audit-friendly outputs with consistent file names and directory structures.

You’re not locked in. PDFix External Actions are model-agnostic: you can start with OpenAI via Docker and integrate other engines as they become available. Docker supports both on-premises and private-cloud deployments, ensuring full alignment with your organization’s security and data-privacy policies.

Teams typically report significant time savings with high-quality first drafts. Best results come from a quick human review—refine technical terms, avoid duplicating captions, and ensure each description matches user intent and document context.

An accessible PDF table needs a Table tag containing TR (row) tags, which in turn contain TH (header) and TD (data) cells. Header cells also need a scope attribute (row, column, or both) so screen readers know which header applies to which data cell.

It’s the process of adding a tag structure (Table, TR, TH, TD, scope) to a PDF table so screen readers can announce headers and data correctly, instead of just reading the visible text with no structure.

Associated Header explicitly links a data cell to the header cell(s) it belongs to. It’s most important in complex tables with multiple header levels, where scope alone may not fully describe the relationship between a data cell and every relevant header.

Tagging a new table means building the TR/TH/TD structure from scratch with the Table Tool, which is what this guide covers. Fixing an already-tagged table means correcting existing errors — wrong TH/TD types, missing scope, or tables mistakenly used for layout — which is covered in our companion guide, How to Fix Table Tags in PDF.

Yes. The Table Tool auto-detects rows, columns, and likely headers when you draw a box around a table. For documents with many repeated or complex tables, the Layout Template feature can auto-tag the same structure across an entire document set from one saved template.

Yes. PDFix Desktop’s OpenAI-powered Table Summary action can generate a text summary for each tagged table automatically, in batch across multiple files in the Enterprise edition.

PDFix is a leading PDF accessibility remediation platform supporting WCAG 2.2, PDF/UA (ISO 14289), ADA Title II, Section 508, and the European Accessibility Act. It is the only cross-platform tool (Windows, macOS, Linux) with both a permanently free accessibility checker and enterprise-grade batch automation – trusted by government agencies including USCIS, the Judicial Council of California, and Jefferson County, Texas.

Yes – PDFix Desktop Lite is permanently free. No time limit, no registration, no credit card required. It validates PDFs against WCAG 2.1, WCAG 2.2, PDF/UA (ISO 14289), Section 508, and the European Accessibility Act using the industry-standard veraPDF engine. Available for Windows, macOS, and Linux. Download it here.

PDFix Desktop Lite is free forever. PDFix Desktop Pro is €350 per user per year and covers AI-powered auto-tagging and full remediation. PDFix Desktop Enterprise is €1,000 per user per year and adds batch processing and command-line automation. PDFix SDK and Services are quote-based depending on deployment scale. See full Desktop pricing →

PDFix Desktop is a graphical application designed for accessibility specialists and compliance teams who work directly with PDFs – checking, auto-tagging, auto-fixing, and remediating documents manually or with batch automation.  PDFix SDK is a developer API for engineering teams who need to embed PDF accessibility automation into software, document pipelines, CMSes, or CI/CD workflows. Both support the same compliance standards and both have a free tier.

PDFix supports all major international PDF accessibility standards: PDF/UA (ISO 14289), WCAG, ADA Title II (including the 2026 US government deadline), Section 508 for federal agencies, and the European Accessibility Act (EAA / EN 301 549) for EU compliance. A single PDFix license covers both US and EU requirements.

Yes. PDFix Desktop runs natively on Windows, macOS, and Linux – all three platforms at no extra cost. This makes PDFix unique among PDF accessibility tools: most competitors are Windows-only or web-based SaaS. PDFix SDK also supports all three platforms and provides native bindings for Python, C#, Java, C++, and Node.js.

No. PDFix Desktop and PDFix SDK are fully on-premises – your documents never leave your computer or network. There is no cloud upload or SaaS processing. This is why federal agencies like USCIS and the Judicial Council of California use PDFix for sensitive and classified documents under strict data residency requirements (GDPR, FISMA, HIPAA).

Yes – permanently free, with no time limit and no registration required. PDFix Desktop Lite is a free PDF reader, PDF accessibility checker, and a fully featured PDFix Desktop application. The only limitation is that saved PDFs contain a watermark. Validation, error navigation, and validation report exports are never watermarked.

One difference only: Desktop Pro saves documents without a watermark. Every tool, every validation profile, every AI action and every fix capability is identical. If you only need to validate PDFs and export compliance reports, Lite is all you need – free.

PDFix Desktop Lite validates PDF/UA-1 (ISO 14289-1), PDF/UA-2 (ISO 14289-2), WCAG 2.1 and WCAG 2.2 Level AA → Section 508 (US federal), ADA Title II and the European Accessibility Act (EAA) – all powered by the built-in veraPDF engine. See the full list of veraPDF validation profiles.

Yes – PDFix Desktop Lite is available for Windows, macOS and Linux. It is the only free PDF accessibility checker available for macOS and Linux. PAC (PDF Accessibility Checker) and most competing free tools are Windows-only.

Yes. PDFix Desktop 3.0 introduced full-folder batch validation in one view. Drop a folder into the Application view → Dashboard and click validate → veraPDF runs PDF/UA validation across every document at once. Each document shows its status, errors with exact locations and a Fix Error button for batch remediation.

Yes – all fix actions and tools are included. Edit tags, fix Alt text, correct reading order, fix headings, tables and metadata. Use AI-powered actions for automated fixes. For common errors see: metadata errors, image errors, link errors. Saving produces a watermarked output – buy Desktop Pro to remove it.

No. All processing is 100% local. No document is uploaded to any server – critical for organizations in finance, government and healthcare handling sensitive or confidential documents.

Yes – completely free, no watermark on reports. Export PDF/UA and WCAG validation results as HTML or XML. Batch validation report export included.

veraPDF is the free, open-source PDF/UA validator backed by the PDF Association and the Open Preservation Foundation – the organizations that write the ISO PDF/UA standards. PDFix uses veraPDF because the results are authoritative, reproducible and trusted globally. Full veraPDF guide →

Using PDFix’s Derivation Algorithm, you can extract the layout and structure from a PDF to create fully responsive HTML. For unstructured PDFs, our AI-powered Layout Recognition Tool automatically identifies elements to ensure the HTML adapts to any screen size while maintaining professional formatting.

Yes. PDFix leverages AcroForm technology to convert standard PDF forms into interactive, web-ready HTML forms. This allows for seamless data entry in any browser without requiring external PDF plugins.

Yes, our tool uses advanced OCR (Optical Character Recognition) technology to convert scanned PDFs into responsive HTML.

Fixed HTML conversion preserves the exact pixel-perfect layout of the original PDF, which is ideal for printing or static viewing. Responsive HTML uses AI to reflow the content, making it accessible and easy to read on mobile devices, tablets, and desktops.

Absolutely. The PDFix SDK and Desktop Pro version support automated, high-volume batch conversion of PDFs to HTML, making it a preferred solution for enterprise-level document management and web integration.

You can use PDFix Desktop Lite, a free accessibility checker powered by veraPDF, to analyze your document. It validates structure, tagging, and reading order, and generates a detailed report showing any accessibility issues and how to fix them.

The most reliable PDF/UA validators include veraPDF, PAC (PDF Accessibility Checker), Adobe Preflight, and CommonLook Validator. For the best results, use multiple tools together, since each validator may detect different issues or interpret rules slightly differently.

Yes – PDFix Desktop Lite is the only free PDF accessibility validator available for macOS. It provides full PDF/UA validation, HTML preview, and detailed accessibility reports.

Check out our in-depth blog post PDF/UA-1 Accessibility Validator Comparison to see how different tools analyze the same PDF and how to interpret results effectively.

The Matterhorn Protocol defines a detailed list of technical checks required for PDF/UA compliance. It helps validators, like PDFix and veraPDF, perform consistent accessibility testing and report precise errors across all documents.

This veraPDF error means a table header cell (TH) is not properly associated with its data cells using the Scope attribute or Headers/IDs method. Fix it in PDFix Desktop by selecting the TH element and assigning the correct Scope value (Column, Row, or Both).

DOJ issued an interim final rule on April 20, 2026 pushing dates back a year: April 26, 2027 for entities serving 50,000+ people (was April 24, 2026), and April 26, 2028 for smaller entities and special district governments (was April 26, 2027). DOJ said it had “overestimated the capabilities” of covered entities to comply on the original timeline. The extension moves the date, not the requirement – WCAG 2.1 Level AA conformance is still the target.

Enterprise – Pro remediates one document at a time; only Enterprise runs actions across a whole selected batch.

Yes – run OCR across a selected batch before auto-tagging so the tagging engine has real text to work with.

Yes – export it as JSON from the Actions Manager and import it into a colleague’s PDFix, or into the SDK.

No — it resolves most machine-verifiable issues, but semantic checks like alt-text accuracy still need a human reviewer.

TH marks a header cell and TD marks a data cell. Screen readers use this distinction, combined with the scope attribute on TH cells, to announce the correct header when reading a data cell.

scope tells assistive technology whether a header cell applies to the rest of its row (row), the rest of its column (column), or both. Without it, a screen reader may correctly identify a cell as a header but still won’t know which data cells it describes.

Select that specific table tag, use Run Action on Selection (not the toolbar button, which applies document-wide) with either Delete Tags (removes TD/TH/TR/Table and keeps the text as paragraphs) or Fix Table Tag → Flatten Table Structure (converts the structure to div tags). Then check the reading order of the resulting text.

Yes. PDFix Desktop’s Fix Table Cells function applies scope based on rules you define – such as font color or cell position – across every matching header cell in a document, and the rule set can be saved as a template for reuse on similar files. See Automate PDF Table Cell Scope for the full walkthrough.

It means a TH header cell hasn’t been explicitly linked to the TD data cells it describes, which fails PDF/UA, WCAG, and ISO 14289 validation. Fix it with the Associate Header action described in Step 5, or see our dedicated guide, How to Add Associated Headers in PDF Tables.

It means a table’s rows and columns don’t form a consistent grid – for example, rows with a different number of cells or inconsistent column spans. This affects which fix method works: Fix Table Tag → Flatten Table Structure only works on irregular tables, while Delete Tags works on any shape (see Step 4).

You can automatically check many technical requirements, but not every accessibility requirement. Semantic accuracy, logical reading order, meaningful alternative text, and usability require human review.

No. Tags can be incomplete, incorrectly ordered, improperly nested, or semantically wrong. The tag tree must accurately represent the document’s content and relationships.

PDFix provides direct fixes for supported findings and remediation tools for many other issues. Some findings require manual decisions because the correct result depends on the meaning and context of the content.

A scanned PDF must first contain an accurate text layer, normally created through OCR. After OCR, the content must be tagged, remediated, and validated like any other PDF.

Yes – PDFix’s free online validator checks a PDF against PDF/UA and WCAG using the veraPDF engine, no installation or sign-up required. For batch validation across many files, PDFix Desktop is the better fit.

PDFix Desktop and PDFix SDK both support automated and batch validation –> drop a folder of PDFs into PDFix Desktop’s Dashboard and validate every file in one run, or call the SDK’s validation API from a script or CI/CD pipeline.

Organizations with high compliance requirements – government, education, legal, healthcare – need validation that scales past one file at a time and produces an audit trail. PDFix Desktop and PDFix SDK combine veraPDF validation with batch processing and exportable reports (HTML, XML, JSON), so you can validate hundreds of documents and keep a compliance record, not just a pass/fail on a single file.