Compress a PDF without removing accessibility features

Reduce a PDF's size by identifying what consumes space, changing selected settings, and checking the output against the original. Avoid judging success by file size alone. A tiny file that has lost its structure, unreadable chart labels, or broken form controls is not a successful public document. Keep the original and create separately named candidates so the comparison is reversible.

Define what must survive

Take an illustrative illustrated visitor guide with a map, photographs, a contents page, and booking links. Photographs may tolerate a reduction that makes the fine text on a map unacceptable. The same document also needs a coherent reading sequence and usable destinations. Write these requirements down before choosing an optimization preset; otherwise the only visible comparison may be a smaller number in the file manager.

Record the original file size, page count, relevant standard or review target, and important interactions. Note any known findings before processing. If the input already has missing descriptions, compression will not resolve them, and the final report should not present those old issues as newly introduced by optimization.

Inspect settings instead of trusting a preset name

Adobe's space-use audit documentation describes inspecting how much space different document components occupy. Use that information to target the actual cause of the size. A report dominated by photographs calls for a different investigation from one dominated by fonts or embedded material. Do not assume that all large PDFs contain the same kind of excess.

The optimizer settings reference lists options that can discard document tags, bookmarks, forms, metadata, attachments, and other features. Review those categories before saving. Removing a feature can be intentional in a particular publication, but it must be a content decision rather than an unnoticed consequence of selecting an aggressive preset.

Change one group of settings at a time

Create a conservative candidate first and record the selected settings. Compare it before trying a stronger reduction. Changing image quality, fonts, structure, and interactive elements together makes a regression harder to diagnose. The aim is to learn which change produces an acceptable result for this document, not to discover one universal preset for every publication.

For the visitor guide, inspect a photograph and the smallest map labels at the size readers will use. Check whether symbols that distinguish facilities remain clear. If the map becomes difficult to read, revise that part of the workflow rather than compensating by adding a longer description to an unnecessarily degraded visual. Preserve both a usable visual and an appropriate text alternative.

Compare structure, text, and interactions

Reopen the saved candidate and compare the title, language, tag structure, and navigation with the original. Adobe's accessibility review documentation describes automated findings and items that require manual review. Use an appropriate checker for structural changes, then inspect the particular reader tasks that the document supports.

1. Read a representative passage and compare extracted text, including punctuation, symbols, and numbers.
2. Navigate using the contents page and bookmarks, checking that labels still match their destinations.
3. Follow booking or contact links by keyboard and verify the intended destination.
4. Review table relationships, image descriptions, and the reading sequence in the optimized output.
5. If forms are present, exercise their required interactions and saved output in the declared supported reader.

Publish a measured result with a clear boundary

Choose the candidate that meets the document's requirements and record its actual size. If no candidate provides a worthwhile reduction without damage, retain the larger file or reconsider the source design. Do not promise a standard percentage saving: the result depends on the original content and configuration. The file-size and page-count reference explains why those measurements are not interchangeable.

Save the reviewed output and its settings with the source. Download the file from the real publication URL to check that caching or an older upload has not delivered a different version. Repeat the relevant checks after any subsequent editing. Use the PDF checker and screen-reader workflow as complementary parts of that review, not as a claim that compression itself improved accessibility.

Frequently asked questions

Sources

The statements above rest on the primary sources below. Where a source is a law or standard, the version and date named in the text are the ones checked on the review date. This guide is general information, not legal advice.

1. Adobe: Audit PDF space usage . Measuring the space occupied by document components.
2. Adobe: PDF Optimizer settings . Options that remove structure, navigation, and other features.
3. Adobe: Create and verify PDF accessibility . Automated checks and manual review.