Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

Link & Button Quality

Action

11 issue(s) across 281 links and 5 buttons

FIX

11 issue(s) across 281 links and 5 buttons

5 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://www.bitdefender.com/consumer/support/; https://www.bitdefender.com/business/support/; https://login.bitdefender.com/central/login.html?lang=en_US&redirect_url=http…; https://gravityzone.bitdefender.com/; https://auth.mdr.bitdefender.com/login

3 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /en-us/business/products/gravityzone-phasr ("Read more"); https://www.bitdefender.com/en-us/scuderiaferrari/ ("Read more"); https://www.bitdefender.com/en-us/news/bitdefender-completes-acquisition-of-m… ("Read more")

3 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: /en-us/business/awards; /en-us/business/renew-upgrade/; https://pan.bitdefender.com/partners/save/

3 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.language-banner__decline-button (#142 on page); button.language-banner__decline-button (#151 on page); button.closeVideo (#1708 on page)

270 link(s) with descriptive text

281 links

5 empty

3 generic text

3 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://www.bitdefender.com/consumer/sup…	(empty)	empty	Add link text or aria-label
https://www.bitdefender.com/business/sup…	(empty)	empty	Add link text or aria-label
https://login.bitdefender.com/central/lo…	(empty)	empty	Add link text or aria-label
https://gravityzone.bitdefender.com/	(empty)	empty	Add link text or aria-label
https://auth.mdr.bitdefender.com/login	(empty)	empty	Add link text or aria-label
/en-us/business/products/gravityzone-pha…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Gravityzone Phasr
https://www.bitdefender.com/en-us/scuder…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Scuderiaferrari
https://www.bitdefender.com/en-us/news/b…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Bitdefender Completes Acquisition Of Mesh Security
/en-us/business/awards	View all	new tab	Add '(opens in new tab)' to text
/en-us/business/renew-upgrade/	For Business	new tab	Add '(opens in new tab)' to text
https://pan.bitdefender.com/partners/sav…	Join Our Network	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

272 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://www.bitdefender.com/consumer/support/; https://www.bitdefender.com/business/support/; https://login.bitdefender.com/central/login.html?lang=en_US&redirect_url=http…; https://gravityzone.bitdefender.com/; https://auth.mdr.bitdefender.com/login

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

/en-us/business/products/gravityzone-phasr ("Read more"); https://www.bitdefender.com/en-us/scuderiaferrari/ ("Read more"); https://www.bitdefender.com/en-us/news/bitdefender-completes-acquisition-of-m… ("Read more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

/en-us/business/awards; /en-us/business/renew-upgrade/; https://pan.bitdefender.com/partners/save/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.language-banner__decline-button (#142 on page); button.language-banner__decline-button (#151 on page); button.closeVideo (#1708 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Web Manifest

Action

Valid manifest

FIX

Valid manifest

Name present: App

192x192 icon present

PWA Install Criteria Not Installable

Name App ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗

Name App Icons 6 icon(s)

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #ffffff

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

5 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 5 <nav> element(s)

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.

Landmark Structure

Action

8 landmarks

REVIEW

8 landmarks

No <main> landmark found

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

5 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

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

Heading Hierarchy

18 headings, 2 skip(s)

REVIEW

18 headings, 2 skip(s)

Single H1 present

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Bitdefender is a Global Leader in Cybersecurity
H5 For Consumer skipped
H5 For Small Business
H5 For Enterprise
H3 Introducing Bitdefender GravityZone PHASR
H3 Cybersecurity partner of Ferrari
H3 Bitdefender Completes Acquisition of Mesh Security
H2 Industry Recognition
H2 Already a Customer?
H2 Take the Next Step
H4 Protecting Family and Friends? skipped
H4 Serious About Securing Business?
H4 Competing to Secure Customers?
H4 Ready to Partner?
H3 Bitdefender is a cybersecurity leader delivering best-in-class threat prevention, detection, and response solutions worldwide.
H2 Read the Latest Cybersecurity Insights:
H2 Trusted.Always.
H3 Quick Links

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

22 icon(s) detected

REVIEW

22 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

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 6 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Bitdefender is a Glo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Industry Recognition	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Already a Customer?	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Take the Next Step	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Read the Latest Cybe…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Trusted.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Always.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Introducing Bitdefen…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Cybersecurity partne…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Bitdefender Complete…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Bitdefender is a cyb…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Quick Links	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Bitdefender - Global…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Placeholder	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span For Consumer	4.67:1	4.5:1	#000000	#006EFF	Pass
span All-in-one plans	4.72:1	4.5:1	#000000	#006FFF	Pass
span All-in-one plans	4.72:1	4.5:1	#000000	#006FFF	Pass
a Individual Plans	4.72:1	4.5:1	#000000	#006FFF	Pass
a Family Plans	4.72:1	4.5:1	#000000	#006FFF	Pass
a Ultimate Small Busin…	4.72:1	4.5:1	#000000	#006FFF	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.

A+

Alt Text Quality

All 18 images OK

PASS

All 18 images OK

18 image(s) with good alt text

18 images 18 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) without accessible label

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

Got: <select>

1 controls

0 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
select	select	(none)	none

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

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

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 22 passed

PASS

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Choose Your Country Australia - English België - Nederlands Belgique - Françai… `div.footer-2025__content > div.footer-2025__main > div.footer-2025__bottom-bar > div#footer-2025-lang-list`

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
For Consumer `div.title > div > div#title-e38000addb > h5.cmp-title__text`
Protecting Family and Friends? `div.column-wrapper > div.we-col-four > div.text-wrap > h4.default`
X (Twitter) DM scam targets users with fake ‘Vote for me’ links sent from hacke… `div.col-outer > div.col-wrap > div.text-wrap > h4`

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.ua-android `html.ua-android`

These items highlight common accessibility best practices.

○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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[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

●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 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

●Touch targets have sufficient size and spacing.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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

○`[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

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○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.

○Elements with visible text labels have matching accessible names.

○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.