# Accessible PDF vs HTML: why a web view isn't the whole fix Canonical: https://paperlyft.com/articles/accessible-pdf-vs-html By Shubham Tiwari Published: 2026-10-22T12:10:50.659Z Updated: 2026-10-22T12:10:50.659Z An accessible web view helps people reading online, but the PDF still gets downloaded, emailed, printed, requested and kept. Here’s where a web view falls short, what ADA Title II says about separate accessible versions, and why fixing the document itself matters. More offices are adding accessible web versions of their PDFs. A resident clicks a document and sees its content as a web page a screen reader can read. For reading on the website, that helps. Here is the short answer. An HTML version makes a document easier to read online. It doesn't make the PDF accessible. People still download, print, email, request and keep the PDF. And under ADA Title II, a separate accessible version is only allowed in limited cases. We kept running into this question while talking with county teams: if residents can read it on the site, isn't that enough? This post explains where a web view helps and where it stops. ## Key Takeaways - A web view helps people reading on your website. It doesn't change the PDF underneath. - The PDF still travels: downloads, email attachments, printouts, records requests and archives. - The ADA Title II rule allows a separate accessible version only when the original can't be made accessible for technical or legal reasons. To be fair to HTML, it is often the better format for reading online. Web pages reflow on phones, work well with screen readers and are easy to navigate. If you are publishing new content that people only read on your site, a web page is a good choice. The problem starts when the web view is placed in front of a PDF as a replacement for fixing it. ## Where the PDF still shows up A web view covers one path: someone reading on your website. Documents take many other paths. - Downloads. The download button gives people the original PDF, not the web version. - Email. Staff send PDFs as attachments to residents, vendors and other agencies every day. - Print. Agendas, notices and forms get printed, handed out and sometimes scanned again. - Records requests. When someone asks for a record, they ask for the document, not a web page. - Archives. Records retention schedules keep the original file, often for years or decades. - Other sites. State portals, partner agencies and news outlets repost the PDF itself. On every one of these paths, a screen reader user gets the original file. If that file is [a scan with no tags](), they get nothing. ## What ADA Title II says about separate accessible versions WCAG has a concept called a conforming alternate version: a separate, accessible version of content that isn't accessible itself. The [ADA Title II]() rule limits when public entities can rely on one. It allows them only where it isn't possible to make the content directly accessible because of technical or legal limitations. The DOJ gave its reasons. Separate versions can create a segregated experience for people with disabilities, and two versions tend to drift apart over time. Guidance from state accessibility offices also notes that a lack of knowledge or training doesn't count as a technical limitation. **Note** The rule's default is to fix the document itself, not to build a second copy next to it. Whether a specific setup meets the rule depends on the details, so it is worth checking with your county attorney or ADA coordinator. ## Why a web view is a temporary fix - It depends on the platform. If you change website vendors or end a subscription, the web versions can go with it. The original PDFs stay exactly as they were. - Two versions drift apart. When someone updates the PDF, the web version has to be updated too. One of them eventually falls behind. - Records outlive websites. A county website might be redesigned every few years. The records on it are kept much longer. ## When a web view still makes sense A web view is a good addition, not a replacement. It works well next to an accessible PDF, especially for long reports people read online. It can also help as a stopgap while a backlog is being fixed, as long as the documents themselves are on the list. ## What to do instead - Fix the original documents, starting with forms, applications and current notices. - Offer an HTML version as an extra, alongside an accessible PDF. - Make new documents accessible before they are posted. - Have a plan for older records, so you can turn one into an accessible file quickly when someone asks. ### Questions and answers **Is HTML more accessible than PDF?** For reading online, it often is. But any PDF you post or share still needs to be accessible on its own. **Does an HTML version of a PDF meet ADA Title II?** Only in limited cases. The rule allows a separate accessible version only when the original can't be made accessible for technical or legal reasons. **If my website is accessible, do my PDFs still need to be?** Yes. PDFs posted on your site count as web content under the rule, and they also get downloaded, emailed and requested. Send us a document. We'll show you the accessible version of the file itself. [Request access]() ## Sources - ["The ADA Title II rule limits when public entities can rely on one"]() - ["a lack of knowledge or training doesn't count as a technical limitation"]()