Skip to content
https://proxmox.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
66
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
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::
Back-to-top link detected
Info::
1 navigation landmark(s) detected
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 1 <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.
C
Heading Hierarchy
Action
12 headings, 3 skip(s)
REVIEW
12 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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 Simplify your data center
  • H5 NEW: Version 9.1 skipped
  • H2 ProxmoxVirtual Environment
  • H5 NEW: Version 4.1 skipped
  • H2 ProxmoxBackup Server
  • H5 NEW: Version 1.0 skipped
  • H2 ProxmoxDatacenter Manager
  • H2 Proxmox is committed to open source
  • H2 Some of our customers
  • H3 Products
  • H3 Resources
  • H3 Newsletter

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 ▾

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 ▾

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

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Error: 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Proxmox
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Proxmox ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name Proxmox Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
title Proxmox - Powerful open-source server so…
1.09:1
#000000
on
#180C00
needs 4.5:1 (normal text)
16px · top of page (header area)
label Search
2.71:1
#000000
on
#714B07
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

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)
ElementRatioRequiredFGBGResult
h1 Simplify your data c…10.71:13.0:1
#000000
#F7AA11
Pass
h2 Proxmox10.71:13.0:1
#000000
#F7AA11
Pass
h2 Virtual Environment10.71:13.0:1
#000000
#F7AA11
Pass
h2 Proxmox10.71:13.0:1
#000000
#F7AA11
Pass
h2 Backup Server10.71:13.0:1
#000000
#F7AA11
Pass
h2 Proxmox10.71:13.0:1
#000000
#F7AA11
Pass
h2 Datacenter Manager10.71:13.0:1
#000000
#F7AA11
Pass
h2 Proxmox is committed…10.71:13.0:1
#000000
#F7AA11
Pass
h2 Some of our customer…10.71:13.0:1
#000000
#F7AA11
Pass
h3 Products10.71:13.0:1
#000000
#F7AA11
Pass
h3 Resources10.71:13.0:1
#000000
#F7AA11
Pass
h3 Newsletter10.71:13.0:1
#000000
#F7AA11
Pass
title Proxmox - Powerful o…1.09:14.5:1
#000000
#180C00
Fail
label Search2.71:14.5:1
#000000
#714B07
Fail
p Select your language10.71:14.5:1
#000000
#F7AA10
Pass
a English10.71:14.5:1
#000000
#F7AA10
Pass
a German10.71:14.5:1
#000000
#F7AA10
Pass
a Home10.71:14.5:1
#000000
#F7AA10
Pass
span Products10.71:14.5:1
#000000
#F7AA10
Pass
span Proxmox Virtual Envi…10.71:14.5:1
#000000
#F7AA10
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 25 passed
REVIEW
85

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.menu-headers > div.menu-search > div.dropdown > button.btn div.menu-headers > div.menu-search > div.dropdown > button.btn
div.menu-headers > div.offcanvas-menu > nav > button.btn div.menu-headers > div.offcanvas-menu > nav > button.btn

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer-main-left > div > label.switch > input.mod_proxmox4jdarkmode__toggle div.footer-main-left > div > label.switch > input.mod_proxmox4jdarkmode__toggle

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.

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
Learn more div.grid-3-col > div.box-shadow > p.mt-auto > a.button-primary
Learn more div.grid-3-col > div.box-shadow > p.mt-auto > a.button-primary
Learn more div.grid-3-col > div.box-shadow > p.mt-auto > a.button-primary
Get support div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary
Find a partner div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary
See training courses div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary
Read the docs div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary
Read success stories div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary
Get involved div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary
Start contributing div.grid-4-col > div.box-shadow > p.mt-auto > a.button-secondary
Proxmox Datacenter Manager 1.0 div.grid-4-col > div.box-shadow > p > a
Proxmox Backup Server 4.1 div.grid-4-col > div.box-shadow > p > a
Proxmox VE 9.1 available div.grid-4-col > div.box-shadow > p > a
Proxmox Mail Gateway 9.0 div.grid-4-col > div.box-shadow > p > a
See all news div.grid-4-col > div.box-shadow > p.mt-auto > a.button-default
View customers div.grid-2-col > div.partner-description > p > a.button-secondary
Contact us div.wide > div.wide-content > p > a.button-primary
Subscribe div.grid-child > div.mod-listmonk-subscriber > form.form-validate > button.btn
Customize settings div#c-inr > div#c-inr-i > div#c-txt > a.cc-link
Privacy policy div#c-inr > div#c-inr-i > div#c-txt > a.cc-link
Reject all div#cm > div#c-inr > div#c-bns > button#c-s-bn
Accept all div#cm > div#c-inr > div#c-bns > button#c-p-bn

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
NEW: Version 9.1 div > div.grid-3-col > div.box-shadow > h5.new-version-tag
NEW: Version 4.1 div > div.grid-3-col > div.box-shadow > h5.new-version-tag
NEW: Version 1.0 div > div.grid-3-col > div.box-shadow > h5.new-version-tag

These are opportunities to improve keyboard navigation in your application.

○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
●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 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
●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.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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.
○`[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
○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
○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.
○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
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 header NAV "Main Menu EN" MAIN CONTENTINFO footer

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+
Alt Text Quality
All 29 images OK
PASS
All 29 images OK
Info::
20 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
29 images 9 good alt text 20 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#mod-finder-searchword381textSearchfor/id
#mod-finder-searchword381textSearchfor/id
#jform_emailemailEmail *for/id
#jform_agreetermscheckboxI agree with the privacy policy *for/id
inputcheckboxnone
A
Favicon & Branding
6 icon(s) detected
PASS
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback