Skip to content
https://podbean.com

Accessibility

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

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

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.
B
Form Accessibility
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="v">; <input type="text" name="v">; <input type="text" name="UserPreSignupEmail[email]" id="userpresignupemail-email">
3 controls
0 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
vtext(Search)placeholder only
vtext(Search)placeholder only
#userpresignupemail-emailtext(Enter your email address)placeholder only

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

<input type="text" name="v">; <input type="text" name="v">; <input type="text" name="UserPreSignupEmail[email]" id="userpresignupemail-email">

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
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 ✓Page Title Error 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
11 icon(s) detected
REVIEW
11 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
Heading Hierarchy
42 headings, 1 skip(s)
PASS
42 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Your Podcast Hosting and Monetizing Platform
  • H2 From podcast newbie to professional podcaster
  • H2 Create and publish your podcast like a pro
  • H2 Grow your podcast, be heard everywhere
  • H2 Turn your passion into a new income stream
  • H2 Empower your podcast with Podbean AI
  • H2 Unlock a beautiful, professional, and customizable podcast website
  • H2 Comprehensive podcast analytics
  • H2 Podbean App simplifying your podcasting
  • H3 Record from Anywhere
  • H3 Edit Like Magic
  • H3 Make It Uniquely Yours
  • H3 Publish & Manage with Ease
  • H2 Download it now.
  • H2 Live stream simplified, engage your audience
  • H2 Secure, Scalable Podcast Hosting Solution
  • H2 We’re helping podcasters of all genres and sizes
  • H3 135410+
  • H3 15946219+
  • H3 15490226524+
  • H2 Featured Podcasts
  • H2 Get the help you need, right when you need it.
  • H3 Blog
  • H3 Tutorials
  • H3 Webinars
  • H3 Help Center
  • H2 Frequently asked questions
  • H2 How to start a podcast.
  • H2 Is starting a podcast easy?
  • H2 Can I really start a podcast for free?
  • H2 How do I get my podcast on Apple Podcasts?
  • H2 How do I get my podcast on Spotify?
  • H2 What statistics come with Podbean podcast hosting?
  • H2 How do I switch to Podbean from another podcast hosting site?
  • H2 What are some good methods to promote a podcast?
  • H2 How do I monetize my podcast?
  • H2 Start a podcast today. It’s FREE.
  • H6 Podcast Services skipped
  • H6 MONETIZATION & MORE
  • H6 KNOWLEDGE BASE
  • H6 Support
  • H6 Podbean

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

A
Alt Text Quality
1 of 99 images have issues
PASS
1 of 99 images have issues
Warning::
1 image(s) with filename as alt text
Info::
1 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
95 image(s) with good alt text
99 images 95 good alt text 2 decorative 1 generic
IssueCount
filename1 image(s)
too long1 image(s)
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 From podcast newbie …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Create and publish y…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Grow your podcast, b…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Turn your passion in…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Empower your podcast…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Unlock a beautiful, …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 and customizable pod…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Comprehensive podcas…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Podbean App simplify…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Download it now.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Live stream simplifi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Secure, Scalable21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We’re helping podc…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Featured Podcasts21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get the help you nee…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Frequently asked que…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Start a podcast toda…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Record from Anywhere21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Edit Like Magic21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Make It Uniquely You…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 91/100 — 4 failing, 28 passed
PASS
91

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Podbean App Simplifying Your Podcasting div.carousel-inner > div.slick-list > div.slick-track > picture.slick-slide
The Tudor Chest Podcast History div.podcasts > div.slick-list > div.slick-track > div#slick-slide30

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.

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
Copyright © 2015-2026 Podbean.com div.footer-share > div.copyright > ul.list-inline > li.list-inline-item

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
PODCAST SERVICES ul.nav > li.list > div.sitemap-list > h6.h6css

These are opportunities to improve keyboard navigation in your application.

Best practices

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.wf-inter-n4-active html.wf-inter-n4-active

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
●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.
●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
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○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
○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