Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 7 REVIEW 3 FIX

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Heading Hierarchy

18 headings, 1 skip(s)

REVIEW

18 headings, 1 skip(s)

Multiple H1 headings (3 found)

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

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

2 hidden heading(s) (aria-hidden)

H1 Your Library
H1 Home duplicate H1
H2 Trending songs hidden
H2 Popular artists hidden
H1 Choose a language duplicate H1
H3 Location skipped
H2 Tailored Advertising Opt-out
H3 Manage Consent Preferences
H4 Enable Tailored Advertising
H5 First Party Targeting Cookies
H5 Targeting Cookies
H5 Store and access information on a device
H4 Other Cookies used on this site
H5 Strictly Necessary Cookies
H5 First Party Functional Cookies
H5 First Party Performance Cookies
H5 Content Selection, Delivery, and Reporting
H3 Cookie List

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

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

Form Accessibility

2 of 12 controls have issues

REVIEW

2 of 12 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

1 control(s) rely on placeholder only

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

Got: <input>

10 control(s) properly labeled

12 controls

10 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
input	range	Resize main navigation	none
input	range	Change progress	none
input	range	Change volume	none
#ot-group-id-BG169	checkbox	Enable Tailored Advertising	for/id
#ot-group-id-BG221	checkbox	Other Cookies used on this site	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
input	input	(Search locations)	placeholder only
#g-recaptcha-response-100000	textarea	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input>

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

Link & Button Quality

Action

4 issue(s) across 291 links and 116 buttons

REVIEW

4 issue(s) across 291 links and 116 buttons

5 link(s) open in new tab without warning

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

Got: https://instagram.com/spotify; https://twitter.com/spotify; https://www.facebook.com/Spotify; https://accounts.spotify.com; https://www.onetrust.com/solutions/consent-and-preferences/?utm_source=cmp&ut…

4 button(s) with no accessible text

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

Got: button[data-testid="unauth-user-widget-link"]; button[data-testid="close-button"]; button (#1985 on page); button (#2035 on page)

286 link(s) with descriptive text

291 links

0 empty

0 generic text

5 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
https://instagram.com/spotify	Instagram	new tab	Add '(opens in new tab)' to text
https://twitter.com/spotify	Twitter	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Spotify	Facebook	new tab	Add '(opens in new tab)' to text
https://accounts.spotify.com	, opens in a new tab	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

398 links and buttons have descriptive text

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

https://instagram.com/spotify; https://twitter.com/spotify; https://www.facebook.com/Spotify; https://accounts.spotify.com; https://www.onetrust.com/solutions/consent-and-preferences/?utm_source=cmp&ut…

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[data-testid="unauth-user-widget-link"]; button[data-testid="close-button"]; button (#1985 on page); button (#2035 on page)

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Favicon & Branding

Action

10 icon(s) detected

REVIEW

10 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'>.

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Spotify

No 192x192 icon

A 192px icon is required for PWA installation.

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name Spotify ✓192×192 icon ✗512×512 icon ✓Start URL https://open.spotify.com/?utm_source=pwa_install ✓Display Mode standalone ✓

Name Spotify Display Mode standalone Theme Color #121212 Background Color #121212 Icons 6 icon(s)

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA

h1 Home

1.53:1

#000000

#34264E

needs 3.0:1 (large text)

32px · bottom of viewport · over background image/gradient

h1 Choose a language

1.00:1

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Tailored Advertising Opt-out

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Location

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Manage Consent Preferences

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Cookie List

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

title Spotify - Web Player: Music for everyone

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

div Skip to main content

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span What do you want to play?

1.30:1

#000000

#212121

needs 4.5:1 (normal text)

16px · top of page (header area)

kbd Ctrl

2.45:1

#000000

#4C4C4C

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

kbd Shift

1.13:1

#000000

#131310

needs 4.5:1 (normal text)

16px · above the fold

span Install App

1.22:1

#000000

#271810

needs 4.5:1 (normal text)

16px · above the fold

button Sign up

1.34:1

#000000

#311F15

needs 4.5:1 (normal text)

16px · above the fold

span Log in

2.05:1

#000000

#573A2C

needs 4.5:1 (normal text)

16px · above the fold

span Create your first playlist

1.96:1

#000000

#3E3E3E

needs 4.5:1 (normal text)

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

span It's easy, we'll help you

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · above the fold

span Create playlist

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · above the fold

span Let's find some podcasts to follow

1.12:1

#000000

#121212

needs 4.5:1 (normal text)

16px · mid-page

span We'll keep you updated on new episodes

2.06:1

#000000

#414141

needs 4.5:1 (normal text)

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

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)

Element	Ratio	Required	FG	BG	Result
h1 Your Library	5.87:1	3.0:1	#000000	#888788	Pass
h1 Home	1.53:1	3.0:1	#000000	#34264E	Fail
h1 Choose a language	1.00:1	3.0:1	#000000	#000000	Fail
h2 Tailored Advertising…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Location	1.00:1	3.0:1	#000000	#000000	Fail
h3 Manage Consent Prefe…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Cookie List	1.00:1	3.0:1	#000000	#000000	Fail
title Spotify - Web Player…	1.00:1	4.5:1	#000000	#000000	Fail
div Skip to main content	1.00:1	4.5:1	#000000	#000000	Fail
span What do you want to …	1.30:1	4.5:1	#000000	#212121	Fail
kbd Ctrl	2.45:1	4.5:1	#000000	#4C4C4C	Fail
kbd Shift	1.13:1	4.5:1	#000000	#131310	Fail
span Install App	1.22:1	4.5:1	#000000	#271810	Fail
button Sign up	1.34:1	4.5:1	#000000	#311F15	Fail
span Log in	2.05:1	4.5:1	#000000	#573A2C	Fail
span Create your first pl…	1.96:1	4.5:1	#000000	#3E3E3E	Fail
span It's easy, we'll hel…	1.12:1	4.5:1	#000000	#121212	Fail
span Create playlist	1.12:1	4.5:1	#000000	#121212	Fail
span Let's find some podc…	1.12:1	4.5:1	#000000	#121212	Fail
span We'll keep you updat…	2.06:1	4.5:1	#000000	#414141	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

7 landmarks

PASS

7 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

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

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

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+

Alt Text Quality

All 32 images OK

PASS

All 32 images OK

30 decorative image(s) correctly marked

2 image(s) with good alt text

32 images 2 good alt text 30 decorative

All images have appropriate alt text.

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 21 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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Company About Jobs For the Record `div.sc-lcIPJg > div.sc-kdBSHD > div.sc-fHjqPf > ul.e-10310-type-list`
Communities For Artists Developers Advertising Investors Vendors `div.sc-lcIPJg > div.sc-kdBSHD > div.sc-fHjqPf > ul.e-10310-type-list`
Useful links Support Free Mobile App Popular by Country Import your music `div.sc-lcIPJg > div.sc-kdBSHD > div.sc-fHjqPf > ul.e-10310-type-list`
Spotify Plans Premium Individual Premium Duo Premium Family Premium Student Sp… `div.sc-lcIPJg > div.sc-kdBSHD > div.sc-fHjqPf > ul.e-10310-type-list`

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.

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.mobile-web-player `html.mobile-web-player`

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

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

●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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

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

○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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

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

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