eset.com Accessibility Report

Accessibility audit of eset.com — scanned on Feb 20, 2026

Technology
0 /100
D Poor

6 issues found across 2 categories

2 Critical 4 Major

WCAG Compliance Overview

Perceivable 1 issues
Operable 4 issues
Understandable 0 issues
Robust 1 issues

Issues Found

Links missing accessible name

Critical

Links must have discernible text so screen reader users understand their purpose.

WCAG 2.4.4
17 element(s) affected
  • <a href="(no href)">
  • <a href="/us/business/entry-protection/">
  • <a href="/us/business/contact-sales/">
  • <a href="/us/business/contact-sales/">
  • <a href="/us/business/contact-sales/">
How to fix

Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

Form inputs missing labels

Critical

Form elements must have associated labels so users know what information to enter.

WCAG 1.3.1
3 element(s) affected
  • <select name="devices">
  • <select name="devices">
  • <select name="devices">
How to fix

Add <label> elements with matching for attributes, or use aria-label.

Frames missing title

Major

Iframes must have title attributes describing their content.

WCAG 2.4.1
2 element(s) affected
  • <iframe src="//sgtm.eset.com/ns.html?id=GTM-M6QG34">
  • <iframe src="//sgtm.eset.com/ns.html?id=GTM-TJ2Z4SC">
How to fix

Add descriptive title attributes to all <iframe> elements.

Duplicate element IDs

Major

Element IDs must be unique to ensure correct assistive technology behavior.

WCAG 4.1.1
29 element(s) affected
  • id="filter0_f_3639_2844"
  • id="filter0_f_3639_2846"
  • id="filter0_f_3639_2866"
  • id="noiseFilter"
  • id="a"
How to fix

Make each id attribute value unique within the page.

No skip navigation link

Major

Pages should have a mechanism to bypass repeated navigation blocks.

WCAG 2.4.1
1 element(s) affected
  • No skip navigation link found
How to fix

Add a 'Skip to main content' link as the first focusable element on the page.

Generic link text

Major

Links must have descriptive text that indicates their purpose. Generic text like 'click here' or 'read more' does not help screen reader users understand where the link goes.

WCAG 2.4.4
1 element(s) affected
  • <a href="/us/business/gartner-the-voice-of-the-customers/">learn more</a>
How to fix

Replace generic link text with descriptive text, e.g., 'Read our accessibility guide' instead of 'Read more'.

Top Priority Fixes

Here are the most impactful changes eset.com should make to improve accessibility:

  1. #1
    Links missing accessible name Critical

    Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

  2. #2
    Form inputs missing labels Critical

    Add <label> elements with matching for attributes, or use aria-label.

  3. #3
    Duplicate element IDs Major

    Make each id attribute value unique within the page.

Frequently Asked Questions

Is eset.com accessible?

eset.com scored 38/100 (grade D) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is eset.com WCAG compliant?

Our scan found 6 accessibility issues on eset.com. Full WCAG compliance requires addressing all critical and major issues identified above.

Is eset.com EAA compliant?

The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see eset.com's compliance status.

What accessibility issues does eset.com have?

See the full issue list above with severity levels, affected elements, and recommended fixes for eset.com.

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing