Skip to content
https://sandisk.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
49
GRADE
F
FIX
6
REVIEW
6
PASS
1
INFO
0
Checks
13
1 PASS 6 REVIEW 6 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://sandisk.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://sandisk.com/manifest.json

Manifest contains invalid JSON.

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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <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.
C
Landmark Structure
Action
4 landmarks
REVIEW
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Warning::
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
BANNER header NAV MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

B
Heading Hierarchy
17 headings, 1 skip(s)
REVIEW
17 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 SSD Recommender Tool for Computer Upgrades
  • H4 SANDISK CFexpress™ Type B Card: FIFA World Cup 2026™ Edition - 256GB skipped
  • H4 Sandisk DJ Flash Drive, 512GB
  • H4 Automotive UFS
  • H4 SanDisk ImageMate® PRO USB-C™
  • H3 Sign In
  • H3 Sign In for Business
  • H3 Reset Password
  • H1 Elite Performance for Every Match
  • H2 More Space for Your Stunts Videos
  • H2 Meet Memory Man
  • H2 Earth Day is April 22
  • H2 More Space for Your Stunts Videos
  • H2 Meet Memory Man
  • H2 Earth Day is April 22
  • H2 More Space for Your Stunts Videos
  • H1 Future‑Ready PCIe Gen5 Speed duplicate H1

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

B
Alt Text Quality
2 of 20 images have issues
REVIEW
2 of 20 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
13 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
20 images 5 good alt text 13 decorative 2 missing
IssueCount
missing2 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
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found | Sandisk ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA
h1 Elite Performance for Every Match
1.12:1
#000000
on
#06150B
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Future‑Ready PCIe Gen5 Speed
1.12:1
#000000
on
#06150B
needs 3.0:1 (large text)
32px · bottom of viewport
h2 SSD Recommender Tool for Computer Upgrad…
1.12:1
#000000
on
#06150B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 More Space for Your Stunts Videos
1.12:1
#000000
on
#06150B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Meet Memory Man
1.12:1
#000000
on
#06150B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Earth Day is April 22
1.12:1
#000000
on
#06150B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 More Space for Your Stunts Videos
1.12:1
#000000
on
#06150B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Meet Memory Man
1.12:1
#000000
on
#06150B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Earth Day is April 22
1.12:1
#000000
on
#06150B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 More Space for Your Stunts Videos
1.12:1
#000000
on
#06150B
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Sign In
1.12:1
#000000
on
#06150B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sign In for Business
1.12:1
#000000
on
#06150B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Reset Password
1.12:1
#000000
on
#06150B
needs 3.0:1 (large text)
19px · bottom of viewport
div and
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Cookie Statement
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
button Manage Cookie Preferences
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
button Reject All Non-Essential Cookies
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Elite Performance fo…1.12:13.0:1
#000000
#06150B
Fail
h1 Future‑Ready PCIe …1.12:13.0:1
#000000
#06150B
Fail
h2 SSD Recommender Tool…1.12:13.0:1
#000000
#06150B
Fail
h2 More Space for Your …1.12:13.0:1
#000000
#06150B
Fail
h2 Meet Memory Man1.12:13.0:1
#000000
#06150B
Fail
h2 Earth Day is April 2…1.12:13.0:1
#000000
#06150B
Fail
h2 More Space for Your …1.12:13.0:1
#000000
#06150B
Fail
h2 Meet Memory Man1.12:13.0:1
#000000
#06150B
Fail
h2 Earth Day is April 2…1.12:13.0:1
#000000
#06150B
Fail
h2 More Space for Your …1.12:13.0:1
#000000
#06150B
Fail
h3 Sign In1.12:13.0:1
#000000
#06150B
Fail
h3 Sign In for Business1.12:13.0:1
#000000
#06150B
Fail
h3 Reset Password1.12:13.0:1
#000000
#06150B
Fail
title Sandisk SSDs, Memory…16.52:14.5:1
#000000
#E4E4E4
Pass
div We use cookies and w…19.09:14.5:1
#000000
#F4F4F4
Pass
a Privacy Statement21.00:14.5:1
#000000
#FFFFFF
Pass
div and1.00:14.5:1
#000000
#000000
Fail
a Cookie Statement1.00:14.5:1
#000000
#000000
Fail
button Manage Cookie Prefer…1.00:14.5:1
#000000
#000000
Fail
button Reject All Non-Essen…1.00:14.5:1
#000000
#000000
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 82/100 — 6 failing, 28 passed
REVIEW
82

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

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search Close div.flex > div.corpSearch > div#searchSummaryView > div.hero-input

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.

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
close icon div#truste-consent-track > div.bb-wrapper > div.truste-icon-box > button#truste-consent-close
div.text > div.md:hidden > p.rd-mobile-account-icon > button div.text > div.md:hidden > p.rd-mobile-account-icon > 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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Manage Cookie Preferences div.bb-wrapper > div#truste-consent-content > div#truste-consent-buttons > button#truste-show-consent
Reject All Non-Essential Cookies div.bb-wrapper > div#truste-consent-content > div#truste-consent-buttons > button#truste-consent-required
Accept All Cookies div.bb-wrapper > div#truste-consent-content > div#truste-consent-buttons > button#truste-consent-button

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
close icon div#truste-consent-track > div.bb-wrapper > div.truste-icon-box > button#truste-consent-close
Privacy Statement div.bb-wrapper > div#truste-consent-content > div#truste-consent-text > a#truste-privacy-button
Cookie Statement div.bb-wrapper > div#truste-consent-content > div#truste-consent-text > a#truste-cookie-button

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
About Us div.-mx-1 > ul.list-reset > li > a.p-1
Responsibility div.-mx-1 > ul.list-reset > li > a.p-1
Investors div.-mx-1 > ul.list-reset > li > a.p-1
Newsroom div.-mx-1 > ul.list-reset > li > a.p-1
Locations div.-mx-1 > ul.list-reset > li > a.p-1
Careers div.-mx-1 > ul.list-reset > li > a.p-1
Contact Us div.-mx-1 > ul.list-reset > li > a.p-1
My Account div.-mx-1 > ul.list-reset > li.show-for-b2c > a.p-1
Product Portfolio div.-mx-1 > ul.list-reset > li > a.p-1
Top Deals div.-mx-1 > ul.list-reset > li.show-for-b2c > a.p-1
Clearance div.-mx-1 > ul.list-reset > li.show-for-b2c > a.p-1
Financing Options div.-mx-1 > ul.list-reset > li.show-for-b2c > a.p-1
Distributors & Resellers div.-mx-1 > ul.list-reset > li.show-for-b2c > a.p-1
Shopping FAQs div.-mx-1 > ul.list-reset > li > a.p-1
Topics Hub div.-mx-1 > ul.list-reset > li > a.p-1
Business Benefits div.-mx-1 > ul.list-reset > li > a.p-1
Sandisk Credit div.-mx-1 > ul.list-reset > li.hide-for-cz > a.p-1
Business Rewards div.-mx-1 > ul.list-reset > li.hide-for-ca > a.p-1
Data Recovery div.-mx-1 > ul.list-reset > li.show-for-b2c > a.p-1
Recycle Program div.-mx-1 > ul.list-reset > li.show-for-b2c > a.p-1
Offer Programs div.-mx-1 > ul.list-reset > li.show-for-b2c > a.p-1
Affiliate Program div.-mx-1 > ul.list-reset > li.show-for-b2c > a.p-1
Ambassador Program div.-mx-1 > ul.list-reset > li.show-for-b2c > a.p-1
Get Help div.-mx-1 > ul.list-reset > li > a.p-1
Warranty Policy div.-mx-1 > ul.list-reset > li > a.p-1
Return Policy div.-mx-1 > ul.list-reset > li > a.p-1
Resource Library div.-mx-1 > ul.list-reset > li > a.p-1
Product Security div.-mx-1 > ul.list-reset > li > a.p-1

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
USB STORAGE & SSDS iPhone 17 Series-Compatible USB Flash Drives & SSDs div.aem-Grid > div.section > section.bg-color > a.block
EN / US div.root > div.aem-Grid > div.button > a.btn
○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
●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
●`[role]` values are valid
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●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
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○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 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.
○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.
○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.
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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
Form Accessibility
1 of 6 controls have issues
PASS
1 of 6 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="predictiveSearchTerm">
Info::
5 control(s) properly labeled
6 controls
5 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#login-selectionselectBuying for yourself or a business?aria-label
#j_usernameemailEmailaria-label
#j_passwordpasswordPasswordaria-label
emailemailEmailaria-label
#user_inputareatextareaType here to beginaria-label
#predictiveSearchTermtext(What can we help you find?)placeholder only

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

<input type="text" name="q" id="predictiveSearchTerm">

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback