Skip to content
https://libsyn.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
D
Heading Hierarchy
Action
47 headings, 3 skip(s)
FIX
47 headings, 3 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: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
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.
  • H1 The Podcast Hosting Platform for Ambitious Creators
  • H3 All the tools you need to reach loyal fans and monetize your podcast. skipped
  • H3 Podcast hosting that sets creators free.
  • H2 Podcast Monetization
  • H2 Social Promotion
  • H2 Audience Insights
  • H2 Intuitive Podcast Publishing
  • H2 Expand Beyond Audio with Video Podcast Hosting
  • H3 Reach every major podcast platform
  • H5 Distribution Everywhere skipped
  • H5 (empty)
  • H5 Custom, Brand-Ready Player
  • H5 (empty)
  • H5 Full Content Ownership and Control
  • H5 (empty)
  • H3 Stackable Podcast Monetization for All
  • H2 Advertising and Earnings Activated
  • H2 Creator Promotion with Podroll
  • H2 Exclusive Content and Subscriptions
  • H3 Podcast hosting features for growth-focused creators
  • H2 YouTube Podcast Publishing Made Easy
  • H2 Multi-User Management for Podcast Teams
  • H2 Built-In Branding Tools for a Standout Podcast
  • H2 Powerful Podcast Analytics You Can Trust
  • H3 Education, Events, and Webinars
  • H2 Live Q&As to Help You Launch, Grow, and Monetize
  • H2 How to Publish an Audio or Video Podcast to YouTube
  • H2 Podcast Advertising FAQ: 10 Common Questions Answered
  • H3 Four steps to launch
  • H3 Sign up in minutes
  • H3 Upload your first episode
  • H3 Distribute to every platform
  • H3 Track your growth with analytics
  • H5 Start risk-free. skipped
  • H5 Your first 30 days are free.
  • H2 Company
  • H2 Community
  • H2 Support
  • H2 Follow Us
  • H2 Do Not Sell My Personal Information
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies
  • H4 Sale of Personal Data
  • H5 Performance Cookies
  • H5 Targeting Cookies
  • H4 Internal Cookies
  • 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

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
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::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <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.
B
Alt Text Quality
2 of 59 images have issues
REVIEW
2 of 59 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
14 decorative image(s) correctly marked
Info::
43 image(s) with good alt text
59 images 43 good alt text 14 decorative 2 missing
IssueCount
missing2 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

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 Page not found - Libsyn ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A
Landmark Structure
13 landmarks
PASS
13 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
2 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Menu" MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A+
Form Accessibility
All 7 controls labeled
PASS
All 7 controls labeled
Info::
7 control(s) properly labeled
7 controls
7 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ot-group-id-SPD_BGcheckboxSale of Personal Datafor/id
#ot-group-id-C6checkboxInternal 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
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
h1 The Podcast Hosting …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Advertising and Earn…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Creator Promotion wi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Exclusive Content an…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Live Q&As to Help Yo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 How to Publish an Au…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Podcast Advertising …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Company21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Community21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Support21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Follow Us21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Do Not Sell My Perso…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 All the tools you ne…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Podcast hosting that…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Reach every major po…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Stackable Podcast Mo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Podcast hosting feat…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Education, Events, a…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Four steps to launch21.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 92/100 — 3 failing, 28 passed
PASS
92

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
Start a new podcast today with a free month of podcast hosting. No promo code n… div.elementor-element > div.elementor-element > div.elementor-widget-container > p
Youtube Publishing div.e-n-tabs > div.e-n-tabs-heading > button#e-n-tab-title-19138471 > span.e-n-tab-title-text
Go beyond audio. Publish to YouTube in one click. Convert episodes to video, ma… div.elementor-widget-container > div > p > span
Create an account to get started. div.e-con-inner > div.elementor-element > div.elementor-widget-container > p

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
All the tools you need to reach loyal fans and monetize your podcast. div.elementor-element > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title
Distribution Everywhere div.elementor-element > div.elementor-element > div.elementor-widget-container > h5.p1

These are opportunities to improve keyboard navigation in your application.

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
About div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
Investor Relations div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
Careers div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
Contact div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
Our Blog div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
Testimonials div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
System Status div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
Libsyn Support div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
Legal div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
Privacy Policy div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
Help Center div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
Facebook div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
Instagram div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
X.com div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
LinkedIn div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
YouTube div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a

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
●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
●`[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.
●`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
●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 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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○`<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.
○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>`.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback