Skip to content
https://directadmin.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
7
REVIEW
5
PASS
1
INFO
0
Checks
13
1 PASS 5 REVIEW 7 FIX
F
Form Accessibility
Action
18 of 19 controls have issues
FIX
18 of 19 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="country" id="country">; <input type="text">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Warning::
15 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="client_id">; <input type="password" id="client_password">; <input type="text" name="fname" id="fname">; <input type="text" name="mname" id="mname">; <input type="text" name="lname" id="lname">; <input type="text" name="name" id="name">; <input type="text" name="street" id="street">; <input type="text" name="city" id="city">; <input type="text" name="state" id="state">; <input type="text" name="zip" id="zip"> (+5 more)
Info::
1 control(s) properly labeled
19 controls
1 labeled
15 placeholder only
3 unlabeled
ControlTypeLabelMethod
optionsRadiosradionone
#client_idtext(Login)placeholder only
#client_passwordpassword(Password)placeholder only
#fnametext(First Name)placeholder only
#mnametext(Middle Names)placeholder only
#lnametext(Last Name)placeholder only
#nametext(Business Name)placeholder only
#streettext(Street Address)placeholder only
#citytext(City)placeholder only
#statetext(State/Province)placeholder only
#ziptext(Zip/Postal Code)placeholder only
#phonetext(Phone Number)placeholder only
#emailtext(E-mail)placeholder only
#websitetext(https://Website URL)placeholder only
#commentstextarea(Additional Comments)placeholder only
querytext(Use '%' for wildcards and quotes for "exact phrases")placeholder only
inputtext(none)none
#countryselect(none)none
#g-recaptcha-response-100000textarea(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select name="country" id="country">; <input type="text">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="text" id="client_id">; <input type="password" id="client_password">; <input type="text" name="fname" id="fname">; <input type="text" name="mname" id="mname">; <input type="text" name="lname" id="lname">; <input type="text" name="name" id="name">; <input type="text" name="street" id="street">; <input type="text" name="city" id="city">; <input type="text" name="state" id="state">; <input type="text" name="zip" id="zip"> (+5 more)

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ 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::
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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (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

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
Heading Hierarchy
26 headings, 1 skip(s)
REVIEW
26 headings, 1 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 What‘s next?..
  • H4 Hello...
  • H4 Dear new client...
  • H4 General Info
  • H4 Ease of Use
  • H4 Speed
  • H4 Stability
  • H1 Your business was waiting for this
  • H1 Evolution dark mode is here! duplicate H1
  • H1 A Better Way To Manage Your Server duplicate H1
  • H2 Why DirectAdmin? Five reasons
  • H3 Ease of use
  • H3 Speed
  • H3 Stability
  • H3 Support
  • H3 Price
  • H2 See our software in action
  • H3 Cutting-Edge Technologies
  • H3 Multilingual Interface
  • H2 DirectAdmin for everyone
  • H4 Pricing options skipped
  • H4 Requirements
  • H4 Contact Us
  • H4 Personal Theme
  • H4 Try Our Demo
  • H2 Let's take your server to the next level

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title DirectAdmin Web Control Panel 404 Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
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 2 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Your business was21.00:13.0:1
#000000
#FFFFFF
Pass
h1 waiting for this21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Evolution dark mode …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 A Better Way To21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Manage Your Server21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why21.00:13.0:1
#000000
#FFFFFF
Pass
h2 ? Five reasons21.00:13.0:1
#000000
#FFFFFF
Pass
h2 See our software21.00:13.0:1
#000000
#FFFFFF
Pass
h2 in action21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Let's take your serv…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Ease of use21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Speed21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Stability21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Support21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Price21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cutting-Edge Technol…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Multilingual Interfa…21.00:13.0:1
#000000
#FFFFFF
Pass
title DirectAdmin Web Cont…5.28:14.5:1
#000000
#1889B4
Pass
h4 What‘s next?..5.28:13.0:1
#000000
#1889B4
Pass
p A Client Account is …5.01:14.5:1
#000000
#1485B0
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 87/100 — 5 failing, 23 passed
REVIEW
87

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
LEARN MORE li.text-center > div.desc > div.button > a.btn
LEARN MORE li.text-center > div.desc > div.button > a.btn
LEARN MORE li.text-center > div.desc > div.button > a.btn
LEARN MORE li.text-center > div.desc > div.button > a.btn
LEARN MORE li.text-center > div.desc > div.button > a.btn
Pricing options li.item > div.item-inner > h4.title > a
Requirements li.item > div.item-inner > h4.title > a
Contact Us li.item > div.item-inner > h4.title > a
Personal Theme li.item > div.item-inner > h4.title > a
Try Our Demo li.item > div.item-inner > h4.title > a
Order Now div.col-xs-12 > div.container > div.text-center > a.btn
2020 JBMC Software, M5159-13432 143 ST NW, Edmonton AB, T5L 5A9, Canada. Mon - … div.container > div.row > div.col-md-12 > p.powerBy

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
Pricing options ul.block-grid > li.item > div.item-inner > h4.title

These are opportunities to improve keyboard navigation in your application.

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.no-js html.no-js

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

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
div.col-xs-12 > nav.navbar > div.navbar-header > a.navbar-brand div.col-xs-12 > nav.navbar > div.navbar-header > a.navbar-brand
div.container > ul#five-reasons > li.text-center > a.image div.container > ul#five-reasons > li.text-center > a.image
div.container > ul#five-reasons > li.text-center > a.image div.container > ul#five-reasons > li.text-center > a.image
div.container > ul#five-reasons > li.text-center > a.image div.container > ul#five-reasons > li.text-center > a.image
div.container > ul#five-reasons > li.text-center > a.image div.container > ul#five-reasons > li.text-center > a.image
div.container > ul#five-reasons > li.text-center > a.image div.container > ul#five-reasons > li.text-center > a.image

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.

Best practices

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.no-js html.no-js

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
●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
●`[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
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●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.
●Deprecated ARIA roles were not used
●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
○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 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
○`<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
○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.
○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+
Alt Text Quality
All 11 images OK
PASS
All 11 images OK
Info::
8 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
11 images 3 good alt text 8 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback