Skip to content
https://wan3video.art

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
86
GRADE
B
FIX
2
REVIEW
6
PASS
16
INFO
0
Checks
24
16 PASS 6 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::
1 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 1 <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.
B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="file">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <textarea>
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
textareatextarea(What should happen on screen? e.g. Slow dolly past a glass perfume bottle at golden hour, soft specular highlights, gentle cloth motion in the background.)placeholder only
inputfile(none)none

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

<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

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

<textarea>

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
Tap Target Adequacy
1 tap target(s) too small or too close together
REVIEW
1 tap target(s) too small or too close together
Info::
1 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.
C
Mobile-Readable Font Sizes
Action
73% of visible text renders at >= 12 CSS px (56 below threshold)
REVIEW
73% of visible text renders at >= 12 CSS px (56 below threshold)
Warning::
56 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> 11.0px ("29"); <span> 11.0px ("49"); <span> 11.0px ("59"); <span> 9.0px ("Limited Offer"); <a> 11.0px ("See yearly options").
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 WAN 3.0 Video 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 From idea to video in 3 simple steps
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Styles you can aim for
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 References that steer the take
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What you can create with WAN 3.0 Video
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why creative teams keep coming back
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Built for people who ship weekly
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Desk capabilities at a glance
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Questions before you generate
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ready for your first take?
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Open the Workspace
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Choose Your Input
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Set Duration & Format
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Runway energy
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sound-led moment
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Aerial brand pass
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Product turntable
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Character walk cycle
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Plaza timelapse feel
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Room for a full beat
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Motion that holds
2.51:1
#000000
on
#574C3E
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 From idea to video i…2.51:13.0:1
#000000
#574C3E
Fail
h2 Styles you can aim f…2.51:13.0:1
#000000
#574C3E
Fail
h2 References that stee…2.51:13.0:1
#000000
#574C3E
Fail
h2 What you can create …2.51:13.0:1
#000000
#574C3E
Fail
h2 Why creative teams k…2.51:13.0:1
#000000
#574C3E
Fail
h2 Built for people who…2.51:13.0:1
#000000
#574C3E
Fail
h2 Desk capabilities at…2.51:13.0:1
#000000
#574C3E
Fail
h2 Questions before you…2.51:13.0:1
#000000
#574C3E
Fail
h2 Ready for your first…2.51:13.0:1
#000000
#574C3E
Fail
h3 Open the Workspace2.51:13.0:1
#000000
#574C3E
Fail
h3 Choose Your Input2.51:13.0:1
#000000
#574C3E
Fail
h3 Set Duration & Forma…2.51:13.0:1
#000000
#574C3E
Fail
h3 Runway energy2.51:13.0:1
#000000
#574C3E
Fail
h3 Sound-led moment2.51:13.0:1
#000000
#574C3E
Fail
h3 Aerial brand pass2.51:13.0:1
#000000
#574C3E
Fail
h3 Product turntable2.51:13.0:1
#000000
#574C3E
Fail
h3 Character walk cycle2.51:13.0:1
#000000
#574C3E
Fail
h3 Plaza timelapse feel2.51:13.0:1
#000000
#574C3E
Fail
h3 Room for a full beat2.51:13.0:1
#000000
#574C3E
Fail
h3 Motion that holds2.51:13.0:1
#000000
#574C3E
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
8 landmarks
PASS
8 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 "WAN 3.0 Video" 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
35 headings
PASS
35 headings
Info::
Single H1 present
  • H1 WAN 3.0 Video — Create engaging video clips with sound—from a prompt or an image
  • H2 From idea to video in 3 simple steps
  • H3 Open the Workspace
  • H3 Choose Your Input
  • H3 Set Duration & Format
  • H2 Styles you can aim for
  • H3 Runway energy
  • H3 Sound-led moment
  • H3 Aerial brand pass
  • H3 Product turntable
  • H3 Character walk cycle
  • H3 Plaza timelapse feel
  • H2 References that steer the take
  • H2 What you can create with WAN 3.0 Video
  • H2 Why creative teams keep coming back
  • H3 Room for a full beat
  • H3 Motion that holds
  • H3 Sound rides along
  • H3 Credits you can forecast
  • H3 Iterate in language
  • H3 Named for the job
  • H2 Built for people who ship weekly
  • H3 Creators who post every week
  • H3 Performance marketers
  • H3 Brand & ecommerce teams
  • H3 Agencies on tight timelines
  • H3 Game & app storytellers
  • H3 Side-project filmmakers
  • H2 Desk capabilities at a glance
  • H3 Text & still inputs
  • H3 Sound when available
  • H3 Feed-ready ratios
  • H3 Extended Short-Form
  • H2 Questions before you generate
  • H2 Ready for your first take?
A+
Heading Text Quality
All 35 heading(s) have substantive, well-formed text
PASS
All 35 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 22 images OK
PASS
All 22 images OK
Info::
22 image(s) with good alt text
22 images 22 good alt text
All images have appropriate alt text.
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 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
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: WAN 3.0 Video
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Installable
Name WAN 3.0 Video 192×192 icon 512×512 icon Start URL /?utm_source=pwa&utm_medium=install Display Mode standalone
Name WAN 3.0 Video Display Mode standalone Theme Color #f7f8fa Background Color #f7f8fa Icons 2 icon(s)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
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 93/100 — 3 failing, 24 passed
PASS
93

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
Start free div.mt-3 > div.min-w-0 > button.inline-flex > span
Fashion div.grid > article.group > div.flex > p.mt-3
Sound-forward · ~15s div.grid > article.group > div.flex > p.mt-3
Wide establishing div.grid > article.group > div.flex > p.mt-3
Tabletop div.grid > article.group > div.flex > p.mt-3
Identity div.grid > article.group > div.flex > p.mt-3
Travel div.grid > article.group > div.flex > p.mt-3
Today on this desk: text-to-video, image-to-video, references, duration/aspect … section#multimodal-proof > div.mx-auto > div.mx-auto > p.mt-2
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
When starter credits are enabled, new accounts receive a trial balance for a fi… div.mx-auto > div.flex > details.group > div.px-5
VIDEO div > div.flex > div.flex > div.mt-1
CREATE div.mx-auto > div.grid > div > p.mb-4
USE CASES div.mx-auto > div.grid > div > p.mb-4
LEGAL div.mx-auto > div.grid > div > p.mb-4
CONTACT div.mx-auto > div.grid > div > p.mt-8
FEATURED ON footer#contact-section > section.border-t > div.mx-auto > p.mb-2.5

These are opportunities to improve the legibility of your content.

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
AI Enhance div.flex > div.relative > div.absolute > button.flex

These items highlight common accessibility best practices.

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
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
`[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
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