Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 4 REVIEW 2 FIX

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

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found — VideoConduit ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

6 icon(s) detected

REVIEW

6 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

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: VideoConduit

No 192x192 icon

A 192px icon is required for PWA installation.

Display mode: standalone

PWA Install Criteria Not Installable

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

Name VideoConduit Display Mode standalone Theme Color #2563eb Background Color #ffffff Icons 2 icon(s)

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #2563eb

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.

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

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

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

25 headings

PASS

25 headings

Single H1 present

H1 One API for video and audio from 1,000+ platforms
H2 Everything you need to work with video
H3 Download from 1,000+ platforms
H3 Extract and process audio
H3 AI-powered transcription
H3 Translate any language
H3 Generate previews instantly
H3 Perceptual fingerprinting
H3 Extract comments and metadata
H3 AI agent integration (MCP)
H2 Start building in 5 minutes
H3 Get your API key
H3 Send a request
H3 Get your result
H2 See it in action
H2 Built for every video workflow
H3 Content Platforms
H3 AI & Data Pipelines
H3 Media Monitoring
H2 Connects with your stack
H2 Ready to build something great?
H3 Product
H3 Developers
H3 Company
H3 Legal

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 decorative image(s) correctly marked

1 images 1 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.

Link & Button Quality

1 issue(s) across 29 links and 11 buttons

PASS

1 issue(s) across 29 links and 11 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /privacy/#cookies ("Learn more")

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/"]

27 link(s) with descriptive text

29 links

0 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	VideoConduit	img no alt	Add alt attribute to the image
/privacy/#cookies	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: #Cookies

38 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/privacy/#cookies ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

A+

Color Contrast (Screenshot)

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 One API for video an…	10.90:1	3.0:1	#000000	#B7BBC2	Pass
h2 Everything you need …	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h2 Start building in 5 …	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h2 See it in action	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h2 Built for every vide…	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h2 Connects with your s…	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h2 Ready to build somet…	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h3 Download from 1,000+…	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h3 Extract and process …	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h3 AI-powered transcrip…	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h3 Translate any langua…	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h3 Generate previews in…	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h3 Perceptual fingerpri…	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h3 Extract comments and…	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h3 AI agent integration…	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h3 Get your API key	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h3 Send a request	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h3 Get your result	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h3 Content Platforms	18.06:1	3.0:1	#000000	#E7EEFE	Pass
h3 AI & Data Pipelines	18.06:1	3.0:1	#000000	#E7EEFE	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.

A+

Lighthouse Accessibility Audits

Score 96/100 — 2 failing, 22 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.

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
Python `div.w-full > div.rounded-xl > div.flex > button.px-4`
JavaScript `div.w-full > div.rounded-xl > div.flex > button.px-4`
RESPONSE `div.mt-16 > div.rounded-xl > div.p-5 > p.text-[11px]`
: { `div.p-5 > pre.text-[13px] > code > span.text-gray-500`
API Status `div > ul.mt-4 > li > span.text-[14px]`
GitHub `div > ul.mt-4 > li > span.text-[14px]`
COMPANY `div.mx-auto > div.grid > div > h3.text-[12px]`
Blog `div > ul.mt-4 > li > span.text-[14px]`
LEGAL `div.mx-auto > div.grid > div > h3.text-[12px]`
© 2025 VideoConduit. All rights reserved. `footer.border-t > div.border-t > div.mx-auto > p.text-[13px]`

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
Got it `body.bg-white > div.fixed > div.max-w-3xl > button.flex-shrink-0`

○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

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

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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