Digital Hospitality: Is Your Church Website a Virtual “No Entry” Sign?
I want to tell you about a Sunday morning I never actually had.
I didn’t get lost on the way to worship. I didn’t sit in an unfamiliar pew or stumble through an order of service I’d never seen. I never even made it that far. I got stopped at the door—except the door was a website, and the website didn’t work for me.
As a person with a visual disability, I rely on screen readers and accessible design every single day. And I can tell you from lived experience: there is nothing quite like the quiet sting of clicking on a church’s “Everyone is welcome here!” banner only to find that the site is a maze of low-contrast text, unlabeled buttons, and images without a single word of alt-text. The message the congregation intended to send and the message I received were completely different things.
One said: Come as you are.
The other said: …unless you navigate the web differently than we do.
That gap—between the welcome a church intends and the welcome it actually extends online—is what digital hospitality is all about. And for most congregations, it’s a gap they don’t even know exists.
Digital Hospitality Starts at the Door
Here’s the reality most church leaders haven’t fully reckoned with yet: the front door of your church isn’t on Main Street anymore. It’s at your domain name.
Before someone visits your congregation in person, they visit you online. They check your service times, read about your values, listen to a sermon clip, and—consciously or not—ask themselves: Do people like me belong here?
For someone who is Deaf or hard of hearing, that question gets answered when they look for a video with captions and find none. For a person who navigates with a keyboard instead of a mouse, it’s answered when they try to tab through your navigation and get completely stuck. For someone with low vision like me, it’s answered in an instant when the text is gray on white, the font is tiny, and the contact form has no visible labels.
These aren’t fringe edge cases. According to the World Health Organization, over 1.3 billion people globally live with some form of disability. Many of them are spiritually curious, deconstructing, rebuilding, and looking for exactly what you’re offering—a community where they belong.
They’re checking your website first. What are you telling them?
WCAG: The Framework Behind Digital Hospitality
WCAG stands for the Web Content Accessibility Guidelines. It’s an internationally recognized framework published by the World Wide Web Consortium (W3C) that defines what it means for a website to be accessible to people with a range of disabilities—visual, auditory, motor, and cognitive.
You might hear it pronounced “wuh-cag,” and at first, it can sound like a technical problem for your web developer to solve. But stay with me, because I want to reframe it entirely.
WCAG is the practical blueprint for digital hospitality.
Every guideline in that framework—every rule about color contrast, every requirement for image descriptions, every standard for keyboard navigation—is answering one fundamental question: Can everyone who visits this space actually use it?
That’s not a technology question. That’s a theology question.
For ministries committed to radical inclusion, WCAG compliance isn’t a nice-to-have. It’s a concrete, measurable way to put your stated values into practice. You can say “all are welcome” in your mission statement, on your signage, and from the pulpit. But if your website fails basic accessibility standards, your digital presence is quietly contradicting everything you preach.
When Technical Errors Feel Like Spiritual Rejection
I want to be honest about something that most conversations about digital hospitality leave out: the emotional impact.
When a person seeking community, healing, or belonging encounters a church website they cannot use, it’s rarely perceived as a technical glitch. It lands as a message. You weren’t on our minds when we built this. People with your needs weren’t considered. You are not the default here.
For someone already carrying wounds from church hurt, already navigating whether progressive faith is a real option for them, already wondering if they’ll be welcomed in their full humanity—an inaccessible website can be the thing that tips the scale. Not toward your church, but away from organized religion altogether.
This is why I say that technical errors can feel like spiritual rejection. The intent rarely matches the impact. But in ministry, we don’t get to choose what others receive—we only get to be responsible for what we build.
And right now, a lot of us have built digital spaces that, however unintentionally, say no entry to the people Jesus consistently and deliberately moved toward.
The Good News (There’s Always Good News)
Here’s what I love about this issue: it is entirely fixable. Unlike some of the deeper structural barriers to inclusion in the church, web accessibility is a space where meaningful change can happen quickly, affordably, and with lasting impact.
You don’t have to rebuild your entire site. You don’t need a massive budget. You need clarity, intentionality, and a willingness to ask: Who are we leaving out, and what can we do today?
Here are some practical places to start for creating truly accessible church websites and practicing genuine digital hospitality:
Start with a free audit. Tools like the WAVE Web Accessibility Evaluation Tool (wave.webaim.org) will scan your site and flag accessibility errors in seconds. Run it on your homepage and your most-visited pages. What you find might surprise you.
Fix your color contrast first. Low contrast text is one of the most common failures and one of the easiest to fix. Text should meet at least a 4.5:1 contrast ratio against its background. If your sage green text is sitting on a cream background, it’s probably failing—even if it looks fine to you.
Add alt-text to every image. Every. Single. One. This isn’t just an accessibility standard; it’s something your brand stylesheet already calls a non-negotiable. Describe what’s in the image, what text appears in it, and why it matters in context. A photo of your congregation isn’t just “people smiling.” It might be: “A diverse group of adults gathered in a circle in an outdoor worship setting, some seated in chairs, some in wheelchairs, all facing a central speaker.”
Make your videos captioned. Every sermon clip, every welcome video, every highlight reel. Auto-captions are a starting point, but edit them for accuracy. Names and theological terms especially need a human review.
Label your forms. If someone can’t tell what a form field is asking for without looking at it visually, your form isn’t accessible. Every input needs a text label that a screen reader can find.
Test with a keyboard only. Unplug your mouse and try to navigate your site using only your Tab key, arrow keys, and Enter. Can you reach everything? Can you complete the contact form? Can you find the service time? If not, people who rely on keyboard navigation cannot either.
Digital Hospitality Is Theological Work
The concept of hospitality runs like a river through scripture. Abraham welcoming strangers at the oak of Mamre. Jesus dining with those the religious establishment had dismissed. The early church building communities where the typical social categories lost their power.
Hospitality, in the biblical tradition, isn’t just being friendly. It’s creating conditions where the other—the stranger, the one who doesn’t fit the default—can be fully present and fully seen.
Digital hospitality is the same work, extended into new territory.
When churches invest in WCAG for ministries, they are not just checking legal compliance boxes or following best practices. They are making a theological statement: We thought about you when we built this. You were on our minds. You matter here, before you ever set foot in the door.
That is the open-door policy, rewritten for the digital age. Not just a sign that says “All Are Welcome” in a curly font over a sunset photo—but a website that proves it with every interaction.
An Invitation to Practice Digital Hospitality
If you’re a church leader, this is not an accusation. Most inaccessible church websites weren’t built to exclude anyone. They were built by well-meaning people who simply didn’t know what they didn’t know.
But we know now. And that changes things.
Start small. Run the WAVE audit this week. Fix your alt-text. Adjust your contrast. Caption one video. Then do it again next month. Every step is an act of digital hospitality—a concrete way of saying: we built this with you in mind.
If you want support on this journey—whether you’re building an accessibility audit process for your ministry or trying to make your entire digital presence more welcoming—I’d love to help. This is exactly the kind of work I do. Reach out through my contact page and let’s talk.
And if you want to go deeper on accessible and inclusive church practice, subscribe to the Faith, Upgraded newsletter—a weekly reflection on making faith livable, inclusive, and future-ready. The link is below.
Your digital door is already open. Let’s make sure everyone can walk through it.
