Skip to content
https://www.daelimtransformer.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
4
REVIEW
5
PASS
15
INFO
0
Checks
24
15 PASS 5 REVIEW 4 FIX
F
Favicon & Branding
Action
No icons detected
FIX
No icons 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::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ 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
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.
B
Landmark Structure
2 landmarks
REVIEW
2 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark 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!) 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

C
Tap Target Adequacy
Action
4 tap target(s) too small or too close together
REVIEW
4 tap target(s) too small or too close together
Warning::
4 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
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 Page not found - Daelim Transformer ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
Lighthouse Accessibility Audits
Score 81/100 — 9 failing, 29 passed
REVIEW
81

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.

ARIA

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.elementor-widget-container > div#uc_simple_slider_elementor_1ae6cb5 > div.slick-list > div.slick-track div.elementor-widget-container > div#uc_simple_slider_elementor_1ae6cb5 > div.slick-list > div.slick-track

When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#uc_simple_slider_elementor_1ae6cb5 > div.slick-list > div.slick-track > div.ue_slide div#uc_simple_slider_elementor_1ae6cb5 > div.slick-list > div.slick-track > div.ue_slide

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.elementor-element > div.elementor-widget-container > div#uc_simple_slider_elementor_1ae6cb5 > button.slick-prev div.elementor-element > div.elementor-widget-container > div#uc_simple_slider_elementor_1ae6cb5 > button.slick-prev
div.elementor-element > div.elementor-widget-container > div#uc_simple_slider_elementor_1ae6cb5 > button.slick-next div.elementor-element > div.elementor-widget-container > div#uc_simple_slider_elementor_1ae6cb5 > button.slick-next

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.elementor-element > ul.elementor-icon-list-items > li.elementor-icon-list-item > a div.elementor-element > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
div.elementor-element > ul.elementor-icon-list-items > li.elementor-icon-list-item > a div.elementor-element > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
div.elementor-element > ul.elementor-icon-list-items > li.elementor-icon-list-item > a div.elementor-element > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
div.elementor-element > div.e-con-inner > div.elementor-element > a div.elementor-element > div.e-con-inner > div.elementor-element > a
div.slick-list > div.slick-track > div.ue_slide > a.ue_slide_link_overlay div.slick-list > div.slick-track > div.ue_slide > a.ue_slide_link_overlay

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
+86 15801656761 ul.elementor-icon-list-items > li.elementor-icon-list-item > a > span.elementor-icon-list-text
Transformer Type fieldset > div.ff-el-group > div.ff-el-input--label > label#label_ff_3_dropdown
Power Rating fieldset > div.ff-el-group > div.ff-el-input--label > label#label_ff_3_input_text
Primary Voltage fieldset > div.ff-el-group > div.ff-el-input--label > label#label_ff_3_input_text_1
Secondary Voltage fieldset > div.ff-el-group > div.ff-el-input--label > label#label_ff_3_input_text_2
Quantity fieldset > div.ff-el-group > div.ff-el-input--label > label#label_ff_3_numeric_field
Name fieldset > div.ff-el-group > div.ff-el-input--label > label#label_ff_3_input_text_3
Email fieldset > div.ff-el-group > div.ff-el-input--label > label#label_ff_3_email
Phone fieldset > div.ff-el-group > div.ff-el-input--label > label#label_ff_3_phone
Country fieldset > div.ff-el-group > div.ff-el-input--label > label#label_ff_3_input_text_4
Company fieldset > div.ff-el-group > div.ff-el-input--label > label#label_ff_3_input_text_5
Request Information fieldset > div.ff-el-group > div.ff-el-input--label > label#label_ff_3_description
Send Message form#fluentform_3 > fieldset > div.ff-el-group > button.ff-btn

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
Solar & BESS project in Southern California div#e-n-tab-content-1217369711 > div.elementor-element > div.elementor-element > h5.elementor-heading-title
SOLUTION div.e-con-inner > div.elementor-element > div.elementor-element > h5.elementor-heading-title

These are opportunities to improve keyboard navigation in your application.

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
Go to slide 1 div.elementor-element > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.elementor-element > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.elementor-element > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.elementor-element > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `[colspan]` attribute may improve the experience for screen reader users. Learn more about captions.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1PH Transformer In Stock Power Rating HV LV 167kVA 7200*14400±2*2.5% Single Pha… div.elementor-element > div.e-con-inner > div.elementor-element > table

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
1PH Transformer In Stock Power Rating HV LV 167kVA 7200*14400±2*2.5% Single Pha… div.elementor-element > div.e-con-inner > div.elementor-element > 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-*]` 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
●Image elements have `[alt]` attributes
●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.
●Select elements have associated label elements.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●`<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
●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.
●Skip links are focusable.
●Document has a main landmark.
●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
○Elements with `role="dialog"` or `role="alertdialog"` 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 `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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○`<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.
A+
Heading Hierarchy
3 headings
PASS
3 headings
Info::
Single H1 present
  • H1 www.daelimtransformer.com
  • H2 Performing security verification
  • H2 Verification successful. Waiting for www.daelimtransformer.com to respond
A+
Heading Text Quality
All 3 heading(s) have substantive, well-formed text
PASS
All 3 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 1 images OK
PASS
All 1 images OK
Info::
1 image(s) with good alt text
1 images 1 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Mobile-Readable Font Sizes
All 8 visible text node(s) render at >= 12 CSS pixels
PASS
All 8 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A+
Color Contrast (Screenshot)
10 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.

10 pass
Show all checked elements (10)
ElementRatioRequiredFGBGResult
h1 www.daelimtransforme…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Performing security …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Verification success…21.00:13.0:1
#000000
#FFFFFF
Pass
title Just a moment...21.00:14.5:1
#000000
#FFFFFF
Pass
p This website uses a …21.00:14.5:1
#000000
#FFFFFF
Pass
div Ray ID:21.00:14.5:1
#000000
#FFFFFF
Pass
code a340e155b8bca62e21.00:14.5:1
#000000
#FFFFFF
Pass
span Performance and Secu…21.00:14.5:1
#000000
#FFFFFF
Pass
a Cloudflare21.00:14.5:1
#000000
#FFFFFF
Pass
a Privacy21.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