Skip to content
https://eset.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
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: #40e0d0
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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Form Accessibility
Action
3 of 19 controls have issues
REVIEW
3 of 19 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="devices">; <select name="devices">; <select name="devices">
Info::
16 control(s) properly labeled
19 controls
16 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#69dffaa8b2c3dselectDevicesfor/id
#69dffaa8b2c8cselectYearfor/id
#69dffaa8702afselectDevicesfor/id
#69dffaa8702f2selectYearfor/id
#69dffaa83ff35selectDevicesfor/id
#69dffaa83ff6fselectYearfor/id
inputnumberEnter number of devices:aria-label
#69dffaaa103abselectYearfor/id
inputnumberEnter number of devices:aria-label
#69dffaa985fafselectYearfor/id
inputnumberEnter number of devices:aria-label
#69dffaa91d941selectYearfor/id
#cc-necessarycheckboxEssential cookiesfor/id
#cc-basiccheckboxBasic Analytical Cookiesfor/id
#cc-advancedcheckboxAdvanced Analytical Cookiesfor/id
#cc-marketingcheckboxMarketing cookiesfor/id
devicesselect(none)none
devicesselect(none)none
devicesselect(none)none

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

<select name="devices">; <select name="devices">; <select name="devices">

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

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 404 error | ESET ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
9 icon(s) detected
REVIEW
9 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
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Antivirus & cyber security for Windows, Android or Mac | ESET
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Antivirus & cyber security for Windows, Android or Mac | ESET ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name Antivirus & cyber security for Windows, Android or Mac | ESET Display Mode standalone Theme Color #008193 Background Color #f4f5f4 Icons 5 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA
div Accesskey is "Alt + 0"
1.19:1
#000000
on
#001C20
needs 4.5:1 (normal text)
16px · top of page (header area)
span MENU
1.33:1
#000000
on
#04272C
needs 4.5:1 (normal text)
16px · top of page (header area)
span CLOSE
1.13:1
#000000
on
#00161A
needs 4.5:1 (normal text)
16px · above the fold
a For Home
1.20:1
#000000
on
#061D1F
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a For Business
1.02:1
#000000
on
#000506
needs 4.5:1 (normal text)
16px · above the fold
a For Partners
1.01:1
#000000
on
#000202
needs 4.5:1 (normal text)
16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 AI-Native Prevention…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 For Home21.00:13.0:1
#000000
#FFFFFF
Pass
h2 For Business21.00:13.0:1
#000000
#FFFFFF
Pass
h2 “A21.00:13.0:1
#000000
#FFFFFF
Pass
h2 must work properly a…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 90% of customers21.00:13.0:1
#000000
#FFFFFF
Pass
h3 would recommend ESET21.00:13.0:1
#000000
#FFFFFF
Pass
h3 FOR HOME21.00:13.0:1
#000000
#FFFFFF
Pass
h3 FOR BUSINESS21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Consistently21.00:13.0:1
#000000
#FFFFFF
Pass
h3 worldwide21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Existing customer?21.00:13.0:1
#000000
#FFFFFF
Pass
title ESET Cybersecurity |…21.00:14.5:1
#000000
#FFFFFF
Pass
button Skip to Content21.00:14.5:1
#000000
#FFFFFF
Pass
div Accesskey is "Alt + …1.19:14.5:1
#000000
#001C20
Fail
span MENU1.33:14.5:1
#000000
#04272C
Fail
span CLOSE1.13:14.5:1
#000000
#00161A
Fail
a For Home1.20:14.5:1
#000000
#061D1F
Fail
a For Business1.02:14.5:1
#000000
#000506
Fail
a For Partners1.01:14.5:1
#000000
#000202
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
27 landmarks
PASS
27 landmarks
Info::
<main> landmark present
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 ASIDE CONTENTINFO footer

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

A+
Heading Hierarchy
33 headings
PASS
33 headings
Info::
Single H1 present
  • H1 AI-Native Prevention for Tomorrow's Threats
  • H2 For Home
  • H2 For Business
  • H2 “A complex IT security solution must work properly and yet be easy to use. ESET masters this balance in an exemplary manner.„
  • H3 90% of customers would recommend ESET
  • H3 OUR TOP-SELLERS
  • H4 For home
  • H4 For business
  • H4 For home
  • H3 FOR HOME
  • H4 For business
  • H3 FOR BUSINESS
  • H3 Consistently validated by customers worldwide
  • H4 Research Excellence
  • H4 Technology Leader
  • H4 Customer service
  • H3 Existing customer?
  • H4 For home
  • H4 Downloads for home
  • H4 For business
  • H4 Downloads for business
  • H4 Partnership
  • H4 Support
  • H4 About ESET
  • H4 For home
  • H4 Downloads for home
  • H4 For business
  • H4 Downloads for business
  • H4 Partnership
  • H4 Support
  • H4 About ESET
  • H5 © 2008-2026 ESET North America. All rights reserved. Trademarks used herein are trademarks or registered trademarks of ESET spol. s r.o. or ESET North America. All other names and brands are register
  • H4 Continue to your country's website for local products, special offers and customer care.
A+
Alt Text Quality
All 5 images OK
PASS
All 5 images OK
Info::
2 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
5 images 3 good alt text 2 decorative
All images have appropriate alt text.
A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 25 passed
PASS
96

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.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div.gws-geoip-countries > div.globe-icon > a div > div.gws-geoip-countries > div.globe-icon > a

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
●`[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.
●`[accesskey]` values are unique
●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.
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`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
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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.
○`[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.
○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