Skip to content
https://haproxy.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
9
REVIEW
2
PASS
2
INFO
0
Checks
13
2 PASS 2 REVIEW 9 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) 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.

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

F
Alt Text Quality
Action
7 of 7 images have issues
FIX
7 of 7 images have issues
Critical::
7 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
6 image-in-link without alt text
An image inside a link with no alt creates an empty link.
7 images 7 missing
IssueCount
missing7 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

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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 Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 52/100 — 8 failing, 9 passed
FIX
52

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.

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
IPv4 tbody > tr > td > span.netw
Your computer is not IPv6-ready tbody > tr > td > span.v6warn
HAProxy 3.3.0 release td > p > b > font
HAProxy 3.2.0 release td > p > b > font

These are opportunities to improve the legibility of your content.

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 html

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

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
tbody > tr > td > img tbody > tr > td > img
center > p > a > img center > p > a > img
center > p > a > img center > p > a > img
center > p > a > img center > p > a > img

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
td > center > p > a td > center > p > a
td > center > p > a td > center > p > a
td > center > p > a td > center > p > a

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
Two vulnerabilities affecting some deep parts of the QUIC parsing were reported… tbody > tr > td > ul
It's no news that many users have been hit by the massive performance cost caus… tbody > tr > td > ul
This stable release as usual introduces significant advancements in performance… tbody > tr > td > ul
This LTS release improves in a lot of areas. First, many improvements were made… tbody > tr > td > ul
contact HAProxy Technologies to hire some professional services or subscribe a … tbody > tr > td > ol
mailing-list : haproxy@formilux.org Read the list archives on mail-archive Read… tbody > tr > td > ul
irc://irc.libera.chat/%23haproxy tbody > tr > td > ul
https://slack.haproxy.org/ tbody > tr > td > ul

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

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Quick News tbody > tr > td > a
Recent News tbody > tr > td > a
Description tbody > tr > td > a
Performance tbody > tr > td > a
Reliability tbody > tr > td > a
Security tbody > tr > td > a
Documentation tbody > tr > td > a
Project on GitHub tbody > tr > td > a
Download sources / doc tbody > tr > td > a
Packages / Images / Distros tbody > tr > td > a
Live demo tbody > tr > td > a
They use it! tbody > tr > td > a
Enterprise Features tbody > tr > td > a
Third party extensions tbody > tr > td > a
Commercial Support tbody > tr > td > a
Contacts tbody > tr > td > a
External links tbody > tr > td > a
Discussions tbody > tr > td > a
Slack channel tbody > tr > td > a
Mailing list tbody > tr > td > a
Coding style tbody > tr > td > a
Open Issues tbody > tr > td > a
Known bugs tbody > tr > td > a
Signing keys tbody > tr > td > a
HATop: Ncurses Interface tbody > tr > td > a
Herald: load feedback agent tbody > tr > td > a
haproxystats: stats collection tbody > tr > td > a
Alpine-based Docker images tbody > tr > td > a
Debian-based Docker images tbody > tr > td > a
RHEL-based Docker images tbody > tr > td > a
Debian/Ubuntu packages tbody > tr > td > a
Performance packages tbody > tr > td > a
3.4-dev tbody > tr > td > a
3.4-dev9 tbody > tr > td > a
2026-04-15 tbody > tr > td > a
3.3 tbody > tr > td > a
3.3.6 tbody > tr > td > a
2026-03-19 tbody > tr > td > a
3.2 tbody > tr > td > a
3.2.15 tbody > tr > td > a
2026-03-19 tbody > tr > td > a
3.0 tbody > tr > td > a
3.0.19 tbody > tr > td > a
2026-03-19 tbody > tr > td > a
2.8 tbody > tr > td > a
2.8.20 tbody > tr > td > a
2026-03-20 tbody > tr > td > a
2.6 tbody > tr > td > a
2.6.25 tbody > tr > td > a
2026-03-20 tbody > tr > td > a
2.4 tbody > tr > td > a
2.4.31 tbody > tr > td > a
2026-03-09 tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a
Web tbody > tr > td > a

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 html

These items highlight common accessibility best practices.

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
Branch Release date End of life Latest version Changelog Links 3.4-dev ~2026-Q2… td > a > p > table
dev 3.3 3.2 3.1 3.0 2.9 2.8 2.7 2.6 2.5 2.4 2.3 2.2 2.1 2.0 1.9 1.8 1.7 1.6 1.… td > a > p > table
○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>`
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Identical links have the same purpose.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[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
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○`[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
○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
○`<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.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA 1 pass AA only
td Mirror Sites:
3.10:1
#000000
on
#4C5D6E
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
h2 The Reliable, High P…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Quick links13.08:13.0:1
#000000
#CCCCCC
Pass
title HAProxy - The Reliab…21.00:14.5:1
#000000
#FFFFFF
Pass
a HAProxy21.00:14.5:1
#000000
#FFFFFF
Pass
td Mirror Sites:3.10:14.5:1
#000000
#4C5D6E
Fail
a Master16.06:14.5:1
#000000
#DDE6B5
Pass
td Language:21.00:14.5:1
#000000
#FFFFFF
Pass
a English21.00:14.5:1
#000000
#FFFFFF
Pass
b Quick News14.78:13.0:1
#000000
#FFD0A0
Pass
a Recent News21.00:14.5:1
#000000
#FFFFFF
Pass
a Description5.93:14.5:1
#000000
#718BA4
Pass
a Performance8.53:14.5:1
#000000
#A5A5A5
Pass
a Reliability16.98:14.5:1
#000000
#E7E7E7
Pass
a Security10.36:14.5:1
#000000
#B6B6B6
Pass
b Documentation21.00:13.0:1
#000000
#FFFFFF
Pass
b Project on GitHub21.00:13.0:1
#000000
#FFFFFF
Pass
b Download sources / d…21.00:13.0:1
#000000
#FFFFFF
Pass
b Packages / Images / …21.00:13.0:1
#000000
#FFFFFF
Pass
b Live demo10.27:13.0:1
#000000
#FF9999
Pass
b They use it!18.59:13.0:1
#000000
#F1F1F1
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+
Heading Hierarchy
12 headings
PASS
12 headings
Info::
Single H1 present
  • H1 HAProxy
  • H2 The Reliable, High Performance TCP/HTTP Load Balancer
  • H3 Quick links
  • H3 Latest versions
  • H3 Quick News
  • H3 Description
  • H3 Performance
  • H3 Reliability - keeping high-traffic sites online since 2002
  • H3 Security - Hardened by default
  • H3 Complete Download Matrix
  • H3 Commercial Support and availability
  • H3 Contacts
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
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.

Send Feedback