Skip to content
https://dovendi.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
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::
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.
D
Lighthouse Accessibility Audits
Action
Score 67/100 — 5 failing, 11 passed
FIX
67

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.container > div.w-full > form#domain_form > button.absolute div.container > div.w-full > form#domain_form > button.absolute
div.container > div.w-full > form#search_form > button.absolute div.container > div.w-full > form#search_form > button.absolute

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
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3

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.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide
div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide
div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide
div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide
div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide
div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide

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
Get to know us too! section.py-10 > div.container > div.w-full > a.inline-flex
Useful tips section.relative > div.container > a.p-4 > div.inline-flex
Our explanation section.relative > div.container > a.p-4 > div.inline-flex
Value of a name section.relative > div.container > a.p-4 > div.inline-flex
Find a cause section.relative > div.container > a.p-4 > div.inline-flex
All services section.text-usps > div.container > div.w-full > a.inline-flex
How it works section.py-12 > div.container > div.w-full > a.inline-flex
Partners overview section.py-10 > div.container > div.w-full > a.inline-flex

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
What makes a good domain name section.relative > div.container > a.p-4 > h3.text-[14px]

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-hidden="true"]` is not present on the document `<body>`
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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.
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Identical links have the same purpose.
○`[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 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
○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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○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.
C
Alt Text Quality
Action
6 of 39 images have issues
REVIEW
6 of 39 images have issues
Critical::
6 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
26 decorative image(s) correctly marked
Info::
7 image(s) with good alt text
39 images 7 good alt text 26 decorative 6 missing
IssueCount
missing6 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

C
Form Accessibility
Action
5 of 5 controls have issues
REVIEW
5 of 5 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="search" id="search-popout--input">; <input type="search" name="search" id="search-popout--input">; <input type="search" name="domain_search" id="domain_search">; <input type="search" name="search" id="search">
5 controls
0 labeled
4 placeholder only
1 unlabeled
ControlTypeLabelMethod
#search-popout--inputsearch(Search on dovendi.com)placeholder only
#search-popout--inputsearch(Search on dovendi.com)placeholder only
#domain_searchsearch(Find your domain name)placeholder only
#searchsearch(Your search starts here)placeholder only
#g-recaptcha-response-100000textarea(none)none

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

<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="search" name="search" id="search-popout--input">; <input type="search" name="search" id="search-popout--input">; <input type="search" name="domain_search" id="domain_search">; <input type="search" name="search" id="search">

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

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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
A
Landmark Structure
4 landmarks
PASS
4 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 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
Heading Hierarchy
19 headings, 1 skip(s)
PASS
19 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 The platform for domain names
  • H1 Your all-in-one portal for domain names
  • H3 What makes a good domain name skipped
  • H3 How do you acquire domain names
  • H3 What do I pay for a domain name
  • H3 I have lost my domain name
  • H2 Use our international expertise in domain names
  • H2 I am looking for a good domain name
  • H2 Good domain names can be very valuable.
  • H2 We are missing crucial donations!
  • H2 I am looking for a good domain name
  • H2 A domain name is up for sale. What exactly does that mean?
  • H3 First registration
  • H3 Second registration
  • H3 Exploitation
  • H3 Aftermarket
  • H3 Termination
  • H3 Quarantine
  • H2 Serving the customer together

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+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Your all-in-one port…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 The platform for dom…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Use our internationa…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 I am looking for a g…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Good domain names ca…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 We are missing cruci…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 I am looking for a g…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 A domain name is up …20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Serving the customer…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 What makes a good do…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 How do you acquire d…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 What do I pay for a …20.82:13.0:1
#000000
#FEFEFE
Pass
h3 I have lost my domai…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 First registration20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Second registration20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Exploitation20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Aftermarket20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Termination20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Quarantine20.82:13.0:1
#000000
#FEFEFE
Pass
title Dovendi - Dovendi - …21.00:14.5:1
#000000
#FFFFFF
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback