Skip to content
https://avira.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
D
Heading Hierarchy
Action
33 headings, 3 skip(s)
FIX
33 headings, 3 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
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.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Avira Prime
  • H3 Avira Internet Security
  • H3 Avira Free Security
  • H3 Avira Prime Mobile for iOS
  • H3 Avira Prime Mobile for Android
  • H1 Protect yourself from cyber threats. Choose your security software.
  • H2 Avira Free Security for Windows
  • H2 Avira Internet Security for Windows
  • H2 Avira Prime. For all your devices.
  • H2 Avira Free Security for Windows
  • H2 Avira Internet Security for Windows
  • H2 Avira Prime. For all your devices.
  • H4 rated 4,5/5 on GOOGLE PLAY skipped
  • H4 rated 4,1/5 in AppStore
  • H4 CNET Editor’s rating Spectacular
  • H2 Make your digital life more secure with just one download.
  • H4 Join the millions of users we help protect. skipped
  • H3 Stay safe against many digital threats.
  • H3 Keep your routine private and protected.
  • H3 Save hard drive space and boost speed.
  • H3 Block scams and protect your accounts.
  • H1 Want to take your digital security and privacy to the next level? duplicate H1
  • H2 Our multi-device Avira Prime package helps you:
  • H2 Find out more about us and how we can help.
  • H4 Why choose us? skipped
  • H4 What’s the best free Avira app to get started with?
  • H4 What’s our best security, privacy, and performance package?
  • H4 Want to optimize your devices, update software, and more?
  • H4 Would you like to help encrypt your web traffic and hide your online activity?
  • H4 Need to make managing your online passwords easier?
  • H2 Get expert advice about cybersecurity and online privacy.
  • H3 Not ready to commit?
  • H3 Manage Consent Preferences

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://avira.com/ieconfig.xml contains invalid JSON. Browsers cannot parse it.
Got: https://avira.com/ieconfig.xml

Manifest contains invalid JSON.

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
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Alt Text Quality
2 of 30 images have issues
REVIEW
2 of 30 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
10 decorative image(s) correctly marked
Info::
18 image(s) with good alt text
30 images 18 good alt text 10 decorative 2 missing
IssueCount
missing2 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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Error | Avira ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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 Missing
✓ 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 20 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Protect yourself fro…4.24:13.0:1
#000000
#707070
Pass
h1 Choose your security…4.24:13.0:1
#000000
#707070
Pass
h1 Want to take your di…4.24:13.0:1
#000000
#707070
Pass
h2 Avira Free Security …4.24:13.0:1
#000000
#707070
Pass
h2 Avira Internet Secur…4.24:13.0:1
#000000
#707070
Pass
h2 Avira Prime. For all…4.24:13.0:1
#000000
#707070
Pass
h2 Avira Free Security …4.24:13.0:1
#000000
#707070
Pass
h2 Avira Internet Secur…4.24:13.0:1
#000000
#707070
Pass
h2 Avira Prime. For all…4.24:13.0:1
#000000
#707070
Pass
h2 Make your digital li…4.24:13.0:1
#000000
#707070
Pass
h2 Our multi-device Avi…4.24:13.0:1
#000000
#707070
Pass
h2 Find out more about …4.24:13.0:1
#000000
#707070
Pass
h2 Get expert advice ab…4.24:13.0:1
#000000
#707070
Pass
h3 Avira Prime4.29:13.0:1
#000000
#6F7174
Pass
h3 Avira Internet Secur…4.30:13.0:1
#000000
#717171
Pass
h3 Avira Free Security4.24:13.0:1
#000000
#707070
Pass
h3 Avira Prime Mobile f…4.24:13.0:1
#000000
#707070
Pass
h3 Avira Prime Mobile f…4.24:13.0:1
#000000
#707070
Pass
h3 Stay safe against ma…4.24:13.0:1
#000000
#707070
Pass
h3 Keep your routine pr…4.24:13.0:1
#000000
#707070
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.

C
Lighthouse Accessibility Audits
Action
Score 73/100 — 9 failing, 22 passed
REVIEW
73

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
2 div#Awards > ul.slick-dots > li.slick-active > button#slick-slide-control01

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
Free optimizer and free security software for more cyber protection, online pri… div.containter > div.row > div.col-xs-offset-1 > div#accordion-21

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
We value your privacy By clicking "OK" you allow cookies that improve your expe… section > div#ensNotifyBanner > div#ensBannerDescription > div.privacyDialog

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Visit our blog div.row > div.col-xs-offset-1 > div.see-blog-art-wrap > a
Terms of Sale div.col-xs-12 > ul > li > a
License & Services Agreement div.col-xs-12 > ul > li > a
as described here div.col-xs-12 > ul > li > a
your account div.col-xs-12 > ul > li > a
contacting us here div.col-xs-12 > ul > li > a
Cancellation & Refund Policy div.col-xs-12 > ul > li > a
To cancel your contract or request a refund, click here div.col-xs-12 > ul > li > a

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Antivirus for Mac div#collapse-21-1 > div.panel-body > p > a.pimcore_glossary

These are opportunities to improve the legibility of your content.

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
System requirements main#mainContent > div#component-sysreq > div.container > h5.system-requirements__title
Free optimizer and free security software for more cyber protection, online pri… div#accordion-21 > div.panel > div#heading-21-1 > h4.panel-title

These are opportunities to improve keyboard navigation in your application.

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.row > div.col-xs-12 > div.snippet-disclaimer > img.disclaimer-logo div.row > div.col-xs-12 > div.snippet-disclaimer > img.disclaimer-logo

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
1 div#Awards > ul.slick-dots > li > button#slick-slide-control00
2 div#Awards > ul.slick-dots > li.slick-active > button#slick-slide-control01
3 div#Awards > ul.slick-dots > li > button#slick-slide-control02
4 div#Awards > ul.slick-dots > li > button#slick-slide-control03

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
Cookies Policy div.privacyDialog > div.privacyContent > div.privacyDescription > a.privacyPolicyLink
○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]`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.
●Select elements have associated label elements.
●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
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○`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 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
○Form elements have associated labels
○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.
○`[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.
○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
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
2 <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" MAIN CONTENTINFO footer
A
Form Accessibility
1 of 26 controls have issues
PASS
1 of 26 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email" id="email-addr">
Info::
25 control(s) properly labeled
26 controls
25 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#mobile-language-dropdownselectLanguage selector for mobile devices. Selected option automatically submits.aria-label
#mobile-language-dropdown-footerselectLanguage selector for mobile devicesaria-label
#PreferenceSlidecheckboxPreference cookiesnone
#Preference-Qualtrics--.qualtrics-.com-slidecheckboxQualtricsnone
#Preference-Youtube-www.youtube.com-slidecheckboxYoutubenone
#PerformanceSlidecheckboxPerformance cookiesnone
#Performance-Akamai-mPulse--.go-mpulse-.net-slidecheckboxAkamai mPulsenone
#Performance-Microsoft-Clarity---.clarity-.ms----.microsoft-.com--slidecheckboxMicrosoft Claritynone
#Performance-Quantum-Metric-quantummetric.com-slidecheckboxQuantum Metricnone
#Performance-Rum--.site24x7rum-.com-slidecheckboxRumnone
#Performance-Spotify--.spotify-.com-slidecheckboxSpotifynone
#Performance-Crazy-Egg--.crazyegg-.com-slidecheckboxCrazy Eggnone
#Performance-Rockerbox--.getrockerbox-.com-slidecheckboxRockerboxnone
#Performance-Online-Metrix--.online-metrix-.net-slidecheckboxOnline Metrixnone
#Performance--Google-Analytics-slidecheckboxGoogle Analyticsnone
#Performance-Hubspot---.--.---hubspot-.-com-net--hs-banner-.com---slidecheckboxHubspotnone
#AdvertisingSlidecheckboxMarketing cookiesnone
#Advertising-Bing---.bing-.com----.bing-.net--slidecheckboxBingnone
#Advertising-LinkedIn--linkedin.com----.rlcdn-.com--slidecheckboxLinkedInnone
#Advertising-Google-Ads----.--.---doubleclick-.net-googleads-.com-googleadservices-.com-googlesyndication-.com-adservice-.google-.com-merchant-center-analytics-.goog---slidecheckboxGoogle Adsnone
#Advertising-Awin---.awin-.com-slidecheckboxAwinnone
#Advertising-Apple-iTune-itunes.apple.com-slidecheckboxApple iTunenone
#Advertising-Upsell-it--.upsellit-.com-slidecheckboxUpsell itnone
#Advertising-Tag4Arm-tag4arm.com-slidecheckboxTag4Armnone
#Advertising-Facebook-Ads---.--.---facebook-.-com-net--fbcdn-.net-meta-.com-instagram-.com---slidecheckboxFacebook Adsnone
#email-addremail(Your email address here)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="email" name="email" id="email-addr">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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

Send Feedback