Skip to content
https://cbs.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
404 Error Page
Action
HTTP 404, custom page
FIX
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 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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
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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
9 headings
REVIEW
9 headings
Warning::
Multiple H1 headings (5 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
5 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H1 (empty)
  • H1 (empty)
  • H1 (empty)
  • H1 (empty)
  • H2 Site Navigation
  • H2 Privacy & Terms
  • H2 Information
  • H2 Follow Us

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 15 fail WCAG AA
REVIEW

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

5 pass 15 fail WCAG AA 2 pass AA only
title CBS TV Network Primetime, Daytime, Late …
1.78:1
#000000
on
#2F3940
needs 4.5:1 (normal text)
16px · top of page (header area)
button Pause Carousel
3.43:1
#000000
on
#576468
needs 4.5:1 (normal text)
16px · top of page (header area)
a CBS News 24/7
1.65:1
#000000
on
#39312B
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a CBS Sports HQ
1.04:1
#000000
on
#0F0407
needs 4.5:1 (normal text)
16px · above the fold
a 48 Hours
2.87:1
#000000
on
#5C5643
needs 4.5:1 (normal text)
16px · above the fold
a Judge Judy
2.42:1
#000000
on
#524B39
needs 4.5:1 (normal text)
16px · above the fold
a Hot Bench
2.59:1
#000000
on
#54503C
needs 4.5:1 (normal text)
16px · above the fold
a CBS Sports Golazo Network
2.12:1
#000000
on
#484330
needs 4.5:1 (normal text)
16px · above the fold
a Inside Edition
1.86:1
#000000
on
#3F3A31
needs 4.5:1 (normal text)
16px · mid-page
a 60 Minutes
1.44:1
#000000
on
#2B291E
needs 4.5:1 (normal text)
16px · mid-page
a UEFA Champions League
1.35:1
#000000
on
#25241D
needs 4.5:1 (normal text)
16px · mid-page
a Car Chase
1.20:1
#000000
on
#1B1915
needs 4.5:1 (normal text)
16px · mid-page
a Schedule
1.16:1
#000000
on
#171614
needs 4.5:1 (normal text)
16px · mid-page
a TV Provider
1.13:1
#000000
on
#131312
needs 4.5:1 (normal text)
16px · mid-page
a Sign In
1.12:1
#000000
on
#121211
needs 4.5:1 (normal text)
16px · mid-page

1 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
title CBS TV Network Prime…1.78:14.5:1
#000000
#2F3940
Fail
button Pause Carousel3.43:14.5:1
#000000
#576468
Fail
a Shows6.04:14.5:1
#000000
#828B8F
Pass
a CBS NEWS9.72:14.5:1
#000000
#A6B3B3
Pass
a CBS SPORTS13.35:14.5:1
#000000
#D3CEBF
Pass
a Live TV17.25:14.5:1
#000000
#F7E8BF
Pass
a CBS5.77:14.5:1
#000000
#8B876A
Pass
a CBS News 24/71.65:14.5:1
#000000
#39312B
Fail
a CBS Sports HQ1.04:14.5:1
#000000
#0F0407
Fail
a 48 Hours2.87:14.5:1
#000000
#5C5643
Fail
a Judge Judy2.42:14.5:1
#000000
#524B39
Fail
a Hot Bench2.59:14.5:1
#000000
#54503C
Fail
a CBS Sports Golazo Ne…2.12:14.5:1
#000000
#484330
Fail
a Inside Edition1.86:14.5:1
#000000
#3F3A31
Fail
a 60 Minutes1.44:14.5:1
#000000
#2B291E
Fail
a UEFA Champions Leagu…1.35:14.5:1
#000000
#25241D
Fail
a Car Chase1.20:14.5:1
#000000
#1B1915
Fail
a Schedule1.16:14.5:1
#000000
#171614
Fail
a TV Provider1.13:14.5:1
#000000
#131312
Fail
a Sign In1.12:14.5:1
#000000
#121211
Fail

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.

B
Lighthouse Accessibility Audits
Score 87/100 — 3 failing, 23 passed
REVIEW
87

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.onnow-wrapper > div.onnow-wrapper-inside > div.channel-logo > img div.onnow-wrapper > div.onnow-wrapper-inside > div.channel-logo > img
div.onnow-wrapper > div.onnow-wrapper-inside > div.label > img div.onnow-wrapper > div.onnow-wrapper-inside > div.label > img
div.onnow-wrapper > div.onnow-wrapper-inside > div.channel-logo > img div.onnow-wrapper > div.onnow-wrapper-inside > div.channel-logo > img

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Your browser … main#main-container > div.top-components > section.hero__wrapper > ul#hero-slider
NEW EPISODE TONIGHT 8/7C From murder & espionage to terrorism & stolen submari… section#hero-content > div.hero__content-wrapper > div.hero__lockup > ul#hero-content-slider
footer > div.container > div.socialIcons > ul.block

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Your browser … section.hero__wrapper > ul#hero-slider > div.swiper-wrapper > li.slide-js
… section.hero__wrapper > ul#hero-slider > div.swiper-wrapper > li.slide-js
… section.hero__wrapper > ul#hero-slider > div.swiper-wrapper > li.slide-js
… section.hero__wrapper > ul#hero-slider > div.swiper-wrapper > li.slide-js
Tyler Perry's Divorced Sistas section.hero__wrapper > ul#hero-slider > div.swiper-wrapper > li.slide-js
NEW EPISODE TONIGHT 8/7C From murder & espionage to terrorism & stolen submari… div.hero__lockup > ul#hero-content-slider > div.swiper-wrapper > li.slide-js
NEW EPISODE TONIGHT 9/8C NCIS: ORIGINS follows a young Leroy Jethro Gibbs in t… div.hero__lockup > ul#hero-content-slider > div.swiper-wrapper > li.slide-js
NEW EPISODE TONIGHT 10/9C A brilliant and eclectic team of NCIS agents and the… div.hero__lockup > ul#hero-content-slider > div.swiper-wrapper > li.slide-js
CATCH UP ON THE LATEST EPISODE From Dick Wolf and the team behind FBI, Tom Ell… div.hero__lockup > ul#hero-content-slider > div.swiper-wrapper > li.slide-js
NEW EPISODE EVERY WEDNESDAY Five friends find strength in their sisterhood as … div.hero__lockup > ul#hero-content-slider > div.swiper-wrapper > li.slide-js

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○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
●`[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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○`<frame>` or `<iframe>` elements have a title
○`<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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○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.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○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.
○Elements with visible text labels have matching accessible names.
○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.
A
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 NAV MAIN ASIDE "Carousel Pause/Play Button" CONTENTINFO footer

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

A+
Alt Text Quality
All 10 images OK
PASS
All 10 images OK
Info::
10 image(s) with good alt text
10 images 10 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
1 controls
0 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback