Skip to content
https://cbn.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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 Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://cbn.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://cbn.com/manifest.json

Manifest contains invalid JSON.

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Heading Hierarchy
56 headings, 1 skip(s)
REVIEW
56 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Spread Christ's Love Worldwide
  • H1 Spread Christ's Love Worldwide duplicate H1
  • H2 Family of Ministries
  • H2 Top Stories
  • H3 This Movement is Calling Gen Z Into a New Type of Evangelism!
  • H3 A T.V. Show Gave Her Hope for Healing
  • H3 A Childhood Filled With Pain
  • H3 A Guide to a Deeper Relationship with the Holy Spirit
  • H2 Luke 17:19
  • H2 CBN’s impact around the world
  • H4 CBN’s impact worldwide skipped
  • H4 USA
  • H3 Daily prayers for people across the country
  • H4 Latin America
  • H3 Highlighting testimonies of God’s faithfulness
  • H4 Ukraine
  • H3 For 30 years, CBN has been serving the people of Ukraine
  • H4 Israel
  • H3 Help in Times of Crisis
  • H4 International
  • H3 Reaching Kids for Christ
  • H4 USA
  • H3 Daily prayers for people across the country
  • H4 Latin America
  • H3 Highlighting testimonies of God’s faithfulness
  • H4 Ukraine
  • H3 For 30 years, CBN has been serving the people of Ukraine
  • H4 Israel
  • H3 Help in Times of Crisis
  • H4 International
  • H3 Reaching Kids for Christ
  • H2 Journey Through the Word
  • H3 Join Our Bible in a Year Reading Adventure
  • H2 CBN News
  • H3 Trump Extends Ceasefire as Iran Hardliners Hold Parades; Israel Celebrates 78th Independence Day
  • H3 Iran's Doomsday Theology and The Far Deadlier Danger Coming from Sunni Extremists
  • H3 Virginia Voters OK New Map That Could Decide House Control - Will High Court Intervene?
  • H3 100 Missionaries Deploy to 10/40 Window Amid Increasing Reports of Visions of 'The Man in White'
  • H3 Live: CBN News Channel
  • H3 Live: CBN News Channel
  • H2 The 700 Club - April 22, 2026
  • H2 Only One Returned
  • H2 More from CBN
  • H2 The Christian Broadcasting Network
  • H2 Connect on social
  • H2 The Christian Broadcasting Network
  • H2 Cookies on this website.
  • H2 Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Necessary Cookies
  • H4 Analytics Cookies
  • H5 Functional Cookies
  • H5 Performance Cookies
  • H4 Tracking Cookies
  • H5 Advertising Cookies
  • H3 Cookie List

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

B
Alt Text Quality
13 of 71 images have issues
REVIEW
13 of 71 images have issues
Warning::
13 image(s) with filename as alt text
Info::
58 image(s) with good alt text
71 images 58 good alt text 13 generic
IssueCount
filename13 image(s)
C
Form Accessibility
Action
28 of 42 controls have issues
REVIEW
28 of 42 controls have issues
Critical::
28 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="op" id="edit-submit">; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select> (+18 more)
Info::
14 control(s) properly labeled
42 controls
14 labeled
0 placeholder only
28 unlabeled
ControlTypeLabelMethod
#edit-keystextSearchfor/id
#edit-email--3emailemail addressaria-label
#edit-submit--3submitsign uparia-label
#newsletter-footer-email-inputemailemail addressaria-label
#edit-submit--2submitsign uparia-label
#ot-group-id-BG35checkboxAnalytics Cookiesfor/id
#ot-sub-group-id-C0003checkboxFunctional Cookiesaria-label
#ot-sub-group-id-C0002checkboxPerformance Cookiesaria-label
#ot-group-id-BG36checkboxTracking Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
#edit-submitsubmit(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit" name="op" id="edit-submit">; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select> (+18 more)

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Site search ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A+
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main" MAIN CONTENTINFO footer
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Luke 17:1921.00:13.0:1
#000000
#FFFFFF
Pass
h2 Journey Through the …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The 700 Club - April…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The Christian Broadc…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Connect on social21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The Christian Broadc…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Cookies on this webs…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Privacy Preference C…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Daily prayers for pe…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Highlighting testimo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 For 30 years, CBN ha…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Help in Times of Cri…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Reaching Kids for Ch…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Daily prayers for pe…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Highlighting testimo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 For 30 years, CBN ha…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Help in Times of Cri…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Reaching Kids for Ch…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Join Our Bible in a …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Manage Consent Prefe…21.00:13.0:1
#000000
#FFFFFF
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
Lighthouse Accessibility Audits
Score 90/100 — 5 failing, 30 passed
PASS
90

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
IRAN NEEDS GOD’S HOPE RIGHT NOW. GIVE TODAY TO PROVIDE LIFE-SAVING RELIEF. div.container > div.relative > div.site-alert__clickable-banner > a.site-alert__title
GIVE NOW div.dropdown__content > ul.menu > li.menu__item > a.bg-orange
Join Our Bible in a Year Reading Adventure div.banner__inner > div.banner__content > div.banner__content-inner > h3.mb-s08

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ISRAEL div.swiper-slide > div.map-panel > div.map-panel__inner > h4.sm:mb-[15px]

These are opportunities to improve keyboard navigation in your application.

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
div.banner__content > div.banner__content-inner > div.banner__top > a.flex-grow-0 div.banner__content > div.banner__content-inner > div.banner__top > a.flex-grow-0
January 2026 Telethon Premium div.combo-news__grid > div.combo-news__middle > div.cbn-component > a.analytics-cta
div.js-watch-live-news > article.news-card--watch-live > div.watch-live-v1__content > a.watch-live-v1__bottom div.js-watch-live-news > article.news-card--watch-live > div.watch-live-v1__content > a.watch-live-v1__bottom

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide 1 div.cbn-m-extend-sm > div.js-map-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.cbn-m-extend-sm > div.js-map-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.cbn-m-extend-sm > div.js-map-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.cbn-m-extend-sm > div.js-map-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div.cbn-m-extend-sm > div.js-map-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 1 div.-mx-cbn30 > div.js-media-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.-mx-cbn30 > div.js-media-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.-mx-cbn30 > div.js-media-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.-mx-cbn30 > div.js-media-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div.-mx-cbn30 > div.js-media-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Terms of use div#block-footersecondarymenu > ul.menu > li.menu__item > a.menu__link
Privacy Policy div#block-footersecondarymenu > ul.menu > li.menu__item > a.menu__link
Donor Privacy div#block-footersecondarymenu > ul.menu > li.menu__item > a.menu__link
CBN Cookie Policy div#block-footersecondarymenu > ul.menu > li.menu__item > a.menu__link
Third Party Processors div#block-footersecondarymenu > ul.menu > li.menu__item > a.menu__link
Cookies Settings div#block-footersecondarymenu > ul.menu > li.menu__item > a.menu__link
myCBN div#block-footersecondarymenu > ul.menu > li.menu__item > a.menu__link

These items highlight common accessibility best practices.

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
CBN Cookie Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●Input buttons have discernible text.
●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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●ARIA input fields have accessible names
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○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.
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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