Add accessibility tags to a PDF
Mark a PDF as a "tagged" document and declare its language and title: three pieces of information that screen readers and accessibility checkers look at first. 100% local processing in your browser — your file never leaves your device.
How it works
Screen readers and accessibility checkers (such as PDF/UA checklists) always start by looking at three signals: the "tagged document" flag (/MarkInfo), the document's declared language, and its title. This tool sets these three elements directly in the PDF structure, without going through a server.
Does this make my PDF fully accessible?
No, and it's important to know that: full accessibility tagging also requires a logical structure tree (headings, paragraphs, lists, tables) and alternative text on every image, which generally calls for specialized software (Adobe Acrobat Pro, or an accessible export from Word/InDesign). This tool lays the minimum groundwork — general tagging, language, title — but does not build that detailed structure tree.
Why declare the document's language?
A screen reader uses the declared language to choose the right pronunciation and speech synthesis engine. Without it, the reader has to guess, which often results in the wrong accent or intonation, especially on technical terms or proper names.
100% local processing: the PDF is modified entirely in your browser — your document is never sent to a server.