Skip to content
https://seedaud.io

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::
6 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 6 <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
Landmark Structure
11 landmarks
REVIEW
11 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
2 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 MAIN ASIDE "Sidebar navigation" CONTENTINFO footer

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

C
Mobile-Readable Font Sizes
Action
81% of visible text renders at >= 12 CSS px (86 below threshold)
REVIEW
81% of visible text renders at >= 12 CSS px (86 below threshold)
Warning::
86 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> 10.0px ("/3"); <span> 10.0px ("selected"); <span> 11.0px ("MP3 · 1.0x · vol 1.0 · pitch 0 · 24000 H..."); <p> 11.0px ("Credits are charged by generated duratio..."); <span> 11.0px ("YouTube & TikTok").
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
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title 404: This page could not be found. Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
9 icon(s) detected
REVIEW
9 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
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 Not set 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
h1 Create AI Voice Audio with
1.07:1
#000000
on
#000D1C
needs 3.0:1 (large text)
32px · mid-page
h2 Reference audio
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Comprehensive AI Audio Suite
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Stop Losing Time to Recording Bottleneck…
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why AI Voice Generation?
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 From Script to Sound in 4 Steps
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Use AI Voice Generation Across Every Aud…
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Generate AI Voice Audio in 4 Steps
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 AI Voice Generation vs Traditional Voice…
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Choose Voices for Different Audio Workfl…
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Example Workflows for
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Seed Audio AI FAQ
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Start Creating AI Voice Audio
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Text to Speech
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 AI Voice Generator
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Voiceover Generator
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Podcast Voice
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Audiobook Narrator
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Character Voice
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Studio Scheduling
1.09:1
#000000
on
#020F1E
needs 3.0:1 (large text)
19px · bottom of viewport

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Create AI Voice Audi…1.07:13.0:1
#000000
#000D1C
Fail
h2 Reference audio1.09:13.0:1
#000000
#020F1E
Fail
h2 Comprehensive AI Aud…1.09:13.0:1
#000000
#020F1E
Fail
h2 Stop Losing Time to …1.09:13.0:1
#000000
#020F1E
Fail
h2 Why AI Voice Generat…1.09:13.0:1
#000000
#020F1E
Fail
h2 From Script to Sound…1.09:13.0:1
#000000
#020F1E
Fail
h2 Use AI Voice Generat…1.09:13.0:1
#000000
#020F1E
Fail
h2 Generate AI Voice Au…1.09:13.0:1
#000000
#020F1E
Fail
h2 AI Voice Generation …1.09:13.0:1
#000000
#020F1E
Fail
h2 Choose Voices for Di…1.09:13.0:1
#000000
#020F1E
Fail
h2 Example Workflows fo…1.09:13.0:1
#000000
#020F1E
Fail
h2 Seed Audio AI FAQ1.09:13.0:1
#000000
#020F1E
Fail
h2 Start Creating AI Vo…1.09:13.0:1
#000000
#020F1E
Fail
h3 Text to Speech1.09:13.0:1
#000000
#020F1E
Fail
h3 AI Voice Generator1.09:13.0:1
#000000
#020F1E
Fail
h3 Voiceover Generator1.09:13.0:1
#000000
#020F1E
Fail
h3 Podcast Voice1.09:13.0:1
#000000
#020F1E
Fail
h3 Audiobook Narrator1.09:13.0:1
#000000
#020F1E
Fail
h3 Character Voice1.09:13.0:1
#000000
#020F1E
Fail
h3 Studio Scheduling1.09:13.0:1
#000000
#020F1E
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
49 headings
PASS
49 headings
Info::
Single H1 present
  • H1 Create AI Voice Audio with Seed Audio AI
  • H2 Reference audio
  • H2 Comprehensive AI Audio Suite
  • H3 Text to Speech
  • H3 AI Voice Generator
  • H3 Voiceover Generator
  • H3 Podcast Voice
  • H3 Audiobook Narrator
  • H3 Character Voice
  • H2 Stop Losing Time to Recording Bottlenecks
  • H3 Studio Scheduling
  • H3 Slow Revisions
  • H3 Inconsistent Voice Direction
  • H3 Language Expansion
  • H3 Reusable Voice Settings
  • H2 Why AI Voice Generation?
  • H3 Video Voiceover Without a Studio
  • H3 Multilingual Content Production
  • H3 Reusable Voice Profiles
  • H2 From Script to Sound in 4 Steps
  • H3 Input Script
  • H3 Choose Voice
  • H3 Shape Delivery
  • H3 Generate and Export
  • H2 Use AI Voice Generation Across Every Audio Workflow
  • H3 Short-Form Video Voiceovers
  • H3 Audiobook Production
  • H3 Podcast Episodes and Intros
  • H3 Advertising and Promo Audio
  • H2 Generate AI Voice Audio in 4 Steps
  • H3 Paste your script
  • H3 Choose a voice
  • H3 Shape delivery
  • H3 Generate and share
  • H2 AI Voice Generation vs Traditional Voice Recording
  • H2 Choose Voices for Different Audio Workflows
  • H2 Example Workflows for Creators and Teams
  • H2 Seed Audio AI FAQ
  • H3 What is Seed Audio AI?
  • H3 What can I generate with Text to Speech?
  • H3 Can I use Seed Audio AI for voice cloning?
  • H3 Can I use generated audio commercially?
  • H3 Is Seed Audio AI affiliated with ByteDance, Seed, Volcengine, or official SeedAudio models?
  • H3 How do credits work?
  • H3 Can I download MP3 audio?
  • H3 What content is not allowed?
  • H3 How do I report unauthorized voice use?
  • H3 How do I get better results?
  • H2 Start Creating AI Voice Audio
A+
Heading Text Quality
All 49 heading(s) have substantive, well-formed text
PASS
All 49 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 41 images OK
PASS
All 41 images OK
Info::
41 image(s) with good alt text
41 images 41 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#scene-free-prompttextareaFree Promptfor/id
inputfileUpload original audionone
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
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
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+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Seed Audio AI
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Installable
Name Seed Audio AI 192×192 icon 512×512 icon Start URL / Display Mode standalone
Name Seed Audio AI Display Mode standalone Theme Color #ccff00 Background Color #010f1f Icons 4 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::
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.
A+
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 32 passed
PASS
100

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.

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
Featured on FreeAI div.mx-auto > div.mt-10 > div.grid > a.external-badge-link
Featured on ToolDirs div.mx-auto > div.mt-10 > div.grid > a.external-badge-link
Featured on ToolPilot div.mx-auto > div.mt-10 > div.grid > a.external-badge-link
Powered by Startup Fast div.mx-auto > div.mt-10 > div.grid > a.external-badge-link
Featured on DeepLaunch.io div.mx-auto > div.mt-10 > div.grid > a.external-badge-link
Featured on First Look div.mx-auto > div.mt-10 > div.grid > a.external-badge-link
Listed on Turbo0 div.mx-auto > div.mt-10 > div.grid > a.external-badge-link
Listed on ToolRain div.mx-auto > div.mt-10 > div.grid > a.external-badge-link
NavFolders div.mx-auto > div.mt-10 > div.grid > a.external-badge-link
Featured on LaunchIgniter div.mx-auto > div.mt-10 > div.grid > a.external-badge-link
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
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
`[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
Background and foreground colors have a sufficient contrast ratio
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.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
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.
`[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 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.
No element has a `[tabindex]` value greater than 0
`<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
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback