Older Members and the Church Site

Older members are, in many congregations, the heaviest users of the church website and the least likely to report a problem with it. They check service times, read the newsletter, look up a funeral arrangement and forward a sermon link to a friend, all while the site's design quietly assumes young eyes, a steady hand and a tolerance for movement. This guide covers the habits that keep a church site readable and calm for members in their seventies and eighties, from text size to menus that stay where they were left.

The Web Accessibility Initiative publishes specific guidance on how aging changes web use, from vision and dexterity to memory and attention, and most of it lands as plain design advice: bigger, steadier, simpler, patient.

How large should text actually be?

Body text around the equivalent of sixteen pixels, with the page reflowing cleanly when the browser's own zoom raises it further, is the working floor. Presbyopia treats every congregation equally, and text sized for the designer's monitor fails in the pew. The page should welcome the browser zoom control and the system wide larger text setting, rather than fighting them with fixed containers that clip their contents. A simple test the whole committee can run: open the site on a phone, raise the text size one notch in the settings, and read the home page. If anything breaks or overflows, that break is a member lost.

Why do moving pages cost more than they seem?

Autoplaying slideshows, drifting background videos, animations that swing in as the page scrolls: each costs an older reader more than a younger one, in attention, in orientation and occasionally in balance, since motion sensitivity increases with age and with certain medications. Members who prefer still pages often set a system flag, "reduce motion", that a well built site respects by turning its animations off. The design advice is simpler still: one strong image beats a rotating set, and the dos and don'ts guide already bans autoplay for everyone's sake. Calm is not a compromise; it is the better design.

What makes a menu work for unsteady hands?

Dropdown menus that open on hover, sub items one line tall, tap targets sized for a mouse cursor: all of these punish a hand that trembles or a finger that lands wide. Menus for a church site should open on a tap or a click, offer items with generous height, and above all stay put: an item that moves as the hand approaches guarantees a mis tap. Hover menus designed on a desktop mouse fail doubly on the phone, where "hover" does not exist and the whole submenu hides behind a first tap that opens a page instead.

Why do breadcrumbs and clear pages beat cleverness?

Memory changes with age, and a site that relies on the visitor remembering where they are, multi level menus, unlabeled icon buttons, a back button as the only way out, charges a toll on every page. Older members stay oriented on pages that say where they are in plain words, keep the same layout from page to page, and offer a visible path home. The discipline is repetition, the opposite of the creative layout that changes structure per page. Consistency reads as welcome.

What do icons and buttons need to carry?

An icon alone, a magnifier, a hamburger, an envelope, is a guess; the same icon with a word beside it is a door. Buttons on church sites serve better with labels than with symbols, and links inside sentences should be underlined, not merely tinted, for the contrast reasons the color blindness guide sets out and the vision reasons this one does. Where a phone number appears, it should be tappable text, since members who still read phone numbers off screens are also members who expect tapping one to call it.

How should contact paths treat patience?

Older members often prefer a person to a form, and the site should offer both: an email address in real text, the office phone with hours, and the name of the human who answers. Forms that expire after ten minutes, demand an account or reject a submission over a missed field charge anxiety instead of patience. Contact information belongs on its own page, linked from the header, not buried in a footer three screens down, a placement the home page checklist sets as standard.

What about content, not just chrome?

The words matter as much as the layout. Short paragraphs, plain words, dates written out in full rather than buried in graphics, and a newsletter page that reads the same on screen as it does in print. Acronyms and ministry names that only insiders parse, "the WMC potluck", exclude quietly; expanding them once, "the Women's Ministry Council potluck", includes everyone, in the way the writing guide prescribes. The habit of the plain written out date also rescues the calendar confusion no design can fix.

Where does a team start on Monday?

Recruit the congregation's own experts: two or three members over seventy, watching them complete three tasks on their own devices, finding the service time, locating the funeral details, sending the office an email. Teams learn more in that half hour than in any audit, and the members asked usually report the session as a gift rather than a chore. The fixes they surface, text size, one hovering menu, a buried phone number, are structural rather than cosmetic, and they fold naturally into the next makeover plan or the standing habits of the accessibility section, which treats older members as one audience among several the site owes honesty.