Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 4 REVIEW 3 FIX

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) landmark

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

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

Favicon & Branding

8 icon(s) detected

REVIEW

8 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 12 fail WCAG AA

REVIEW

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

8 pass 12 fail WCAG AA

h1 Content Restricted

2.16:1

#000000

#444444

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Who was baby "Jess" and why was she left…

2.94:1

#000000

#525864

needs 3.0:1 (large text)

24px · mid-page · over background image/gradient

h2 Africa, Middle East, and India

2.16:1

#000000

#444444

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Asia Pacific

2.16:1

#000000

#444444

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Europe

2.16:1

#000000

#444444

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Latin America and the Caribbean

2.16:1

#000000

#444444

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The United States and Canada

2.16:1

#000000

#444444

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Africa, Middle East, and India

2.16:1

#000000

#444444

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Asia Pacific

2.16:1

#000000

#444444

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Europe

2.16:1

#000000

#444444

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Latin America and the Caribbean

2.16:1

#000000

#444444

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The United States and Canada

2.16:1

#000000

#444444

needs 3.0:1 (large text)

24px · bottom of viewport

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)

Element	Ratio	Required	FG	BG	Result
h1 New	16.95:1	3.0:1	#000000	#EDE6DC	Pass
h1 Content Restricted	2.16:1	3.0:1	#000000	#444444	Fail
h2 A young Marine's wif…	7.26:1	3.0:1	#000000	#A39685	Pass
h2 Amanda Hirsch sits d…	20.19:1	3.0:1	#000000	#F9FBF9	Pass
h2 Who was baby "Jess" …	2.94:1	3.0:1	#000000	#525864	Fail
h2 Deeply reported spor…	10.13:1	3.0:1	#000000	#B4B4B4	Pass
h2 Africa, Middle East,…	2.16:1	3.0:1	#000000	#444444	Fail
h2 Asia Pacific	2.16:1	3.0:1	#000000	#444444	Fail
h2 Europe	2.16:1	3.0:1	#000000	#444444	Fail
h2 Latin America and th…	2.16:1	3.0:1	#000000	#444444	Fail
h2 The United States an…	2.16:1	3.0:1	#000000	#444444	Fail
h2 Africa, Middle East,…	2.16:1	3.0:1	#000000	#444444	Fail
h2 Asia Pacific	2.16:1	3.0:1	#000000	#444444	Fail
h2 Europe	2.16:1	3.0:1	#000000	#444444	Fail
h2 Latin America and th…	2.16:1	3.0:1	#000000	#444444	Fail
h2 The United States an…	2.16:1	3.0:1	#000000	#444444	Fail
title Apple Podcasts - Web…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label Search	20.65:1	4.5:1	#000000	#FDFDFD	Pass
span Home	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span New	21.00:1	4.5: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.

Heading Hierarchy

42 headings

PASS

42 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 New
H2 A young Marine's wife becomes a suspect in his untimely death.
H2 Amanda Hirsch sits down for juicy chats with the stars.
H2 Who was baby "Jess" and why was she left on a country lane?
H2 Deeply reported sports rabbit holes from Pablo Torre.
H2 Top Shows
H2 New Shows
H2 Top Series
H2 Top Episodes
H3 Inside the Five Days That Remade the Supreme Court
H3 MURDERED: Stephanie Casberg
H3 How Iranians See the War
H3 NFL Draft With Todd McShay, NBA And NHL Playoffs And We Eliminate Some Teams, Plus Dexter Lawrence Trade And Who's Back Of The Week
H3 A Magic Upset, a Lakers Surprise, Playoff Wemby, El Cheapo, Bill’s Award Flip, and Other Round 1 Notes With Zach Lowe
H3 Iran Ceasefire Deadline, Labor Secretary Out, Hearing For New Fed Chair
H3 Infidelity
H3 "Aubrey Plaza"
H3 MAGA Media Turns on Trump (feat. David Pakman)
H3 Trump and Iran Talks, Iran Reacts to Ship Seized, Tariff Refunds
H2 The Moment
H2 Earth Day
H2 Worth the Watch
H2 New Seasons
H2 Top Society & Culture Shows
H2 Top Comedy Shows
H2 Top True Crime Shows
H2 Explore Video
H2 New Trailers
H2 Global Hits
H2 Essentials
H2 More to Discover
H2 Africa, Middle East, and India
H2 Asia Pacific
H2 Europe
H2 Latin America and the Caribbean
H2 The United States and Canada
H1 Content Restricted duplicate H1
H2 Africa, Middle East, and India
H2 Asia Pacific
H2 Europe
H2 Latin America and the Caribbean
H2 The United States and Canada

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

A+

Alt Text Quality

All 128 images OK

PASS

All 128 images OK

1 image(s) with alt text over 125 characters

42 decorative image(s) correctly marked

85 image(s) with good alt text

128 images 85 good alt text 42 decorative

Issue	Count
too long	1 image(s)

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search-input__text-field	search	Search	for/id

A+

Link & Button Quality

523 links, 189 buttons — all OK

PASS

523 links, 189 buttons — all OK

523 link(s) with descriptive text

523 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

712 links and buttons have descriptive text

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Apple Podcasts

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Apple Podcasts ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Apple Podcasts Display Mode standalone Background Color #ffffff Icons 4 icon(s)

A+

Lighthouse Accessibility Audits

Score 95/100 — 1 failing, 25 passed

PASS

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mini-player__container > div.mini-player > div.mini-player__body > button.mini-player__metadata `div.mini-player__container > div.mini-player > div.mini-player__body > button.mini-player__metadata`

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.

○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]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Elements with the `role=text` attribute do not have focusable descendents.

●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.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`[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

○`[role]`s are contained by their required parent element

○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

○Background and foreground colors have a sufficient contrast ratio

○`<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.

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○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.