PDF accessibility basics when you only have scans

Accessible PDFs expose structure: headings, lists, tables, and alt text for figures. Screen readers navigate that tree. A scan PDF is one picture per page—usable visually, silent for assistive tech until text and tags exist.

QuickConvert’s browser tools help you build better inputs: Office to PDF from structured Word files, Image OCR for text drafts, PDF Merge for packets. Finishing tags may still need desktop software for public sites.

Start with structured sources

When you can, author in Word with heading styles, export to PDF locally or via Office to PDF, and keep headings in the source. Scans should be the fallback, not the first choice for public information.

OCR text is a starting point, not accessibility compliance. Screen readers want tagged order, not a plain text file dumped beside an image. Still, OCR helps editors rebuild content faster than typing 40 pages.

Export scans with PDF to Images, OCR segments, and paste into a structured template. Publish the tagged export your organisation requires.

Alt text thinking

Every meaningful figure needs a short description. Decorative lines do not. When charts are central, describe trend and units in prose near the figure.

Low-contrast grey text fails readers with low vision. Watermarks that are too dark interfere—tune PDF Watermark opacity on public drafts.

Do not rely on colour alone for meaning in charts; label series directly.

Multi-column layouts confuse assistive tech when tags are wrong. Single-column source simplifies life. For newsletters, use simple Word columns sparingly.

Merged PDFs combine whatever order you set in PDF Merge. Put cover letter before exhibits so screen reader order matches human expectation.

Fillable PDF forms need labeled fields. Scanned forms are flat images unless someone adds fields in Acrobat or similar. Signatures may be images merged from Images to PDF.

Tell users when a PDF is image-only so they know to request an accessible alternate format.

Many jurisdictions require accessible government communications. QuickConvert is a toolkit, not a certification service. Validate with checkers your org trusts.

Accessibility work often involves disability-related documents. Keep OCR and conversion local when possible—QuickConvert’s browser model helps.

Tag the document language in source apps when available. Write link text that makes sense out of context, not “click here”.

Cross-link longer guides on privacy when explaining why local processing matters for sensitive health PDFs.

Is QuickConvert PDF/A tagged? Not by default. Use specialised export for strict archives.

Can OCR alone make WCAG? No. Tags and structure remain required.

Should headings be typed? Yes in source Word files.

What about math PDFs? Use formats your audience’s tools support.

Can I test with a screen reader? NVDA and VoiceOver are free tests on desktop/mobile.

Do watermarks hurt accessibility? If they obscure text, yes. Keep opacity low.

Are merged scans accessible? Only if you add text layers and tags later.

Who fixes public PDFs? Usually communications staff with desktop tagging tools after content is final.

Publish an email address for accessible format requests beside PDF downloads on your site. When the public PDF is a scan, the alternate might be HTML rebuilt from OCR under human review. QuickConvert helps produce the text draft; policy decides the SLA.

Train front desk staff to offer the alternate without making people prove disability. Good faith requests should not require forms.

Post the expected turnaround time beside the contact link so requesters know a human will rebuild the document, not an instant bot.

Municipal PDFs

Council agendas uploaded as scans frustrate residents using screen readers. Offer HTML agendas alongside PDF scans until tagging budget exists. Announce both links in the meeting notice.

University syllabi

Students need headings for weekly topics. Word-authored syllabi exported with Office to PDF beat scanned flyers taped to doors.

Healthcare leaflets

Patient education PDFs must describe diagrams, not only show them. OCR draft text helps writers write alt text faster, but clinicians should approve medical wording.

Procurement

Vendor PDFs in RFPs are often scans. Procurement officers can request machine-readable copies in the RFP template language before award.

Testing cadence

Quarterly, run a screen reader on your top ten public PDFs. Log failures in the same tracker as website bugs. Accessibility is regression testing, not one project.

Link readers to Image OCR for internal remediation drafts, but never imply OCR alone satisfies law or policy without review and tagging.

Merged packets via PDF Merge should list exhibit order in the cover letter so assistive tech users get a roadmap even when exhibits remain images.

Caption videos with transcripts even when the downloadable handout is a PDF scan; multimedia accessibility spans more than one file format on the same policy page.

Invite disability advocates to user-test new PDF templates before mass mailing; a thirty-minute session finds heading mistakes templates hide from sighted reviewers.

School districts posting IEP summaries as scans should plan upgrades: parents searching for services by keyword need text, not only pictures of pages.

Transit agencies posting schedule PDFs should not rely on scan images of printed timetables; structured data feeds and tagged PDFs serve riders who cannot read tiny columns on phone photos.

Federal contractors maintaining Section 508 inventories should tag QuickConvert as a client-side prep tool, not as the final certifier, in the architecture diagram auditors request each year.

Museum audio guides linked from QR codes should still provide text transcripts for deaf visitors; the QR landing page is part of the accessible experience, not an afterthought to the exhibit scan PDF.