Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 2 REVIEW 6 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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-wutyq3

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.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://anchor.fm/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://anchor.fm/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #000000

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

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.

Link & Button Quality

Action

12 issue(s) across 39 links and 30 buttons

REVIEW

12 issue(s) across 39 links and 30 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://creators.spotify.com/features/video ("Learn more")

21 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://instagram.com/spotifyforcreators; https://facebook.com/spotifyforcreators; https://x.com/spotifycreator; https://www.spotify.com/us/about-us/contact; https://newsroom.spotify.com; https://www.lifeatspotify.com/jobs; https://support.spotify.com/us/creators/contact-spotify-anonymous/; https://www.spotify.com/legal; https://spotify.com/privacy; https://www.spotify.com/legal/privacy-policy (+11 more)

11 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.e-10310-legacy-button (#114 on page); button (#331 on page); button (#341 on page); button (#355 on page); button (#369 on page); button (#383 on page); button (#397 on page); button (#411 on page); button (#425 on page); button (#439 on page) (+1 more)

17 link(s) with descriptive text

39 links

0 empty

1 generic text

21 new tab

11 empty buttons

Element	Text	Issue	Suggested Fix
https://creators.spotify.com/features/vi…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Video
https://instagram.com/spotifyforcreators	Instagram	new tab	Add '(opens in new tab)' to text
https://facebook.com/spotifyforcreators	Facebook	new tab	Add '(opens in new tab)' to text
https://x.com/spotifycreator	X	new tab	Add '(opens in new tab)' to text
https://www.spotify.com/us/about-us/cont…	About	new tab	Add '(opens in new tab)' to text
https://newsroom.spotify.com	Press & Media	new tab	Add '(opens in new tab)' to text
https://www.lifeatspotify.com/jobs	Careers	new tab	Add '(opens in new tab)' to text
https://support.spotify.com/us/creators/…	Contact Us	new tab	Add '(opens in new tab)' to text
https://www.spotify.com/legal	Legal	new tab	Add '(opens in new tab)' to text
https://spotify.com/privacy	Privacy Center	new tab	Add '(opens in new tab)' to text
https://www.spotify.com/legal/privacy-po…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.spotify.com/legal/cookies-po…	Cookies	new tab	Add '(opens in new tab)' to text
http://creators.spotify.com/help	Help Center	new tab	Add '(opens in new tab)' to text
https://megaphone.spotify.com/	Megaphone	new tab	Add '(opens in new tab)' to text
https://artists.spotify.com/home	Spotify for Artists	new tab	Add '(opens in new tab)' to text
https://authors.spotify.com/	Spotify for Authors	new tab	Add '(opens in new tab)' to text
https://x.com/spotifycreator	Twitter link	new tab	Add '(opens in new tab)' to text
https://instagram.com/spotifyforcreators	Instagram link	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/en/app/spotify-fo…	Apple Store badge	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Google Play badge	new tab	Add '(opens in new tab)' to text
https://www.spotify.com/legal/cookies-po…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/solutions/conse…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

36 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://creators.spotify.com/features/video ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://instagram.com/spotifyforcreators; https://facebook.com/spotifyforcreators; https://x.com/spotifycreator; https://www.spotify.com/us/about-us/contact; https://newsroom.spotify.com; https://www.lifeatspotify.com/jobs; https://support.spotify.com/us/creators/contact-spotify-anonymous/; https://www.spotify.com/legal; https://spotify.com/privacy; https://www.spotify.com/legal/privacy-policy (+11 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.e-10310-legacy-button (#114 on page); button (#331 on page); button (#341 on page); button (#355 on page); button (#369 on page); button (#383 on page); button (#397 on page); button (#411 on page); button (#425 on page); button (#439 on page) (+1 more)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Color Contrast (Screenshot)

Action

20 text elements analyzed, 14 fail WCAG AA

REVIEW

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

6 pass 14 fail WCAG AA 2 pass AA only

h1 All the tools to grow your show

1.67:1

#000000

#4D2B18

needs 3.0:1 (large text)

32px · above the fold · over background image/gradient

title Tools to manage and grow your podcast - …

1.23:1

#000000

#2B1617

needs 4.5:1 (normal text)

16px · top of page (header area)

div Features

1.28:1

#000000

#321813

needs 4.5:1 (normal text)

16px · top of page (header area)

span Resources

1.32:1

#000000

#361A15

needs 4.5:1 (normal text)

16px · top of page (header area)

span Video

1.38:1

#000000

#3B1D19

needs 4.5:1 (normal text)

16px · top of page (header area)

span Help

1.44:1

#000000

#412012

needs 4.5:1 (normal text)

16px · above the fold

a Log in

1.43:1

#000000

#402010

needs 4.5:1 (normal text)

16px · above the fold

span Sign up

1.68:1

#000000

#582413

needs 4.5:1 (normal text)

16px · above the fold

span Make your show the next big thing

1.57:1

#000000

#4F2217

needs 4.5:1 (normal text)

16px · above the fold

span Powerful tools from Spotify to manage an…

1.76:1

#000000

#59291C

needs 4.5:1 (normal text)

16px · above the fold

span Build a dedicated following

1.22:1

#000000

#271713

needs 4.5:1 (normal text)

16px · mid-page

span Tap into millions of fans on Spotify who…

1.08:1

#000000

#130B0A

needs 4.5:1 (normal text)

16px · mid-page

span More about growth on Spotify

1.08:1

#000000

#150A0A

needs 4.5:1 (normal text)

16px · mid-page

span Earn on your show

1.06:1

#000000

#150507

needs 4.5:1 (normal text)

16px · mid-page

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 All the tools to gro…	1.67:1	3.0:1	#000000	#4D2B18	Fail
h2 Privacy Preference C…	18.10:1	3.0:1	#000000	#EEEEEE	Pass
h3 Manage Consent Prefe…	18.10:1	3.0:1	#000000	#EEEEEE	Pass
h3 Cookie List	18.10:1	3.0:1	#000000	#EEEEEE	Pass
title Tools to manage and …	1.23:1	4.5:1	#000000	#2B1617	Fail
div Features	1.28:1	4.5:1	#000000	#321813	Fail
span Resources	1.32:1	4.5:1	#000000	#361A15	Fail
span Video	1.38:1	4.5:1	#000000	#3B1D19	Fail
span Podcast	8.46:1	4.5:1	#000000	#C49D7B	Pass
span Switch	4.81:1	4.5:1	#000000	#98714F	Pass
span Help	1.44:1	4.5:1	#000000	#412012	Fail
a Log in	1.43:1	4.5:1	#000000	#402010	Fail
span Sign up	1.68:1	4.5:1	#000000	#582413	Fail
span Make your show the n…	1.57:1	4.5:1	#000000	#4F2217	Fail
span Powerful tools from …	1.76:1	4.5:1	#000000	#59291C	Fail
span Get started	5.09:1	4.5:1	#000000	#997659	Pass
span Build a dedicated fo…	1.22:1	4.5:1	#000000	#271713	Fail
span Tap into millions of…	1.08:1	4.5:1	#000000	#130B0A	Fail
span More about growth on…	1.08:1	4.5:1	#000000	#150A0A	Fail
span Earn on your show	1.06:1	4.5:1	#000000	#150507	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.

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

A+

Heading Hierarchy

14 headings

PASS

14 headings

Single H1 present

H1 All the tools to grow your show
H2 Privacy Preference Center
H3 Manage Consent Preferences
H4 Strictly Necessary Cookies
H4 First Party Functional Cookies
H4 First Party Performance Cookies
H4 First Party Targeting Cookies
H4 Store and access information on a device
H4 Content Selection, Delivery, and Reporting
H4 Performance Cookies
H4 Targeting Cookies
H4 Match and combine data from other sources
H4 Creation and Use of Universal Identifiers
H3 Cookie List

A+

Alt Text Quality

All 10 images OK

PASS

All 10 images OK

10 image(s) with good alt text

10 images 10 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 14 controls labeled

PASS

All 14 controls labeled

14 control(s) properly labeled

14 controls

14 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#ot-group-id-f00	checkbox	First Party Functional Cookies	for/id
#ot-group-id-m00	checkbox	First Party Performance Cookies	for/id
#ot-group-id-t00	checkbox	First Party Targeting Cookies	for/id
#ot-group-id-i00	checkbox	Store and access information on a device	for/id
#ot-group-id-f11	checkbox	Content Selection, Delivery, and Reporting	for/id
#ot-group-id-m02	checkbox	Performance Cookies	for/id
#ot-group-id-t02	checkbox	Targeting Cookies	for/id
#ot-group-id-m03	checkbox	Match and combine data from other sources	for/id
#ot-group-id-ID01	checkbox	Creation and Use of Universal Identifiers	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id

A+

Lighthouse Accessibility Audits

Score 95/100 — 1 failing, 27 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.sc-6019c79e-5 > header.sc-fAomSb > div.sc-hUAZgl > button.e-10310-legacy-button `div.sc-6019c79e-5 > header.sc-fAomSb > div.sc-hUAZgl > button.e-10310-legacy-button`

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

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

●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

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

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

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

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