Skip to content
https://discovery.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
42
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark 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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header SEARCH MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
Heading Hierarchy
Action
62 headings, 2 skip(s)
FIX
62 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
26 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H6 Live Now
  • H1 Discovery Homepage
  • H3 Fridays at 8/7c skipped
  • H3 Sundays at 8/7c
  • H3 Sundays at 9/8c
  • H3 Mondays at 8/7c
  • H3 schedule
  • H4 (empty)
  • H5 The Last Woodsmen
  • H4 (empty)
  • H5 The Last Woodsmen
  • H4 (empty)
  • H5 The Last Woodsmen
  • H4 (empty)
  • H5 The Last Woodsmen
  • H4 (empty)
  • H5 Homestead Rescue
  • H4 (empty)
  • H5 Homestead Rescue
  • H4 (empty)
  • H5 Homestead Rescue
  • H4 (empty)
  • H5 Moonshiners
  • H4 (empty)
  • H5 Moonshiners
  • H4 (empty)
  • H5 Moonshiners
  • H4 (empty)
  • H5 Moonshiners
  • H4 On Tonight
  • H5 Moonshiners
  • H4 (empty)
  • H5 (empty)
  • H4 (empty)
  • H5 (empty)
  • H4 (empty)
  • H5 Filthy Fortunes
  • H4 (empty)
  • H5 Filthy Fortunes
  • H4 (empty)
  • H5 Moonshiners
  • H4 (empty)
  • H5 (empty)
  • H4 (empty)
  • H5 (empty)
  • H4 (empty)
  • H5 Filthy Fortunes
  • H4 (empty)
  • H5 Filthy Fortunes
  • H4 (empty)
  • H5 Truck Dynasty
  • H4 (empty)
  • H5 Gold Rush: Dave Turin's Lost Mine
  • H2 What to Watch
  • H3 Moonshiners: Master Distiller
  • H3 Expedition X
  • H3 Harpoon Hunters
  • H2 Do Not Sell or Share My Personal Information
  • H5 For residents of certain states only. Please visit ourU.S. State Supplement for more information. skipped
  • H4 Allow the Sale, Sharing or use of My Personal information for Targeted Advertising
  • H4 Global Privacy Control (GPC)
  • H3 Cookie List

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

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

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

F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 403 Page Title Access Denied Custom Styling Navigation Homepage Link Search Form
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Alt Text Quality
1 of 18 images have issues
REVIEW
1 of 18 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
8 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
18 images 9 good alt text 8 decorative 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

C
Favicon & Branding
Action
17 icon(s) detected
REVIEW
17 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
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 2 pass AA only
h1 Discovery Homepage
2.72:1
#000000
on
#704A37
needs 3.0:1 (large text)
32px · mid-page · over background image/gradient
title Discovery Channel Shows and Articles | D…
1.29:1
#000000
on
#21201F
needs 4.5:1 (normal text)
16px · top of page (header area)
div Deadliest Catch
1.82:1
#000000
on
#790103
needs 4.5:1 (normal text)
16px · above the fold
div Moonshiners
2.40:1
#000000
on
#9B0203
needs 4.5:1 (normal text)
16px · above the fold
div Harpoon Hunters
2.59:1
#000000
on
#A40203
needs 4.5:1 (normal text)
16px · above the fold
div Homestead Rescue
3.00:1
#000000
on
#B60202
needs 4.5:1 (normal text)
16px · mid-page
a See All Shows
2.49:1
#000000
on
#4F4E3C
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
label Search For
3.00:1
#000000
on
#79502B
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

3 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 Discovery Homepage2.72:13.0:1
#000000
#704A37
Fail
h2 Do Not Sell or Share…4.53:13.0:1
#000000
#B85A29
Pass
h3 schedule4.53:13.0:1
#000000
#B85A29
Pass
h3 Cookie List4.53:13.0:1
#000000
#B85A29
Pass
title Discovery Channel Sh…1.29:14.5:1
#000000
#21201F
Fail
span Moonshiners8.44:14.5:1
#000000
#ACA48C
Pass
a Stream Now18.26:14.5:1
#000000
#EFEFEF
Pass
button Shows18.26:14.5:1
#000000
#EFEFEF
Pass
a Shows19.26:14.5:1
#000000
#F5F5F5
Pass
a See All Shows21.00:14.5:1
#000000
#FFFFFF
Pass
div Gold Rush21.00:14.5:1
#000000
#FFFFFF
Pass
div Naked and Afraid21.00:14.5:1
#000000
#FFFFFF
Pass
div Expedition Unknown5.10:14.5:1
#000000
#B56768
Pass
div Deadliest Catch1.82:14.5:1
#000000
#790103
Fail
div Moonshiners2.40:14.5:1
#000000
#9B0203
Fail
div Harpoon Hunters2.59:14.5:1
#000000
#A40203
Fail
div Homestead Rescue3.00:14.5:1
#000000
#B60202
Fail
a See All Shows2.49:14.5:1
#000000
#4F4E3C
Fail
a Schedule5.69:14.5:1
#000000
#A07F5C
Pass
label Search For3.00:14.5:1
#000000
#79502B
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 88/100 — 4 failing, 27 passed
REVIEW
88

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
What to Watch 6 SEASONS Moonshiners: Master Distiller Binge on discovery+ 9 SEA… div.full-width > div.main > div.fullWidthPromo > section#mod-full-width-promo-2

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Fridays at 8/7c div.o-FullWidthPromo__m-Body > div#mod-card-1 > div.m-Card__m-TextWrap > h3.m-Card__a-Headline
Moonshiners div#mod-on-tv-full-width-1 > div.m-ScheduleCard__m-TextWrap > div.m-ScheduleCard__m-ScheduleItem--OnNow > h5.m-ScheduleCard__a-Headline

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js-support html.js-support

These items highlight common accessibility best practices.

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]`s are contained by their required parent element
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Form elements have associated labels
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.
Links have a discernible name
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
Touch targets have sufficient size and spacing.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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 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.
Image elements have `[alt]` attributes
Input buttons have discernible text.
`<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.
`[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.
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.
A+
Form Accessibility
All 8 controls labeled
PASS
All 8 controls labeled
Info::
8 control(s) properly labeled
8 controls
8 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#typeaheadinputtextsite search inputaria-label
emailtextEnter your emailaria-label
#ot-group-id-BG2713checkboxAllow the Sale, Sharing or use of My Personal information for Targeted Advertisingfor/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
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback