Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 6 REVIEW 3 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 ✗

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

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 2 <nav> element(s)

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.

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No banner (header) landmark

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

1 control(s) without accessible label

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

Got: <input type="file">

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

Control	Type	Label	Method
textarea	textarea	(Describe your idea to generate...)	placeholder only
input	file	(none)	none

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

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.

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

Link & Button Quality

1 issue(s) across 96 links and 37 buttons

REVIEW

1 issue(s) across 96 links and 37 buttons

2 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://x.com/bestvid; https://discord.gg/bestvid

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.inline-flex (#247 on page)

94 link(s) with descriptive text

96 links

0 empty

0 generic text

2 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://x.com/bestvid	X	new tab	Add '(opens in new tab)' to text
https://discord.gg/bestvid	Discord	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

130 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://x.com/bestvid; https://discord.gg/bestvid

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.inline-flex (#247 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Mobile-Readable Font Sizes

Action

75% of visible text renders at >= 12 CSS px (137 below threshold)

REVIEW

75% of visible text renders at >= 12 CSS px (137 below threshold)

137 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: <p> 11.0px ("The ultimate AI portal powered by Sora, ..."); <span> 11.0px ("TRY:"); <span> 10.0px ("Seedance 2.0"); <span> 10.0px ("Seedance 2.0"); <span> 10.0px ("Seedance 2.0").

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 Featured Masterpieces

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 BestVid AI Video Generator Workflow: Fro…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 AI Video Generator Use Cases for Every I…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Professional AI Video & Image Generator …

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Beyond Raw Generation:

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Trusted AI Video Generator for Creators …

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Flexible pricing that scales with output

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Starter

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Premium

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Advanced

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 AI Video Generator FAQ

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Transform your vision with BestVid: the …

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Seedance 1.5 Pro

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Sora 2

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Veo 3.1

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Kling 3.0

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Key Metrics Assessment

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Smart Ideation

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Multi-Model Generation

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Ultra-Clear Download

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Featured Masterpiece…	1.00:1	3.0:1	#000000	#000000	Fail
h2 BestVid AI Video Gen…	1.00:1	3.0:1	#000000	#000000	Fail
h2 AI Video Generator U…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Professional AI Vide…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Beyond Raw Generatio…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Trusted AI Video Gen…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Flexible pricing tha…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Starter	1.00:1	3.0:1	#000000	#000000	Fail
h2 Premium	1.00:1	3.0:1	#000000	#000000	Fail
h2 Advanced	1.00:1	3.0:1	#000000	#000000	Fail
h2 AI Video Generator F…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Transform your visio…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Seedance 1.5 Pro	1.00:1	3.0:1	#000000	#000000	Fail
h3 Sora 2	1.00:1	3.0:1	#000000	#000000	Fail
h3 Veo 3.1	1.00:1	3.0:1	#000000	#000000	Fail
h3 Kling 3.0	1.00:1	3.0:1	#000000	#000000	Fail
h3 Key Metrics Assessme…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Smart Ideation	1.00:1	3.0:1	#000000	#000000	Fail
h3 Multi-Model Generati…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Ultra-Clear Download	1.00:1	3.0:1	#000000	#000000	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+

Heading Hierarchy

48 headings

PASS

48 headings

Single H1 present

H1 BestVid AI Video & Image Generator
H2 Featured Masterpieces
H2 Advanced AI Video Generator Models:Seedance, Sora, Veo & Kling
H3 Seedance 1.5 Pro
H3 Sora 2
H3 Veo 3.1
H3 Kling 3.0
H3 Key Metrics Assessment
H2 BestVid AI Video Generator Workflow: From Prompt to Ultra-Clear Video
H3 Smart Ideation
H3 Multi-Model Generation
H3 Ultra-Clear Download
H2 AI Video Generator Use Cases for Every Industry
H3 Viral Social Media Content
H3 Professional Ad Creatives
H3 Cinema-Quality Storytelling
H3 Educational Visuals
H3 Game Asset Generation
H3 Enterprise Brand Scaling
H2 Professional AI Video & Image Generator Tools
H3 Multi-Model Generation Hub
H3 AI Image Generator: nanobanana pro
H3 Detail Pro-Restoration
H3 Enterprise API
H3 AI Video Generator Templates
H2 Beyond Raw Generation:Professional Ultra-Clear Enhancement
H3 Detail Pro-Restoration: Cinematic Quality
H3 Ultimate Portal: One Subscription, All Models
H3 Superior Physics & Motion Stability
H2 Trusted AI Video Generator for Creators & Teams
H2 Flexible pricing that scales with output
H2 Starter
H2 Premium
H2 Advanced
H2 AI Video Generator FAQ
H3 What makes BestVid the ultimate multi-model AI video generator?
H3 Can I really create cinematic videos with this platform?
H3 Which AI models does BestVid support for video and image generation?
H3 Does BestVid support text-to-video and image-to-video?
H3 Can I use the generated content for commercial purposes?
H3 How do credits work in the BestVid AI Video Generator?
H3 Is BestVid suitable for beginners without video experience?
H3 How does BestVid ensure character and visual consistency?
H3 Do you offer API access for high-volume generation?
H3 Can I switch models for the same creative idea in BestVid?
H3 Do I need a powerful computer to use BestVid?
H3 What is the "Direct Export" feature in BestVid?
H2 Transform your vision with BestVid: the professional AI video & image generator

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 82 images OK

PASS

All 82 images OK

82 image(s) with good alt text

82 images 82 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

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

<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

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

Favicon & Branding

7 icon(s) detected

PASS

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

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

Meets PWA install criteria

Name present: BestVid

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name BestVid ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name BestVid Display Mode standalone Theme Color #0B1120 Background Color #0B1120 Icons 2 icon(s)

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.

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 25 passed

PASS

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.theme-bestvid-marketing > div.fixed > div.relative > button.absolute `div.theme-bestvid-marketing > div.fixed > div.relative > button.absolute`

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
02 `div.space-y-8 > div.relative > div.relative > span.font-bold`
03 `div.space-y-8 > div.relative > div.relative > span.font-bold`
Model Capability `div.mx-auto > div.mx-auto > div.mt-10 > a.hover:text-blue-400`
FAQ `div.mx-auto > div.mx-auto > div.mt-10 > a.hover:text-blue-400`
Pricing Plans `div.mx-auto > div.mx-auto > div.mt-10 > a.hover:text-blue-400`
© 2026 BestVid. All rights reserved. `footer.w-full > div.mx-auto > div.flex > span`
Privacy Policy `div.mx-auto > div.flex > div.flex > a.text-slate-500`
Terms of Service `div.mx-auto > div.flex > div.flex > a.text-slate-500`
Refund Policy `div.mx-auto > div.flex > div.flex > a.text-slate-500`
Cookie Policy `div.mx-auto > div.flex > div.flex > a.text-slate-500`

These are opportunities to improve the legibility of your content.

○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

●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 are distinguishable without relying on color.

●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

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

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

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

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