Skip to content
https://belkin.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #000000
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 ModePartial Dark Mode
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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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
Heading Hierarchy
29 headings, 2 skip(s)
REVIEW
29 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 iPhone 15, Samsung, iPad, PC & MacBook accessory products
  • H2 Power Up, Play On
  • H4 Keep your Nintendo Switch 2 charged and protected. skipped
  • H2 Fuel Your Galaxy S26
  • H4 Rapid power. Rock-solid protection. skipped
  • H3 Shop by Category
  • H2 Cables
  • H2 Adapters
  • H2 Certified Refurbished
  • H2 Switch 2 Accessories
  • H2 Wireless Chargers
  • H2 Chargers
  • H2 Docks and Hubs
  • H2 Screen Protection
  • H2 Audio
  • H2 Cables
  • H2 Adapters
  • H2 Certified Refurbished
  • H2 Switch 2 Accessories
  • H2 Wireless Chargers
  • H2 Chargers
  • H2 Docks and Hubs
  • H2 Screen Protection
  • H2 Audio
  • H2 Cables
  • H2 Adapters
  • H2 Certified Refurbished
  • H3 Featured in
  • H3 Discover Tech with Belkin

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

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::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Sites-BELKUS-Site ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
15 icon(s) detected
REVIEW
15 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Lighthouse Accessibility Audits
Action
Score 78/100 — 7 failing, 23 passed
REVIEW
78

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Switch 2 Accessories div.tabs-container > nav.tabs > div.col-12 > div.experience-component
Galaxy S26 Must-Haves div.tabs-container > nav.tabs > div.col-12 > div.experience-component
25W Fast Chargers div.tabs-container > nav.tabs > div.col-12 > div.experience-component
iPhone 17 Essentials div.tabs-container > nav.tabs > div.col-12 > div.experience-component

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
Switch 2 Accessories Galaxy S26 Must-Haves 25W Fast Chargers iPhone 17 Essentia… div.experience-component > div.section-bg > div.tabs-container > nav.tabs

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Previous ScreenForce TemperedGlass Anti-Reflective Screen Protector for Nintend… div.section-bg > div.tabs-container > div.tab-panels > div#tab-0-0

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Bienvenue. Souhaitez-vous être redirigé vers le site web FR de Belkin ? France … body.is-sticky > div.page > div#site-main > div#locale-detection-modal

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.

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
Keep your Nintendo Switch 2 charged and protected. div.row > div.heading-inner > div.description > h4
Rapid power. Rock-solid protection. div.row > div.heading-inner > div.description > h4

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
Gaming div.product-tile__main > div.product-tile__family-name__block > div.product-tile__family-name > a.product-tile__family-name__link
Gaming div.product-tile__main > div.product-tile__family-name__block > div.product-tile__family-name > a.product-tile__family-name__link

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
Switch 2 Accessories div.pd-slide > div.row > div.col-12 > a.nav-link
Wireless Chargers div.pd-slide > div.row > div.col-12 > a.nav-link
○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-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
●Buttons have an accessible name
●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
●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
●No element has a `[tabindex]` value greater than 0
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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.
○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.
○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
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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 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
Alt Text Quality
All 500 images OK
PASS
All 500 images OK
Info::
12 image(s) with alt text over 125 characters
Info::
138 decorative image(s) correctly marked
Info::
350 image(s) with good alt text
500 images 350 good alt text 138 decorative
IssueCount
too long12 image(s)
A+
Form Accessibility
All 13 controls labeled
PASS
All 13 controls labeled
Info::
13 control(s) properly labeled
13 controls
13 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cio-autocomplete-0-inputinputnone
#reset-password-emailemailEmailfor/id
#save-geo-prefcheckboxEnregistrer vos préférencesfor/id
#dwfrm_mcsubscribe_emailtextEnter Emailaria-label
#subscribe_allcheckboxSign me up! Send me all Belkin updates and special offers (Select All)for/id
#Apple_DevicecheckboxApple Device Accessoriesfor/id
#Blog_AlertscheckboxBelkin Blog Alertsfor/id
#OfferscheckboxExclusive Offers & Promotionsfor/id
#NetworkingcheckboxNetwork Accessoriesfor/id
#New_ProductscheckboxNew Product Launchesfor/id
#Android_DevicecheckboxSamsung and Android Device Accessoriesfor/id
#BusinesscheckboxSmall Businessfor/id
#Speakers_HeadphonescheckboxSpeakers & Headphonesfor/id
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Belkin
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Belkin ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name Belkin Display Mode standalone Theme Color #000000 Background Color #FFFFFF Icons 7 icon(s)
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 iPhone 15, Samsung, …5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Power Up, Play On5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Fuel Your Galaxy S265.24:13.0:1
#000000
#7F7F7F
Pass
h2 Cables5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Adapters5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Certified Refurbishe…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Switch 2 Accessories5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Wireless Chargers5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Chargers5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Docks and Hubs5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Screen Protection5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Audio5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Cables5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Adapters5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Certified Refurbishe…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Switch 2 Accessories5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Wireless Chargers5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Chargers5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Docks and Hubs5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Screen Protection5.24:13.0:1
#000000
#7F7F7F
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.

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

Send Feedback