support@accesssure.in | +91 8691-914444
ITQCR · STQC SAB SETL-1 Empanelled Lab
Home/Platforms/PDF Accessibility Engine
Built inside ITQCR · STQC SAB SETL-1 empanelled testing laboratory

Every other PDF accessibility tool hands you a report. We hand you back a fixed PDF.

An AI remediation engine for PDF/UA-1 and WCAG 2.2 AA, built for Indian content. Upload a PDF — scanned or digital, Hindi or Bengali, government circular or banking disclosure. Sixty seconds later, you have a tagged, accessible version that veraPDF verifies independently. ₹5 per page. Fifty pages free on signup.

60s
Average remediation
per document
94.7%
veraPDF rule pass
across customer corpus
105/106
PDF/UA-1 rules
on a real banking document
13
Indian languages
natively supported
The remediation difference

Auditors find the problems. We fix them.

The PDF accessibility industry is built on the idea that a tool's job is to tell you what is wrong with your document. Adobe Acrobat Pro's accessibility check, axe for PDF, the PAC checker — all of them produce a list. None of them produce a fixed PDF. AccessSure inverts that idea. Validation is a quality gate on the remediator's output, not the product you pay for.

Conventional tools

Audit and report

  • ×Scan the PDF and list violations by clause
  • ×Hand the report to a trained accessibility specialist
  • ×Two to five days of manual remediation per document
  • ×₹2,000 to ₹8,000 per document at typical Indian rates
  • ×Verification is the next sale, not the deliverable
AccessSure PDF

Actually remediate

  • AI detects structure, images, headings, reading order, language
  • Generates tag tree, alt text, metadata, PDF/UA-1 catalog
  • Sixty seconds per document, on a single upload
  • ₹5 per page on pay-as-you-go; from ₹50 per document at volume
  • veraPDF verification bundled in the output — independent and reproducible
Externally verifiable

The score is veraPDF's. Not ours.

Every PDF accessibility vendor reports a compliance percentage. Most are computed by the vendor's own validator against rules of the vendor's choosing. The number means nothing the moment a buyer's auditor runs their own check and sees a different result.

AccessSure uses veraPDF — the open-source PDF/UA-1 conformance validator built by the PDF Association and the Open Preservation Foundation — as the headline score. The number you see is the rule pass rate against ISO 14289-1. Anyone with veraPDF installed on their machine can re-run the validation and confirm the same number. STQC reviewers use it. EU national libraries use it. We use it because the alternative is asking buyers to trust us, and asking is the wrong starting point.

The certification threshold is set at 90 percent veraPDF rule pass. Documents below that bar receive their audit report — we will not stamp a compliance certificate on a PDF the open-source validator does not endorse.

Best documented case

105of 106
PDF/UA-1 rules passed on a real Indian banking loan certificate — a bilingual, stamped, originally untagged scan.
veraPDF rule set: ua1 (ISO 14289-1). Verification timestamp embedded in output metadata. Re-runnable with verapdf -f ua1 output.pdf. The one residual rule is an artifact-marking heuristic on the logo image — a known engineering target, not a customer-facing defect.
The output bundle

What you actually receive.

One upload returns four artifacts — every one of them defensible in an audit room. No exports. No conversion steps. No "send a separate request for the certificate."

01 · PDF

The remediated PDF

Fully tagged structure tree. Document language set. Title metadata corrected. Reading order rebuilt. Decorative content marked as artifact. Alt text on every figure. The page looks identical to the original; the structure underneath is rewritten.

02 · HTML

The criterion-level audit report

Per-criterion status with evidence — page numbers, hex colour pairs for contrast, structure tree counts, OCR confidence. Not a checklist. A reproducible audit you can hand to a STQC reviewer without further explanation.

03 · PDF

The compliance certificate

Issued for documents scoring at least 90% veraPDF rule pass against ISO 14289-1. References the rule set version, timestamp, and the empanelled lab credentials of the issuing entity. Below 90%: audit report only, no certificate.

04 · ZIP

The evidence pack — for the auditors who will not believe you

Before-and-after page renders. The raw veraPDF JSON output. The internal WCAG validator output. The structure tree dump. The OCR confidence map. If your compliance reviewer is the kind of person who asks how you arrived at your numbers, this is the answer to that conversation. Bundled as a single ZIP with every job.

India-first by design

Built for the languages your auditors actually test in.

Most global PDF tools ship with English-only OCR and treat Indian-language documents as edge cases. That is a problem for any government department, any bilingual circular, any annual report from a state-listed PSU, any university transcript. AccessSure was built the other way round. Thirteen Indian scripts are first-class citizens of the pipeline — recognised, tagged, language-attributed, and rendered correctly for regional screen readers.

हिन्दीHindi தமிழ்Tamil తెలుగుTelugu বাংলাBengali मराठीMarathi ગુજરાતીGujarati ಕನ್ನಡKannada മലയാളംMalayalam ਪੰਜਾਬੀPunjabi ଓଡ଼ିଆOdia অসমীয়াAssamese اردوUrdu English(en-IN)

Bilingual documents — Hindi and English on the same page, the typical pattern for central government circulars — are detected automatically and tagged with en-IN or per-span /Lang markers where dominance is mixed. No manual configuration needed.

The pipeline

Four steps. Sixty seconds.

What happens between drag-and-drop and the green tick. The pipeline is deterministic where it can be — structure inference, tag tree construction, validation — and uses AI only for the tasks that genuinely need language generation: alt text and document titles.

01

Upload

Drag and drop, or batch upload up to several hundred PDFs at once. Up to 100 MB per file. Scanned, digital, or mixed.

02

Structure detection

OCR runs on scanned content across the thirteen-language pipeline. AI-driven object detection identifies figures, tables, and charts. Headings and reading order are inferred from layout. AI generates alt text and document titles where missing.

03

Tag tree construction

PDF/UA-1 structure tree built deterministically — Document → H1..H6 → P / L / Figure / Table. ParentTree wired. Artifacts marked. Language attributes set per page and per span. Metadata stream injected.

04

veraPDF verification

The remediated PDF is fed to veraPDF. Rule pass rate calculated. Compliance certificate issued if the document scores 90% or higher. Output bundle assembled. Wallet charged for the pages processed.

Pricing

What it actually costs, in rupees.

No annual licence. No enterprise contract minimums to access the engine. A prepaid wallet via Razorpay, drawn down by pages remediated. New accounts start with 50 free pages — enough to remediate a complete board report, a financial statement, or a fortnight of office circulars before you have committed a rupee.

For perspective: manual PDF remediation by a trained accessibility specialist in India runs ₹2,000 to ₹8,000 per document. CommonLook and Equidox start at $299 to $349 per user per month in USD, with an annual minimum. AccessSure removes both the labour cost and the foreign-currency floor.

All prices in Indian Rupees, exclusive of GST. Enterprise commitments above 10,000 pages per month qualify for the ₹50-per-document floor under a custom contract.

New account — sign up 50 pages free
Pay-as-you-go ₹5/ page
Starter (monthly wallet refill) ₹4/ page
Business (priority queue) ₹3/ page
Enterprise (volume) from ₹50/ doc
Standards in scope

What the output is conformant to, and verified against.

Four documents define what "PDF accessibility" means in any defensible audit. AccessSure produces output aligned with all four, with veraPDF as the one machine-checkable proof point.

Verified standard
PDF/UA-1
ISO 14289-1:2014. Verified per-job by veraPDF. The score you see is this score.
Conformance target
WCAG 2.2 AA
For the criteria that apply to static PDFs per the W3C's WCAG2ICT mapping.
Indian context
GIGW 3.0
MeitY guidelines for Indian government websites, including downloadable PDF artefacts.
SEBI mandate
IS 17802
Indian Standard for ICT accessibility — the testable basis for the August 2023 SEBI circular.

Also referenceable: Section 508 (US Federal), EN 301 549 (European public sector), RPWD Act 2016 (India). Full WCAG 2.2 mapping →

Where it matters

When the page is real, and the audit is coming.

Three contexts where automated PDF remediation moves the needle from "compliance theatre" to "actually accessible." Each one carries a specific deadline pressure that manual remediation cannot match.

GOVERNMENT

Central and State government circulars

MeitY circulars are bilingual (English + Hindi or an Indian regional language), released on short timelines, and required to ship as accessible PDFs under GIGW 3.0 before being uploaded to the ministry portal. Manual remediation breaks the publication cycle. AccessSure absorbs it.

GIGW 3.0 · PDF/UA-1 · STQC CQW readiness
SEBI · LISTED

SEBI-mandated annual disclosures

Since the August 2023 SEBI accessibility circular, listed companies, mutual funds and stockbrokers must publish accessible annual reports and disclosures. Hundreds of pages, dense tables, exhibits, signatures. AccessSure ships them in hours; manual remediation takes weeks.

IS 17802 · WCAG 2.2 AA · SEBI Cir/CFD/CMD/...
EDUCATION · BFSI

Education and banking documents

Admission notifications, transcripts, marksheets, loan certificates, KYC forms — the long-tail of documents that fall under RPWD Act provisions and that no manual team can keep up with at the volumes BFSI and education institutions actually publish. Pay-per-page pricing matches the long-tail shape.

RPWD Act 2016 · PDF/UA-1 · WCAG 2.2 AA
Questions buyers ask

The things compliance teams actually want to know.

Not the polished marketing FAQ. The ten questions we hear in every prospect call, answered the way we answer them on a call.

Still unanswered?
support@accesssure.in
Does the visual layout of my PDF change after remediation?
No. The remediation engine preserves the visible page rendering byte-for-byte where possible. What changes is the invisible structure layer underneath — the tag tree, the reading order, the language attributes, the metadata. Open the before and after side by side in any PDF viewer and you will see no difference. Run a screen reader on each and the difference is total.
What about scanned PDFs?
Scanned PDFs are handled through a thirteen-language OCR pipeline. The engine OCRs the page, builds an invisible text overlay aligned to the image, then constructs the accessibility tag tree on top of that text layer. The visual page remains the original scan; assistive technology gets a fully readable document.
How is the compliance score externally verified?
Every remediated PDF is validated by veraPDF. The score reported is the rule pass rate (passed_rules ÷ total_rules) from veraPDF's ISO 14289-1 rule set. Anyone with veraPDF installed can re-run the validation and confirm the number independently. This is not vendor self-report.
What WCAG version and level does AccessSure target?
WCAG 2.2 AA as the stated target, with PDF/UA-1 (ISO 14289-1) as the externally verified standard. The two overlap substantially for static PDF content. For the WCAG criteria that are PDF-applicable per the W3C's WCAG2ICT mapping, the engine produces output that passes the static-document subset of 2.2 AA.
What is the compliance certificate, and when is it issued?
A downloadable PDF certifying that the remediated document achieved a veraPDF rule pass rate of at least 90 percent against ISO 14289-1. It references the validation timestamp, rule set version, rule rate, and the empanelled lab credentials. Documents below 90 percent receive the audit report but not the certificate — we will not certify what veraPDF will not.
How does AccessSure differ from Adobe Acrobat Pro auto-tag?
Acrobat Pro's auto-tag is a desktop feature that ships acceptable structure on simple Latin-script documents. It produces poor results on scanned PDFs, on Indian-language content, and on bilingual government circulars. AccessSure is purpose-built for the Indian compliance context — thirteen-language OCR, bilingual handling, GIGW-aware output, and veraPDF verification on every job. Acrobat does none of those four things.
What if my PDF has complex tables or nested lists?
Simple data tables and ordered/unordered lists are detected and tagged correctly. Heavily nested tables, complex matrix layouts, and mathematical typesetting are areas of active engineering. For those documents we recommend the manual remediation route through our audit lab. The honest answer is that no current tool — automated or assisted — handles arbitrary complex tables perfectly.
Can I use AccessSure for STQC / GIGW 3.0 submission?
Yes, and this is the use case the engine was built for. The output is PDF/UA-1 conformant per veraPDF, with WCAG 2.2 AA structural targets and the language metadata GIGW 3.0 requires for bilingual government content. Many STQC reviewers run veraPDF themselves; the AccessSure score matches what they will see.
What happens if the engine cannot fully remediate a PDF?
The customer receives the audit report regardless, with manual-review items flagged. The wallet is charged for the pages processed. If a PDF is fundamentally unfixable — encrypted with no accessibility permission, corrupt, or zero-byte — the job is rejected before any charge is applied. We do not ship degraded PDFs as a successful output.
Try it on real documents

Upload your worst PDF. Fifty pages, free.

The fastest way to decide if AccessSure is right for your compliance position is to put a real document through it. No demo file, no sample data. Use the gnarliest bilingual circular or the most-marked-up annual report you have. If we cannot remediate it, you have not spent a rupee.