Skip to content
https://spreaker.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
49
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Landmark Structure
Action
No landmarks
FIX
No 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
Info::
No banner (header) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

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
15 headings, 4 skip(s)
FIX
15 headings, 4 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
3 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Trending on Spreaker
  • H2 Trending episodes today
  • H2 Spreaker Prime Network
  • H2 Our Top Podcasts
  • H2 Explore our Supporters Club Podcasts
  • H2 Featured Categories
  • H4 Looks like you don't have any active episode skipped
  • H2 Current
  • H4 (empty)
  • H6 (empty)
  • H4 Looks like you don't have any episodes in your queue
  • H4 Next Up
  • H6 (empty)
  • H3 Unlock Spreaker's full potential
  • H3 Unlock Spreaker's full potential

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

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

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

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">; <input type="text">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtext(Search over 10M podcast episodes)placeholder only
inputtext(Search over 10M podcast episodes)placeholder only

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

<input type="text">; <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

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Spreaker ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 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::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Spreaker
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name Spreaker ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode browser ✗
Name Spreaker Display Mode browser Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Trending on Spreaker
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trending episodes today
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Spreaker Prime Network
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Top Podcasts
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore our Supporters Club Podcasts
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Categories
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Current
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Unlock Spreaker's full potential
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
19px · bottom of viewport
title Spreaker
1.39:1
#000000
on
#262626
needs 4.5:1 (normal text)
16px · top of page (header area)
span Discover
1.39:1
#000000
on
#262626
needs 4.5:1 (normal text)
16px · top of page (header area)
span Your Library
1.06:1
#000000
on
#0A0A0A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Search
1.06:1
#000000
on
#0A0A0A
needs 4.5:1 (normal text)
16px · top of page (header area)
div For Podcasters
1.22:1
#000000
on
#1B1B1B
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Your Podcasts
1.39:1
#000000
on
#262626
needs 4.5:1 (normal text)
16px · above the fold
div Free
1.39:1
#000000
on
#262626
needs 4.5:1 (normal text)
16px · above the fold
div Our Platform
1.39:1
#000000
on
#262626
needs 4.5:1 (normal text)
16px · above the fold
span How Spreaker Works
1.39:1
#000000
on
#262626
needs 4.5:1 (normal text)
16px · above the fold
span Podcasts App
1.39:1
#000000
on
#262626
needs 4.5:1 (normal text)
16px · above the fold
span Spreaker Create
1.23:1
#000000
on
#1C1C1C
needs 4.5:1 (normal text)
16px · above the fold
div New
1.06:1
#000000
on
#0A0A0A
needs 4.5:1 (normal text)
16px · above the fold

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
h2 Trending on Spreaker1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Trending episodes to…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Spreaker Prime Netwo…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Our Top Podcasts1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Explore our Supporte…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Featured Categories1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Current1.06:13.0:1
#000000
#0A0A0A
Fail
h3 Unlock Spreaker's fu…1.06:13.0:1
#000000
#0A0A0A
Fail
title Spreaker1.39:14.5:1
#000000
#262626
Fail
span Discover1.39:14.5:1
#000000
#262626
Fail
span Your Library1.06:14.5:1
#000000
#0A0A0A
Fail
span Search1.06:14.5:1
#000000
#0A0A0A
Fail
div For Podcasters1.22:14.5:1
#000000
#1B1B1B
Fail
span Your Podcasts1.39:14.5:1
#000000
#262626
Fail
div Free1.39:14.5:1
#000000
#262626
Fail
div Our Platform1.39:14.5:1
#000000
#262626
Fail
span How Spreaker Works1.39:14.5:1
#000000
#262626
Fail
span Podcasts App1.39:14.5:1
#000000
#262626
Fail
span Spreaker Create1.23:14.5:1
#000000
#1C1C1C
Fail
div New1.06:14.5:1
#000000
#0A0A0A
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.

A+
Alt Text Quality
All 187 images OK
PASS
All 187 images OK
Info::
187 image(s) with good alt text
187 images 187 good alt text
All images have appropriate alt text.
A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 27 passed
PASS
96

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
3m 13s div.flex > div.flex > div.flex > span
45m 18s div.flex > div.flex > div.flex > span
9h 59m 59s div.flex > div.flex > div.flex > span
50m 43s div.flex > div.flex > div.flex > span
9m 35s div.flex > div.flex > div.flex > span
32m 59s div.flex > div.flex > div.flex > span
8m 42s div.flex > div.flex > div.flex > span
24m 10s div.flex > div.flex > div.flex > span
32m 17s div.flex > div.flex > div.flex > span
8m 17s div.flex > div.flex > div.flex > span
9m 50s div.flex > div.flex > div.flex > span
8m 8s div.flex > div.flex > div.flex > span
10h 10s div.flex > div.flex > div.flex > span
36m 9s div.flex > div.flex > div.flex > span
8m 41s div.flex > div.flex > div.flex > span
59m 38s div.flex > div.flex > div.flex > span
21m 48s div.flex > div.flex > div.flex > span
5m 21s div.flex > div.flex > div.flex > span
3m 37s div.flex > div.flex > div.flex > span
8m 18s div.flex > div.flex > div.flex > span
Terms of Service div#onetrust-policy > div#onetrust-policy-text > p > a
Privacy Policy div#onetrust-policy > div#onetrust-policy-text > p > a

These are opportunities to improve the legibility of your content.

○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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
●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.
●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.
●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.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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.
○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