7 pages · open.spotify.com · shared view
The experience works, but accessibility, decision-making and visual hierarchy need attention in key moments.
Advertising is buried behind the consumer experience
The desktop header prioritizes Premium, Support, Download, Install App, Sign up, and Log in. The available Advertising link sits in the footer rather than alongside these prominent routes.
The empty right rail cuts into discovery space
A narrow dark rail with only a chevron remains visible at the right edge while the last cards in each row are visibly clipped.
The contact page opens with an About Us introduction
The page titled “Contact” leads with several general product-description paragraphs under “About Us.” The actionable customer-support routes appear farther down and are presented as a numbered list.
The main support action looks like an ordinary text link
“Contact us” is embedded inline in the third item of a five-item support list and has similar visual treatment to secondary destinations such as the help site, Community, and audiobook refunds.
The office directory leaves a large empty column
The two-column page layout keeps the long worldwide office directory on the right after the left-side support content ends, producing a large blank area across most of the lower page before the footer.
Runtime failures on page load
Runtime failures on page load
Certain ARIA roles must be contained by particular parents
Certain ARIA roles must be contained by particular parents
WCAG 1.3.1
ARIA roles used must conform to valid values
ARIA roles used must conform to valid values
WCAG 4.1.2
Certain ARIA roles must contain particular children
Certain ARIA roles must contain particular children
WCAG 1.3.1
Zooming and scaling must not be disabled
Zooming and scaling must not be disabled
WCAG 1.4.4
The Israel office entry has no location details
In the worldwide directory, “Spotify Israel” is followed only by the generic office@spotify.com email address, unlike neighboring entries that provide street, city, and country details.
Elements must only use supported ARIA attributes
Elements must only use supported ARIA attributes
WCAG 4.1.2
Text is difficult to read
Text is difficult to read
WCAG 1.4.3
Page content has no main landmark
Page content has no main landmark
Heading levels skip a rank
Heading levels skip a rank
“Company”
The email path gives no sense of what comes next
The form asks only for an email address and labels the primary action “Next,” without showing the number of remaining steps or briefly explaining what the next step requests.
“Next”
The reCAPTCHA notice is difficult to read
The reCAPTCHA disclosure and its policy links appear in very small, low-emphasis gray text near the bottom of the dark page.
The repository command is visibly cut off
The long Debian/Ubuntu repository command extends beyond its code box, and the captured state shows neither its full contents nor an obvious copy control or horizontal-scroll cue.
Two repository commands are presented as one step
The Debian repository block visibly contains a key-import command followed by an “echo” repository command, but there is no displayed separator, continuation marker, or instruction to run them individually. The surrounding copy calls it one command.
Elements must only use supported ARIA attributes
Elements must only use supported ARIA attributes
WCAG 4.1.2
Scrollable region must have keyboard access
Scrollable region must have keyboard access
WCAG 2.1.1
Repeated “Discover more” buttons hide their destinations
Several sections use the same generic “Discover more” label even though they lead to different topics, including getting started, ad formats, and campaign goals.
Key performance claims lack quick comparison context
The statistics cards prominently show claims such as “#1 most home-screened app,” “777m+ monthly active users,” and “90% incremental sales.” Superscript references are present, but the visible cards do not consistently state the comparison group, study period, or market.
Runtime failures on page load
Runtime failures on page load
Empty contact fields are hard to read
In the captured focused form state, the “First Name” and “Last Name” placeholder text is a muted gray against dark gray fields. The green focus outline is visible, but the field text itself has weak visual prominence.
Page has no h1
Page has no h1
“The numbers don't lie”
Control without a label
Control without a label
WCAG 4.1.2
A button has no clear name
A button has no clear name
WCAG 4.1.2
An image is missing a description
An image is missing a description
WCAG 1.1.1
A link has no clear destination
A link has no clear destination
WCAG 2.4.4
Text is difficult to read
Text is difficult to read
WCAG 1.4.3
Sign up looks like plain text
In the captured hover state, “Sign up” remains plain white text without an underline, container, color shift, or other visible hover treatment. Its nearby prompt is also subdued, so the account-creation path has weak interactive affordance.
“Sign up”
Legal notice is tiny and faint
The reCAPTCHA disclosure and its policy links appear in very small gray text near the bottom of the dark page, making them substantially less legible than the rest of the form.
“This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.”
The budget amounts have no unit or context
The budget illustration shows “$15,” “$25,” “$50,” and “$100,” but the captured section does not say whether these are daily amounts, campaign totals, minimums, or simply examples.
The delivery-goal step stays too abstract
“Select your delivery goal” says Spotify will find people more likely to take the desired action, but it does not show examples of delivery goals or explain how this choice differs from the campaign objective in step 1.
The free production promise lacks visible scope
The creation section promises “without spending a dime on production” and “free audio ad creation services,” then offers only a “Create an ad” button in the captured section. No visible supporting detail explains what the service includes.
Runtime failures on page load
Runtime failures on page load
Form placeholders are hard to read
In the captured focused form state, the gray “First Name” and “Last Name” placeholder text has very little visual separation from the dark gray input backgrounds.
A link has no clear destination
A link has no clear destination
WCAG 2.4.4
Text is difficult to read
Text is difficult to read
WCAG 1.4.3
A button has no clear name
A button has no clear name
WCAG 4.1.2
Page has no h1
Page has no h1
“Ready to measure your ad’s performance?”