Why Web Accessibility Matters for Churches and Nonprofits
—Even If It’s Not Legally Required
By Stoneroller Cooperative
If you’ve heard the buzz lately about ADA compliance for websites, you’re not alone. Church communicators, nonprofit leaders, and web teams across the country are fielding questions from vendors, emails from consultants, and murky government updates. So let’s start with the simple answer:
Most churches and small nonprofits are not currently required by law to have an ADA-compliant website, but that’s not the same as saying accessibility doesn’t matter.
Most churches and small nonprofits are not currently required by law to have an ADA-compliant website, but that’s not the same as saying accessibility doesn’t matter.
The Legal Landscape, Briefly
In 2025, the U.S. Department of Justice issued updated rules under the Americans with Disabilities Act (ADA), focused on state and local government websites (Title II)[1]. These changes do not apply to churches or religious nonprofits—at least not yet.
So if someone tells you your congregation’s site is suddenly out of compliance, take a breath. That may be marketing language, not legal truth.
But while your site may be in the clear legally, the question remains: Is it welcoming? Is it usable? Is it built with care?
The Real Stakes Aren’t Legal—They’re Human
When a website is hard to read, navigate, or understand, people don’t always ask for help.
They don’t file complaints... they just quietly click away.
They may be blind or have low vision.
They may rely on captions.
They may struggle with cognitive overload or use keyboard navigation instead of a mouse.
They may be older, neurodivergent, using a phone with a cracked screen, or simply overwhelmed.
Inaccessible design doesn’t just create a technical problem. It creates distance—between your mission and the people who might need it most[2].
Churches and nonprofits are often the first to say all are welcome.
But when our websites unintentionally exclude, we send a different message.
That’s why accessibility isn’t just a technical upgrade—it’s a spiritual practice. It’s part of how we care for others. It’s how we ensure our digital spaces match the values we live out in person.
The good news? You don’t need a redesign to get started.
Quick Accessibility Guide for Churches and Nonprofits
You can start improving your site without a full rebuild.
These are real, actionable steps—designed for small teams, part-time communicators, and people doing their best.
Essential First Steps
Start here. These updates are high-impact and low-tech.Alt Text for Images
Every image should include a short description of its purpose or content.
WebAIM Alt Text Basics
Clear Heading Structure
Use real heading tags (
<h1>, <h2>, etc.) in logical order. Don’t just bold or enlarge text.W3C Headings Tutorial
High Color Contrast
Ensure text stands out clearly from its background. Avoid light gray on white.
WebAIM Contrast Checker
Accessible Fonts
Use sans-serif fonts like Arial, Lato, or Helvetica at 16px or larger.
NNG Typography Tips
Simple, Consistent Navigation
Menus and buttons should be predictable and consistent across your site.
WebAIM: Navigation Techniques
Descriptive Link Text
Use link text that describes the destination, not “click here.”
W3C: Link Purpose Guidelines
Captions and Transcripts
Caption all videos. Offer transcripts for podcasts, livestreams, or audio.
YouTube Captions Help Guide
Keyboard Navigation
All content should be accessible using a keyboard.
WebAIM Keyboard Accessibility Guide
Plain, Inclusive Language
Avoid jargon and overly academic phrasing. Use clear, welcoming language.
Plain Language Checklist
No Auto-Playing Media
Don’t autoplay sound or video. Let users decide when to engage.
WCAG on Auto-Play
Next-Level Accessibility
For teams ready to go further.Label Your Forms Clearly
Each form field (like Name, Email) should have a visible label—not just placeholder text.
WebAIM: Form Labels
Mobile-Friendly Design
Make sure your site adapts well to phones and tablets.
Google Mobile-Friendly Test
Skip Navigation Links
Add a “Skip to Content” link to let keyboard users bypass your menu.
WebAIM Skip Navigation Guide
Avoid PDF-Only Content
If you use PDFs, ensure they’re accessible—or offer an HTML version.
Adobe: Make PDFs Accessible
Declare Page Language
Use
<html lang=\"en\"> so screen readers pronounce words correctly.W3C Language Declaration Guide
No Flashing or Blinking Content
Flashing content can cause seizures. Don’t use it.
WCAG 2.1 Seizure Guidelines
Accessible Social Embeds
Avoid autoplay and ensure embedded content is captioned.
W3C: Accessible Social Media
Add an Accessibility Statement
Let visitors know you’re working on accessibility and invite feedback.
W3C Sample Accessibility Statement
Download a PDF of our tips here.
This Isn’t About Pressure. It’s About Purpose.
Even if the DOJ never changes the rules again, accessibility will always matter—for the person using captions, for the elder trying to navigate your menu, for the disabled visitor wondering if your community has room for them.
Digital welcome is still welcome. Let’s make it real!
Design with soul.
Strategy with ethics.
Endnotes[1] U.S. Department of Justice, “Web Accessibility Guidance Under the ADA.”
https://www.ada.gov/resources/web-guidance/
[2] Pew Research Center, “People With Disabilities Are Less Likely to Use Tech.”
https://www.pewresearch.org/fact-tank/2021/09/10/people-with-disabilities-less-likely-to-use-tech/
[3] W3C Web Accessibility Initiative, “Introduction to Web Accessibility.”
https://www.w3.org/WAI/fundamentals/accessibility-intro/