Skip to content
https://bose.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
D
Alt Text Quality
Action
4 of 24 images have issues
FIX
4 of 24 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
4 image(s) with alt text over 125 characters
Info::
6 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
24 images 10 good alt text 6 decorative 4 missing
IssueCount
missing4 image(s)
too long4 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

D
Form Accessibility
Action
10 of 24 controls have issues
FIX
10 of 24 controls have issues
Critical::
9 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <input>
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="notify-me-form-email" id="notify-me-form-email">
Info::
14 control(s) properly labeled
24 controls
14 labeled
1 placeholder only
9 unlabeled
ControlTypeLabelMethod
qtextEnter Keyword or Item No.aria-label
qtextEnter Keyword or Item No.aria-label
#sandstoneslflxii-speakerwireless-ptlpk-ww-b4d398d33cfb6d547ed4ee2e33radioSelect Sandstone coloraria-label
#sunsetpeachslflxii-speakerwireless-ptlpk-ww-b4d398d33cfb6d547ed4ee2e33radioSelect Sunset Peach coloraria-label
#blueduskslflxii-speakerwireless-ptlpk-ww-b4d398d33cfb6d547ed4ee2e33radioSelect Blue Dusk coloraria-label
#warmwoodslhm-speakerwireless-a1e5277cba9052dcae5542c1earadioSelect Warm Wood coloraria-label
#lightsilverslhm-speakerwireless-a1e5277cba9052dcae5542c1earadioSelect Light Silver coloraria-label
#coolgrayslhm-speakerwireless-a1e5277cba9052dcae5542c1earadioSelect Cool Gray coloraria-label
#blackult-headphoneopn-mlgry-ww-731a7fc89c5f278e0e555f6f1cradioSelect Black coloraria-label
#whitesmokeult-headphoneopn-mlgry-ww-731a7fc89c5f278e0e555f6f1cradioSelect White Smoke coloraria-label
#midnightvioletult-headphoneopn-mlgry-ww-731a7fc89c5f278e0e555f6f1cradioSelect Midnight Violet coloraria-label
#newsletterEmailemailEmailaria-label
#footerEmailModalInputemailEmailaria-label
#optinNotifyMecheckboxSign up to get Bose emails & communications for exclusive first looks at promotions, new products, and more. Private Policyfor/id
#notify-me-form-emailemail(* Email)placeholder only
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
inputinput(none)none

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

<select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <input>

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 type="email" name="notify-me-form-email" id="notify-me-form-email">

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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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
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
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Search form present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Sites-Bose_US-Site | Bose Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 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
A
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
2 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation" MAIN ASIDE "Email sign-up prompt" 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

A
Heading Hierarchy
29 headings, 1 skip(s)
PASS
29 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Shop Sunset Peach
  • H2 Sound up on sunset
  • H3 Music deserves Bose
  • H2 Music deserves Bose
  • H2 Trade in and trade up
  • H3 Mother’s Day Gift Guide
  • H2 Mother’s Day Gift Guide
  • H3 Shop Sunset Peach
  • H1 My Bose Day deals are on
  • H2 Trending products
  • H2 Sound that says it all
  • H2 Sound, meet style
  • H2 Shades of sound
  • H2 Sound never settles
  • H2 Bose Automotive
  • H2 Why buy from Bose
  • H2 90-day return policy
  • H2 Price match promise
  • H2 Complimentary shipping & returns
  • H2 My Bose perks
  • H2 Sound is Power
  • H2 Being first has its perks
  • H2 Customer Care Customer Care
  • H2 Our company Our company
  • H2 Offers Offers
  • H2 Additional Links Additional Links
  • H2 Get 10% off your first purchase*
  • H2 Next step: Join My Bose to unlock your 10% discount!
  • H5 Notify me when available skipped

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

A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 My Bose Day deals ar…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Sound up on sunset21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Music deserves Bose21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trade in and trade u…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Mother’s Day Gift …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trending products21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Sound that says it a…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Sound, meet style21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Shades of sound21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Sound never settles21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Bose Automotive21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why buy from Bose21.00:13.0:1
#000000
#FFFFFF
Pass
h2 90-day return policy21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Price match promise21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Complimentary shippi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 My Bose perks21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Sound is Power21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Being first has its …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get 10% off your fir…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Next step: Join My B…21.00:13.0:1
#000000
#FFFFFF
Pass

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.

A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 26 passed
PASS
100

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.

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
Form elements have associated labels
`[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
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
ARIA IDs are unique
`[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
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.
Image elements have `[alt]` attributes
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
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.

Send Feedback