Skip to content
https://kling4ai.app

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
86
GRADE
B
FIX
2
REVIEW
5
PASS
17
INFO
0
Checks
24
17 PASS 5 REVIEW 2 FIX
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::
2 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 2 <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.
C
Form Accessibility
Action
5 of 6 controls have issues
REVIEW
5 of 6 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="file">; <input type="file">; <input type="file">; <input type="file">; <input type="file">
Info::
1 control(s) properly labeled
6 controls
1 labeled
0 placeholder only
5 unlabeled
ControlTypeLabelMethod
textareatextareaDescribe the video to generate… e.g. A runner jogs along a misty park trail at sunrise as autumn leaves drift past.aria-label
inputfile(none)none
inputfile(none)none
inputfile(none)none
inputfile(none)none
inputfile(none)none

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

<input type="file">; <input type="file">; <input type="file">; <input type="file">; <input type="file">

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

C
Mobile-Readable Font Sizes
Action
83% of visible text renders at >= 12 CSS px (26 below threshold)
REVIEW
83% of visible text renders at >= 12 CSS px (26 below threshold)
Warning::
26 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 9.0px ("Annual Plan · Save 20%"); <a> 11.0px ("Explore Annual Plans"); <span> 10.0px ("20% OFF"); <span> 10.0px ("EN"); <span> 11.0px ("English").
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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Kling 4 ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
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 #f7f8fa ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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 What is Kling 4?
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why use Kling 4 for video production?
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Built for practical digital workflows
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Core Strengths of Kling 4 Studio
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Start creating with Kling 4
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Kling 4 FAQ — Everyday Video & Workflo…
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Speed up your daily video drafting
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Fast draft iteration
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Single-image motion precision
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Optional audio integration
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Unified browser studio
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Fast text-guided adjustments
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Purpose-built draft workspace
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Digital content creators
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Marketing specialists
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 E-commerce sellers
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Creative directors & animators
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 App & game developers
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Independent storytellers
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Clean HD Video Renders
1.20:1
#000000
on
#300C1F
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 What is Kling 4?1.20:13.0:1
#000000
#300C1F
Fail
h2 Why use Kling 4 for …1.20:13.0:1
#000000
#300C1F
Fail
h2 Built for practical …1.20:13.0:1
#000000
#300C1F
Fail
h2 Core Strengths of Kl…1.20:13.0:1
#000000
#300C1F
Fail
h2 Start creating with …1.20:13.0:1
#000000
#300C1F
Fail
h2 Kling 4 FAQ — Ever…1.20:13.0:1
#000000
#300C1F
Fail
h2 Speed up your daily …1.20:13.0:1
#000000
#300C1F
Fail
h3 Fast draft iteration1.20:13.0:1
#000000
#300C1F
Fail
h3 Single-image motion …1.20:13.0:1
#000000
#300C1F
Fail
h3 Optional audio integ…1.20:13.0:1
#000000
#300C1F
Fail
h3 Unified browser stud…1.20:13.0:1
#000000
#300C1F
Fail
h3 Fast text-guided adj…1.20:13.0:1
#000000
#300C1F
Fail
h3 Purpose-built draft …1.20:13.0:1
#000000
#300C1F
Fail
h3 Digital content crea…1.20:13.0:1
#000000
#300C1F
Fail
h3 Marketing specialist…1.20:13.0:1
#000000
#300C1F
Fail
h3 E-commerce sellers1.20:13.0:1
#000000
#300C1F
Fail
h3 Creative directors &…1.20:13.0:1
#000000
#300C1F
Fail
h3 App & game developer…1.20:13.0:1
#000000
#300C1F
Fail
h3 Independent storytel…1.20:13.0:1
#000000
#300C1F
Fail
h3 Clean HD Video Rende…1.20:13.0:1
#000000
#300C1F
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
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "Kling 4" 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
27 headings
PASS
27 headings
Info::
Single H1 present
  • H1 Kling 4Image-to-Video Iteration & Motion Drafts
  • H2 What is Kling 4?
  • H2 Why use Kling 4 for video production?
  • H3 Fast draft iteration
  • H3 Single-image motion precision
  • H3 Optional audio integration
  • H3 Unified browser studio
  • H3 Fast text-guided adjustments
  • H3 Purpose-built draft workspace
  • H2 Built for practical digital workflows
  • H3 Digital content creators
  • H3 Marketing specialists
  • H3 E-commerce sellers
  • H3 Creative directors & animators
  • H3 App & game developers
  • H3 Independent storytellers
  • H2 Core Strengths of Kling 4 Studio
  • H3 Clean HD Video Renders
  • H3 Integrated Audio Options
  • H3 Flexible Clip Durations
  • H3 Smooth Motion Iteration
  • H2 Start creating with Kling 4
  • H3 Access the workspace
  • H3 Drop your still or prompt
  • H3 Check quote and refine
  • H2 Kling 4 FAQ — Everyday Video & Workflow Guide
  • H2 Speed up your daily video drafting
A+
Heading Text Quality
All 27 heading(s) have substantive, well-formed text
PASS
All 27 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 4 images OK
PASS
All 4 images OK
Info::
1 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
4 images 3 good alt text 1 decorative
All images have appropriate alt text.
A+
Form Input Types
6 form control(s) checked, no type mismatches
PASS
6 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
6 form control(s) checked, no input-semantic issues
PASS
6 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
1 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A
Favicon & Branding
8 icon(s) detected
PASS
8 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
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Kling 4
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Kling 4 ✓192×192 icon ✓512×512 icon ✓Start URL /?utm_source=pwa&utm_medium=install ✓Display Mode standalone ✓
Name Kling 4 Display Mode standalone Theme Color #EA580C Background Color #f7f8fa Icons 3 icon(s)
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::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
A+
Lighthouse Accessibility Audits
Score 96/100 — 2 failing, 24 passed
PASS
96

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
CORE CAPABILITIES section#what-section > div.mx-auto > div.mt-10 > p.mb-4
01 div.rounded-2xl > div.flex > div.min-w-0 > span.font-display
02 div.rounded-2xl > div.flex > div.min-w-0 > span.font-display
03 div.rounded-2xl > div.flex > div.min-w-0 > span.font-display
04 div.rounded-2xl > div.flex > div.min-w-0 > span.font-display
05 div.rounded-2xl > div.flex > div.min-w-0 > span.font-display
06 div.rounded-2xl > div.flex > div.min-w-0 > span.font-display
01 div.mt-12 > article.group > div.flex > span.font-display
02 div.mt-12 > article.group > div.flex > span.font-display
03 div.mt-12 > article.group > div.flex > span.font-display
04 div.mt-12 > article.group > div.flex > span.font-display
05 div.mt-12 > article.group > div.flex > span.font-display
06 div.mt-12 > article.group > div.flex > span.font-display
Kling 4 on kling4ai.app is an independent multi-model AI video workbench that d… div.mx-auto > div.flex > details.group > div.px-5

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Install App div.relative > div.fixed > div.group > button.inline-flex
○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
●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 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 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
○`[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
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback