Make a PDF Accessible
Turn a normal PDF into one a blind person can read with a screen reader. We detect the structure — you confirm it in a few clicks.
How it works
Upload a PDF
A text document - report, letter, form, or syllabus. The tool analyzes the structure automatically
Confirm the structure
Click on the document to mark headings, describe images, and confirm tables
Download an accessible PDF
A compliant PDF/UA file that screen readers read correctly, including Hebrew
Key Features
- Automatic structure detection. Headings, images, and tables are pre-detected and marked on the document - you only confirm or fix with a click, instead of marking everything from scratch
- Correct Hebrew reading order. Hebrew text is stored in the correct reading order, so screen readers read it properly - not reversed, as happens with most tools built for English
- Alt text for images. Add a short description to each meaningful image, or mark it decorative so the screen reader skips it silently
- Tables with headers. For each table, choose where the headers are - top row, first column, or both - so the screen reader connects every cell to the right header
- Reading preview before download. See exactly what the screen reader will hear, page by page - and fix issues before downloading
- Official standards validation. The file is automatically checked against PDF/UA-1 (ISO 14289), and if it passes you get explicit confirmation on the final screen
Why Make PDFs Accessible?
Accessibility regulations in many countries require public bodies, local authorities, educational institutions, and businesses serving the public to make the documents they publish online accessible. A registration form, annual report, tender, meeting minutes, course syllabus - every such document needs to meet the accessibility standard, which for PDF files means PDF/UA. An inaccessible document exposes the organization to complaints and lawsuits - and above all leaves part of the public out.
The problem: professional remediation of a single document can cost hundreds and take days, and existing tools require expensive software and technical expertise. Hebrew adds a unique difficulty - most remediation tools were built for English and break the reading order of Hebrew text, so screen readers read it backwards. The result: many organizations simply give up, and their documents stay inaccessible.
This tool was built exactly for that gap: remediation with full Hebrew support, free, nothing to install, no prior knowledge. Automatic detection does most of the work, your confirmation takes minutes, and the result is officially validated against the standard. Even without a legal obligation you gain: an accessible document is one everyone can read - including a student with low vision receiving your syllabus, or an older customer who relies on read-aloud.
How Does PDF Remediation Work?
A screen reader is software that reads aloud what appears on screen, for people who are blind or have low vision. For it to know what to read and in what order, the PDF must contain a hidden structure: what is a heading and what is a paragraph, what each image shows, where each table begins and ends. Most PDFs are created without this structure - they look great on screen, but a screen reader reads them as a confusing stream, skips images, and breaks tables. With Hebrew it is even worse: many files store the text in reversed order, so the reading comes out as gibberish.
The tool does the heavy lifting for you: upload the file, and the system automatically detects headings, images, and tables. What remains is to confirm - click a line in the document and answer a simple question ("main heading or normal text?"), add a short description to each meaningful image, and choose where the headers are in each table. No technical knowledge, no jargon - everything in plain language, directly on the document.
Before finishing, the reading preview shows exactly what the screen reader will hear - page by page, with Hebrew in the correct order. When you confirm, the system builds the tagging layer inside the file and runs automatic validation against the international accessibility standard PDF/UA-1 (ISO 14289). If the file passes, you get explicit confirmation. The document's appearance does not change at all: same layout, same fonts, same colors.
Frequently asked questions
What is an accessible PDF?
An accessible PDF contains, beyond what you see on screen, a hidden structure layer: what is a heading and what is a paragraph, what each image shows, where each table starts, and in what order the content should be read. This structure is what lets a screen reader - the software blind people use - read the document sensibly. The document looks exactly the same, but becomes readable to people who cannot see it.
Does the tool handle Hebrew documents?
Yes - it was built for exactly that. The most common failure in Hebrew document remediation is reading order: tools built for English store Hebrew text in reversed order, so the screen reader reads gibberish. This tool fixes Hebrew reading order as part of the process, and the reading preview lets you verify the result before downloading.
I have a scanned document - can I make it accessible?
A scanned document is essentially a photo of paper, with no real text to tag. Run the "Make searchable" (OCR) tool first to recognize the text, then come back and remediate the new file. Special case: documents from legacy software that look fine but have broken text encoding are detected automatically and their text is restored as part of remediation.
What is alt text and why do images need it?
A screen reader cannot see what an image shows - it can only read a description someone wrote. Alt text is a short sentence describing the image: "CEO signature", "Q3 sales growth chart". Without it, a blind reader simply loses that information. Purely decorative images are marked as decorative, so the screen reader skips them silently.
How do I know the file is really accessible?
When remediation finishes, the file is automatically validated against the PDF/UA-1 standard (ISO 14289), and if it passes you see an explicit confirmation. Before downloading, the reading preview shows exactly what the screen reader will hear, page by page.
Do I need technical knowledge?
No. The tool detects the structure automatically and asks simple questions: "Is this line a heading or normal text?", "What does this image show?". You do not need to know the standard, heading levels, or any technical terms. Professional manual remediation can cost hundreds per document - here you do it yourself, free, in minutes.
Does remediation change how the document looks?
No. Everything added to the file - heading tags, image descriptions, reading order, document title - is a hidden layer used by screen readers. The printed and on-screen document looks exactly like the original, including layout, fonts, and colors.
This tool helps create accessible documents, but does not constitute legal advice and does not guarantee compliance with all legal requirements. Meeting the accessibility obligations that apply to your organization is your responsibility alone, and we recommend consulting a certified accessibility expert about your specific requirements.