Accessibility

F

Heading Hierarchy

Action

43 headings, 5 skip(s)

FIX

43 headings, 5 skip(s)

Multiple H1 headings (6 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.

Heading level skipped: H3 → H5 (missing H4)

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

Heading level skipped: H1 → H5 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H6 (missing H2)

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

H1 The whole-home sound system
H1 Meet Sonos Play duplicate H1
H1 Hear how sound should sound duplicate H1
H3 Astonishingly clear skipped
H5 4000+ skipped
H3 Expertly tuned
H3 Beautifully balanced
H3 Play your way
H1 Create your perfect sound system duplicate H1
H5 Mix and match speakers skipped
H1 Create your perfect sound system duplicate H1
H4 Mix and match speakers skipped
H3 Bring every room together
H3 Breeze through setup
H3 Stream everything you love
H3 Discover new favourites
H3 Control it all like magic
H1 Start your system duplicate H1
H6 Sets skipped
H6 Speakers
H6 Home Theatre
H6 Portable Speakers
H5 Why buy from Sonos
H4 Help
H4 Help
H4 Offers
H4 Offers
H4 About Sonos
H4 About Sonos
H4 For Businesses
H4 For Businesses
H4 Categories
H4 Categories
H4 Products
H4 Products
H2 Your Privacy Choices
H3 Manage Consent Preferences
H4 Strictly Necessary Cookies
H4 Sale of Personal Data
H5 Functional Cookies
H5 Performance Cookies
H5 Targeting Cookies
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

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

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

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

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

F

Link & Button Quality

Action

10 issue(s) across 95 links and 19 buttons

FIX

10 issue(s) across 95 links and 19 buttons

4 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://www.facebook.com/sonos; https://instagram.com/sonos; https://twitter.com/sonos; https://youtube.com/sonos

3 link(s) with generic text

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

Got: /en/controller-app ("Learn more"); /en/sonos-radio ("Learn more"); /en/controller-app ("Learn more")

3 link(s) open in new tab without warning

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

Got: /en/contact; https://www.sonos.com/legal/privacy; https://www.onetrust.com/products/cookie-consent/

3 button(s) with no accessible text

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

Got: button[data-testid="close-button"]; button (#996 on page); button (#1006 on page)

85 link(s) with descriptive text

95 links

4 empty

3 generic text

3 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
/en/controller-app	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Controller App
/en/sonos-radio	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Sonos Radio
/en/controller-app	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Controller App
/en/contact	Contact us	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/sonos	(empty)	empty	Add link text or aria-label
https://instagram.com/sonos	(empty)	empty	Add link text or aria-label
https://twitter.com/sonos	(empty)	empty	Add link text or aria-label
https://youtube.com/sonos	(empty)	empty	Add link text or aria-label
https://www.sonos.com/legal/privacy	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	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

101 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://www.facebook.com/sonos; https://instagram.com/sonos; https://twitter.com/sonos; https://youtube.com/sonos

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

/en/controller-app ("Learn more"); /en/sonos-radio ("Learn more"); /en/controller-app ("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.

/en/contact; https://www.sonos.com/legal/privacy; https://www.onetrust.com/products/cookie-consent/

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="close-button"]; button (#996 on page); button (#1006 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

D

404 Error Page

Action

HTTP 410, custom page

FIX

HTTP 410, custom page

Unexpected status code: HTTP 410

Expected HTTP 404 but received 410. This may confuse search engine crawlers.

Got: HTTP 410

Custom styled 404 page

Navigation links present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 410 ✗Page Title Sites-Sonos_World-Site ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

D

Favicon & Branding

Action

3 icon(s) detected

FIX

3 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

D

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D

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.

D

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 ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

4 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 4 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

B

Alt Text Quality

2 of 43 images have issues

REVIEW

2 of 43 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

7 decorative image(s) correctly marked

34 image(s) with good alt text

43 images 34 good alt text 7 decorative 2 missing

Issue	Count
missing	2 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

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA

h1 Meet Sonos Play

1.29:1

#000000

on

#1B2126

needs 3.0:1 (large text)

32px · mid-page

title Sonos: Introducing Sonos Play and Era 10…

1.72:1

#000000

on

#1F355A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.72:1

#000000

on

#1F355A

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 The whole-home sound…	5.41:1	3.0:1	#000000	#8C806A	Pass
h1 Meet Sonos Play	1.29:1	3.0:1	#000000	#1B2126	Fail
h1 Hear how sound shoul…	11.24:1	3.0:1	#000000	#C3BDB2	Pass
h1 Create your perfect …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Create your perfect …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Start your system	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Your Privacy Choices	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Astonishingly clear	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Expertly tuned	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Beautifully balanced	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Play your way	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Bring every room tog…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Breeze through setup	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Stream everything yo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Discover new favouri…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Control it all like …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Manage Consent Prefe…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Cookie List	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Sonos: Introducing S…	1.72:1	4.5:1	#000000	#1F355A	Fail
a Skip to main content	1.72:1	4.5:1	#000000	#1F355A	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 — 4 failing, 24 passed

REVIEW

86

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.basis-full > div#q3fy26-earth-day-refurb > div.w-2 > button.flex `div.basis-full > div#q3fy26-earth-day-refurb > div.w-2 > button.flex`
Search `nav#right > ul.inline-flex > li.flex > button.flex`
Menu `nav#right > ul.inline-flex > li.flex > button.flex`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.flex > ul.flex > li > a `div.flex > ul.flex > li > a`
div.flex > ul.flex > li > a `div.flex > ul.flex > li > a`
div.flex > ul.flex > li > a `div.flex > ul.flex > li > a`
div.flex > ul.flex > li > a `div.flex > ul.flex > li > a`

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
Astonishingly clear `section.lg:order-none > section.w-full > div > h3.tw-typography-h3`
4000+ `div > div.border > div.flex > h5.block`
Mix and match speakers `section.order-none > section.w-full > div.mb-4 > h5.block`
Sets `nav.flex > div.flex > a.flex > h6.block`

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
Home `body.has-cookie-banner > header.tw-header-nav-spacing > nav#left > ul.inline-flex`
My Account `body.has-cookie-banner > header.tw-header-nav-spacing > nav#right > ul.inline-flex`

These are opportunities to improve the experience of reading tabular or list data using 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

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

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

●Skip links are focusable.

●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

○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

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

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

A

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

4 <nav> landmark(s) found

4 of 4 <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+

Form Accessibility

All 6 controls labeled

PASS

All 6 controls labeled

6 control(s) properly labeled

6 controls

6 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#ot-group-id-BG102	checkbox	Sale of Personal Data	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