Skip to content
https://smartthings.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 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: #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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Breadcrumb navigation detected
Got: aria-label
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs aria-label navigation
Search
Skip Link Skip link detected
Labeled Navigation 3 <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
Alt Text Quality
1 of 273 images have issues
REVIEW
1 of 273 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
17 image(s) with alt text over 125 characters
Info::
26 decorative image(s) correctly marked
Info::
229 image(s) with good alt text
273 images 229 good alt text 26 decorative 1 missing
IssueCount
missing1 image(s)
too long17 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

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 We’ve Lost this Page ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
12 icon(s) detected
REVIEW
12 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
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 4 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Your home saves ener…6.41:13.0:1
#000000
#8E8E8E
Pass
h2 Your Companion6.41:13.0:1
#000000
#8E8E8E
Pass
h2 to AI Living6.41:13.0:1
#000000
#8E8E8E
Pass
h2 Your home saves ener…6.41:13.0:1
#000000
#8E8E8E
Pass
h2 Your Companion6.41:13.0:1
#000000
#8E8E8E
Pass
h2 to AI Living6.41:13.0:1
#000000
#8E8E8E
Pass
h2 Shop SmartThings6.41:13.0:1
#000000
#8E8E8E
Pass
h2 SmartThings 1016.41:13.0:1
#000000
#8E8E8E
Pass
h3 A new way to enjoy y…6.41:13.0:1
#000000
#8E8E8E
Pass
h3 Play6.41:13.0:1
#000000
#8E8E8E
Pass
h3 Your Home Speaks You6.41:13.0:1
#000000
#8E8E8E
Pass
h3 Latest updates6.41:13.0:1
#000000
#8E8E8E
Pass
h3 Inspiring ideas6.41:13.0:1
#000000
#8E8E8E
Pass
h3 Get more from your p…6.41:13.0:1
#000000
#8E8E8E
Pass
h3 More compatible than…6.41:13.0:1
#000000
#8E8E8E
Pass
h3 Explore the SmartThi…6.41:13.0:1
#000000
#8E8E8E
Pass
title Smart home with Sams…6.25:14.5:1
#000000
#8C8C8C
Pass
a Skip to content6.92:14.5:1
#000000
#949494
Pass
span close6.92:14.5:1
#000000
#949494
Pass
label Choose your location…6.92:14.5:1
#000000
#949494
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.

B
Lighthouse Accessibility Audits
Score 84/100 — 4 failing, 27 passed
REVIEW
84

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

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
section.spop-overlay-651597 > div.spop-card > div.spop-wrap > button.spopunder-close section.spop-overlay-651597 > div.spop-card > div.spop-wrap > button.spopunder-close

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.

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
Explore div.nv07-explore-floating-navigation__menu-wrap > ul.nv07-explore-floating-navigation__menu-list > li.nv07-explore-floating-navigation__menu > a.nv07-explore-floating-navigation__menu-link

These items highlight common accessibility best practices.

○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●`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
●`[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
○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.
A+
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "main navigation" MAIN ASIDE CONTENTINFO footer
A+
Heading Hierarchy
43 headings
PASS
43 headings
Info::
Single H1 present
  • H1 SmartThings
  • H2 Your home saves energy
  • H2 Your Companionto AI Living
  • H2 Your home saves energy
  • H2 Your Companionto AI Living
  • H3 A new way to enjoy your home
  • H4 Care
  • H4 Secure
  • H4 Save
  • H3 Play
  • H2 Shop SmartThings
  • H3 Your Home Speaks You
  • H3 Latest updates
  • H4 Home Insight
  • H4 Home Routine
  • H4 Device Control
  • H2 SmartThings 101
  • H3 Inspiring ideas
  • H3 Get more from your products
  • H4 Control devices seamlessly
  • H4 Cast what you want
  • H4 See your home at a glance
  • H4 New AI Smart Monitors
  • H4 Create your smart home seamlessly
  • H4 Track your fitness
  • H4 Peek inside with AI Vision
  • H4 Monitor your energy usage
  • H4 Keep it closed
  • H4 Manage energy use
  • H4 Wash and dry your way
  • H4 Care for the devices that care for you
  • H4 Pet care from afar
  • H4 Use off-peak energy
  • H4 Say it. SmartThings does it.
  • H3 More compatible than ever
  • H4 Smart Home Hubs
  • H4 Smart Lighting
  • H4 Sensors
  • H4 Smart Plugs
  • H4 Cameras
  • H4 Thermostats
  • H4 Doorbells
  • H3 Explore the SmartThings app
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#gnb-search-keywordtextSearcharia-label
#getStockAlertEmailInputtextEnter Your Emailfor/id
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: gatsby-starter-default
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: minimal-ui
PWA Install Criteria ✓ Installable
Name gatsby-starter-default ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode minimal-ui ✓
Name gatsby-starter-default Display Mode minimal-ui Theme Color #402087 Background Color #402087 Icons 8 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback