Accessible church social graphics: a practical review for alt text, type, and contrast

The graphic looks finished on your laptop. The type is crisp, the colors work, and nothing touches the edge. Then you open the phone preview. A line is too small, the crop cuts off the source, or the event details exist only inside the image.

That is why the final review belongs in the place where people will see the post. It has four parts:

1. Put essential information in usable post text, not only inside the image.
2. Inspect the final pixels at phone size, then measure contrast where the words actually sit.
3. Write alternative text for the image's purpose and final crop.
4. Check the destination preview, rights, consent, safeguarding, links, and response plan before publishing.

One passing check does not cover the rest. A 4.5:1 color pair can sit behind text that is too small to read. Accurate alt text can accompany an image with expired event details. A clear square graphic can lose its attribution in a portrait crop. The whole post has to work together.

Review five parts of the post separately

A static social post can carry meaning in several places. Name each one before you edit anything.

These parts are related, but they are not interchangeable.

Suppose a graphic announces a community meal. The image says Community meal, Thursday, 6:00 p.m. over a photograph of a table. The visible post copy says only Everyone is welcome.

Longer alt text will not fix this. Put the date, time, location, access details, registration requirements, and contact route in usable post text.

People may need to copy an address, translate a sentence, enlarge the words, or follow a link. Do not trap information they need inside an image.

Once the post copy holds the essential details, ask what the image adds. A photo of the entrance people should use may carry helpful information. A generic photo of a table may only set a mood. Those images need different treatment.

The W3C Images Tutorial bases text alternatives on purpose and context. Informative images need their essential information conveyed. Functional images describe the action or destination. Decorative images use a null alternative in HTML. Social platforms do not all offer the same decorative-image control, so check the destination. If an image adds nothing and the platform gives you no suitable way to treat it as decorative, omitting the image may be the cleaner choice.

Start with the one thing the post must do

Write one sentence before designing:

This post helps [specific reader] understand or do [specific thing].

That sentence sets the hierarchy. It also exposes crowded briefs.

This post helps a first-time visitor find the correct entrance for the 10:30 service is workable. The graphic might need a location cue, while the post copy carries the full address, parking note, access information, and contact link.

This post teaches the sermon, advertises Sunday, thanks volunteers, promotes a course, and asks for prayer requests is not one graphic. Split the jobs or choose the most important one.

Purpose also controls alternative text. A photograph of an open church door could support an entrance notice, illustrate a reflection about welcome, or decorate a general invitation. The pixels may be identical. The useful description changes because the image's job changes.

Do not turn alt text into a keyword field. Repeating search phrases does not help a person understand the image. Do not use it as a design inventory either. A list such as navy rectangle, yellow circle, white sans serif type describes ingredients while missing the message.

Keep essential wording outside the image

Words baked into a graphic cannot be restyled, reflowed, copied, or translated as easily as real text. WCAG 2.2 guidance on images of text prefers real text when the technology can provide the intended presentation. It also recognizes limited cases where the visual presentation is essential, including logotypes.

That does not ban every quote card or event graphic. It does change what the image can be trusted to carry.

Put these items in the surrounding post copy when they matter:

• dates, times, locations, prices, registration limits, and access details
• links, email addresses, phone numbers, and other next steps
• a sermon quotation or Scripture wording that must be accurate and available as text
• attribution and source context needed to understand a quotation
• corrections, exceptions, and qualifications
• response, accessibility, or safeguarding contact information

The image may repeat a short headline or selected detail for visual emphasis. The post copy remains the usable record.

A link pictured inside a graphic is not a working link. Put the real link in the destination field or visible post text. Use words that tell the reader where it goes, such as Register for the community meal, instead of a bare Click here.

Test type in the real phone preview

There is no defensible universal point size for every social graphic. A point measurement in a design file does not tell you how large the words will appear after export, crop, compression, and display inside a phone feed.

Use the destination preview at the expected display size. Hold the phone at an ordinary reading distance. Do not zoom during the first pass. Ask a reviewer who did not make the graphic to read it in normal order.

Check these details:

• Can the main line be read without opening the image?
• Does the eye find the main message before supporting details?
• Are line breaks natural, or do they split a name, Scripture reference, date, or phrase?
• Is there enough space between lines, blocks, and the edge of the crop?
• Do thin strokes, condensed letters, all caps, italics, or decorative forms slow recognition?
• Does any word cross a busy photograph, gradient, glare, fabric pattern, face, or architectural detail?
• Do descenders, accents, diacritics, and punctuation remain complete?
• Does the typeface contain every glyph required by the language?
• Does a translated version expand, wrap, or reorder without clipping?

Hierarchy is more than size. Weight, placement, open space, and a solid backing can separate a headline from supporting information. Keep the number of visual levels low enough that the reader does not have to decode the layout.

A short headline can still be hard to read when it sits over a photograph. Sampling the cleanest part of the photo proves little. Inspect the weakest area behind the letter strokes. If the background changes, use a solid text panel, a sufficiently opaque overlay that you test in its final form, a different crop, or another image.

Use the contrast ratios at their actual scope

WCAG 2.2 Success Criterion 1.4.3 sets these Level AA minimums for text and images of text in web content:

• 4.5:1 for ordinary text
• 3:1 for large-scale text

WCAG defines large-scale text as at least 18 point when not bold or at least 14 point when bold, with equivalent sizing for Chinese, Japanese, and Korean fonts. It also lists exceptions, including incidental text, pure decoration, text that is not visible to anyone, and logotypes.

Use 4.5:1 as the default when you cannot establish that the delivered text meets the large-scale definition. Do not call a social headline large because it occupies much of the source canvas. Delivery size matters.

Measure the foreground against the background directly behind it. If a word crosses several background colors, test the weakest expected pair. A passing navy-and-cream swatch does not prove the same navy text passes over a cream photograph with bright windows and dark shadows.

Contrast is not a readability score. A passing result does not tell you whether:

• the type is large enough at phone size
• the letterforms are familiar or thick enough in practice
• the words are clipped, crowded, or badly spaced
• the reading order is clear
• the destination crop preserves the message
• the alternative text is useful
• color is the only cue
• the whole post conforms to WCAG

Meaningful graphic objects need a separate check. WCAG guidance on non-text contrast generally uses 3:1 against adjacent colors for parts of graphics required to understand the content, with stated exceptions. A decorative shape does not become informative because it has high contrast. An unlabeled slice in a chart does not become understandable because its border passes.

Do not call the post compliant after measuring a few pairs. WCAG conformance concerns complete web content, and legal duties depend on the organization, jurisdiction, content, and relationship. A qualified adviser can assess legal scope when it matters.

Never make color carry the message alone

Color can organize a graphic. It cannot be the only visible clue for assigned meaning.

A schedule that marks open in green and closed in red still depends on color, even when both colors contrast strongly with the background. Add visible words, patterns, shapes, or another cue. A person should understand the distinction without naming the color.

The same rule applies to:

• available and full event sessions
• confirmed and changed service times
• two speakers in a quotation graphic
• categories in a chart
• required and optional actions
• safe and unsafe route markings

WCAG 2.2 guidance on use of color makes this visible requirement explicit. Alt text for a color key may help a screen-reader user, but it does not fix a color-only cue for a sighted person who cannot distinguish the colors.

Write alt text after the final crop

Alt text should replace the image's relevant information or function in this post. Write it after the crop, overlay, and visible post copy are final.

Use this sequence:

1. Read the visible post copy without looking at the image.
2. State what the image adds to the post.
3. Include any essential words visible only in the image.
4. Describe visual information needed for the same purpose.
5. Remove details that do not help with that purpose.
6. Read the post copy and alt text together to catch repetition.

Here are three common failures.

Do not infer what the pixels cannot establish. Avoid guessing a person's disability, ethnicity, gender, relationship, emotion, diagnosis, immigration status, financial condition, spiritual state, or consent. Use known, relevant facts only when the church has authority to publish them.

For a complex chart, timetable, map, or diagram, a short alt field may be the wrong place for all the detail. Provide a short identification and summary, then place the full information in usable post text, a properly structured page, or another accessible format. If the destination cannot carry an adequate equivalent, do not use that graphic there.

