Skip to content
https://samsung.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
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
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: #0c4da2
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::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
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.
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Home Electronics | Home Appliances | Mobile | Computing | ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Samsung
1.76:1
#000000
on
#35354A
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Experience a whole new Galaxy
1.76:1
#000000
on
#35354A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Recommended for you
1.76:1
#000000
on
#35354A
needs 3.0:1 (large text)
24px · bottom of viewport
title Samsung US | Mobile | TV | Home Electron…
1.11:1
#000000
on
#050F2B
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.14:1
#000000
on
#06122F
needs 4.5:1 (normal text)
16px · top of page (header area)
span close
1.14:1
#000000
on
#061232
needs 4.5:1 (normal text)
16px · top of page (header area)
div Welcome to the
1.15:1
#000000
on
#051334
needs 4.5:1 (normal text)
16px · top of page (header area)
div Please enjoy our special offers for you
1.16:1
#000000
on
#071336
needs 4.5:1 (normal text)
16px · above the fold
a MY BENEFITS
1.17:1
#000000
on
#081439
needs 4.5:1 (normal text)
16px · above the fold
a SPECIAL OFFERS
1.18:1
#000000
on
#08143C
needs 4.5:1 (normal text)
16px · above the fold
span Search
1.18:1
#000000
on
#07153C
needs 4.5:1 (normal text)
16px · above the fold
span Search
1.21:1
#000000
on
#081740
needs 4.5:1 (normal text)
16px · above the fold
span Cart
1.24:1
#000000
on
#091A44
needs 4.5:1 (normal text)
16px · above the fold
span Number of Products :
1.28:1
#000000
on
#0A1C49
needs 4.5:1 (normal text)
16px · above the fold
span Sign in
1.33:1
#000000
on
#0B204C
needs 4.5:1 (normal text)
16px · above the fold
span Open My Menu
1.30:1
#000000
on
#0B1E4C
needs 4.5:1 (normal text)
16px · above the fold
span Navigation
1.29:1
#000000
on
#0A1D4C
needs 4.5:1 (normal text)
16px · mid-page
span Back
1.32:1
#000000
on
#0B1F4F
needs 4.5:1 (normal text)
16px · mid-page
span Search
1.47:1
#000000
on
#0E285A
needs 4.5:1 (normal text)
16px · mid-page
p SHOP BY CATEGORY
2.14:1
#000000
on
#1E4570
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Samsung1.76:13.0:1
#000000
#35354A
Fail
h2 Experience a whole n…1.76:13.0:1
#000000
#35354A
Fail
h2 Recommended for you1.76:13.0:1
#000000
#35354A
Fail
title Samsung US | Mobile …1.11:14.5:1
#000000
#050F2B
Fail
a Skip to content1.14:14.5:1
#000000
#06122F
Fail
span close1.14:14.5:1
#000000
#061232
Fail
div Welcome to the1.15:14.5:1
#000000
#051334
Fail
div Please enjoy our spe…1.16:14.5:1
#000000
#071336
Fail
a MY BENEFITS1.17:14.5:1
#000000
#081439
Fail
a SPECIAL OFFERS1.18:14.5:1
#000000
#08143C
Fail
span Search1.18:14.5:1
#000000
#07153C
Fail
span Search1.21:14.5:1
#000000
#081740
Fail
span Cart1.24:14.5:1
#000000
#091A44
Fail
span Number of Products :1.28:14.5:1
#000000
#0A1C49
Fail
span Sign in1.33:14.5:1
#000000
#0B204C
Fail
span Open My Menu1.30:14.5:1
#000000
#0B1E4C
Fail
span Navigation1.29:14.5:1
#000000
#0A1D4C
Fail
span Back1.32:14.5:1
#000000
#0B1F4F
Fail
span Search1.47:14.5:1
#000000
#0E285A
Fail
p SHOP BY CATEGORY2.14:14.5:1
#000000
#1E4570
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.

A+
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "main navigation" MAIN CONTENTINFO footer
A+
Heading Hierarchy
3 headings
PASS
3 headings
Info::
Single H1 present
  • H1 Samsung
  • H2 Experience a whole new Galaxy
  • H2 Recommended for you
A
Alt Text Quality
1 of 201 images have issues
PASS
1 of 201 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
2 decorative image(s) correctly marked
Info::
198 image(s) with good alt text
201 images 198 good alt text 2 decorative 1 missing
IssueCount
missing1 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

A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#gnb-search-keywordtextSearcharia-label
A
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 28 passed
PASS
92

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

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
Samsung Electronics, and its partners, use cookies, web beacons, pixels and sim… body.ae-device-mobile > div#consent_blackbar

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.truste-custom-samsung-wrap > div.truste-custom-wrapper > div#audioeEyeLabeledby_0 > img div.truste-custom-samsung-wrap > div.truste-custom-wrapper > div#audioeEyeLabeledby_0 > img

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.

○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 have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`[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 have a discernible name
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[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
●Uses ARIA roles only on compatible elements
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○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.
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback