The Church Bulletin PDF Problem Most Churches Don’t Know About

Someone on your team put real effort into the bulletin this week.

They confirmed the order of service. They got the announcements right. They made sure the event details were accurate. Then they saved the church bulletin PDF, uploaded it to the church website, and sent the link to the congregation.

That is not a small thing. It means someone thought beyond Sabbath morning and tried to reach people where they are. The instinct was right.

But most churches haven’t had a chance to think through what actually happens next: what it looks like when someone opens that PDF on their phone. The gap between "we posted it" and "people can actually read it" is wider than most bulletin coordinators realize, and most members will never say anything about it.

The bulletin still does its job on Sabbath morning. But when that same file goes online, designed for paper, formatted for a folded page, sized for a printer, it enters a world it was never built for. This article is about what happens in that gap, why it matters, and what you can do about it.

The experience your members won’t tell you about

Here is a scene that plays out in more congregations than most churches realize.

A church member visits a new church. He prefers digital. If he can avoid picking up a paper bulletin, he will. So before he arrives, he goes to the church website to find the bulletin online. He finds it. A multi-page production. Some churches put real love into their bulletins, treating them like a small magazine, full of photos and announcements and ministry updates. This was one of those.

He clicks to download. The file is several megabytes. Church buildings are not always great for Wi-Fi. A hundred people on the same network on Sabbath morning will slow things down. The download takes a while. The file finally opens, but it’s choppy. Loading slowly. Hard to interact with.

Then he looks at it. The bulletin was designed for a folded page, wider than it is tall. On his phone, which is tall and narrow, the whole document is shrunken to fit the screen. The text is tiny. Impossible to read as-is.

So he zooms in. Now he can read. But only a small portion of the page at a time. He wants to follow the order of service. "Opening Song" is on one side of the column. The name of the song is on the other. To read one single line of the program, he has to scroll left, then scroll right, then back again. Every. Single. Line.

He knows a workaround, because he has used PDF bulletins before. On a well-formatted PDF, you can press and hold on a phone number or a date and your phone will offer to call it or create a calendar event. That is how he usually engages with a bulletin. He saves events directly to his calendar while he reads. That is his participation system.

But the experience was too frustrating to even get there. He put the phone down. He picked up the paper bulletin instead.

Not because paper is better technology. Because paper disappears. You open it, you read it, it stays out of your way. The digital version was pulling his attention away from the service before it even started.

The cost that never shows up anywhere: he did not save a single event that day. He most likely missed something that would have mattered to him. The information was in the bulletin. It just was not reachable.

What actually happens when someone opens a church bulletin PDF on their phone?

A PDF is a fixed-layout document. It was invented so that a file looks exactly the same no matter where it is printed: same fonts, same spacing, same layout, regardless of the printer or the computer. That is useful for print. For phones, it is a significant problem.

A phone screen is tall and narrow. A church bulletin is almost always designed for a page that is wider, or for a folded format that is wider still. When you open a PDF on a phone, the document does not reshape itself to fit the screen. It just appears in its original proportions. Either it is shrunken down to fit (making the text too small to read), or it is shown at full size and requires scrolling in all directions (which most people find disorienting). Most PDF viewers default to the first option. Neither works well.

These are the problems your members are running into:

The layout does not fit the screen. Most bulletins are designed for an 8.5 x 11 inch page, or for a page folded in half. A typical phone screen is roughly 2.5 inches wide. The bulletin does not reformat itself to fit. It simply appears, shrunken, the way a newspaper would look if you photographed it from across the room. To read it, you have to zoom in, which means you can only see a small piece of the page at a time.

Two-column layouts are nearly impossible to follow on a small screen. Many bulletins divide the page into two columns side by side, the way a newspaper or a brochure is laid out. On paper, your eye moves naturally from the bottom of the left column to the top of the right. On a phone, once you zoom in to read the left column, you have to scroll right to reach the right column, then scroll back left and figure out where the next section begins. Most readers give up before they make it through the first column.

Phone numbers, websites, and event links cannot be tapped. In print, a phone number is something you read and then dial separately. Online, it should be something you tap and call immediately. A PDF bulletin almost never has live links. The phone number is plain text. The website address is plain text. The event registration link is plain text. To use any of them, a member has to read the information, switch to another app, and type it in by hand. For most people, that is too much friction. They move on.

Large files load slowly on weak connections. A multi-page bulletin with photos, graphics, and color backgrounds can easily be two to five megabytes or more. On a slow or shared connection, the kind common in church buildings on Sabbath morning when many people are on the same network, a file that size takes real time to download. While it loads, it may be choppy and hard to interact with. For a communication that should take seconds, that is a barrier many members will not push through.

There is no way to navigate the document. A website has sections you can jump to. An app has a menu. A PDF bulletin has neither. To find the announcements, you scroll. To find the event details, you scroll. There are no shortcuts, no bookmarks, no search that works reliably on a phone. You start at the top and read through, or you scroll until you find what you need. Often you do not.

The design choices that work in print and break on screen

Some of the problems above come from the PDF format itself. These next ones come from design decisions that made perfect sense in print and became problems the moment the file went online.

Thin, decorative fonts. Print designers often use elegant serif fonts, the kind with small decorative strokes at the tips of each letter. On high-quality paper with a good printer, they look refined. On a phone screen, especially at small sizes, those thin strokes disappear. Letters blend into each other. The text becomes blurry and hard to read. Fonts that look polished in print are often the hardest to read on glass.

Low contrast between text and background. Contrast, in design terms, is the difference in brightness between text and the surface behind it. Black text on white paper is very high contrast and easy to read. Light gray text on a cream background is low contrast and harder to read. Tan text on a warm gold panel is very low contrast. Difficult for most readers, and effectively invisible for anyone with low vision or color blindness.

Decorative church bulletins, the ones with warm background tones, colored section panels, and styled header text, are often the worst offenders here. And this matters more broadly than churches realize. Low contrast does not only affect people with vision difficulties. Anyone reading a phone screen in bright sunlight knows how quickly a text color that seemed readable indoors becomes invisible when daylight hits the screen.

Light text inside callout boxes and sidebar panels. Bulletins often use styled boxes, a colored background with white or light-colored text inside, to highlight an announcement or feature an upcoming event. On paper, this can look clean and polished. On a phone, light text on a colored background is often illegible, especially when the document is zoomed out to show the full page.

What does "accessible" mean, and why does it matter for a church bulletin?

Accessible, for a digital document, means the document can be used and understood by as many people as possible, including people who use assistive technology.

The most common example of assistive technology is a screen reader: software that reads the text of a document aloud, word by word, through the device’s speaker or a pair of headphones. People who are blind or have significant vision loss use screen readers to access websites, apps, and documents.

An estimated one in four American adults lives with some form of disability. That number includes your congregation, and likely more members than any church has counted, because many people do not disclose a disability or ask for accommodation.

For a screen reader to work, it needs one thing above everything else: real text to read. Not a photograph of text. Not a graphic that looks like words. Actual, digital, selectable text.

Most church bulletin PDFs fail this in at least one of the following ways.

Scanned bulletins have no text at all. This is the most common and most serious problem. The process works like this: a church creates the bulletin in a word processor, prints it, then scans the printed page and uploads the scan to the website. The result is a photograph of a document. It looks like text on the screen. You can read the words visually. But the computer does not see words. It sees an image. A screen reader trying to access that file gets nothing to read, because there is nothing there to read.

The same applies to the search function. You cannot search inside a scanned bulletin for the potluck date or the event sign-up, because there is no text to search. There is only a picture of words.

This is more common than most people realize. Many bulletin workflows end with a print step, and the file that gets uploaded is a scan of what came out of the printer, not the original digital document.

Columns and sidebars break the reading order. Screen readers read content in sequence: top to bottom, left to right, following the logical flow of the document. A bulletin with two columns, a decorative sidebar, and a styled callout box does not have a clear linear sequence. The screen reader has to guess what order to read things in, and it often guesses wrong. It might read the first line of the left column, then jump to the first line of the right column, then go back to the second line of the left. For someone listening to the document rather than reading it visually, this makes the content come out as a jumble of disconnected phrases.

Images have no description. Bulletins often include photos: a ministry team photo, an image for an upcoming camp meeting or youth event, a headshot of the speaker. In a fully accessible document, each image has a short text description attached to it (called alt text) that a screen reader can read aloud: "Photo of the women’s ministry team at the fall retreat." Without alt text, the screen reader announces "image" and moves on. Whatever information the photo was meant to communicate is lost entirely for anyone who cannot see it.

The document has no title or language tag. Every digital document should have a title embedded in its file properties. Not just a file name like "Bulletin_06-28.pdf," but a proper document title that software can read and report. The document should also declare what language it is written in. Neither of these things is visible to someone reading the file normally. But for screen readers, for search engines, and for any software that needs to understand what this document is, they matter. A PDF without them is harder to identify, harder to index, and harder to navigate using assistive technology.

Accessibility is not a niche design concern. It is a baseline. Met, it makes the document better for your whole congregation. Ignored, it quietly fails the members who needed it most.

If you’re going to use a PDF, here is the minimum standard

There is no rule that says every church must stop using PDFs. But if a PDF is going to live online, on the website, in an email, in a group chat, it should be built for those environments. Not just saved from a print file and uploaded as-is.

Here is a practical checklist. These are things any coordinator can do, or ask a designer to do, before the next bulletin goes out.

• Export from the source file, never upload a scan. If the bulletin was created in Microsoft Word, Google Docs, Canva, or any design program, export it directly to PDF from that program. That produces a real, text-based document. Uploading a photo of a printed page is not the same thing, even if it looks similar on screen.
• Use a sans-serif font at a readable size. Fonts like Arial, Helvetica, Aptos, or Calibri hold up well on screens because they have clean, even letter shapes without decorative strokes. Use at least 11-12 point for body text and larger for headings. Avoid thin or decorative fonts for anything that needs to be read quickly.
• Check your contrast. If the bulletin uses colored backgrounds or light-colored text, test whether the contrast is readable. A free tool called the WebAIM Contrast Checker lets you enter the text color and background color and tells you whether the combination passes the standard. If it does not, adjust the colors.
• Make your links tappable. Phone numbers, website addresses, and event registration links should be real, clickable hyperlinks, not just text that looks like a link. In Word and Google Docs, highlight the text, right-click, and choose "Add link." In Canva and most design tools, look for a link icon when editing text. A member should be able to tap a phone number and call, without typing anything.
• Set a document title. In Adobe Acrobat, go to File, then Properties, and fill in the Title field. In other tools, look for document properties or export settings. This takes less than a minute and makes a real difference for anyone using assistive technology.
• Reduce the file size before uploading. Most design and word-processing tools include an export option for web or screen use that compresses images and cuts the file size without making the document look worse on screen. Aim for under two megabytes where possible.
• Test it on your own phone. Before sharing the link, open the PDF on your personal phone without zooming. Read it as it appears at the default size. If you have to pinch the screen to make it usable, it is not ready.

Even a bulletin that passes every item on this list is still a workaround. These steps make a PDF better. They do not make it mobile-first. Every one of these problems exists because the PDF format was designed for printing, not for phones. A digital bulletin built for the screen solves these problems at the foundation, because it was built for the environment your members actually live in, not adapted to it after the fact.

These problems cost you more than you realize

What happens to the bulletin after Sabbath is where most of the losses occur. The event someone meant to attend. The ministry sign-up they were going to fill out. The giving link they planned to use during the week.

When a bulletin is hard to navigate on a phone, members do not complain. They just move on. They put the phone down. They forget the event. The church never finds out that the information was there. It just was not reachable in the moment when it could have moved someone to act.

Making the bulletin readable online is not a technology project. It is a hospitality decision. It is the same instinct that made someone upload the file in the first place, carried one step further, toward the actual experience your congregation has when they open it.

This is exactly the problem a digital bulletin is built to solve: not a PDF uploaded to a website, but an actual mobile-first experience your congregation opens on their phone the same way they open a text message. That is what Gathad is built to be.

Frequently Asked Questions

Does a church bulletin PDF need to be accessible by law?

Churches are generally exempt from the Americans with Disabilities Act requirements that apply to public businesses. But legal compliance and genuine hospitality are two different standards. If a member who is blind or has low vision cannot read your bulletin online, that is worth addressing, not because of a legal requirement, but because of who your church says it is.

What is the difference between a scanned PDF and a digital PDF?

A scanned PDF is a photograph of a printed page, so the computer sees it as an image with no actual text that software can read, search, or interact with. A digital PDF is exported directly from a design program and contains real, selectable, searchable text; the difference matters enormously for screen readers and mobile usability.

Can we make our current PDF bulletin more accessible without redesigning it?

If the bulletin is created in a word processor or design program and exported directly to PDF, yes. Font choices, contrast, and live links can all be improved without changing the overall layout. If the bulletin is a scanned image of a printed page, the accessibility problems run deeper and cannot be fixed without going back to a digital source file.

What does "low color contrast" look like in a church bulletin?

Contrast is the difference in brightness between text and its background. Light-colored text on a light-colored background, like cream on beige or gray on white, is low contrast and hard to read on a phone screen, especially in daylight.

What is the real alternative to posting a PDF bulletin online?

The alternative is a document built for screens from the beginning: one that reformats to fit any screen, loads quickly, has tappable links, and needs no zooming or sideways scrolling. A PDF can be improved, but a web-based bulletin does not have the same problems to fix because it starts where your members are.