Design

Accessibility Basics for PDF Guides (Readable on Phones and Screen Readers)

Accessibility Basics for PDF Guides (Readable on Phones and Screen Readers)

By AI Creation Forge · 11 min read

The Direct Answer

Start with a single-column layout, large body type, high contrast, and real text (not text locked inside images). Add bookmarks and a linked table of contents so readers can jump sections on a phone. Test on a real device before you publish.

Picture a buyer, call her Ruth, on a bus at 8 a.m., opening a guide she paid for overnight. The page is a screenshot of a two-column spread. She pinches to read a heading, loses her place, and the phone's screen reader says nothing useful because the words are pixels. The file looked finished on a desktop monitor. It is not readable in her hand, and it is not usable with assistive technology.

This article is about that gap: structure, text, and a phone test. It is not a Section 508 certification, and it does not score design tools. A separate production choice, which app to lay the file out in, is covered in Canva vs Adobe InDesign for PDF Guide Design. Use that piece for speed and control. Use this one for whether a person and a screen reader can follow the guide.

Why mobile readability matters for digital guides

People buy PDF guides and open them on phones. A file that only works as a wide poster fails the person who paid. It also fails anyone who reads with a screen reader, magnification, or a simplified reading order.

W3C's Web Accessibility Initiative publishes the standards that define accessible web content and related guidance. The W3C WAI standards and guidelines overview explains that the Web Content Accessibility Guidelines (WCAG) apply to web content, including text and images, and that WCAG can also be applied to documents, as described in WCAG2ICT. Those guidelines are how the field talks about text alternatives, structure, and content people can perceive and operate. This article does not restate the full standard. Read it before you claim conformance.

The U.S. Access Board's ICT accessibility standards address information and communication technology under Section 508 of the Rehabilitation Act and Section 255 of the Communications Act. Section 508 requires access to ICT developed, procured, maintained, or used by federal agencies. Electronic documents are one of the examples the Access Board lists, alongside computers, software, and websites. The standards are mandatory for federal agencies subject to Section 508. They are not a certificate an independent guide seller can award themselves by following a blog checklist.

You might be thinking, "I am not a federal agency, so this does not apply to me." The legal duty described on the Access Board's page is aimed at federal ICT. The reader's problem is still yours if you sold the file. A guide no one can read on a phone, or that a screen reader cannot walk through, is a product that does not match the promise of a practical PDF. Fix the file. Do not print "Section 508 certified" on the cover because you increased the font.

Page size, margins, and single-column layouts

Fixed pages do not reflow the way a web article does. Letter and A4 are fine page sizes for a guide. The reading order inside the page is what breaks on a phone.

Use one column. When a reader zooms a single column, the line still runs in one direction. Two or three columns force horizontal hunting, and they often export in an order that does not match the visual order. A screen reader follows the order in the file, not the order your eye guesses.

Keep margins wide enough that lines are not edge to edge. Short lines are easier to track under magnification. Do not solve a cramped page by shrinking the type. Shrink the content per page instead: one idea, then a break.

Page numbers and a running header can stay, as long as they are real text and they are not the only way to navigate. A phone user who can jump with a linked table of contents will not depend on flipping past decorative chapter openers.

If your layout tool offers a "mobile" or "reflow" export, try it and then run the phone test at the end of this article. A setting name is not a result. Selectable text in the right order is the result.

Fonts, contrast, and heading hierarchy

Body text has to be real text. If you outlined the letters, flattened them into a photo, or exported a page as one image, a screen reader has no words. You also cannot search the guide. After export, drag across a sentence. If the selection grabs characters, you have text. If it grabs a rectangle of the page, you have a picture of text. Rebuild that page.

Pick a body face you can read at arm's length on your own phone without pinch-zoom. That is a practical test, not a number copied from a standard. If you have to zoom, increase the type or shorten the line and export again. Avoid decorative faces for paragraphs. One family for headings and body is enough. Bold for emphasis beats all-caps paragraphs, which are harder to read and are often announced letter by letter.

Contrast means the words separate from the background. Dark text on a light page, or light text on a dark page, with a difference you can see in sunlight on a phone, is the practical bar for this checklist. Pale gray on a tinted panel fails that bar even when it looks elegant on a calibrated monitor. WCAG, published through W3C WAI, is where formal contrast criteria live. This article will not invent a ratio or a score. Check the guideline if you need the numeric criterion, and do not write "WCAG compliant" on the sales page unless you have actually evaluated the file against the version you name.

Heading hierarchy is how both people and software see the outline. One title. Section headings in order. Subsections under the section they belong to. Do not skip levels because a smaller size "looked nicer," and do not fake a heading with bold body text if your tool can mark a real heading. In a tagged PDF, those headings are what a screen reader can list and jump to. Visual size without a heading mark helps a sighted reader and leaves an assistive-tech user paging line by line.

W3C WAI's overview also points to ARIA and other specifications for user-interface structure in web content. A PDF guide is not a web app. You do not need a widget library. You need headings, reading order, and text alternatives that assistive technologies can follow. The overview is the map. The phone test below is the check you can do this week.

Bookmarks and linked TOC

Bookmarks are the PDF panel that lists chapters. Build them from the same headings as the document, in the same order, with names a person would recognize. "Section 3" is weaker than the section's real title. A buyer on a phone opens the bookmark list and jumps. A screen-reader user can often move by the same structure when the file is tagged to match.

A linked table of contents does the same job inside the first pages. Each entry should be a link to that heading, not a line of text that only looks like a link. Test every link. A contents page that sends people to the wrong section is worse than no link, because it teaches them not to trust the next one.

Add bookmarks even if you also have a linked contents page. Some phone viewers hide one and show the other. Redundant navigation is a feature here.

If the guide is the free chapter you give away for an email, the same navigation belongs in that shorter file. Turn One Chapter Into a Lead Magnet is about what to give away. This article is about making that file, and the paid one, something people can move through.

Alt text for figures and diagrams

W3C WAI treats text alternatives as part of accessible content: images carry information, and that information needs a text form. For each figure in the guide, write what a reader must know that the surrounding paragraphs do not already say.

"Chart" is not alt text. "Bar chart of three unnamed months" is still thin if the point of the figure is which month was highest. State the point: "Bar chart showing March higher than January and February in this illustrative example." If the paragraph under the figure already states that point in full, the alt text can be shorter and should not dump a second essay into a screen reader.

Decorative rules, empty boxes, and repeated icons that add no information should not be announced. Mark them as background or artifacts when the tool allows, so the reading order stays on the words.

Diagrams with arrows need a text path. Describe the sequence: "Three boxes in a row: outline, draft, edit." A reader who cannot see the arrows still gets the order.

Complex tables are better as real tables with header cells than as pictures of tables. If you can only export a picture, put the same numbers in text next to it and say so in the alt text. Do not rely on color alone. If a step is "the red row," also label it with words.

Images you did not create raise a separate ownership question. Alt text does not give you a copyright in a generated picture. How to Disclose AI Help When You Sell a PDF Guide covers what you can claim and what you should say on the sales page.

Export checklist from common design tools (high level)

Canva, Word, Google Docs, InDesign, and similar tools can all export a PDF. This list does not rank them and does not assign scores. After any export, check the file, not the menu label.

The Canva and InDesign comparison on this site is about production, not about which app is "more accessible." Either tool can produce a file that fails the checks above. Either can produce a file that passes a basic phone test if you set headings, real text, and links on purpose.

If a vendor advertises an "accessible PDF" button, run the same checks. A button is not a conformance claim you can repeat.

Quick phone test before launch

Do this on a device you can hold. A desktop preview window is not the test.

1. Send the PDF to your phone and open it in the viewer your buyers are likely to use, not only inside the design app. 2. Read one full section without pinching. If you pinch to recognize words, increase type or margins and export again. 3. Use the contents links and the bookmarks. Jump to a late section and back. 4. Turn on the phone's screen reader. On an iPhone that is VoiceOver. On many Android phones that is TalkBack. You do not need to be an expert. Move through one section and listen. 5. Check three things in that audio: a heading is announced as a heading, a figure is described with your alt text rather than "image," and the spoken order matches the order a sighted reader would use. 6. Fix the first failure and test that section again. Then listen to a second section so you are not only checking the page you just edited.

This pass will not find every barrier. It will catch flattened text, missing headings, empty alt text, and a reading order that snakes through columns. It is not a Section 508 conformance test, not an audit, and not a certification. Federal agencies have their own obligations under the Access Board's standards. Your job as a guide seller, on this checklist, is to ship a file a person can read on a phone and a screen reader can start to follow.

When the phone test matches what you hear, put the file in front of a buyer. Until then, the guide is still a draft, no matter how finished the cover looks.

FAQ

Is this a Section 508 certification guide? No. The Access Board's ICT page explains that Section 508 standards apply to federal agency technology, including electronic documents. This article is a practical checklist for independent PDF sellers. It does not certify a file.

Do I have to follow WCAG? W3C WAI publishes WCAG and notes that it can be applied to documents. Whether a law requires you to conform depends on your situation, which this article does not decide. Using the ideas here (real text, structure, text alternatives, contrast you can actually see) makes the file more usable either way. Do not claim conformance you did not evaluate.

What font size should I use? There is no single size in the sources this article cites. Read the exported PDF on your phone. If you cannot read the body without zooming, the type is too small for that layout.

Are bookmarks the same as a table of contents? They do the same job from different places. Bookmarks live in the viewer's panel. A linked table of contents lives on a page. Include both.

What if my tool cannot add alt text? Put the figure's point in the paragraph next to it, in real text, and say in the caption what the figure shows. Then consider a tool that can attach alt text before you call the file accessible. A caption is not a full substitute when the image is the only place the information lives.

Does a screen reader test mean the PDF is done? It means you checked one path. It does not replace the W3C guidance or, for federal work, the Access Board standards. It does catch the failures buyers feel first.

Should the free lead magnet follow the same rules? Yes. A short file still needs real text, a sensible order, and a way to move if it has more than one section.

Where are the sources? The W3C WAI standards overview and the U.S. Access Board's ICT accessibility page, linked below. This article does not add tool rankings or invented scores.

Sources