Skip to content
https://synthesia.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://synthesia.io/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://synthesia.io/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set Dark theme-color Not set CSS indicators Not detected

Detection limited to meta tags and inline styles.

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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
12 landmarks
REVIEW
12 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
1 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 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
Alt Text Quality
Action
25 of 214 images have issues
REVIEW
25 of 214 images have issues
Critical::
25 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
167 decorative image(s) correctly marked
Info::
22 image(s) with good alt text
214 images 22 good alt text 167 decorative 25 missing
IssueCount
missing25 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

C
Form Accessibility
Action
17 of 25 controls have issues
REVIEW
17 of 25 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="submit" id="generate-demo-video-btn">
Warning::
16 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <textarea type="text" name="Video-Script" id="Video-Script">; <input type="text" name="eventid" id="free-demo-eventID">; <input type="text" name="ga_client_id" id="free-demo-ga_client_id">; <input type="text" name="fbp" id="free-demo-fpb">; <input type="text" name="fbc" id="free-demo-fbc">; <input type="text" name="liclid" id="free-demo-liclid">; <input type="text" name="user-agent" id="free-demo-user-agent">; <input type="text" name="msclkid" id="free-demo-msclkid">; <input type="text" name="ip_submissions" id="free-demo-ip_submissions">; <input type="text" name="ip_country_geojs" id="free-demo-ip_country_geojs"> (+6 more)
Info::
8 control(s) properly labeled
25 controls
8 labeled
16 placeholder only
1 unlabeled
ControlTypeLabelMethod
templateIdradionone
templateIdradionone
templateIdradionone
#First-NametextFirst Namefor/id
#Last-NametextLast Namefor/id
#EmailemailEmailfor/id
#Free-demo-Lead-SourceselectHow did you hear about us?aria-label
#Content-Guidelines-2checkboxnone
#Video-Scripttext(Hey, Alex here! Ready to create your own AI video? Let me help you get started—it's quick, easy, and you can customize it just the way you need. Let's bring your ideas to life!)placeholder only
#free-demo-eventIDtext(eventid)placeholder only
#free-demo-ga_client_idtext(ga_client_id)placeholder only
#free-demo-fpbtext(fbp)placeholder only
#free-demo-fbctext(fbc)placeholder only
#free-demo-liclidtext(liclid)placeholder only
#free-demo-user-agenttext(user-agent)placeholder only
#free-demo-msclkidtext(msclkid)placeholder only
#free-demo-ip_submissionstext(ip_submissions)placeholder only
#free-demo-ip_country_geojstext(ip_country_geojs)placeholder only
#free-demo-ga_session_idtext(ga_session_id)placeholder only
#free-demo-gclidtext(gclid)placeholder only
#free-demo-ttqclickidtext(ttqclickid)placeholder only
#free-demo-recent_form_utm_stringtext(recent_form_utm_string)placeholder only
#free-demo-submission_page_languagetext(submission_page_language)placeholder only
#grecaptcha_responsetext(grecaptcha_response)placeholder only
#generate-demo-video-btnsubmit(none)none

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

<input type="submit" id="generate-demo-video-btn">

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 type="text" name="Video-Script" id="Video-Script">; <input type="text" name="eventid" id="free-demo-eventID">; <input type="text" name="ga_client_id" id="free-demo-ga_client_id">; <input type="text" name="fbp" id="free-demo-fpb">; <input type="text" name="fbc" id="free-demo-fbc">; <input type="text" name="liclid" id="free-demo-liclid">; <input type="text" name="user-agent" id="free-demo-user-agent">; <input type="text" name="msclkid" id="free-demo-msclkid">; <input type="text" name="ip_submissions" id="free-demo-ip_submissions">; <input type="text" name="ip_country_geojs" id="free-demo-ip_country_geojs"> (+6 more)

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
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Not Found Custom Styling Navigation Homepage Link Search Form
A+
Heading Hierarchy
32 headings
PASS
32 headings
Info::
Single H1 present
  • H1 All-in-one AI Video platform for business
  • H2 Train, market and sell like a Fortune 100 company
  • H2 One platform to create, localize, manage and publish AI videos
  • H3 Create your own expressive AI Avatar
  • H3 Turn any content into AI videos, instantly
  • H3 Collaborate with your team in real time
  • H3 Translate any video in 160+ languages
  • H3 Create polished screen recordings in one take
  • H3 Watch all your videos in one multilingual player
  • H3 Make every video perfectly on-brand
  • H3 Update your AI videos with one-click
  • H3 Export videos in SCORM format for any LMS
  • H3 Optimize every video with powerful analytics
  • H2 Try out our free AI Video Tool
  • H2 You’ll get your video via email in minutes
  • H3 We are processing your submission.
  • H2 Loved by users. Approved by legal. Signed off by CFOs
  • H3 No video editing skills or equipment required.
  • H3 SOC2. GDPR. ISO42001. SAML/SSO. Locked down.
  • H3 One budget, one login. No extra tools. No agencies.
  • H2 Get the skills, insights, and support to help you scale
  • H3 Enroll in the Synthesia Academy
  • H3 Join a community of creators like you
  • H3 Level up with our full suite of services
  • H2 You’ve likely got a few questions
  • H3 Is Synthesia free?
  • H3 Can I customize AI videos to add brand identity?
  • H3 Does AI video creation integrate with existing LMS?
  • H3 How does AI video creation improve employee productivity?
  • H3 Is it safe for businesses to create AI videos in Synthesia?
  • H3 What can you do with Synthesia's AI video tools?
  • H2 Ready to try Synthesia?
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)
ElementRatioRequiredFGBGResult
h2 Train, market and se…12.97:13.0:1
#000000
#A5D0F7
Pass
h2 One platform to crea…12.97:13.0:1
#000000
#A5D0F7
Pass
h2 Loved by users. Appr…12.97:13.0:1
#000000
#A5D0F7
Pass
h2 Get the skills, insi…12.97:13.0:1
#000000
#A5D0F7
Pass
h2 You’ve likely got …12.97:13.0:1
#000000
#A5D0F7
Pass
h2 Ready to try Synthes…12.97:13.0:1
#000000
#A5D0F7
Pass
h3 Create your own expr…12.97:13.0:1
#000000
#A5D0F7
Pass
h3 Turn any content int…12.97:13.0:1
#000000
#A5D0F7
Pass
h3 Collaborate with you…12.97:13.0:1
#000000
#A5D0F7
Pass
h3 Translate any video …12.97:13.0:1
#000000
#A5D0F7
Pass
h3 Create polished scre…12.97:13.0:1
#000000
#A5D0F7
Pass
h3 Watch all your video…12.97:13.0:1
#000000
#A5D0F7
Pass
h3 Make every video per…12.97:13.0:1
#000000
#A5D0F7
Pass
h3 Update your AI video…12.97:13.0:1
#000000
#A5D0F7
Pass
h3 Export videos in SCO…12.97:13.0:1
#000000
#A5D0F7
Pass
h3 Optimize every video…12.97:13.0:1
#000000
#A5D0F7
Pass
h3 We are processing yo…12.97:13.0:1
#000000
#A5D0F7
Pass
h3 Enroll in the Synthe…12.97:13.0:1
#000000
#A5D0F7
Pass
h3 Join a community of …12.97:13.0:1
#000000
#A5D0F7
Pass
h3 Level up with our fu…12.97:13.0:1
#000000
#A5D0F7
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 94/100 — 2 failing, 29 passed
PASS
94

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
div > div.text-color-base-dark > div.input-standard-container > textarea#Video-Script div > div.text-color-base-dark > div.input-standard-container > textarea#Video-Script

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
Go to slide 1 of 3 fieldset > div#embla-free-demo > div.embla__dots > button.embla__dot
Go to slide 2 of 3 fieldset > div#embla-free-demo > div.embla__dots > button.embla__dot
Go to slide 3 of 3 fieldset > div#embla-free-demo > div.embla__dots > button.embla__dot
EN div.w-locales-list > div.w-locales-items > div.w-locales-item > a.pointer-event-none

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>`
`[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
Input buttons have discernible text.
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.
Select elements have associated label elements.
`button`, `link`, and `menuitem` elements have accessible names
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
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
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 type="image">` elements have `[alt]` text
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
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.

Send Feedback