Skip to content
https://stitcher.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
4
REVIEW
8
PASS
1
INFO
0
Checks
13
1 PASS 8 REVIEW 4 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-6qie8f
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://www.stitcher.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://www.stitcher.com/manifest.json

Manifest contains invalid JSON.

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 ✗
D
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) 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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV SEARCH 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

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

C
Heading Hierarchy
Action
8 headings, 1 skip(s)
REVIEW
8 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Want a podcast-only subscription?
  • H2 Your Podcasts+ subscription opens the door to every genre you love.
  • H2 Get Podcasts+
  • H2 You've got questions?
  • H6 How do I manage my account or cancel my SiriusXM Podcasts+ subscription? skipped
  • H6 I am currently a SiriusXM subscriber. Do I get access to SiriusXM Podcasts+?
  • H6 Will I get access to SiriusXM radio content with this subscription?
  • H6 What if I have more questions about SiriusXM Podcasts+?

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

C
Alt Text Quality
Action
2 of 71 images have issues
REVIEW
2 of 71 images have issues
Critical::
2 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::
2 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
65 image(s) with good alt text
71 images 65 good alt text 2 decorative 2 missing
IssueCount
missing2 image(s)
too long2 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
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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.

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
title Podcasts+ | SiriusXM
2.35:1
#000000
on
#0E0DF1
needs 4.5:1 (normal text)
16px · top of page (header area)
span Help & Support
2.32:1
#000000
on
#0C0AF0
needs 4.5:1 (normal text)
16px · top of page (header area)
span Help Center
2.56:1
#000000
on
#2121F2
needs 4.5:1 (normal text)
16px · top of page (header area)
a Transfer my subscription
2.33:1
#000000
on
#0C0CF0
needs 4.5:1 (normal text)
16px · top of page (header area)
a Request radio signal
2.27:1
#000000
on
#0506EE
needs 4.5:1 (normal text)
16px · above the fold
a Do Not Call Policy
2.62:1
#000000
on
#2322F5
needs 4.5:1 (normal text)
16px · above the fold
a Manage or cancel my subscription
2.37:1
#000000
on
#0C0DF3
needs 4.5:1 (normal text)
16px · above the fold
a Add new vehicle
2.38:1
#000000
on
#0B0BF5
needs 4.5:1 (normal text)
16px · above the fold
div Start Listening
2.69:1
#000000
on
#2526F6
needs 4.5:1 (normal text)
16px · above the fold
p Search
2.38:1
#000000
on
#110EF3
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Close
2.30:1
#000000
on
#0708F0
needs 4.5:1 (normal text)
16px · above the fold
p Suggestions
2.64:1
#000000
on
#2524F4
needs 4.5:1 (normal text)
16px · above the fold
span MLB
2.38:1
#000000
on
#0E0EF3
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Country Music
2.23:1
#000000
on
#0101ED
needs 4.5:1 (normal text)
16px · mid-page
span College Basketball
2.63:1
#000000
on
#2424F4
needs 4.5:1 (normal text)
16px · mid-page
span Luke Combs
2.38:1
#000000
on
#0E0FF3
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
span Lineup Changes
2.24:1
#000000
on
#0101EE
needs 4.5:1 (normal text)
16px · mid-page
span My Account
2.67:1
#000000
on
#2525F6
needs 4.5:1 (normal text)
16px · mid-page
span Blog
2.39:1
#000000
on
#1111F2
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
span New, hot, and trending!
2.27:1
#000000
on
#0707EE
needs 4.5:1 (normal text)
16px · mid-page

4 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
title Podcasts+ | SiriusXM2.35:14.5:1
#000000
#0E0DF1
Fail
span Help & Support2.32:14.5:1
#000000
#0C0AF0
Fail
span Help Center2.56:14.5:1
#000000
#2121F2
Fail
a Transfer my subscrip…2.33:14.5:1
#000000
#0C0CF0
Fail
a Request radio signal2.27:14.5:1
#000000
#0506EE
Fail
a Do Not Call Policy2.62:14.5:1
#000000
#2322F5
Fail
a Manage or cancel my …2.37:14.5:1
#000000
#0C0DF3
Fail
a Add new vehicle2.38:14.5:1
#000000
#0B0BF5
Fail
div Start Listening2.69:14.5:1
#000000
#2526F6
Fail
p Search2.38:14.5:1
#000000
#110EF3
Fail
span Close2.30:14.5:1
#000000
#0708F0
Fail
p Suggestions2.64:14.5:1
#000000
#2524F4
Fail
span MLB2.38:14.5:1
#000000
#0E0EF3
Fail
span Country Music2.23:14.5:1
#000000
#0101ED
Fail
span College Basketball2.63:14.5:1
#000000
#2424F4
Fail
span Luke Combs2.38:14.5:1
#000000
#0E0FF3
Fail
span Lineup Changes2.24:14.5:1
#000000
#0101EE
Fail
span My Account2.67:14.5:1
#000000
#2525F6
Fail
span Blog2.39:14.5:1
#000000
#1111F2
Fail
span New, hot, and trendi…2.27:14.5:1
#000000
#0707EE
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 86/100 — 5 failing, 25 passed
REVIEW
86

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.drawer_drawer__eEVQM > div.drawer_drawer__eEVQM > div.drawer_innerDrawerHeader__pReqh > button.drawer_chevronIcon__4tavc div.drawer_drawer__eEVQM > div.drawer_drawer__eEVQM > div.drawer_innerDrawerHeader__pReqh > button.drawer_chevronIcon__4tavc

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.contentcard_mediaContainer__eGjZF > div.contentcard_imageContainer__mkPe6 > picture > img div.contentcard_mediaContainer__eGjZF > div.contentcard_imageContainer__mkPe6 > picture > img

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.

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
How do I manage my account or cancel my SiriusXM Podcasts+ subscription? details > summary.accordion_accordionButton__QneYP > div.accordion_buttonLeft__VOim1 > h6.accordion_accordionHeadline__NF_Ek

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Discover Channel Guide Subscriptions body.w2 > div.drawer_drawer__eEVQM > ul.drawer_navList__Do2HQ

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Help & Support body.w2 > div.drawer_drawer__eEVQM > button.drawer_mobileSupportButton__abhUl
Privacy Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●`[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
●Background and foreground colors have a sufficient contrast ratio
●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
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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 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.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="_R_5nacslubvb_">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#_R_5nacslubvb_text(What are you looking for?)placeholder only

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

<input type="text" id="_R_5nacslubvb_">

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback