DEV Community: Julia

How tags are saved in the initial PDF. OpenDataLoader experience

Julia — Mon, 15 Jun 2026 07:15:03 +0000

TL;DR: OpenDataLoader’s auto-tagging engine analyzes the document’s layout, detecting headings by visual text properties, identifying tables by grid patterns, recognizing lists by bullet positions and then writes this structural information directly into the PDF’s internal structure tree.

PDF accessibility begins with mapping document content (headings, paragraphs, tables, lists) into a logical structure tree that assistive technologies can navigate. Manual tagging is slow, error-prone, and impractical for large document volumes.

⁉️ How OpenDataLoader Implements Tag Writing
OpenDataLoader is the first open-source tool which adds tags directly into the initial PDF file without altering the visual appearance of the document. The AI analyzes document structure, distinguishes components such as titles, tables, lists, and images, and inserts the corresponding tags into the source PDF.

Key characteristics of OpenDataLoader’s approach:

No proprietary SDK dependency: most existing tools rely on commercial SDKs for the tag-writing step;
#OpenDataLoader does it all under Apache 2.0 license.
On-premise processing : sensitive documents never leave your network
No page caps or watermarks unlimited use without document quantity restrictions

OpenDataLoader’s auto-tagging was built in collaboration with the
Dual Lab (Member of PDF Association, supports veraPDF, developers of
PDF4WCAG Accessibility checker.

OpenDataLoader’s auto-tagging preserves visual integrity by design. The technology adds semantic structure without touching the presentation layer, follows industry specifications validated by PDF accessibility experts, and has been built specifically to solve the accessibility problem without creating new ones.

GitHub:
https://github.com/opendataloader-project/opendataloader-pdf

Metadata and PDF accessibility checker PDF4WCAG

Julia — Fri, 12 Jun 2026 11:13:33 +0000

PDF accessibility is always associated with tags, headings and alternative text. But there's another critical component: metadata.

PDF documents may include general information, such as the document’s title, author, and creation and modification dates. Such information about the document (as opposed to its content or structure) is called metadata and is intended to assist in cataloguing and searching for documents in external databases.

Metadata plays a tremendous role in modern PDF files, especially in accessibility, document management and AI-based document processing. In PDF files metadata is commonly stored using XMP (Extensible Metadata Platform) package, directly embedded into the document.

Document title and accessibility
Well-Tagged PDF (WTPDF) declarations are metadata, embedded in PDF 2.0 files within the XMP metadata, that assert a document's conformity with WTPDF 1.0 requirements for accessibility or content reuse. Developed by the PDF Association, these declarations allow software to identify if a file is optimized for assistive technology (similar to PDF/UA-2) or for structured data extraction.

The title helps users understand the purpose of the document before reading its content. Screen readers and other assistive technologies often announce the title when the PDF is opened.

For example:

“Accessibility Report 2026”
“PDF4WCAG PDF Accessibility Checker”

are significantly more useful than:

“doc.pdf”
“pic001.pdf”

PDF/UA identification metadata
In accessible PDFs, XMP metadata may also contain identification information about conformance standards. There are several mechanisms at work here: one used by PDF/UA, another by WCAG. Both are important, as the document may conform to both PDF/UA and PDF/UA, as the latest LaTeX-generated Tagged PDFs do.

This metadata allows validators and accessibility tools to determine whether the document claims compliance with standards such as: PDF/UA and WCAG.

Additional metadata fields
XMP metadata also may contain valuable document information, including: creation and modification date, author or organization, producer and creator tool, language information.

Metadata provides assistive technologies with an initial description of the document before content navigation begins. Without proper metadata, accessible PDFs lose important semantic and usability information.

What PDF4WCAG checks
PDF4WCAG checks:

dc:title is present and not empty.
The PDF/UA or WCAG compliance declarations, if the document is validated against PDF/UA or WCAG profiles respectively. These declarations are recommended, but not mandatory for WCAG.
The XMP package is properly attached to the document catalog.

Accessible PDFs should contain a meaningful dc:title. More advanced workflows should also include standardized identification metadata and descriptive document properties to support both human users and machine processing systems.

You can open discussions and submit issues in our public GitHub https://github.com/duallab/PDF4WCAG-public/issues repository or start the discussion https://github.com/duallab/PDF4WCAG-public/discussions to propose improvements or share ideas.

Dual Lab releases PDF4WCAG Accessibility Checker 1.10

Julia — Fri, 05 Jun 2026 06:28:39 +0000

Dual Lab announces the release of PDF4WCAG Accessibility Checker 1.10, introducing usability enhancements, expanded localization support, and new document inspection panels.

PDF4WCAG is a professional accessibility validation solution for PDF documents, designed to support compliance with PDF/UA, WCAG, and WTPDF accessibility requirements. It is powered by the veraPDF validation architecture and is identical to veraPDF in Machine verifiable checks of PDF/UA and WTPDF validation profiles.

What’s new in Version 1.10

Enhanced localization and user experience

PDF4WCAG 1.10 improves interface usability and multilingual support:

Redesigned switching between technical terminology and user-friendly language, providing a more intuitive experience for both accessibility experts (developers) and non-technical users.

Added support for German and Dutch interface localizations.

Improved zoom and navigation controls
Accessibility issue navigation has been refined for better usability:

Enhanced zoom behavior for small issue regions and error highlights.

New inspection panels

PDF4WCAG 1.10 introduces several new analysis panels to provide deeper document insights:

Annotations panel

Inspects PDF annotations, comments, hyperlinks, form controls, and other interactive elements relevant to accessibility and usability evaluation.

Metadata panel

Displays document metadata including:

document title
author information
document language
accessibility properties
PDF/UA-related metadata entries

Fonts panel

Provides detailed analysis of:

embedded fonts
font types and subsets
encoding information

Persistent user preferences

PDF4WCAG now preserves user configuration settings between sessions, improving workflow continuity and efficiency. Persisted settings include:

selected interface language
active filters
right-side panel state and opened sections
structure tree role map visibility
auto-scaling preferences

CLI enhancements

The command-line interface has been extended with initial support for additional validation profiles:

WCAG Machine
WCAG Machine & Human

These profiles are now available under paid commercial licenses on the PDF4WCAG website.

Public API documentation
A new public documentation section is now available. API is available under paid commercial licenses on the PDF4WCAG website.

Integration API Beta testing

The PDF4WCAG Integration API is in the process of beta testing. The API is designed to simplify integration of accessibility validation workflows into enterprise systems, document processing pipelines, and third-party accessibility platforms.

About Dual Lab
Founded in 2008, Dual Lab specializes in science- and technology-intensive software development across multiple domains including PDF Technologies, complex Document Management workflows, 3D Modelling, Fintech and others. Dual lab is a partner member of PDF Association.

For more information, visit the website.

duallab #pdf4wcag #wcag #accessibility

Auto-Tagging in OpenDataLoader PDF: How Visual Integrity Is Guaranteed

Julia — Wed, 03 Jun 2026 09:23:55 +0000

OpenDataLoader’s auto-tagging guarantees that the document remains visually unchanged because it separates structure from presentation.

How do we do it?

The Core Principle: Tags vs. Visuals

PDFs are ambivalent documents. They contain:

A visual layer: the exact positioning of text, images, and graphics on each page.
A structural layer (optional): tags that describe what each element means (heading, paragraph, table, etc.)

Untagged PDFs have only the visual layer. When screen readers encounter these, they see a mess of text with no hierarchy like reading a magazine where someone has cut every article into individual words and thrown them on a table.

Auto-tagging adds the structural layer without touching the visual layer. It’s like adding an invisible table of contents and semantic labels to a book without changing a single word on the pages.

How OpenDataLoader Preserves Visual Integrity

1. Structure is written, not rendered

OpenDataLoader’s auto-tagging engine analyzes the document’s layout, detecting headings by visual text properties, identifying tables by grid patterns, recognizing lists by bullet positions and then writes this structural information directly into the PDF’s internal structure tree.

Critically, this structural information exists alongside the existing visual instructions, not instead of them.

The tags are simply additional data that assistive technologies can use.

2. The Guarantee of preserve appearance

OpenDataLoader produces a screen-reader-ready PDF with structure tags (headings, paragraphs, lists, tables, reading order). The output is a Tagged PDF, not a reformatted or redrawn document.

This means:

No repositioning: text stays exactly where it was
No reformatting: fonts, spacing, and layout remain identical
No content removal: everything visible stays visible
No visual additions: tags are invisible metadata.

3. Validated against industry standards

OpenDataLoader’s auto-tagging was built in collaboration with the Dual Lab (Member of PDF Association, supports veraPDF, developers of PDF4WCAG Accessibility checker.

4. Two Engine Options for Accuracy

OpenDataLoader offers two processing modes:

Both modes operate on the same principle: analyze the visual layer, infer structure, write tags. Neither mode alters the underlying visual instructions.

How Hybrid Mode Works for Auto-Tagging

Hybrid mode combines fast local Java processing with AI backends. Simple pages stay local (0.02s); complex pages route to AI for +90% table accuracy.

Simple pages — processed locally (approximately 0.02s per page)

Complex pages — routed to AI backend for enhanced accuracy

What Hybrid Mode Enables

Hybrid mode specifically handles content types that deterministic local processing struggles with:

Accuracy Improvements

The results show dramatic accuracy improvements with hybrid mode:
Table extraction accuracy: Jumps from 0.489 (local mode) to 0.928 (hybrid mode)
Overall benchmark score: 0.907 overall #1 overall, leading in reading order (0.934) and table extraction (0.928)
Reading order accuracy: 0.934

OpenDataLoader’s auto-tagging preserves visual integrity by design. The technology adds semantic structure without touching the presentation layer, follows industry specifications validated by PDF accessibility experts, and has been built specifically to solve the accessibility problem without creating new ones.

Official website: https://opendataloader.org/?utm_source=medium

GitHub: https://github.com/opendataloader-project/opendataloader-pdf?utm_source=medium

What is an Artifact in PDF?

Julia — Mon, 01 Jun 2026 07:27:21 +0000

PDF artifacts are non-semantic visual elements introduced during document generation, rendering, scanning, or OCR processing. In AI pipelines, these artifacts reduce extraction quality and negatively impact downstream tasks such as embeddings, retrieval, and LLM reasoning.

Typical PDF artifacts include:

page header/footer
table headers for multi-page tables
decorative elements interpreted as content Artifacts should generally be ignored by assistive technologies such as: screen readers, text-to-speech systems, accessibility APIs, AI semantic extraction pipelines.

This concept is very similar to decorative elements in HTML accessibility.

For example, in HTML: decorative images use alt="", layout containers may use ARIA presentation roles, CSS-generated visuals are ignored semantically. In PDFs, the equivalent mechanism is marking content as an Artifact.

By the way artifacts play a critical role in PDF/UA compliance and screen reader usability. Without proper artifact handling, assistive technologies may read decorative or repetitive content aloud, creating confusion and misunderstandings for users.

Modern accessibility validation tools such as PDF4WCAG Accessibility Checker help identify these issues and ensure PDFs correctly distinguish meaningful content from decorative elements.

The core requirement of both PDF/UA and WCAG **is that every piece of content must be designated either as an artifact or as part of the structure tree nothing can be left. This is exactly what PDF4WCAG verifies.

Sample of Artifact errors after PDF4WCAG validation

PDF 2.0 and richer artifact semantics

PDF 2.0 (ISO 32000-2:2020) brought significant improvements to the handling and definition of artifacts compared to previous versions.

Key improvements to the Artifact model in PDF 2.0 include:

Standardized Tagging: PDF 2.0 provides clearer, more robust mechanisms for marking items as artifacts, especially in tagged PDF, reducing ambiguity for accessibility tools.

Reduced Vague Wording: It addresses ambiguities in earlier PDF 1.7 specifications, providing clearer rules for how developers and software should handle artifacts.

Better Annotation Handling: Annotations and their relation to structural elements are better defined, reducing issues where background decorations or marginalia are misidentified as content.
Improved Structural Hierarchy: It clarifies how artifacted content can interact with the document structure tree, particularly regarding how tags should be ordered or ignored, which was a point of ambiguity in older standards.

To sum it up, proper use of artifacts is one of the foundational concepts of PDF accessibility.

A well-structured accessible PDF must clearly separate: meaningful semantic content and decorative or auxiliary presentation elements.

As PDF accessibility evolves, especially with PDF 2.0 semantics and AI-driven document processing, artifact classification becomes increasingly important not only for accessibility specialists, but also for developers, publishers, and AI engineers building intelligent document systems.

Why OpenDataLoader PDF Uses a Hybrid Recognition Pipeline

Julia — Mon, 25 May 2026 07:26:48 +0000

HANCOM | OpenDataLoader | Published: May 2026
TL;DR: Reliable PDF extraction is one of the hardest problems in AI pipelines. No single recognition method visual, glyph, or semantic handles every document well. OpenDataLoader PDF combines all three in a hybrid pipeline that prefers fast, lossless paths (Tagged PDF, glyph analysis) and falls back to OCR plus optional LLM only when needed delivering 93% table accuracy across 80+ OCR languages without forcing GPU on every page.

Introduction

PDF files power the modern enterprise from legal records and scientific publications to invoices and accessibility reports. However, extracting reliable structured data from PDFs remains one of the most difficult challenges in AI pipelines.

A PDF document may look visually perfect to a human reader while containing little or no machine-readable structure. This creates major problems for AI systems that rely on accurate text extraction, table understanding, logical reading order, semantic hierarchy, and metadata interpretation.

To solve this challenge, modern AI systems use different approaches to PDF recognition. Each method has strengths and weaknesses.

OpenDataLoader PDF takes a hybrid OCR & AI approach because no single recognition strategy can consistently achieve high-quality results across all document types.

The Three Layers of PDF Recognition
1. Visual Approach (OCR + Deep Learning)

How It Works

The visual approach recognizes a PDF page as an image, similar to how humans visually interpret a document.

Strengths

The visual approach is extremely powerful for:

Scanned PDFs
Photographed documents
Image-only PDFs
Handwritten annotations
Visually complex layouts
Mathematical expressions OpenDataLoader supports 80+ OCR languages in the visual layer.

Limitations

Despite its flexibility, the visual approach has important limitations. Visual recognition is:

Computationally expensive
Time-consuming
Energy-intensive
Often GPU-dependent

Role in ODL

In OpenDataLoader, the visual layer acts as an intelligent recovery and enhancement mechanism. The system also supports optional LLM enhancement for OCR and complex tables as a cost-control fallback mechanism, activating deeper processing only when confidence thresholds are not met.

2. PDF Internals Approach: Glyph & Operator Analysis

How It Works

The PDF internals approach works directly with the native PDF structure. Instead of rasterizing pages into images, the system analyzes:

Glyph positioning
Bounding box coordinates [x1, y1, x2, y2]
Text operators
Font mappings
Vector instructions
Coordinate systems
Rendering commands
Content streams

OpenDataLoader implements the XY-Cut++ reading order algorithm to reconstruct logical flow from geometric layout.

Strengths

This method can process very large PDFs quickly while maintaining high positional accuracy.

Limitations

The primary limitation is semantic ambiguity. The method also depends on:

Valid font mappings
Proper text encoding
Usable content streams
Poorly generated PDFs may reduce extraction quality.

Role in ODL

The PDF internals layer is the foundation of OpenDataLoader. Most enterprise PDFs can be processed effectively using this layer alone, making it the core engine for large-scale AI ingestion pipelines.

3. Semantic Layer Approach (Tagged PDF)

How It Works

PDF 1.4 introduced "Tagged PDF" to represent the logical reading order (structure) of a document. It defines a set of standard structure elements and attributes that allow page content (text, graphics, images, annotations, and form fields) to be extracted and reused for other purposes.

Strengths

The semantic approach offers:

Direct semantic reuse with no GPU requirement
Reliable reading order
Accessible structure extraction
Immediate hierarchy reconstruction
Improved AI understanding

Well-tagged PDFs can provide nearly ideal structured input for AI systems.

Limitations

The semantic approach only works reliably when PDFs are properly tagged. In poorly tagged documents, semantic extraction quality drops significantly.

Role in ODL

OpenDataLoader uses Tagged PDF semantics whenever available. Instead of rebuilding structure from scratch, when enabled, ODL can:

Reuse accessibility semantics
Preserve reading order
Inherit hierarchy
Retain metadata
Improve downstream AI quality

ODL reads and preserves PDF/UA tagged output as a first-class asset. Its accessibility auto-tagging produces structures compatible with WCAG and PDF/UA workflows.

Why OpenDataLoader Uses a Hybrid Approach

No single PDF recognition method is sufficient for all document types. Each approach solves a different part of the problem.
OpenDataLoader combines all three layers into a unified hybrid pipeline.

The system dynamically decides:

When to trust semantic tags
When to use glyph analysis
When to activate visual AI models
How to combine multiple signals

The core mission of OpenDataLoader is to transform PDFs into structured, reliable, and semantically rich data pipelines. Modern AI systems depend heavily on input quality.

Instead of running expensive OCR on every single page, ODL's hybrid approach intelligently applies deep learning only where it's needed on complex tables, scanned documents, and tricky layouts. Simple pages process in real time. Simple pages process in ~0.02 seconds per page on CPU (60+ pages per second).

OpenDataLoader achieves 93% table accuracy in benchmarks, a headline result that demonstrates the effectiveness of combining all three recognition layers.

Key capabilities include:

Table border + merged cell detection for accurate table reconstruction
80+ OCR languages in the visual fallback layer
XY-Cut++ reading order algorithm for logical flow reconstruction
Optional LLM enhancement as a cost-controlled fallback for low-confidence extractions

Unlike OCR-only pipelines or pure deep-learning parsers, ODL does not force a single recognition path. It routes each document to the most efficient and accurate method available.

You don't need to choose between quality and performance. OpenDataLoader's hybrid mode delivers both automatically, and without altering the visual layout of the source PDF.

Open source. The full pipeline is available on GitHub, runs on CPU for most workloads, scales to GPU when needed, and respects data residency through optional self-hosting.

FAQ
Q1. What is hybrid mode?
Hybrid mode combines fast local Java processing with an AI backend. Simple pages are processed locally (0.02s/page); complex pages (tables, scanned content, formulas, charts) are automatically routed to the AI backend for higher accuracy. The backend runs locally on your machine — no cloud required. See Which Mode Should I Use? and Hybrid Mode Guide.

Q2. Does it support OCR for scanned PDFs?
Yes, via hybrid mode. Install with pip install "opendataloader-pdf[hybrid]", start the backend with --force-ocr, then process as usual. Supports multiple languages including Korean, Japanese, Chinese, Arabic, and more via --ocr-lang.

Q3. How fast is it?
Local mode processes 60+ pages per second on CPU (0.02s/page). Hybrid mode processes 2+ pages per second (0.46s/page) with significantly higher accuracy for complex documents. No GPU required. Benchmarked on Apple M4. Full benchmark details. With multi-process batch processing, throughput exceeds 100 pages per second on 8+ core machines.

Q4. Is this really the first open-source PDF auto-tagging tool?
Yes. Existing tools either depend on proprietary SDKs for writing structure tags, only output non-PDF formats (e.g., Docling outputs Markdown/JSON but cannot produce Tagged PDFs), or require manual intervention. OpenDataLoader is the first to do layout analysis → tag generation → Tagged PDF output entirely under an open-source license (Apache 2.0), with no proprietary dependency. Auto-tagging follows the PDF Association's Well-Tagged PDF specification and is validated using veraPDF, the industry-reference open-source PDF/A and PDF/UA validator.

Q5. How do I make my PDFs accessible for EAA compliance?
ODL reads and preserves PDF/UA tagged output. Its accessibility auto-tagging produces structures compatible with WCAG and PDF/UA workflows.

Conclusion
OpenDataLoader PDF combines visual OCR, glyph-level PDF internals, and semantic Tagged PDF into a single hybrid pipeline. The system prioritizes fast, lossless extraction paths Tagged PDF and glyph analysis and falls back to OCR plus optional LLM only when needed. This approach delivers 93% benchmark accuracy across diverse document types without requiring GPU for every page.

Get started:

GitHub: https://github.com/opendataloader-project/opendataloader-pdf?utm_source=medium&utm_medium=blog&utm_campaign=hybrid_approach&utm_content=github

Docs: https://opendataloader.org/docs?utm_source=medium&utm_medium=blog&utm_campaign=hybrid_approach&utm_content=docs

Try the pipeline:https://opendataloader.org/demo?utm_source=medium&utm_medium=blog&utm_campaign=hybrid_approach&utm_content=demo

HANCOM open-sources AI auto-tagging in OpenDataLoader PDF

Julia — Fri, 22 May 2026 09:12:22 +0000

HANCOM has open-sourced an AI auto-tagging feature in OpenDataLoader PDF that automatically writes accessibility tags directly into existing PDF documents, running on-premise with no per-page or per-document limits.
HANCOM has open-sourced an AI auto-tagging feature that automatically writes accessibility tags into PDF documents. The capability ships inside OpenDataLoader PDF and is released globally as open source, with Python, Node.js and Java libraries — distributed via GitHub, PyPI (opendataloader-pdf), npm (@opendataloader/pdf) and Maven Central (org.opendataloader:opendataloader-pdf-core) — alongside a command-line tool for developers worldwide. The release was announced on 30 April 2026.

How auto-tagging works
AI analyzes a document‘s structure and writes the results directly inside the original PDF file. It distinguishes components such as titles, tables, lists and images, then reflects them inside the PDF as tags that carry the accessibility structure. The auto-tagging output is written back into the actual PDF in a complete form — and this end-to-end stage is included in the free, open-source release.

Why PDF accessibility matters
PDF is one of the most widely used digital document formats worldwide, yet a large share of documents have circulated without accessibility tags. When tags are missing, screen readers cannot properly recognize document structure, making it difficult for people with visual impairments and other groups with limited access to information to understand the content.

Global regulatory backdrop
Demand is expanding quickly in step with regulatory changes across multiple jurisdictions. In the United States, the main obligations under ADA (Americans with Disabilities Act) Title II begin to apply in April 2026. In Europe, the EAA (European Accessibility Act) is taking effect in parallel. In Asia, Korea‘s Act on the Prohibition of Discrimination Against Persons with Disabilities is aligning with the same trajectory. Together, these regimes are pushing enterprises and public institutions worldwide to remediate their PDF archives at scale.

How it compares to existing offerings
In the global market, free tiers for cloud-API offerings have typically been limited to dozens of pages per month, and full-scale adoption has incurred annual corporate license costs in the tens of thousands of dollars. Some desktop products insert watermarks in outputs during free trials, or restrict key features behind separate paid tiers.

OpenDataLoader PDF, by contrast, can be used without limits on the number of documents. It is processed in an on-premise environment, so sensitive documents are not sent to external servers — an important property for organizations operating under data-residency regimes worldwide. Python, Node.js and Java libraries, as well as a command-line tool, are provided to integrate with existing workflows.

Standards alignment and collaboration
The open-source auto-tagging engine generates tag structures that reference PDF Association technical specifications and align with the PDF/UA (PDF Universal Accessibility) international standard. Full PDF/UA-compliant output is being developed for the upcoming commercial solution. HANCOM is enhancing its quality verification system in collaboration with Dual Lab, the team behind the open-source PDF accessibility validation tool veraPDF.

Free open-source core, paid PDF/UA-compliant commercial tier
HANCOM is pursuing this release as part of a document AI platform strategy that goes beyond document processing tools to encompass accessibility readiness and regulatory compliance. The split is explicit:

Free, open source: the AI auto-tagging core in OpenDataLoader PDF, with no document or page limits, available to developers and organizations worldwide.
Paid commercial solution (Q2 2026): a separate offering that outputs results compliant with the PDF/UA international standard, targeted at enterprises and public institutions that need to respond to audits and comply with regulations.
About HANCOM

HANCOM is a document software company headquartered in the Republic of Korea, contributing to the global document AI and PDF ecosystem through open-source releases, international standards participation, and partnerships with members of the PDF Association.

_“HANCOM aims to open-source core features so anyone can start accessibility conversion without expense burdens. For corporations that need to convert large volumes of documents, we will provide free core tools alongside commercial solutions compliant with PDF/UA.”
_ Jung Ji-hwan, Chief Technology Officer, HANCOM

AI-based PDF Auto-tagging

Julia — Thu, 30 Apr 2026 06:46:51 +0000

AI-based PDF Auto-tagging
🎯 Most open-source PDF tools extract structure.
🚀 OpenDataLoader PDF open-sourced the part nobody else gives away for free — writing accessibility tags back into the original Хэштег#PDF itself.
🚀 Released Apr 30, 2026, in OpenDataLoader PDF.
💢 Why it matters now:
🇺🇸 DA Title II — Apr 2026 deadline now in force
🇪🇺 EU Accessibility Act (EAA) — already mandatory
Millions of untagged PDFs need conversion.
Existing tools cap free tiers at ~tens of pages/month, or charge tens of thousands of dollars per year for production use.
What #OpenDataLoader https://opendataloader.org/ shipped:
💢 AI detects headings, tables, lists, and images
💢 Rebuilds them as accessibility-compliant tags
💢 Writes them directly into the original PDF
💢 Runs on-premise — sensitive docs never leave your network
💢 No page caps, no watermarks
💢 Python · Node.js · Java libraries + CLI Generates Tagged PDFs to PDF Association specifications and the PDF/UA standard, with quality validation co-developed with the veraPDF team (Dual Lab).

Structural Tree Samples

GitHub → https://github.com/opendataloader-project/opendataloader-pdf?utm_source=x&utm_medium=social&utm_campaign=auto_tagging_release
Site → https://opendataloader.org/

Hancom's 'OpenDataLoader PDF v2.0' claimed the #1 trending position across all programming languages

Julia — Wed, 29 Apr 2026 06:45:50 +0000

The global open-source platform Github hosts approximately 400 million registered projects. Within this vast ecosystem, Hancom's 'OpenDataLoader PDF v2.0'claimed the #1 trending position across all programming languages on April 23 — selected as the most-watched project by developers worldwide.

The repository has surpassed 19,200 GitHub stars and 1,700 forks, with monthly downloads exceeding 50,000 — a clear testament to its real-world impact.

This achievement is rooted in the technical expertise Hancom has built over more than 35 years of processing document data for public institutions and enterprises. As AI and RAG (Retrieval-Augmented Generation) systems continue to scale, the accuracy of document data extraction has emerged as a decisive factor — accounting for up to 90% of overall AI quality. While approximately 80–90% of enterprise data exists in unstructured formats such as PDF, conventional LLMs are built around web-based data, creating a critical gap in handling real-world business documents. Hancom developed OpenDataLoader PDF to bridge exactly that gap.

The solution's core strengths are speed and accuracy. In local mode, it processes documents at 0.015 seconds per page with 90% accuracy — the highest benchmark among currently available open-source PDF parsers.
This is made possible thanks to Hancom's high-performance OCR engine — supporting more than 80 languages — deployed in a hybrid architecture. Plain text is handled instantly via rule-based processing, while AI is engaged only for complex layout analysis, maximizing efficiency without the need for a dedicated GPU. The result: enterprise-grade performance on CPU alone, making it accessible even for small and medium-sized businesses with limited infrastructure.

Where conventional parsers fall short — breaking down on complex tables, multi-column layouts, or image-embedded text — OpenDataLoader PDF restores reading order and full table structures, converting content into AI-ready formats including Markdown, JSON, and HTML. Benchmark evaluations confirm strong results across key metrics: reading order recognition (NID), table extraction accuracy (TEDS), and heading hierarchy recognition (MHS). Designed with enterprise security in mind, the solution operates entirely on-premises and includes built-in filtering against prompt injection attacks.

Hancom has released OpenDataLoader PDF under the Apache 2.0 License — a bold strategic commitment to making Hancom's technology the global standard, rather than pursuing short-term revenue. OpenDataLoader PDF anchors a broader AI product lineup: 'DataLoader' for data extraction, 'Hancompedia' as a RAG-integrated solution, and 'Assistant' for intelligent workflow support. The ultimate vision is an 'AI Orchestrator' — a platform where customers can freely compose and deploy the AI capabilities that fit their needs.

Looking ahead to Q2, Hancom will introduce MCP support and commercial add-ons, enabling AI agents to directly invoke OpenDataLoader for seamless document processing. A 'PDF Accessibility Tag Auto-Generation' feature for visually impaired users is also on the roadmap — reflecting Hancom's commitment to building a more equitable digital environment through document structure recognition technology.

Hancom has declared 2025 as its inaugural year of AX (AI Transformation). Building on this milestone, Hancom will leap forward to establish itself as the standard infrastructure of the global AI document ecosystem.

New Release: PDF4WCAG 1.8 Accessibility Checker

Julia — Fri, 17 Apr 2026 12:36:47 +0000

Dual Lab team is ready to announce a new update 1.8 to PDF4WCAG, delivering further improvements in validation accuracy, user experience, and overall stability.

Improved Accuracy

Fixes in PDF/UA validation to align with latest technical discussions within TWGs of PDF Association and veraPDF improvements:

permit Math to be not necessarily an immediate child of Formula structure element;
improve glyph name calculation for Type1 and TrueType fonts;
adjusted validation of the PDF Table structure element.

Missing translations of error messages have also been added to improve clarity across languages (Dutch, German, English).

Enhanced User Experience

Error preview filters have been reworked for more convenient error inspection.

Export Validation Results: users can export validation results as PDF for client reporting, documentation or internal audits purposes. Just click on the Export results on the Summary page.

One-Click Refresh: users can reupload and repeat the analysis of the document in one click (Web) or just via Refresh button in the Desktop version.

GitHub and collaboration: PDF4WCAG now includes a direct link to its GitHub repository within the feedback popup, inviting developers and users to contribute to the tool's roadmap.

The ability to use PDF4WCAG command line in the console (paid subscription).

Commercial use of PDF4WCAG: the commercial use of Desktop version and CLI automation is available in the annual subscription for just 299 EUR / 359 USD (excl. taxes).

This release 1.8 reflects our ongoing commitment to providing precise, standards-aligned accessibility validation and a smoother user experience for organizations working toward WCAG and PDF/UA compliance.

Roadmap Update
We're excited to announce the start of beta testing for the PDF4WAG Integration API. If you're interested in participating as a beta tester, please send us your request to info@pdf4wcag.com.

License change (Apache 2.0): Brand image enhancement through tech openness

Julia — Fri, 17 Apr 2026 12:25:43 +0000

OpenDataLoader PDF has officially moved from MPL-2.0 to Apache License 2.0. This change removes adoption friction for enterprise integrations, provides explicit patent protection, and signals long-term commitment to transparency. Apache 2.0 is the most widely adopted permissive license among enterprise-grade open-source projects.

License change (Apache 2.0): Brand image enhancement through tech openness

Julia — Thu, 09 Apr 2026 12:12:14 +0000

OpenDataLoader PDF has officially moved from MPL-2.0 to Apache License 2.0. This change removes adoption friction for enterprise integrations, provides explicit patent protection, and signals long-term commitment to transparency. Apache 2.0 is the most widely adopted permissive license among enterprise-grade open-source projects.

With over 13,000 GitHub stars and growing, OpenDataLoader PDF has become one of the most recognized open-source PDF processing tools in the developer community. The move to Apache 2.0 reflects this momentum making it easier for the next 10,000 contributors and adopters to join.
Apache License 2.0 has officially been adopted for OpenDataLoader PDF converter as a strategic decision that reflects the long-term vision for transparency, innovation, and ecosystem growth.

Initially ODL used the MPL-2.0 (Mozilla Public License 2.0) license.
The license change is not just a legal update. It is a conscious move to strengthen the brand through technological openness.

By adopting one of the most permissive commercial licenses available, Hancom has significantly reduced friction for external developers and global enterprises looking to build on the platform. This is expected to foster the growth of a diverse business model ecosystem including WebApps and SaaS solutions built on #OpenDataLoader PDF.

Comparative table of Apache License 2.0 MIT License

The Apache License 2.0 provides a strong and permissive framework that has significantly influenced the evolution of open-source software. Its main advantages are legal clarity, flexibility, and support for dual licensing making it well suited for a wide range of projects, from big data platforms to modern web technologies such as OpenDataLoader.

Principles of community trust and transparency
Making a comparative analysis of products related to PDF documents-processing technologies, ODL team has concluded that the majority are distributed under restrictive or proprietary licenses. By choosing

Apache 2.0, OpenDataLoader sends a clear and open message to partners and clients:

Our technology is open.
Our roadmap is transparent.
Our community is welcome.

Apache 2.0 is widely recognized as a permissive, business-friendly open-source license. It allows commercial use, modification and integration into proprietary systems. These factors lower adoption barriers and build confidence among users. At the same time, Apache 2.0 preserves intellectual clarity and patent protection, providing legal safety for contributors.

In modern software markets brand trust is built on transparency and collaboration. Open-source licensing is no longer just a development model, it is a brand statement.

Openness strengthens credibility. Credibility strengthens adoption. Adoption strengthens the brand.

Driving ecosystem growth

Openness speeds up innovation.

By choosing Apache 2.0 for OpenDataLoader, the team encourages:
Community contributions: you can create an issue in the GitHub Issues · opendataloader-project/opendataloader-pdf
Benchmark transparency

This creates a stronger technical ecosystem around OpenDataLoader.
By removing licensing barriers, OpenDataLoader enables broader integration and faster innovation.
Open technology builds stronger ecosystems and stronger brands.

Frequently Asked Questions

Q: Why did OpenDataLoader switch from MPL-2.0 to Apache 2.0?

A: MPL-2.0's file-level copyleft requirement created integration friction for enterprise users combining OpenDataLoader with proprietary systems. Apache 2.0 removes this barrier while still providing contributor protections and explicit patent grants.

Q: Does this license change affect existing users?

A: No. Apache 2.0 is more permissive than MPL-2.0, so all existing use cases remain fully supported with fewer restrictions.

Q: Can I use OpenDataLoader PDF in a commercial product?

A: Yes. Apache 2.0 explicitly allows commercial use, modification, and redistribution. You only need to include the license notice and state any changes made.

Q: How does Apache 2.0 compare to MIT for enterprise adoption?

A: Both are permissive, but Apache 2.0 adds an explicit patent grant and contributor license agreement critical protections for enterprise legal teams evaluating open-source dependencies.

Q: How can I contribute to OpenDataLoader?

A: You can open issues or submit pull requests on GitHub (opendataloader-project/opendataloader-pdf). Community contributions are welcome under the Apache 2.0 CLA.
Homepage GitHub

Homepage: https://opendataloader.org?utm_source=medium&utm_medium=blog&utm_campaign=apache2_license_change
**GitHub: **https://github.com/opendataloader-project/opendataloader-pdf?utm_source=medium&utm_medium=blog&utm_campaign=apache2_license_change