Church Website Accessibility: A Practical Guide for 2026

If someone in your congregation uses a screen reader, can't see a low-contrast "Watch Live" button, or can't navigate your menu with a keyboard, can they still find service times, get directions, or watch your sermon online? For millions of visitors with disabilities, the answer on most church websites is no. Church website accessibility means designing and building your site so that people with visual, auditory, motor, or cognitive disabilities can use it just as easily as anyone else. It's increasingly a legal issue too, but the pastoral reason matters more.

This guide walks through what accessibility actually requires, whether your church is legally on the hook, a practical checklist you can start on today, the tools to test your site for free, and the mistakes that trip up even well-meaning church websites. Along the way we'll touch on how your church website design and the graphics you put on it play a bigger role in accessibility than most people realize.

Table of Contents

• Why Website Accessibility Matters for Your Church
• Is Your Church Website Legally Required to Be Accessible?
• WCAG Explained: The Standard Your Site Should Meet
• The Church Website Accessibility Checklist
• Free Tools to Test Your Church Website's Accessibility
• Common Accessibility Mistakes Churches Make
• Making Sermon Graphics, Videos, and PDFs Accessible
• Keeping Your Site Accessible Long-Term
• Frequently Asked Questions

Why Website Accessibility Matters for Your Church

About 1 in 4 adults in the United States lives with some form of disability, and that ratio almost certainly shows up in your congregation and your community, whether or not anyone has told you about it. A person with low vision, color blindness, a hearing impairment, or a motor condition that makes a mouse difficult to use is either able to find your service times, watch your sermon, and fill out your connect card, or they're not. There's no in-between.

Accessibility isn't only about the small number of people using screen readers. Captions help the person watching your livestream in a loud coffee shop. Clear contrast helps an older visitor reading on their phone in bright sunlight. Simple, predictable navigation helps a first-time guest who's never used your site before. Good accessibility practice overlaps heavily with good design practice. Building for the edge cases tends to make the site better for everyone.

There's also a plain pastoral argument here: a church that wants to welcome everyone shouldn't have a front door that quietly locks some people out.

Is Your Church Website Legally Required to Be Accessible?

The short answer: it depends on your church's specific situation, and you should treat this section as general information rather than legal advice.

The Americans with Disabilities Act (ADA) Title III covers "places of public accommodation," and courts have increasingly applied that concept to websites, especially for organizations that offer goods, services, or public-facing programs online. Religious organizations have historically had more legal protection here than typical businesses, but that protection isn't absolute, and it gets murkier the more your church operates like a business online: selling tickets to events, running an online store, processing donations, or offering a school or daycare through the same website.

Beyond the legal question, many church web platforms, grant programs, and denominational bodies are starting to expect a baseline level of accessibility as a condition of funding or partnership. Treating accessibility as standard practice, instead of something you only address after a threat of legal action, is both safer and closer to what your church is actually trying to do.

If your church has received a demand letter or lawsuit related to website accessibility, talk to an attorney familiar with ADA website compliance rather than relying on a blog post, including this one.

WCAG Explained: The Standard Your Site Should Meet

The Web Content Accessibility Guidelines (WCAG), published by the W3C's Web Accessibility Initiative, are the closest thing the internet has to an official accessibility rulebook. Courts, government agencies, and most accessibility consultants point to WCAG 2.1 Level AA as the practical target for most organizations, including churches.

WCAG is organized around four principles, often remembered by the acronym POUR:

• Perceivable - Information and interface elements must be presentable in ways people can perceive, such as text alternatives for images and captions for video.
• Operable - Navigation and interactive elements must work with a keyboard alone, not just a mouse or touchscreen.
• Understandable - Text should be readable and pages should behave in predictable, consistent ways.
• Robust - Content should work reliably across browsers, devices, and assistive technologies, including screen readers.

You don't need to memorize the full WCAG specification to run a church website well. Most of what matters in practice comes down to a manageable checklist, which is exactly what's next.

The Church Website Accessibility Checklist

Work through these in order of impact. You don't have to fix everything in one afternoon; even a partial pass through this list will meaningfully improve your site.

Content and Structure

• Use real heading tags (H1, H2, H3) in the order they appear, instead of just making text bold and bigger.
• Write link text that describes the destination ("View this Sunday's sermon notes"), never "click here."
• Keep paragraphs short and language plain; this helps readers with cognitive disabilities and every other visitor too.
• Make sure the page's language is set correctly in the site's code (most website builders handle this automatically, but it's worth confirming).

Visual Design

• Maintain a color contrast ratio of at least 4.5:1 between text and its background for normal-size text.
• Never use color as the only way to convey information (e.g., a red-only error message with no icon or text label).
• Make sure text can be resized up to 200% in the browser without breaking the layout or cutting off content.
• Avoid auto-playing video or animation with sound, and give users a way to pause background motion.

Media and Interactive Elements

• Add descriptive alt text to every meaningful image, including sermon graphics, event flyers, and staff photos.
• Add captions or a transcript to sermon videos and any pre-recorded media.
• Make sure every button, link, and form field can be reached and operated using only the Tab key and Enter.
• Label every form field clearly (name, email, prayer request) so screen readers can identify what each field is for.

Area	Quick Win	Why It Matters
Images	Add alt text to sermon graphics and photos	Screen readers announce alt text aloud; without it, images are invisible to blind users
Color	Check text-to-background contrast	Low contrast makes text hard to read for low-vision and older visitors
Video	Add captions to sermons and announcements	Helps Deaf and hard-of-hearing visitors, plus anyone watching with sound off
Navigation	Test your menu using only the Tab key	Confirms the site works for people who can't use a mouse
Forms	Label every field (connect card, giving, contact)	Unlabeled fields are a guessing game for screen reader users

Free Tools to Test Your Church Website's Accessibility

You don't need a budget to start finding accessibility issues. These tools will catch a large share of common problems in a few minutes:

• WAVE (a free browser extension) highlights missing alt text, contrast issues, and structural problems directly on your page.
• Google Lighthouse, built into Chrome's developer tools, includes an accessibility score along with specific fixes.
• Keyboard-only testing costs nothing: unplug your mouse and try to reach every link, button, and form field using only Tab, Shift+Tab, and Enter.
• Screen reader spot-checks using VoiceOver (built into Mac) or NVDA (a free Windows screen reader) will show you exactly what a blind visitor hears when they land on your homepage.

Automated tools like WAVE and Lighthouse typically catch somewhere between a third and half of all accessibility issues; the rest require the kind of manual, human testing described above. Run both regularly rather than relying on one automated scan and calling it done.

Common Accessibility Mistakes Churches Make

Most church websites don't fail accessibility on purpose; they fail because these issues are easy to miss unless you're specifically looking for them.

• Relying on an accessibility overlay widget as a complete fix. These popular plug-in tools can help with a few surface-level adjustments, but they don't fix underlying code problems, and several have faced lawsuits themselves for failing to deliver real compliance. Treat them as a supplement, not a substitute for actual fixes.
• Embedding sermon graphics and announcement slides with no alt text. If your homepage is mostly images announcing events and series, and none of them have alt text, a screen reader user gets almost no information from your homepage at all.
• Using low-contrast brand colors on top of photos or busy backgrounds. A design that looks stylish on a designer's monitor can be nearly unreadable for a visitor with low vision.
• Posting PDF bulletins and giving forms that aren't screen-reader friendly. A scanned PDF with no real text layer is invisible to assistive technology, no matter how nicely it's designed.
• Skipping captions on livestream and recorded sermons. This is one of the most commonly requested accessibility features and one of the most frequently skipped.

Making Sermon Graphics, Videos, and PDFs Accessible

Church websites lean heavily on visual and video content (sermon graphics, series art, countdown videos, event flyers), so media accessibility deserves its own attention separate from general web design.

For images and graphics: write alt text that describes the actual content and purpose, not just "graphic" or "banner." For a sermon series graphic, something like "Faith Over Fear sermon series, starting October 5, with pastor speaking on courage" gives a screen reader user real information instead of nothing.

For video: add captions to sermons, testimonies, and promotional videos. Many video hosting platforms (YouTube, Vimeo) offer auto-captioning as a starting point, though it's worth reviewing and correcting the output, since names, scripture references, and theological terms often get mangled by automatic transcription.

For PDFs: export bulletins and forms with real, selectable text rather than flattened images, and add a document title and heading structure where your PDF software allows it. If a document only exists as a scanned image, consider also offering the same information as a plain web page.

For color and design: high-contrast text, clear hierarchy, and readable fonts help accessibility, and they tend to perform better for engagement too, since most visitors are scrolling quickly and skimming rather than reading closely.

Keeping Your Site Accessible Long-Term

Accessibility isn't a one-time project you finish and forget. Every new page, blog post, sermon graphic, and form you add is a fresh chance to introduce (or avoid) an accessibility problem.

• Run a full accessibility check at least once a year, and after any major redesign.
• Add "check alt text and contrast" as a standing step in your content publishing checklist, right alongside spell-check.
• Whoever manages your website should know the basics of WCAG well enough to catch obvious issues without needing a specialist every time.
• Ask a member of your congregation with a disability, if they're willing, for honest feedback on what's hard to use; real feedback beats guesswork every time.

If your team is also working on broader church website SEO, good news: many accessibility fixes (clear headings, descriptive alt text, logical structure) improve search rankings at the same time. The two efforts reinforce each other instead of competing for your time.

Frequently Asked Questions

Is my church website legally required to be ADA compliant?

It depends on your specific circumstances, including how your church uses its website (donations, e-commerce, programs) and your state's laws. Many churches have some legal protection as religious organizations, but that protection isn't unlimited, and it's shrinking as courts continue to weigh in. When in doubt, consult an attorney rather than relying on general guidance.

What WCAG level should a church website aim for?

WCAG 2.1 Level AA is the generally accepted practical standard used by courts, government agencies, and most accessibility consultants, and it's a reasonable target for a church website.

Do accessibility overlay widgets make my site compliant?

No, not on their own. Overlay tools can offer helpful adjustments like font resizing or contrast toggles, but they don't fix underlying code issues like missing alt text or poor heading structure, and several overlay vendors have themselves been named in accessibility lawsuits. Use them as one small piece of a broader effort, not the whole strategy.

How much does it cost to make a church website accessible?

Many of the highest-impact fixes, like adding alt text, checking color contrast, labeling form fields, and testing keyboard navigation, cost nothing but time. A full professional audit or redesign costs more, but most churches can meaningfully improve accessibility using free tools and a volunteer or staff member's afternoon.

Does our livestream need captions?

Captions aren't universally legally mandated for every church, but they're one of the most requested and most impactful accessibility features you can add, and most streaming platforms now offer built-in captioning options that make this far easier than it used to be.

How often should we audit our website for accessibility?

At minimum, once a year and after any major redesign. Many churches build a lighter version of this check into their regular content workflow so new pages and graphics don't quietly introduce new problems.

What's the single easiest first fix for a church website?

Adding alt text to your images, starting with your homepage and any sermon or event graphics. It takes minutes, requires no technical skill, and immediately makes your most visible content available to screen reader users.

Will improving accessibility also help our SEO?

In many cases, yes. Descriptive alt text, clear heading structure, and well-labeled content all help search engines understand your pages too, so accessibility work and SEO work often overlap.

Bringing It Together

Church website accessibility comes down to a handful of habits: descriptive alt text, sufficient color contrast, keyboard-friendly navigation, captioned video, and labeled forms. None of it requires a redesign or a big budget. It takes attention, a checklist, and a willingness to test your site the way a visitor with a disability actually would.

If part of your challenge is simply keeping up with professional-looking sermon graphics, event flyers, and worship backgrounds on top of everything else on your plate, that's exactly where Local Church Media's unlimited subscription can help: sermon series graphics, worship motion backgrounds, texture packs, and more, starting at $19/month, so your team can spend less time on production and more time making sure what you publish actually reaches everyone in your community.