Skip to content
https://whmcs.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 FIX
D
Alt Text Quality
Action
9 of 13 images have issues
FIX
9 of 13 images have issues
Critical::
9 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
4 image(s) with good alt text
13 images 4 good alt text 9 missing
IssueCount
missing9 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

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) 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.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV 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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Oops something went wrong! | WHMCS ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 11 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Web Hosting Automati…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 All the tools you ne…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Same WHMCS. Zero Set…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Let WHMCS automate y…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Product21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Uses21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Support21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Company21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Resources21.00:13.0:1
#000000
#FFFFFF
Pass
title WHMCS | Web Hosting …5.12:14.5:1
#000000
#3D82BC
Pass
a Product5.12:14.5:1
#000000
#3D82BC
Pass
a Feature Tour5.12:14.5:1
#000000
#3D82BC
Pass
a WHMCS Cloud5.12:14.5:1
#000000
#3D82BC
Pass
span New5.12:14.5:1
#000000
#3D82BC
Pass
a Web Hosting5.12:14.5:1
#000000
#3D82BC
Pass
a Sell Domains5.12:14.5:1
#000000
#3D82BC
Pass
a Billing Automation5.12:14.5:1
#000000
#3D82BC
Pass
a Support Tools5.12:14.5:1
#000000
#3D82BC
Pass
a cPanel & WHM™5.12:14.5:1
#000000
#3D82BC
Pass
span New5.12:14.5:1
#000000
#3D82BC
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.

C
Lighthouse Accessibility Audits
Action
Score 72/100 — 8 failing, 22 passed
REVIEW
72

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
nav.navbar > div.container > div.navbar-header > button.navbar-toggle nav.navbar > div.container > div.navbar-header > button.navbar-toggle

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
main.main > section.section > div.container > img main.main > section.section > div.container > img
main.main > section.section > div.container > img main.main > section.section > div.container > img
div.footer__bottom-inner > div.footer__bottom-inner__item > a.cpanel-partner-badge > img div.footer__bottom-inner > div.footer__bottom-inner__item > a.cpanel-partner-badge > 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
div.container > div.footer__bottom-inner > div.footer__bottom-inner__item > a.cpanel-partner-badge div.container > div.footer__bottom-inner > div.footer__bottom-inner__item > a.cpanel-partner-badge

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
All the tools you need to start a web hosting business today. main.main > section.section > div.container > h2
Launch Now section.section > div.container > center > a.cust-green-btn
Matt Parkinson div.flickity-viewport > div.flickity-slider > div.carousel-cell > h5
Trusted by over 35,000 customers in over 200 countries main.main > section.section > div.container > p.lead
Tour div.col-sm-2 > ul.list-unstyled > li > a
Services div.col-sm-2 > ul.list-unstyled > li > a
Integrations div.col-sm-2 > ul.list-unstyled > li > a
What's New div.col-sm-2 > ul.list-unstyled > li > a
Pricing div.col-sm-2 > ul.list-unstyled > li > a
Web Hosting div.col-sm-2 > ul.list-unstyled > li > a
Domain Registrars div.col-sm-2 > ul.list-unstyled > li > a
Software Developers div.col-sm-2 > ul.list-unstyled > li > a
Cloud Hosting div.col-sm-2 > ul.list-unstyled > li > a
Web Designers div.col-sm-2 > ul.list-unstyled > li > a
ISP Billing div.col-sm-2 > ul.list-unstyled > li > a
Technical Support div.col-sm-2 > ul.list-unstyled > li > a
Community Forums div.col-sm-2 > ul.list-unstyled > li > a
Tutorials & Guides div.col-sm-2 > ul.list-unstyled > li > a
Documentation div.col-sm-2 > ul.list-unstyled > li > a
Contact Us div.col-sm-2 > ul.list-unstyled > li > a
About Us div.col-sm-2 > ul.list-unstyled > li > a
Blog div.col-sm-2 > ul.list-unstyled > li > a
Customers div.col-sm-2 > ul.list-unstyled > li > a
Jobs We're hiring! div.col-sm-2 > ul.list-unstyled > li > a
We're hiring! ul.list-unstyled > li > a > span.label
Contact div.col-sm-2 > ul.list-unstyled > li > a
Free Tools div.col-xs-6 > ul.list-unstyled > li > a
Marketplace div.col-xs-6 > ul.list-unstyled > li > a
Partners div.col-xs-6 > ul.list-unstyled > li > a
Download div.col-xs-6 > ul.list-unstyled > li > a
Feature Requests div.col-xs-6 > ul.list-unstyled > li > a
Developer Portal div.col-xs-6 > ul.list-unstyled > li > a
License Verification div.col-xs-6 > ul.list-unstyled > li > a
Media Resources div.col-xs-6 > ul.list-unstyled > li > a
Affiliate Program div.col-xs-6 > ul.list-unstyled > li > a
Reseller Program div.col-xs-6 > ul.list-unstyled > li > a
Responsible Disclosure div.col-xs-6 > ul.list-unstyled > li > a
The World's Leading Web Hosting Automation Platform Registered in England & Wal… div.container > div.footer__bottom-inner > div.footer__bottom-inner__item > p
About div.footer__bottom-inner__item > ul.content-nav > li.content-nav__item > a.content-nav__link
Privacy Policy div.footer__bottom-inner__item > ul.content-nav > li.content-nav__item > a.content-nav__link
Terms of Service div.footer__bottom-inner__item > ul.content-nav > li.content-nav__item > a.content-nav__link
Legal div.footer__bottom-inner__item > ul.content-nav > li.content-nav__item > a.content-nav__link
Contact div.footer__bottom-inner__item > ul.content-nav > li.content-nav__item > a.content-nav__link
Copyright © 2026 WHMCS Limited. All rights reserved. div.container > div.footer__bottom-inner > div.footer__bottom-inner__item > p
Accept All footer#uc-cmp-footer > div.buttons > div.buttons-row > button#accept
Deny footer#uc-cmp-footer > div.buttons > div.buttons-row > button#deny

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Press for Accessibility for blind people who use screen readers div#INDquickAccess > ul > li > button.INDshortcutBtn
Press for Accessibility menu div#INDquickAccess > ul > li > button

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
Matt Parkinson div.flickity-viewport > div.flickity-slider > div.carousel-cell > h5

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
Integrations div.col-sm-2 > ul.list-unstyled > li > a
What's New div.col-sm-2 > ul.list-unstyled > li > a
Feature Requests div.col-xs-6 > ul.list-unstyled > li > a
Developer Portal div.col-xs-6 > ul.list-unstyled > li > a
Media Resources div.col-xs-6 > ul.list-unstyled > li > a
Affiliate Program div.col-xs-6 > ul.list-unstyled > li > a
Reseller Program div.col-xs-6 > ul.list-unstyled > li > a

These items highlight common accessibility best practices.

○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
●`[accesskey]` values are unique
●`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-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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching 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.
○`<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.
○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
Heading Hierarchy
19 headings, 1 skip(s)
PASS
19 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Web Hosting Automation Made Easy
  • H2 All the tools you need to start a web hosting business today.
  • H2 Same WHMCS. Zero Setup.
  • H2 Let WHMCS automate your business
  • H4 Save Time skipped
  • H4 Automate Billing
  • H4 Web & Domains
  • H4 Support Tools
  • H4 Developer Friendly
  • H4 Secure & Scalable
  • H5 Matt Parkinson
  • H5 Steve Amstad
  • H5 Phil Williams
  • H5 Nick Lea
  • H3 Product
  • H3 Uses
  • H3 Support
  • H3 Company
  • H3 Resources

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

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