Free PDF editing and file tools

Open a PDF to edit, annotate or add a visible signature. Combine several PDF documents, split selected pages, or compress a document for easier sharing.

Run a preliminary PDF accessibility check

Use a browser-local, read-only inspection of title, document language, tagging metadata, form tooltips and a bounded text-layer sample. Download an explanatory JSON report. This is an early warning tool, not WCAG or PDF/UA certification.

Use this tool in the editor above

Browser-local PDF processing · No required account · No watermark · Public Beta

Accessibility is more than a PDF that opens

An accessible PDF typically requires meaningful document structure, document language, helpful form labels, understandable navigation, correct text reading order, alternate descriptions for graphics and usable color contrast. A PDF can contain selectable text but still be difficult to use with a screen reader. Conversely, a PDF with no extractable text may be blank or a scanned image.

LHTSOFT PDF provides a preliminary inspection, not a PDF/UA or WCAG conformance certificate. The tool reads recognizable metadata and structural indicators to help you decide which document issues deserve manual follow-up. It cannot prove that a structure tree has correct semantics or that readers will speak the content in the intended order.

Run the browser-local review and save a findings report

The scan runs in your browser, is read-only, supports PDFs up to 32 MiB and 2,000 pages, and checks text extraction on at most 30 pages. Existing PDF bytes and Undo history are untouched. Any unscanned pages are explicitly reported.

  1. Open a PDF on your device and choose Tools > Accessibility preflight, or expand the section in the Document Properties tool.
  2. Click Check accessibility basics. The editor inspects standard document title, catalog language, tagged structure-tree marker, marked-content flag, viewer title display preference and conventional form tooltips.
  3. For files within the stated limits, the first 30 PDF pages are also scanned for extractable text. Pages without text are listed as review candidates rather than automatically declared inaccessible.
  4. Download the JSON report and compare the findings to your source document. Use a dedicated PDF/UA validator and assistive technology for a complete assessment.

What each finding can and cannot establish

The document title is read from the standard PDF Info dictionary and may not match title metadata stored elsewhere. Catalog language is checked for a plausible language tag; it is not checked against every word. A structure-tree dictionary or /MarkInfo /Marked flag shows that some tagging metadata exists, but does not prove logically ordered headings, complete tags or correct image alternate text.

AcroForm tooltip checks look for directly defined /TU strings on supported conventional fields. A missing tooltip may be compensated for by another accessible label in some readers, and a present tooltip does not prove it is meaningful. Fields inside XFA or unusual parent structures may be unverified. No automated color contrast, image alt-text, heading hierarchy, reading-order or screen-reader test is performed.

Practical remediation and privacy

Set a meaningful document title and document language in the authoring tool when possible. Create true headings and tags in Word, InDesign or another supported editor before exporting the PDF. Give graphics accurate descriptions and verify tab order and field labels with an assistive technology tester. If any page is a scan, consider an OCR workflow appropriate to your security requirements; LHTSOFT PDF does not claim to include OCR under its no-AI policy.

The report contains summary metadata and page indexes but not the original page text or any uploaded file. It is created locally and downloaded as JSON. Avoid treating a report with few warnings as a clean certificate: PDF/UA and WCAG validation require more thorough automated and human review.

How to use this tool

  1. Open a PDF and choose Tools > Accessibility preflight.
  2. Run Check accessibility basics; no PDF content is uploaded or modified.
  3. Review metadata and text extraction findings and download the JSON report.
  4. For formal compliance, test the PDF in a specialized validator and with assistive technologies.

Related PDF tools

PDF editing depends on fonts, encryption and source file structure. Modifying digitally signed PDFs can invalidate signatures. Visible signatures do not provide certificate verification, and deleting comments is not guaranteed secure erasure. Keep the original and inspect downloaded copies in another PDF reader.