Sermon accessibility: captions, transcripts, and ADA compliance

Most religious organizations are exempt from Title III of the ADA (which applies to 'public accommodations'). However, if your church operates programs that receive federal funding — most commonly preschools, daycare, food banks, or community education — those programs are subject to ADA Title II. Additionally, many states have stricter local accessibility laws. Federal court precedent has been moving toward expecting church websites to meet WCAG 2.1 AA standards even when not legally mandated.

Web Content Accessibility Guidelines 2.1, level AA, is the de facto international standard for web accessibility. It covers captioning of pre-recorded media (Criterion 1.2.2), transcripts of audio-only content (1.2.1), and live captions for streamed services (1.2.4). Even if your church isn't legally bound, meeting WCAG 2.1 AA signals to your members and community that you take accessibility seriously.

About 15-20% of U.S. adults have some level of hearing loss, with the percentage rising steeply with age. In congregations skewing older, 30-50% of members over 65 have measurable hearing loss. Many never request accommodations — they just quietly stop attending, listening, or staying engaged. Captions and transcripts are often the single most appreciated change a church can make.

Captions are time-synced text that appears on screen during video playback (SRT/VTT files). They serve Deaf and hard-of-hearing viewers in real-time. A transcript is a static document of the full sermon text, served as a separate page or PDF. Best practice is to provide BOTH — captions for the video, transcript on the sermon page. We export both formats from a single upload.

WCAG 2.1 requires captions to be 'accurate'. Most legal and accessibility advisors interpret this as ~99% accuracy. Whisper output typically lands at 95-98% out of the box; a 10-minute proofread on a 35-minute sermon gets you to 99%+. That's substantially less work than typing captions from scratch.

Per WCAG 2.1 AA Criterion 1.2.4, yes — live captions for live media. Realistic options: (1) Use a live captioning service like Ai-Media or Verbit, (2) Stream with YouTube Live or Vimeo and enable their auto-captions, (3) Use a dedicated live transcription tool integrated with your stream. Then post the polished Sermon Transcription version as a corrected transcript within 24 hours.

Beyond captions and transcripts, an accessible church website includes: alt-text on images, sufficient color contrast (4.5:1 minimum for normal text), keyboard navigation, descriptive link text (not 'click here'), accessible PDFs (tagged structure), and clear page hierarchy with proper H1/H2/H3 usage. Many themes for Squarespace, Wix, and Subsplash now meet these standards by default.

A clean, semantically structured transcript works perfectly with screen readers like JAWS, NVDA, and VoiceOver. Avoid PDFs without tags — they're inaccessible to screen reader users. Publish transcripts as HTML pages with proper heading structure. The audio of the sermon also remains available for low-vision members.