Skip to content
https://haproxy.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
6 landmarks
FIX
6 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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" MAIN (missing!) CONTENTINFO footer

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

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

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
Alt Text Quality
8 of 35 images have issues
REVIEW
8 of 35 images have issues
Warning::
8 image(s) with filename as alt text
Info::
3 decorative image(s) correctly marked
Info::
24 image(s) with good alt text
35 images 24 good alt text 3 decorative 8 generic
IssueCount
filename8 image(s)
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 404 - Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Privacy Settings
1.05:1
#000000
on
#06080E
needs 3.0:1 (large text)
24px · top of page (header area)
h2 Watch HAProxy success stories from indus…
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 KubeCon Amsterdam was huge. Here's what …
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Learn why we are G2's top-ranked solutio…
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Do more with
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 HAProxy Enterprise
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 HAProxy Fusion Control Plane
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 HAProxy Edge
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 World-class experience
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trusted solutions from the experts in
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Powering the future of secure applicatio…
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Real experiences, better solutions
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 See how it works in practice
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
24px · bottom of viewport
h3 High-performance traffic management at m…
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Next-gen security with threat intelligen…
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Uptime for mission-critical applications
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Simplify Kubernetes on-premises or in th…
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Incredible technology
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Open source and independent
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Relentless customer focus
1.02:1
#000000
on
#04010D
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Privacy Settings1.05:13.0:1
#000000
#06080E
Fail
h2 Watch HAProxy succes…1.02:13.0:1
#000000
#04010D
Fail
h2 KubeCon Amsterdam wa…1.02:13.0:1
#000000
#04010D
Fail
h2 Learn why we are G2'…1.02:13.0:1
#000000
#04010D
Fail
h2 Do more with1.02:13.0:1
#000000
#04010D
Fail
h2 HAProxy Enterprise1.02:13.0:1
#000000
#04010D
Fail
h2 HAProxy Fusion Contr…1.02:13.0:1
#000000
#04010D
Fail
h2 HAProxy Edge1.02:13.0:1
#000000
#04010D
Fail
h2 World-class experien…1.02:13.0:1
#000000
#04010D
Fail
h2 Trusted solutions fr…1.02:13.0:1
#000000
#04010D
Fail
h2 Powering the future …1.02:13.0:1
#000000
#04010D
Fail
h2 Real experiences, be…1.02:13.0:1
#000000
#04010D
Fail
h2 See how it works in …1.02:13.0:1
#000000
#04010D
Fail
h3 High-performance tra…1.02:13.0:1
#000000
#04010D
Fail
h3 Next-gen security wi…1.02:13.0:1
#000000
#04010D
Fail
h3 Uptime for mission-c…1.02:13.0:1
#000000
#04010D
Fail
h3 Simplify Kubernetes …1.02:13.0:1
#000000
#04010D
Fail
h3 Incredible technolog…1.02:13.0:1
#000000
#04010D
Fail
h3 Open source and inde…1.02:13.0:1
#000000
#04010D
Fail
h3 Relentless customer …1.02:13.0:1
#000000
#04010D
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+
Heading Hierarchy
31 headings
PASS
31 headings
Info::
Single H1 present
  • H2 Privacy Settings
  • H1 Powering the world's busiest websites and applications
  • H2 Watch HAProxy success stories from industry leaders at HAProxyConf
  • H2 KubeCon Amsterdam was huge. Here's what happened
  • H2 Learn why we are G2's top-ranked solution
  • H2 Do more with HAProxy One
  • H2 HAProxy Enterprise
  • H2 HAProxy Fusion Control Plane
  • H2 HAProxy Edge
  • H2 World-class experience
  • H2 Trusted solutions from the experts in application delivery
  • H3 High-performance traffic management at massive scale
  • H3 Next-gen security with threat intelligence
  • H3 Uptime for mission-critical applications
  • H3 Simplify Kubernetes on-premises or in the cloud
  • H2 Powering the future of secure application delivery
  • H3 Incredible technology
  • H3 Open source and independent
  • H3 Relentless customer focus
  • H2 Real experiences, better solutions
  • H3 Data informed decision making: Roblox use case for more metrics
  • H3 Modernizing LinkedIn’s traffic stack
  • H3 Load balancing and high availability on Postgres using HAProxy
  • H3 Handling 80 petabytes a month: autoscaling with traffic volume to protect revenue and reputation
  • H3 Load balancers at DigitalOcean
  • H3 Inside the GitHub load balancer
  • H3 How we achieved 2 million RPS: HAProxy on Arm processors
  • H2 See how it works in practice
  • H3 Centralized security and management at scale: introducing HAProxy Fusion 2.0
  • H3 Life After Ingress NGINX: A Zero-Stress Migration Guide to HAProxy
  • H3 Discover what's possible
A
Form Accessibility
1 of 6 controls have issues
PASS
1 of 6 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="q">
Info::
5 control(s) properly labeled
6 controls
5 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
functionalcheckboxFunctional Cookies that make the website usable.none
analytics_storagecheckboxAnalytics Help website owners understand how visitors interact with websites.none
ad_storagecheckboxAds Enables advertising related storage.none
ad_user_datacheckboxUser data Consent for sending user data to Google for advertising purposes.none
ad_personalizationcheckboxAd personalization Consent for personalized advertising.none
qsearch(Search HAProxy Technologies...)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="search" name="q">

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

A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 27 passed
PASS
100

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.

○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
●Buttons have an accessible name
●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
●Elements use only permitted ARIA attributes
●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
●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
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○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
○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
○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.
○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.

Send Feedback