Skip to content
https://zimbra.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
6
REVIEW
6
PASS
1
INFO
0
Checks
13
1 PASS 6 REVIEW 6 FIX
F
Form Accessibility
Action
6 of 8 controls have issues
FIX
6 of 8 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">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s">; <input type="text" name="s">; <input type="email" name="email" id="email-9b4d77cf-0b8b-4201-9263-9bf8f06d410b">
Info::
2 control(s) properly labeled
8 controls
2 labeled
3 placeholder only
3 unlabeled
ControlTypeLabelMethod
#gdpr_consent-9b4d77cf-0b8b-4201-9263-9bf8f06d410bcheckboxnone
#trustarc-lang-selectselectSelect languagefor/id
#email-9b4d77cf-0b8b-4201-9263-9bf8f06d410bemail(Business Email*)placeholder only
stext(Search...)placeholder only
stext(Search...)placeholder only
inputsubmit(none)none
inputsubmit(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">

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="text" name="s">; <input type="text" name="s">; <input type="email" name="email" id="email-9b4d77cf-0b8b-4201-9263-9bf8f06d410b">

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
No navigation patterns
FIX
No navigation patterns
Info::
3 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 3 <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
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) 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 (missing!) NAV MAIN CONTENTINFO footer

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

C
Alt Text Quality
Action
14 of 162 images have issues
REVIEW
14 of 162 images have issues
Critical::
14 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
42 decorative image(s) correctly marked
Info::
106 image(s) with good alt text
162 images 106 good alt text 42 decorative 14 missing
IssueCount
missing14 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

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 Page not found | Open Standards | Low-Risk Alternative | Data Sovereignty | Zimbra ✓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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA 1 pass AA only
h1 Deploy Email and Collaboration
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Your Way. Your Data. Your Rules.
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Blogs
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h2 Stay Safe with Secure Email
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why Zimbra?
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Email and Collaboration. Hosted Your Way…
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trusted by thousands of clients
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get Started with the Right Email Solutio…
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Support Levels
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
24px · bottom of viewport
h2 FAQs
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What’s New in Zimbra?
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Subscribe
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Ready To Make The Switch?
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h3 Trusted Alternative to Technology Giants
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Your Data, Your Choice
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Open Source Transparency
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Scalability Without Compromise
2.16:1
#000000
on
#404450
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient

9 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 Deploy Email and Col…2.16:13.0:1
#000000
#404450
Fail
h1 Your Way. Your Data.…2.16:13.0:1
#000000
#404450
Fail
h1 Blogs2.16:13.0:1
#000000
#404450
Fail
h2 Stay Safe with Secur…2.16:13.0:1
#000000
#404450
Fail
h2 Why Zimbra?2.16:13.0:1
#000000
#404450
Fail
h2 Email and Collaborat…2.16:13.0:1
#000000
#404450
Fail
h2 Trusted by thousands…2.16:13.0:1
#000000
#404450
Fail
h2 Get Started with the…2.16:13.0:1
#000000
#404450
Fail
h2 Support Levels2.16:13.0:1
#000000
#404450
Fail
h2 FAQs2.16:13.0:1
#000000
#404450
Fail
h2 What’s New in Zimb…2.16:13.0:1
#000000
#404450
Fail
h2 Subscribe2.16:13.0:1
#000000
#404450
Fail
h2 Ready To Make The Sw…2.16:13.0:1
#000000
#404450
Fail
h3 Mailboxes Deployed W…4.65:13.0:1
#F6A04B
#404450
Pass
h3 Years of Proven Stab…4.43:13.0:1
#57C389
#404450
Pass
h3 Partners for Localiz…4.77:13.0:1
#4FC7C6
#404450
Pass
h3 Trusted Alternative …2.16:13.0:1
#000000
#404450
Fail
h3 Your Data, Your Choi…2.16:13.0:1
#000000
#404450
Fail
h3 Open Source Transpar…2.16:13.0:1
#000000
#404450
Fail
h3 Scalability Without …2.16:13.0:1
#000000
#404450
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.

C
Lighthouse Accessibility Audits
Action
Score 77/100 — 8 failing, 26 passed
REVIEW
77

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

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
End Users div > div.tabsbutton > ul.resp-tabs-list > li.resp-tab-item
Back-End Features div > div.tabsbutton > ul.resp-tabs-list > li.resp-tab-item

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
End Users div > div.tabsbutton > ul.resp-tabs-list > li.resp-tab-item
Back-End Features div > div.tabsbutton > ul.resp-tabs-list > li.resp-tab-item

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Email: Where Collaboration Starts Intuitive email interface for seamless inbox… div.verticaltabs > div > div.resp-tabs-container > div.tabcontentcontainer

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
Back-End Features div.tabsbutton > ul.resp-tabs-list > li.resp-tab-item > h3

These are opportunities to improve the legibility of your content.

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.tabcontent > div.tabimagewrap > div.pattern > img div.tabcontent > div.tabimagewrap > div.pattern > img

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
End Users Back-End Features div.verticaltabs > div > div.tabsbutton > ul.resp-tabs-list

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `[colspan]` attribute may improve the experience for screen reader users. Learn more about captions.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SUPPORT TYPES Premier Standard In addition to Standard Business Hours support… div.supportOfferings > div.column > div.tablewrap > table.support
PREMIER ADD ONS Elite Prioritized organizational relationship with Zimbra, in… div.supportOfferings > div.column > div.tablewrap > table.support

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FEATURES Standard Professional Email, Contacts & Calendar Sharing & Dele… div.parallaxcontent > div.blockcontent > div.tablewrap > table.get_started
○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
●Buttons have an accessible name
●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.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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 are distinguishable without relying on color.
●Links have a discernible name
●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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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.
○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.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<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.
A
Heading Hierarchy
48 headings
PASS
48 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Deploy Email and Collaboration
  • H1 Your Way. Your Data. Your Rules. duplicate H1
  • H2 Stay Safe with Secure Email
  • H3 Mailboxes Deployed Worldwide
  • H3 Years of Proven Stability
  • H3 Partners for Localized Support
  • H2 Why Zimbra?
  • H3 Trusted Alternative to Technology Giants
  • H3 Your Data, Your Choice
  • H3 Open Source Transparency
  • H3 Scalability Without Compromise
  • H3 Open Standards = Zero Lock-In
  • H2 Email and Collaboration. Hosted Your Way.
  • H3 End Users
  • H3 Back-End Features
  • H3 End Users
  • H4 Email: Where Collaboration Starts
  • H4 Chat: Connect Instantly, Securely
  • H4 Calendar: Stay organized, in sync — and on the move
  • H4 Briefcase: File Management Simplified
  • H4 Office: Create, Edit, and Collaborate
  • H4 Anywhere, Anytime Access: Web • Mobile (ActiveSync) • Desktop (Offline)
  • H3 Back-End Features
  • H4 Admin Capabilities
  • H2 Trusted by thousands of clients
  • H2 Get Started with the Right Email Solution
  • H3 Features
  • H4 Expanded Features
  • H2 Support Levels
  • H3 Support Types
  • H3 Premier Add Ons
  • H2 FAQs
  • H3 What is Zimbra?
  • H3 Which platforms and devices are compatible with Zimbra?
  • H3 Do I need a commercial license?
  • H3 How does Zimbra ensure secure email communication?
  • H3 Is Zimbra GDPR and HIPAA compliant?
  • H3 How does Zimbra handle Backup & Restore?
  • H3 How do I get started on Zimbra?
  • H3 Is Zimbra mobile-friendly?
  • H3 Does Zimbra have integrated messaging?
  • H3 How scalable is Zimbra?
  • H3 How can I renew support?
  • H3 How do I get support?
  • H1 Blogs duplicate H1
  • H2 What’s New in Zimbra?
  • H2 Subscribe
  • H2 Ready To Make The Switch?

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

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

Send Feedback