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 6 REVIEW 5 FIX

Link & Button Quality

Action

3 issue(s) across 33 links and 1 buttons

FIX

3 issue(s) across 33 links and 1 buttons

2 link(s) with no accessible text

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

Got: https://www.virtualmin.com/changelog/virtualmin-8.1.0-released/; #virtualmin-intro

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://www.virtualmin.com/account/"]

3 link(s) open in new tab without warning

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

Got: https://github.com/virtualmin; https://t.me/virtualmin; https://youtube.com/virtualmin

1 button(s) with no accessible text

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

Got: button#theme-toggle

27 link(s) with descriptive text

33 links

2 empty

0 generic text

3 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.virtualmin.com/changelog/vir…	(empty)	empty	Add link text or aria-label
#virtualmin-intro	(empty)	empty	Add link text or aria-label
https://www.virtualmin.com/account/	My Account	img no alt	Add alt attribute to the image
https://github.com/virtualmin	GitHub	new tab	Add '(opens in new tab)' to text
https://t.me/virtualmin	Telegram	new tab	Add '(opens in new tab)' to text
https://youtube.com/virtualmin	YouTube	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

27 links and buttons have descriptive text

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

https://www.virtualmin.com/changelog/virtualmin-8.1.0-released/; #virtualmin-intro

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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://www.virtualmin.com/account/"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://github.com/virtualmin; https://t.me/virtualmin; https://youtube.com/virtualmin

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#theme-toggle

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

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-9uj6ud

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.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

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

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

Manifest contains invalid JSON.

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

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

Heading Hierarchy

9 headings, 1 skip(s)

REVIEW

9 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 (empty)
H2 Virtualmin Features
H2 Why Virtualmin?
H4 Flexibility where you need it skipped
H4 Ease of use where you want it
H4 Maximize efficiency
H4 Extensible, scriptable, customizable
H4 Command line friendly
H4 Professional support

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Alt Text Quality

Action

2 of 3 images have issues

REVIEW

2 of 3 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image-in-link without alt text

An image inside a link with no alt creates an empty link.

1 decorative image(s) correctly marked

3 images 1 decorative 2 missing

Issue	Count
missing	2 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Favicon & Branding

5 icon(s) detected

REVIEW

5 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 Missing

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #2e2e33 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

title Virtualmin — Open Source Web Hosting C…

1.05:1

#000000

#00071C

needs 4.5:1 (normal text)

16px · top of page (header area)

span Advanced web hosting control panel

1.06:1

#000000

#000923

needs 4.5:1 (normal text)

16px · top of page (header area)

span Run WordPress at scale with full control…

1.08:1

#000000

#000B2A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Try Virtualmin

1.10:1

#000000

#000D32

needs 4.5:1 (normal text)

16px · top of page (header area)

a What is WP Workbench?

1.13:1

#000000

#010F3A

needs 4.5:1 (normal text)

16px · above the fold

div 20Y+

1.15:1

#000000

#021041

needs 4.5:1 (normal text)

16px · above the fold

div Of trusted service

1.17:1

#000000

#021046

needs 4.5:1 (normal text)

16px · above the fold

div 1M+

1.18:1

#000000

#02114B

needs 4.5:1 (normal text)

16px · above the fold

div Managed domains

1.20:1

#000000

#031150

needs 4.5:1 (normal text)

16px · above the fold

div 200K+

1.22:1

#000000

#031155

needs 4.5:1 (normal text)

16px · above the fold

div Active users

1.24:1

#000000

#04125A

needs 4.5:1 (normal text)

16px · above the fold

span DNS

1.25:1

#000000

#03125E

needs 4.5:1 (normal text)

16px · above the fold

div Local DNS and cloud DNS (Route 53, Cloud…

1.27:1

#000000

#031361

needs 4.5:1 (normal text)

16px · above the fold

span SSL

1.27:1

#000000

#021165

needs 4.5:1 (normal text)

16px · mid-page

div Auto-renewed SSL from Let's Encrypt, Zer…

1.28:1

#000000

#021068

needs 4.5:1 (normal text)

16px · mid-page

span Web

1.28:1

#000000

#020E6B

needs 4.5:1 (normal text)

16px · mid-page

div Apache or Nginx with HTTP/2, multiple PH…

1.28:1

#000000

#020C6F

needs 4.5:1 (normal text)

16px · mid-page

div Manage WordPress core, plugins, themes, …

1.29:1

#000000

#020A72

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Virtualmin Features	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 Why Virtualmin?	19.26:1	3.0:1	#000000	#F5F5F5	Pass
title Virtualmin — Open …	1.05:1	4.5:1	#000000	#00071C	Fail
span Advanced web hosting…	1.06:1	4.5:1	#000000	#000923	Fail
span Run WordPress at sca…	1.08:1	4.5:1	#000000	#000B2A	Fail
a Try Virtualmin	1.10:1	4.5:1	#000000	#000D32	Fail
a What is WP Workbench…	1.13:1	4.5:1	#000000	#010F3A	Fail
div 20Y+	1.15:1	4.5:1	#000000	#021041	Fail
div Of trusted service	1.17:1	4.5:1	#000000	#021046	Fail
div 1M+	1.18:1	4.5:1	#000000	#02114B	Fail
div Managed domains	1.20:1	4.5:1	#000000	#031150	Fail
div 200K+	1.22:1	4.5:1	#000000	#031155	Fail
div Active users	1.24:1	4.5:1	#000000	#04125A	Fail
span DNS	1.25:1	4.5:1	#000000	#03125E	Fail
div Local DNS and cloud …	1.27:1	4.5:1	#000000	#031361	Fail
span SSL	1.27:1	4.5:1	#000000	#021165	Fail
div Auto-renewed SSL fro…	1.28:1	4.5:1	#000000	#021068	Fail
span Web	1.28:1	4.5:1	#000000	#020E6B	Fail
div Apache or Nginx with…	1.28:1	4.5:1	#000000	#020C6F	Fail
div Manage WordPress cor…	1.29:1	4.5:1	#000000	#020A72	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.

Lighthouse Accessibility Audits

Score 88/100 — 3 failing, 18 passed

REVIEW

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Enter Full Screen (Alt + F) `div.chocolat-center > div.chocolat-image-canvas > div.chocolat-image-wrapper > div.screen-full-container`

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
Flexibility where you need it `div.post-content > div.docs-cards-container > div.docs-card > h4.docs-title`

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
section.index-page-intro-container > div.index-page-intro-container-inner > div.index-page-intro-container-inner-content > a.index-page-intro-container-inner-content-satellite `section.index-page-intro-container > div.index-page-intro-container-inner > div.index-page-intro-container-inner-content > a.index-page-intro-container-inner-content-satellite`
section.index-page-intro-container > div.index-page-intro-container-inner > div.index-page-intro-container-inner-content > a.index-page-intro-container-inner-content-alien `section.index-page-intro-container > div.index-page-intro-container-inner > div.index-page-intro-container-inner-content > a.index-page-intro-container-inner-content-alien`

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

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

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

●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

●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

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

●Document has a main landmark.

●All heading elements contain content.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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 have all required `[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

○`[role]` values are valid

○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

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

○Uses ARIA roles only on compatible elements

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

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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