Test the exact destination, not a size label

Square, portrait, and story are starting canvases. They are not promises about every feed, device, account, composer, preview, share card, or embedded view.

Before publishing, use the current composer and check:

• the exact destination account and audience
• the feed preview and expanded image
• automatic crops, safe areas, and interface overlays
• the first image in a multi-image post
• the visible post copy, line breaks, mentions, and hashtags
• the alt-text or image-description field
• the working link and its destination
• any cross-post, scheduler, or approval path that sits between the draft and the provider

Current LinkedIn photo guidance says feed photos render at a maximum 4:5 ratio and that the first image in a multi-image post receives greater visual emphasis. Another destination can behave differently. Provider interfaces also change. Recheck near publication.

Do not assume a scheduler preserves alt text because its draft form has an alt field. Publish one controlled test through the actual path, then inspect the resulting post with the tools your church supports. A saved description is evidence to carry forward, not proof of delivery.

Static graphics are not video accessibility

This review applies to a static image. Animated stories, GIFs, livestreams, and videos introduce other needs.

Moving content may need accurate captions, a transcript, audio description, controls for pause or motion, flash review, enough display time, and a media player people can operate. A static cover image and its alt text do not make the video accessible. If the team cannot review motion and audio, publish the information in a format it can support.

The same boundary applies when a destination turns a set of still images into an animated format. Check the final format, timing, reading order, and controls rather than reusing the static approval.

Review language and cognitive load

A readable typeface cannot rescue unclear writing.

Explain church-specific terms when the intended reader may not know them. Keep instructions concrete. Put one action in one sentence where possible. Avoid crowding a prayer invitation, event notice, doctrine summary, and registration process into one visual.

For every language version:

• use a reviewer who understands the language and church context
• confirm the typeface contains the needed script, accents, and punctuation
• check shaping, direction, line breaks, and reading order
• allow for expansion or contraction rather than shrinking the words until they fit
• repeat the phone-size and destination tests on the translated asset

Do not claim that one font is universally accessible. Letter familiarity, weight, spacing, size, language support, display quality, and reader needs all matter. Clear hierarchy and open space can reduce clutter, but no arrangement works for everyone.

Ask people with relevant lived experience to review recurring formats. Do not simulate disability by blurring an image, applying a color filter, or covering your eyes and treating the result as user research.

Check the people and material in the image

Accessibility review does not replace rights, consent, privacy, dignity, or safeguarding review.

For every photograph, illustration, font, texture, icon, quotation, and other asset, record what allows the church to publish it. Check ownership, licence scope, required credit, allowed edits, destination, territory, and expiry. Credit does not create permission.

For recognizable people, confirm the church's consent and safeguarding process for the planned channel and use. A photograph can reveal worship attendance, a child's location, a name badge, a school uniform, a house number, a prayer request, a medical detail, or another fact the subject did not intend to publish.

The Church of England's current consent-form guidance records permission by activity, wider communication, channel, and name treatment. That is useful operational guidance in its setting. Your church still needs its own policy and advice for the applicable jurisdiction.

Hold the post when rights or consent are unclear. Replace the asset, remove identifying details, use a non-identifying illustration, or publish plain text. A calendar deadline is not permission.

Make sure someone can handle the response

A post can be visually readable and operationally careless.

If it asks people to share prayer needs, disclose a hardship, register a child, request financial help, report a safeguarding concern, or send a direct message, name the person who will monitor the route. Set the coverage window and escalation path. Check that the public wording does not ask people to place sensitive information in comments.

If nobody can respond appropriately, change the call to action or omit it. An unanswered invitation can create confusion at best and a pastoral or safeguarding problem at worst.

Where Church Media Kit fits

In the Church Media Kit build reviewed for this guide, a saved Sermon Kit can retain caption and alternative-text drafts. Studio also provides manual controls for static text, fonts, colors, backgrounds, images, shapes, layers, position, and size.

Those controls support editing. They do not automatically test contrast, certify accessibility, clear rights, guarantee crop safety, send alt text to every destination, prove platform acceptance, or decide compliance.

Review the final pixels and revise the saved description for the image's actual purpose. Then confirm the destination field and published result through the path your church uses.

Omit the graphic when the graphic is the problem

Use plain text or another format when:

• essential wording will not fit at a readable phone size
• the destination crop changes the meaning or removes required context
• the platform or publishing path cannot carry an adequate text equivalent
• a complex chart, map, or timetable cannot be explained usefully there
• rights, consent, privacy, dignity, or safeguarding remains unresolved
• the needed language or script renders incorrectly
• the post relies on color alone and cannot be repaired in time
• motion or audio needs exceed the team's review capacity
• the call to action has no responsible response owner

Omission is an editorial decision, not a failure to fill a slot. The goal is to communicate the information, not to defend the graphic.

A reusable destination review

Record pass, hold, or a reasoned not applicable decision for the exact post.

Purpose and information

• The post has one named purpose and intended reader.
• Essential details, links, context, and next steps appear in usable post text.
• The image adds information or a deliberate visual purpose.
• Facts, quotations, names, dates, and source wording match an approved source.

Type and contrast

• A second person can read the graphic at its actual phone-preview size.
• Hierarchy, line breaks, spacing, accents, glyphs, and reading order remain clear.
• Ordinary text reaches 4.5:1 against the weakest background area.
• Any use of 3:1 for large-scale text fits WCAG's delivered-size definition.
• Meaningful graphic objects receive their separate contrast review.
• Color is not the only visible cue for information or action.
• Essential words remain available outside the image.

Alternative text and destination

• The alternative is based on the final pixels, purpose, and surrounding copy.
• It includes essential image information without keyword stuffing or decorative inventory.
• It avoids unsupported inference about people, feelings, identity, or outcomes.
• Every intended crop and overlay preserves the subject and meaning.
• The current destination field, preview, account, audience, and link were checked.
• The publishing path was tested for description delivery where that path matters.

People, rights, and response

• The church has the required rights, licence, credit, and edit authority for every asset.
• Consent, privacy, dignity, and safeguarding were reviewed for the planned use.
• The post does not expose a location, identity, story, or sensitive detail without authority.
• A named person can handle replies, direct messages, registrations, disclosures, and escalation.
• An authorized publisher approved this exact destination version.

A checked box should point to evidence. Keep the destination preview, contrast reading, source, consent or rights record, alt-text version, and approver with the post record your church uses.

Frequently asked questions

What contrast ratio should church social graphics use?

Use at least 4.5:1 for ordinary text and images of text. Use 3:1 only when the delivered text meets WCAG's large-scale definition, which is at least 18 point when not bold or at least 14 point when bold, with equivalent sizing for CJK fonts. Test the actual background behind the text. These ratios are one web-accessibility check, not proof that a complete social post conforms or complies with law.

Is there a minimum font size for Instagram or Facebook graphics?

There is no useful universal point size across source files, crops, devices, and destination previews. Test the exported graphic at the size it occupies in the current phone preview. If a person needs to open or zoom the image to discover the main message, simplify the graphic or move the information into post text.

Should alt text repeat the words in the image?

Include essential words that are available only in the image. When the visible post copy already provides the same information, avoid needless repetition and describe what the image adds. Read the post copy and alternative together before publishing.

Should every image have alt text?

Every informative or functional image needs a suitable text alternative. A purely decorative image uses a null alternative in HTML. Social platforms vary, and some do not expose an equivalent decorative control in every workflow. Check the destination. If the image adds nothing and cannot be treated appropriately, omit it.

Does passing contrast make the graphic accessible?

No. Contrast does not test type size, hierarchy, spacing, clipping, language support, color-only meaning, alternative text, crop behavior, links, rights, consent, safeguarding, or the rest of the destination post.

Can automatic alt text be left as published?

Review it against the final image and purpose. Automatic descriptions may identify objects while missing the event information, relationship, action, or context the post needs. They can also infer details inaccurately. Replace or edit the text through the current destination controls when possible.

What if the church cannot make the graphic work?

Publish the essential information as clear text, choose a simpler asset, or use another format the team can review. A plain post that people can understand and act on is a better decision than a polished graphic that withholds the message.