A PDF looks the same to everyone who can see it. To a person using a screen reader, an untagged PDF can be a wall of text read in the wrong order, with images that announce nothing and tables read as a jumble of words. As governments and courts turn digital accessibility from a courtesy into an obligation, the humble PDF has become one of the most common compliance gaps. This article sets out what the rules in India, the EU and the US actually say, what an accessible PDF needs, and how to judge a tool that promises to fix one.
What makes a PDF accessible
Accessibility in a PDF is mostly invisible structure. A tagged PDF carries a hidden map of its content: headings, paragraphs, lists, tables and images. A screen reader follows that map. The essentials are a correct reading order, meaningful headings, alternative text for images that carry information, table headers so cell values make sense, labelled form fields, a declared document language and a usable title. Two standards describe this. WCAG, the W3C's Web Content Accessibility Guidelines, is the reference most laws cite, usually at level AA and version 2.1 (version 2.2 was published in October 2023). PDF/UA, formally ISO 14289, is the technical standard for accessible PDF files themselves.
India: an obligation with growing teeth
The Rights of Persons with Disabilities Act, 2016 requires accessibility of services for persons with disabilities. Commentary on the Act generally reads it as applying to both public and private establishments, including digital services. The clearest recent statement from the courts came on 30 April 2025, when the Supreme Court decided Amar Jain v. Union of India, a case brought by a blind petitioner who could not complete digital KYC. The Court held that inclusive digital access is part of the right to life and liberty under Article 21, and directed changes to the KYC process for people with disabilities. The directions include implementing WCAG 2.1 and the Indian government's own web guidelines, GIGW, setting up grievance mechanisms and helplines, and training staff at regulated entities.
The case concerned digital KYC, so its directions are specific to that setting. But the principle, that digital access is a constitutional matter, is broader, and it gives disability-rights advocates and regulators a stronger footing for challenging inaccessible documents.
The Supreme Court did not write a PDF rule. It made clear that digital access is part of a dignified life.
The European Union: the Accessibility Act is now in force
The European Accessibility Act applied from 28 June 2025. Products and services placed on the EU market or substantially updated after that date must comply, and member states can now investigate complaints, order fixes and impose penalties. Services already on the market get a longer transition, until 28 June 2030 or their next update, whichever comes first. The Act covers areas such as e-commerce, banking services and e-books, so the documents those services produce, statements, contracts, terms and invoices among them, can fall within scope where they are part of the service. The harmonised technical standard is EN 301 549. Indian companies that sell into the EU should not assume the rules stop at the border.
The United States: a rule with a later deadline
In April 2024, the Department of Justice finalised a rule requiring state and local governments to make their web content and mobile apps meet WCAG 2.1 level AA under Title II of the Americans with Disabilities Act. On 20 April 2026 it issued an interim final rule pushing back the deadlines by a year, to 26 April 2027 for larger entities and 26 April 2028 for smaller ones and special districts. According to law-firm summaries of the notice, the Department cited limited resources, slower-than-expected technology, including the limits of generative AI for remediation, and litigation risk. Federal agencies already work under Section 508 of the Rehabilitation Act, which sets accessibility requirements for their electronic content.
