Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 5 REVIEW 5 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Landmark Structure

Action

4 landmarks

REVIEW

4 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

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

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

Mobile-Readable Font Sizes

Action

86% of visible text renders at >= 12 CSS px (42 below threshold)

REVIEW

86% of visible text renders at >= 12 CSS px (42 below threshold)

42 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 ("NEW"); <span> 11.0px ("Cinematic MV"); <span> 11.0px ("Neon Visualizer"); <span> 11.0px ("Lyric Style"); <span> 11.0px ("Beat Sync").

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

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.

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 Three ways to refine an AI music video d…

1.13:1

#000000

#150F25

needs 3.0:1 (large text)

24px · mid-page

h2 Three ways to refine an AI music video d…

1.01:1

#000000

#010103

needs 3.0:1 (large text)

24px · bottom of viewport

h2 See what creators say about

1.01:1

#000000

#010103

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How Music Video AI turns songs into vide…

1.01:1

#000000

#010103

needs 3.0:1 (large text)

24px · bottom of viewport

h2 No track yet? Music Video AI

1.01:1

#000000

#010103

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Made by the AI music video community wit…

1.01:1

#000000

#010103

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Powerful

1.01:1

#000000

#010103

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Loved by the

1.01:1

#000000

#010103

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Choose your plan

1.01:1

#000000

#010103

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Questions & Answers

1.01:1

#000000

#010103

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Meet your

1.01:1

#000000

#010103

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Built for music-first workflows

1.01:1

#000000

#010103

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Upload your song

1.01:1

#000000

#010103

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Set the mood and visual direction

1.01:1

#000000

#010103

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Generate and refine your video draft

1.01:1

#000000

#010103

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Automatic music generation

1.01:1

#000000

#010103

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Smart dialogue & narration synthesis

1.01:1

#000000

#010103

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Mood & genre analysis

1.01:1

#000000

#010103

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Automatic audio-visual editing

1.01:1

#000000

#010103

needs 3.0:1 (large text)

19px · bottom of viewport

h3 One-stop storyboard delivery

1.01:1

#000000

#010103

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Three ways to refine…	1.13:1	3.0:1	#000000	#150F25	Fail
h2 Three ways to refine…	1.01:1	3.0:1	#000000	#010103	Fail
h2 See what creators sa…	1.01:1	3.0:1	#000000	#010103	Fail
h2 How Music Video AI t…	1.01:1	3.0:1	#000000	#010103	Fail
h2 No track yet? Music …	1.01:1	3.0:1	#000000	#010103	Fail
h2 Made by the AI music…	1.01:1	3.0:1	#000000	#010103	Fail
h2 Powerful	1.01:1	3.0:1	#000000	#010103	Fail
h2 Loved by the	1.01:1	3.0:1	#000000	#010103	Fail
h2 Choose your plan	1.01:1	3.0:1	#000000	#010103	Fail
h2 Questions & Answers	1.01:1	3.0:1	#000000	#010103	Fail
h2 Meet your	1.01:1	3.0:1	#000000	#010103	Fail
h3 Built for music-firs…	1.01:1	3.0:1	#000000	#010103	Fail
h3 Upload your song	1.01:1	3.0:1	#000000	#010103	Fail
h3 Set the mood and vis…	1.01:1	3.0:1	#000000	#010103	Fail
h3 Generate and refine …	1.01:1	3.0:1	#000000	#010103	Fail
h3 Automatic music gene…	1.01:1	3.0:1	#000000	#010103	Fail
h3 Smart dialogue & nar…	1.01:1	3.0:1	#000000	#010103	Fail
h3 Mood & genre analysi…	1.01:1	3.0:1	#000000	#010103	Fail
h3 Automatic audio-visu…	1.01:1	3.0:1	#000000	#010103	Fail
h3 One-stop storyboard …	1.01:1	3.0:1	#000000	#010103	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.

Lighthouse Accessibility Audits

Score 88/100 — 3 failing, 19 passed

REVIEW

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
header.sticky > nav.mx-auto > div.flex > button.inline-flex `header.sticky > nav.mx-auto > div.flex > button.inline-flex`

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
128K subscribers `div.flex > div.flex > div.text-right > div.text-xs`
574K subs `div.mt-8 > div.group > div.p-4 > div.mt-1`
475K subs `div.mt-8 > div.group > div.p-4 > div.mt-1`
466K subs `div.mt-8 > div.group > div.p-4 > div.mt-1`
374K subs `div.mt-8 > div.group > div.p-4 > div.mt-1`
292K subs `div.mt-8 > div.group > div.p-4 > div.mt-1`
285K subs `div.mt-8 > div.group > div.p-4 > div.mt-1`
Content Creators & Social Media `div.grid > div > div.mt-8 > button.cursor-pointer`
Brands & Marketers `div.grid > div > div.mt-8 > button.cursor-pointer`
Filmmakers `div.grid > div > div.mt-8 > button.cursor-pointer`
Designers `div.grid > div > div.mt-8 > button.cursor-pointer`
Photographers `div.grid > div > div.mt-8 > button.cursor-pointer`
Independent Musician `div.rounded-2xl > div.flex > div.min-w-0 > div.truncate`
Producer / Beatmaker `div.rounded-2xl > div.flex > div.min-w-0 > div.truncate`
Singer-Songwriter `div.rounded-2xl > div.flex > div.min-w-0 > div.truncate`
Short-Form Creator `div.rounded-2xl > div.flex > div.min-w-0 > div.truncate`
Label Content Manager `div.rounded-2xl > div.flex > div.min-w-0 > div.truncate`
Creative Director `div.rounded-2xl > div.flex > div.min-w-0 > div.truncate`
$39.90 `div.relative > div.mt-4 > div.flex > span.text-sm`
Billed annually at $383.04 as a single upfront payment `div.mt-12 > div.relative > div.mt-4 > div.mt-1`
Cancel anytime, no hidden fees `section#pricing > div.mt-12 > div.relative > div.mt-3`
$69.90 `div.relative > div.mt-4 > div.flex > span.text-sm`
Billed annually at $671.04 as a single upfront payment `div.mt-12 > div.relative > div.mt-4 > div.mt-1`
Cancel anytime, no hidden fees `section#pricing > div.mt-12 > div.relative > div.mt-3`
$159.90 `div.relative > div.mt-4 > div.flex > span.text-sm`
Billed annually at $1,535.04 as a single upfront payment `div.mt-12 > div.relative > div.mt-4 > div.mt-1`
Get Started `section#pricing > div.mt-12 > div.relative > button.mt-5`
Cancel anytime, no hidden fees `section#pricing > div.mt-12 > div.relative > div.mt-3`
All plans include our AI-powered video generation technology `body.__variable_geist_1432zhy > div.min-h-screen > section#pricing > p.mt-8`
© 2026 Music Video AI. All rights reserved. `footer.border-t > div.mx-auto > div.mt-14 > p.text-xs`
Made with for creators worldwide `footer.border-t > div.mx-auto > div.mt-14 > p.flex`

These are opportunities to improve the legibility of your content.

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.dark `html.dark`

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>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●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

●`<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

●Image elements do not have `[alt]` attributes that are redundant text.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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

○`[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

○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

○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

○Identical links have the same purpose.

○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.

A+

Heading Hierarchy

42 headings

PASS

42 headings

Single H1 present

H1 AI Music Video Generatorfor Musicians
H2 Three ways to refine an AI music video draft.
H2 Three ways to refine an AI music video draft.
H2 See what creators say about Music Video AI
H2 How Music Video AI turns songs into videos
H3 Built for music-first workflows
H3 Upload your song
H3 Set the mood and visual direction
H3 Generate and refine your video draft
H2 No track yet? Music Video AI generates the music for you.
H3 Automatic music generation
H3 Smart dialogue & narration synthesis
H3 Mood & genre analysis
H3 Automatic audio-visual editing
H3 One-stop storyboard delivery
H3 Swap audio anytime
H2 Made by the AI music video community with
H2 Powerful features
H3 Music-first AI music video generator workflow
H3 AI Director Agent
H3 One-click AI generator
H3 Upload & go: automatic music sync engine
H3 Custom editing studio
H3 AI music & toolkit engine
H3 Flexible AI video model options
H2 Create music videos fasterwithout manual beat editing
H3 Start from the track
H3 Create polished visuals on a lean budget
H3 Your vision. Your control.
H3 Silence is no longer a problem
H3 Ready to visualize your music?
H2 A visual engine built for the ambition of every sound creator
H2 Loved by the community
H2 Choose your plan
H3 Basic
H3 Pro
H3 Creator
H2 Questions & Answers
H2 Meet your AI music video director
H3 Product
H3 Company
H3 Legal

A+

Heading Text Quality

All 42 heading(s) have substantive, well-formed text

PASS

All 42 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 80 images OK

PASS

All 80 images OK

23 decorative image(s) correctly marked

57 image(s) with good alt text

80 images 57 good alt text 23 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

28 links, 34 buttons — all OK

PASS

28 links, 34 buttons — all OK

28 link(s) with descriptive text

28 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

62 links and buttons have descriptive text

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

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

No form controls on this page

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

2 explicit tabindex attribute(s) checked, no anti-patterns

PASS

2 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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.

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