Skip to content
https://churchofjesuschrist.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
favicon.ico Present
PNG Icons Missing
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set Dark theme-color Not set CSS indicators Not detected

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found Inline @media print Not detected
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
2 landmarks
REVIEW
2 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
No contentinfo (footer) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header MAIN CONTENTINFO (missing!)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Page Not Found Custom Styling Navigation Homepage Link Search Form
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

12 pass 8 fail WCAG AA 5 pass AA only
h2 What We Believe
2.29:1
#000000
on
#4A4749
needs 3.0:1 (large text)
24px · above the fold · over background image/gradient
h2 Common Questions
1.81:1
#000000
on
#003E52
needs 3.0:1 (large text)
24px · mid-page
div Come Celebrate This Historic Event on Ap…
3.35:1
#000000
on
#5F615C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Learn More
3.30:1
#000000
on
#605F5F
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
div Feel the Love of Jesus Christ at General…
2.72:1
#000000
on
#515354
needs 4.5:1 (normal text)
16px · above the fold
p Talks now available to watch, read, and …
2.76:1
#000000
on
#545450
needs 4.5:1 (normal text)
16px · above the fold
a Study Now
2.87:1
#000000
on
#545756
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
div Learn about The Church of Jesus Christ o…
3.28:1
#000000
on
#6C5D42
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

4 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Salt Lake Temple Cel…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 What We Believe2.29:13.0:1
#000000
#4A4749
Fail
h2 Explore the Temple S…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Common Questions1.81:13.0:1
#000000
#003E52
Fail
h2 All are welcome. Vis…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Jesus Christ, Our Pe…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Grow closer to God. …5.24:13.0:1
#000000
#7F7F7F
Pass
h2 A Community of Faith…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Get the latest news …5.24:13.0:1
#000000
#7F7F7F
Pass
title Homepage - The Churc…5.24:14.5:1
#000000
#7F7F7F
Pass
div Come Celebrate This …3.35:14.5:1
#000000
#5F615C
Fail
a Learn More3.30:14.5:1
#000000
#605F5F
Fail
div Feel the Love of Jes…2.72:14.5:1
#000000
#515354
Fail
p Talks now available …2.76:14.5:1
#000000
#545450
Fail
a Study Now2.87:14.5:1
#000000
#545756
Fail
div Learn about The Chur…3.28:14.5:1
#000000
#6C5D42
Fail
div Learn About Jesus Ch…5.24:14.5:1
#000000
#7F7F7F
Pass
div Get to know and foll…5.24:14.5:1
#000000
#7F7F7F
Pass
div Find Meaning in Your…5.24:14.5:1
#000000
#7F7F7F
Pass
div Seek God’s perspec…5.24:14.5:1
#000000
#7F7F7F
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+
Heading Hierarchy
9 headings
PASS
9 headings
Info::
Single H1 present
  • H1 Salt Lake Temple Celebration
  • H2 What We Believe
  • H2 Explore the Temple Square Visitors’ Center Media Kit
  • H2 Common Questions
  • H2 All are welcome. Visit a church near you.
  • H2 Jesus Christ, Our Perfect Example
  • H2 Grow closer to God. Meet with missionaries.
  • H2 A Community of Faith Focused on Jesus Christ
  • H2 Get the latest news from the Church.
A+
Alt Text Quality
All 13 images OK
PASS
All 13 images OK
Info::
11 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
13 images 2 good alt text 11 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtext(Enter full address)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A+
Lighthouse Accessibility Audits
Score 97/100 — 2 failing, 27 passed
PASS
97

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Temple Square Visitors’ Center: Christus Statue body > div.sc-cpclqO > div.sc-dTWiOz > a.sc-gSifMm

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
What We Believe Learn about The Church of Jesus Christ of Latter-day Saints main > div.sc-hqtLyI > div.sc-iVnIWt > a.sc-jBaHRL
Learn About Jesus Christ Get to know and follow Him main > div.sc-hqtLyI > div.sc-ikkVnJ > a.sc-hldWLq
Find Meaning in Your Life Seek God’s perspective main > div.sc-hqtLyI > div.sc-ikkVnJ > a.sc-hldWLq
Navigate Life’s Challenges Discover strength, direction, and peace main > div.sc-hqtLyI > div.sc-ikkVnJ > a.sc-hldWLq
Visit Newsroom div.sc-gvqKNf > div.sc-cOpnSz > div#Get the latest news from the Church.-content > a.sc-1lb7nf5-0
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback