Skip to content
https://malwarebytes.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Form Accessibility
Action
4 of 7 controls have issues
FIX
4 of 7 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">; <input type="submit" id="cta-footer-newsletter-subscribe-email-en">
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="cta-footer-newsletter-input-email-en">
Info::
3 control(s) properly labeled
7 controls
3 labeled
1 placeholder only
3 unlabeled
ControlTypeLabelMethod
ssearchSearch for:none
ssearchSearch for:none
#wg69e7e40869b418.594672041776804872405checkboxEnglishfor/id
#cta-footer-newsletter-input-email-enemail(Email Address)placeholder only
inputsubmit(none)none
#cta-footer-newsletter-subscribe-email-ensubmit(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="submit">; <input type="submit" id="cta-footer-newsletter-subscribe-email-en">

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

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

<input type="email" name="email" id="cta-footer-newsletter-input-email-en">

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

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - Page Not Found ✓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
Lighthouse Accessibility Audits
Score 89/100 — 4 failing, 27 passed
REVIEW
89

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.

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
Family ul.tabTitles > li#cta-homepage-pricing-toggle-family-click > div.tab-title-wrap > h5.tab-title-text
Small business ul.tabTitles > li#cta-homepage-pricing-toggle-teams-click > div.tab-title-wrap > h5.tab-title-text

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
others miss div.kt-inside-inner-col > p.kt-adv-heading4_7273fa-7b > mark.has-inline-color > a

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
Individual ul.tabTitles > li#cta-homepage-pricing-toggle-individual-click > div.tab-title-wrap > h5.tab-title-text

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.kt-row-column-wrap > div.wp-block-kadence-column > div.kt-inside-inner-col > a.kb-advanced-heading-link div.kt-row-column-wrap > div.wp-block-kadence-column > div.kt-inside-inner-col > a.kb-advanced-heading-link
div.wp-block-kadence-column > div.kt-inside-inner-col > p#brand-homepage-reviews > a.kb-advanced-heading-link div.wp-block-kadence-column > div.kt-inside-inner-col > p#brand-homepage-reviews > a.kb-advanced-heading-link
div.site-footer__top > div.container > div.site-footer__info > a#cta-navbar-footer-company-logo-en div.site-footer__top > div.container > div.site-footer__info > a#cta-navbar-footer-company-logo-en

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
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●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
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` 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 type="image">` elements have `[alt]` text
○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.
○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
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE "Language selected: English" CONTENTINFO footer
A
Heading Hierarchy
67 headings, 1 skip(s)
PASS
67 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Malwarebytes top all-in-one cybersecurity software is trusted and loved by millions.
  • H2 Proven threat
stopping power
  • H3 0M+
  • H3 0M+
  • H3 0
  • H3 0M+
  • H2 Complete protection from malware, scams, and beyond
  • H3 Clean and secure your devices
  • H3 Protect your privacy online
  • H3 Keep your identity safe
  • H2 Plans that put your safety first
  • H5 Individual skipped
  • H5 Family
  • H5 Small business
  • H2 50% OFF
  • H2 169,99 €/yr.
  • H2 50% OFF
  • H2 229,99 €/yr.
  • H2 734,99 €/yr.
  • H2 Cover all your protection needs
  • H3 Premium Security
  • H3 Browser Guard
  • H3 Privacy VPN
  • H3 Identity Theft Protection
  • H3 Scam-proof your scroll
  • H2 Why Malwarebytes?
  • H3 Loved by experts
  • H4 Seamless and easy to use
  • H4 Low resources and high, high-end benefits.
  • H3 Trusted by users
  • H3 Built and run by humans
  • H4 We’re here to help
  • H3 Meet some of the cybersecurity nerds securing your world
  • H2 Arpy
  • H3 Senior Product Manager
  • H2 Ashley
  • H3 Public Relations
  • H2 Russ
  • H3 Information Security Analyst
  • H2 Laura
  • H3 VP, Global People
  • H2 Nilay
  • H3 Site Reliability Engineer
  • H2 Marcin
  • H3 Founder and CEO
  • H2 Pieter
  • H3 Malware Intelligence Researcher
  • H2 Uriya
  • H3 Mobile Product Lead
  • H2 Arpy
  • H3 Senior Product Manager
  • H2 Ashley
  • H3 Public Relations
  • H2 Russ
  • H3 Information Security Analyst
  • H2 Laura
  • H3 VP, Global People
  • H2 Nilay
  • H3 Site Reliability Engineer
  • H2 Marcin
  • H3 Founder and CEO
  • H2 Pieter
  • H3 Malware Intelligence Researcher
  • H2 Uriya
  • H3 Mobile Product Lead
  • H2 Protection that’s got your back
  • H2 Cybersecurity info you can’t live without

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

A+
Alt Text Quality
All 42 images OK
PASS
All 42 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
9 decorative image(s) correctly marked
Info::
32 image(s) with good alt text
42 images 32 good alt text 9 decorative
IssueCount
too long1 image(s)
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Malwarebytes top all…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Proven threat
stop…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Complete protection …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 malware, scams, and …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Plans that put your …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 50% OFF21.00:13.0:1
#000000
#FFFFFF
Pass
h2 50% OFF21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Cover all your prote…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why Malwarebytes?21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Arpy21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ashley21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Russ21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Laura21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Nilay21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Marcin21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Pieter21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Uriya21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Arpy21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ashley21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Russ21.00:13.0:1
#000000
#FFFFFF
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.

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

Send Feedback