Skip to content
https://avast.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
D
Landmark Structure
Action
8 landmarks
FIX
8 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
6 <nav> landmark(s) found
Warning::
5 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No contentinfo (footer) landmark
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 navigation" MAIN (missing!) CONTENTINFO (missing!)

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

D
Heading Hierarchy
Action
26 headings, 3 skip(s)
FIX
26 headings, 3 skip(s)
Warning::
Multiple H1 headings (4 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (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.
  • H2 Ya casi has acabado...
  • H3 Busca y haz clic en el archivo descargado avast.exeavast.dmg para completar la instalación.
  • H3 Parece que estás usando {currentOS}
  • H1 El antivirus gratuito mejor valorado, ahora con protección contra estafas y malware en línea
  • H1 El antivirus gratuito mejor valorado, ahora con protección contra estafas y malware en línea duplicate H1
  • H1 El antivirus gratuito mejor valorado, ahora con protección contra estafas y malware en línea duplicate H1
  • H1 El antivirus gratuito mejor valorado, ahora con protección contra estafas y malware en línea duplicate H1
  • H2 Consigue un antivirus gratuito con funciones de privacidad y seguridad avanzadas
  • H6 Recibe orientación contra estafas basada en IA skipped
  • H6 Fácil de instalar y usar
  • H6 Seguridad de la red wifi
  • H6 Protección contra los ataques de ransomware
  • H2 Seguridad digital reforzada para PC, macOS y dispositivos móviles
  • H2 Usa una VPN para reforzar tu privacidad en internet
  • H2 Disfruta de un dispositivo más rápido y con más espacio de almacenamiento
  • H2 Es muy fácil de instalar; bastan unos segundos para cambiar a Avast
  • H2 Es muy fácil de instalar; bastan unos segundos para cambiar a Avast
  • H2 Es muy fácil de instalar; bastan unos segundos para cambiar a Avast
  • H2 Es muy fácil de instalar; bastan unos segundos para cambiar a Avast
  • H2 Avast cuenta con cientos de millones de usuarios en todo el mundo
  • H6 Carol J. skipped
  • H6 James M.
  • H6 OB
  • H2 Recibe consejos sobre seguridad, privacidad y rendimiento directamente de los expertos
  • H2 Mantenemos más seguras a millones de personas en todo el mundo
  • H4 Avast recommends using the FREE Chrome™ internet browser. skipped

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

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
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
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::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 6 <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 404 Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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 mejor valorado, ahora con protección co…
1.22:1
#000000
on
#071D2B
needs 3.0:1 (large text)
32px · bottom of viewport
h1 mejor valorado, ahora con protección co…
1.22:1
#000000
on
#071D2B
needs 3.0:1 (large text)
32px · bottom of viewport
h1 mejor valorado, ahora con protección co…
1.22:1
#000000
on
#071D2B
needs 3.0:1 (large text)
32px · bottom of viewport
h1 mejor valorado, ahora con protección co…
1.22:1
#000000
on
#071D2B
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Ya casi has acabado...
1.73:1
#000000
on
#253844
needs 3.0:1 (large text)
24px · top of page (header area) · over background image/gradient
h2 Consigue un antivirus gratuito con funci…
1.22:1
#000000
on
#071D2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Seguridad digital reforzada para PC, mac…
1.22:1
#000000
on
#071D2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Usa una VPN para reforzar tu privacidad …
1.22:1
#000000
on
#071D2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Disfruta de un dispositivo más rápido …
1.22:1
#000000
on
#071D2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Es muy fácil de instalar; bastan unos s…
1.22:1
#000000
on
#071D2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Es muy fácil de instalar; bastan unos s…
1.22:1
#000000
on
#071D2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Es muy fácil de instalar; bastan unos s…
1.22:1
#000000
on
#071D2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Es muy fácil de instalar; bastan unos s…
1.22:1
#000000
on
#071D2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Recibe consejos sobre seguridad, privaci…
1.22:1
#000000
on
#071D2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mantenemos más seguras a millones de pe…
1.22:1
#000000
on
#071D2B
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Busca y haz clic en el archivo descargad…
2.28:1
#000000
on
#394A55
needs 3.0:1 (large text)
19px · top of page (header area)
h3 para completar la instalación.
2.28:1
#000000
on
#394A55
needs 3.0:1 (large text)
19px · above the fold
h3 Parece que estás usando {currentOS}
1.22:1
#000000
on
#071D2B
needs 3.0:1 (large text)
19px · above the fold
title Avast | Descargar VPN y antivirus gratis…
1.21:1
#000000
on
#071C2A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Cerrar
1.21:1
#000000
on
#071C2A
needs 4.5:1 (normal text)
16px · top of page (header area)

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 mejor valorado, ahor…1.22:13.0:1
#000000
#071D2B
Fail
h1 mejor valorado, ahor…1.22:13.0:1
#000000
#071D2B
Fail
h1 mejor valorado, ahor…1.22:13.0:1
#000000
#071D2B
Fail
h1 mejor valorado, ahor…1.22:13.0:1
#000000
#071D2B
Fail
h2 Ya casi has acabado.…1.73:13.0:1
#000000
#253844
Fail
h2 Consigue un antiviru…1.22:13.0:1
#000000
#071D2B
Fail
h2 Seguridad digital re…1.22:13.0:1
#000000
#071D2B
Fail
h2 Usa una VPN para ref…1.22:13.0:1
#000000
#071D2B
Fail
h2 Disfruta de un dispo…1.22:13.0:1
#000000
#071D2B
Fail
h2 Es muy fácil de ins…1.22:13.0:1
#000000
#071D2B
Fail
h2 Es muy fácil de ins…1.22:13.0:1
#000000
#071D2B
Fail
h2 Es muy fácil de ins…1.22:13.0:1
#000000
#071D2B
Fail
h2 Es muy fácil de ins…1.22:13.0:1
#000000
#071D2B
Fail
h2 Recibe consejos sobr…1.22:13.0:1
#000000
#071D2B
Fail
h2 Mantenemos más segu…1.22:13.0:1
#000000
#071D2B
Fail
h3 Busca y haz clic en …2.28:13.0:1
#000000
#394A55
Fail
h3 para completar la in…2.28:13.0:1
#000000
#394A55
Fail
h3 Parece que estás us…1.22:13.0:1
#000000
#071D2B
Fail
title Avast | Descargar VP…1.21:14.5:1
#000000
#071C2A
Fail
span Cerrar1.21:14.5:1
#000000
#071C2A
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 22 passed
REVIEW
85

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
Para el hogar div.c-footer__content > div.c-footer__navigation > div.c-footer__nav-column1 > div.c-footer__column1-title
Para empresas div.c-footer__content > div.c-footer__navigation > div.c-footer__nav-column2 > div.c-footer__column2-title
Para socios div.c-footer__content > div.c-footer__navigation > div.c-footer__nav-column3 > div.c-footer__column3-title
Acerca de div.c-footer__content > div.c-footer__navigation > div.c-footer__nav-column4 > div.c-footer__column4-title

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
Respetamos su privacidad Al hacer clic en «OK», permites las cookies que mejora… 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.

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
Recibe orientación contra estafas basada en IA div.c-featurecard__container > div.c-featurecard__content-Wrapper > div.c-featurecard__content-container > h6.c-featurecard__title
Carol J. div.c-testimonialcard__body-cta-wrapper > div.c-testimonialcard__reviewer-cont > div.c-testimonialcard__reviewer-content > h6.c-testimonialcard__reviewer-name

These are opportunities to improve keyboard navigation in your application.

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.text > div#text-text-5fdd1d4334 > p.t-rtf-style--body2 > a div.text > div#text-text-5fdd1d4334 > p.t-rtf-style--body2 > 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-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
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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 are distinguishable without relying on color.
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Elements with visible text labels have matching accessible names.
○`[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 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
○`<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
○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.
○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
Alt Text Quality
1 of 205 images have issues
PASS
1 of 205 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
90 decorative image(s) correctly marked
Info::
114 image(s) with good alt text
205 images 114 good alt text 90 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 4 controls labeled
PASS
All 4 controls labeled
Info::
4 control(s) properly labeled
4 controls
4 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#NecessarySlidecheckboxCookies necesariasSiempre activasnone
#PreferenceSlidecheckboxCookies de preferenciasnone
#PerformanceSlidecheckboxCookies de rendimientonone
#AdvertisingSlidecheckboxCookies de marketingnone
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback