Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 4 REVIEW 7 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

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

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-hnub2r

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://mailenable.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://mailenable.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Heading Hierarchy

12 headings, 1 skip(s)

REVIEW

12 headings, 1 skip(s)

Multiple H1 headings (4 found)

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

Heading level skipped: H1 → H3 (missing H2)

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

H2 World's Most Popular Windows Mail Server
H3 Microsoft Exchange Alternative
H3 Affordable Unlimited User Licensing
H3 Highest Level of Outlook Integration
H1 Standard Edition (FREE)
H1 Professional Edition duplicate H1
H1 Enterprise Edition duplicate H1
H1 Enterprise Premium duplicate H1
H3 Our Mailing List skipped
H3 Latest Version
H3 Our Global Partners
H2 Follow Us

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

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

2 control(s) without accessible label

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

Got: <input type="text" name="search_string" id="site_search">; <input type="text" name="email" id="email">

2 controls

0 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#site_search	text	(none)	none
#email	text	(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

Link & Button Quality

Action

6 issue(s) across 163 links and 0 buttons

REVIEW

6 issue(s) across 163 links and 0 buttons

6 link(s) with no accessible text

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

Got: /; /version10/; /mailenable-mail-server.asp; /outlook-collaboration.asp; /mobile-contacts-calendar-tasks.asp; /partners_list.asp?Type=Resellers

14 link(s) open in new tab without warning

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

Got: /onlineservices; /video-gallery.asp; /webmail_demo_note.asp; https://www.mailenable.com/rss/article.asp?Source=RSSADMIN&ID=MAILENABLEVERSI…; https://www.mailenable.com/rss/article.asp?Source=RSSADMIN&ID=MAILENABLEVERSI…; https://www.mailenable.com/rss/article.asp?Source=RSSADMIN&ID=SECURITY1055; /plesk; https://www.24x.com/; https://www.trisoft.co.uk/; https://hostingcontroller.com/ (+4 more)

143 link(s) with descriptive text

163 links

6 empty

0 generic text

14 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
/onlineservices	Online Services	new tab	Add '(opens in new tab)' to text
/version10/	(empty)	empty	Add link text or aria-label
/mailenable-mail-server.asp	(empty)	empty	Add link text or aria-label
/outlook-collaboration.asp	(empty)	empty	Add link text or aria-label
/mobile-contacts-calendar-tasks.asp	(empty)	empty	Add link text or aria-label
/partners_list.asp?Type=Resellers	(empty)	empty	Add link text or aria-label
/video-gallery.asp	NEW! View Online Video Tutoria…	new tab	Add '(opens in new tab)' to text
/webmail_demo_note.asp	View Latest Version Online Dem…	new tab	Add '(opens in new tab)' to text
https://www.mailenable.com/rss/article.a…	16 April 2026	new tab	Add '(opens in new tab)' to text
https://www.mailenable.com/rss/article.a…	18 March 2026	new tab	Add '(opens in new tab)' to text
https://www.mailenable.com/rss/article.a…	18 Mar 2026	new tab	Add '(opens in new tab)' to text
/plesk	Parallels	new tab	Add '(opens in new tab)' to text
https://www.24x.com/	24X	new tab	Add '(opens in new tab)' to text
https://www.trisoft.co.uk/	Trisoft	new tab	Add '(opens in new tab)' to text
https://hostingcontroller.com/	Hosting Controller	new tab	Add '(opens in new tab)' to text
https://www.aptum.com/	Aptum Hosting	new tab	Add '(opens in new tab)' to text
https://www.gurucube.com/	Gurucube Hosting Solutions & W…	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/mailena…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/mailenable/	FaceBook	new tab	Add '(opens in new tab)' to text

143 links and buttons have descriptive text

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

/; /version10/; /mailenable-mail-server.asp; /outlook-collaboration.asp; /mobile-contacts-calendar-tasks.asp; /partners_list.asp?Type=Resellers

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

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

/onlineservices; /video-gallery.asp; /webmail_demo_note.asp; https://www.mailenable.com/rss/article.asp?Source=RSSADMIN&ID=MAILENABLEVERSI…; https://www.mailenable.com/rss/article.asp?Source=RSSADMIN&ID=MAILENABLEVERSI…; https://www.mailenable.com/rss/article.asp?Source=RSSADMIN&ID=SECURITY1055; /plesk; https://www.24x.com/; https://www.trisoft.co.uk/; https://hostingcontroller.com/ (+4 more)

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 7 fail WCAG AA

REVIEW

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

13 pass 7 fail WCAG AA 1 pass AA only

title Windows Mail Server, Email Server Softwa…

2.62:1

#000000

#31546E

needs 4.5:1 (normal text)

16px · top of page (header area)

a Online Services

2.07:1

#000000

#27445C

needs 4.5:1 (normal text)

16px · top of page (header area)

a Mail Server

1.66:1

#000000

#1D354A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Overview

2.15:1

#000000

#254667

needs 4.5:1 (normal text)

16px · top of page (header area)

a Webmail

2.91:1

#000000

#425A6B

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Anti-spam & Security

1.85:1

#000000

#1F3C5A

needs 4.5:1 (normal text)

16px · above the fold

a Administration

1.88:1

#000000

#203D5B

needs 4.5:1 (normal text)

16px · above the fold

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)

Element	Ratio	Required	FG	BG	Result
h2 World's Most Popular…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Follow Us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Microsoft Exchange A…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Affordable Unlimited…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Highest Level of Out…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Our Mailing List	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Latest Version	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Our Global Partners	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Windows Mail Server,…	2.62:1	4.5:1	#000000	#31546E	Fail
a Online Services	2.07:1	4.5:1	#000000	#27445C	Fail
a Mail Server	1.66:1	4.5:1	#000000	#1D354A	Fail
a Overview	2.15:1	4.5:1	#000000	#254667	Fail
a Features	5.69:1	4.5:1	#000000	#858585	Pass
a New Features	13.58:1	4.5:1	#000000	#C8D1D9	Pass
a Outlook Collaboratio…	17.94:1	4.5:1	#000000	#EDEDED	Pass
a Mobile Solutions	19.60:1	4.5:1	#000000	#F7F7F7	Pass
a Exchange ActiveSync	18.76:1	4.5:1	#000000	#F2F2F2	Pass
a Webmail	2.91:1	4.5:1	#000000	#425A6B	Fail
a Anti-spam & Security	1.85:1	4.5:1	#000000	#1F3C5A	Fail
a Administration	1.88:1	4.5:1	#000000	#203D5B	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.

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

Lighthouse Accessibility Audits

Score 94/100 — 1 failing, 16 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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.ui-mobile `html.ui-mobile`

These are opportunities to improve the interpretation of your content by users in different locales.

○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

●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-hidden="true"]` elements do not contain focusable descendents

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

○ARIA attributes are used as specified for the element's role

○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 use only permitted ARIA attributes

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○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 a valid value for its `[lang]` attribute

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

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

○Identical links have the same purpose.

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