Skip to content
https://wondershare.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

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::
19 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 19 <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
24 landmarks
REVIEW
24 landmarks
Info::
<main> landmark present
Info::
19 <nav> landmark(s) found
Warning::
19 of 19 <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 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
Heading Hierarchy
Action
18 headings, 3 skip(s)
REVIEW
18 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 ws
  • H4 Text to Image skipped
  • H4 AI Sound Effect
  • H4 AI Image to Video
  • H2 Explore Wondershare AI >
  • H4 AI Music Generator skipped
  • H4 Text to Video
  • H4 Chat with PDF
  • H2 Explore Wondershare AI >
  • H2 AI at Play, Creative Video.
  • H4 Microsoft Xbox Research team uses Wondershare Filmora for a large group user study skipped
  • H4 Puma Turkey uses Wondershare EdrawMind to digitize internal processes
  • H4 Bose Automotive reduces costs by 70% with Wondershare PDFelement
  • H4 LGMS accelerates growth with Wondershare PDFelement
  • H5 Hero Products
  • H5 Wondershare
  • H5 Explore AI
  • H5 Help Center

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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 Page Not Found | Wondershare ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

1 pass 19 fail WCAG AA
h2 Explore Wondershare AI >
1.04:1
#000000
on
#070608
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore Wondershare AI >
1.04:1
#000000
on
#070608
needs 3.0:1 (large text)
24px · bottom of viewport
h2 AI at Play, Creati…
1.04:1
#000000
on
#070608
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
div Cookies Service
2.43:1
#000000
on
#4D4B4C
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
div We use cookies to process end device inf…
1.05:1
#000000
on
#0A080A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Reject All
1.11:1
#000000
on
#121111
needs 4.5:1 (normal text)
16px · top of page (header area)
span Accept All
1.43:1
#000000
on
#072B3F
needs 4.5:1 (normal text)
16px · above the fold
span Save and Exit
1.53:1
#000000
on
#003145
needs 4.5:1 (normal text)
16px · above the fold
a Settings
1.56:1
#000000
on
#003346
needs 4.5:1 (normal text)
16px · above the fold
span wondershare
1.26:1
#000000
on
#2B172E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Featured Products
1.34:1
#000000
on
#1A223D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
div AIGC Digital Creativity
2.12:1
#000000
on
#3C4543
needs 4.5:1 (normal text)
16px · above the fold
nav Video Creativity Products
2.21:1
#000000
on
#3D4845
needs 4.5:1 (normal text)
16px · above the fold
div Filmora
1.83:1
#000000
on
#3A3A30
needs 4.5:1 (normal text)
16px · above the fold
div Complete Video Editing Tool.
1.85:1
#000000
on
#3F3938
needs 4.5:1 (normal text)
16px · above the fold
div ToMoviee AI
1.51:1
#000000
on
#322B24
needs 4.5:1 (normal text)
16px · mid-page
div All-in-One AI Creative Studio.
1.04:1
#000000
on
#070608
needs 4.5:1 (normal text)
16px · mid-page
div UniConverter
1.04:1
#000000
on
#070608
needs 4.5:1 (normal text)
16px · mid-page
div High-Speed Media Conversion.
1.04:1
#000000
on
#070608
needs 4.5:1 (normal text)
16px · mid-page

4 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
h2 Explore Wondershare …1.04:13.0:1
#000000
#070608
Fail
h2 Explore Wondershare …1.04:13.0:1
#000000
#070608
Fail
h2 AI at Play, …1.04:13.0:1
#000000
#070608
Fail
title Wondershare Official…9.90:14.5:1
#000000
#B2B2B2
Pass
div Cookies Service2.43:14.5:1
#000000
#4D4B4C
Fail
div We use cookies to pr…1.05:14.5:1
#000000
#0A080A
Fail
span Reject All1.11:14.5:1
#000000
#121111
Fail
span Accept All1.43:14.5:1
#000000
#072B3F
Fail
span Save and Exit1.53:14.5:1
#000000
#003145
Fail
a Settings1.56:14.5:1
#000000
#003346
Fail
span wondershare1.26:14.5:1
#000000
#2B172E
Fail
span Featured Products1.34:14.5:1
#000000
#1A223D
Fail
div AIGC Digital Creativ…2.12:14.5:1
#000000
#3C4543
Fail
nav Video Creativity Pro…2.21:14.5:1
#000000
#3D4845
Fail
div Filmora1.83:14.5:1
#000000
#3A3A30
Fail
div Complete Video Editi…1.85:14.5:1
#000000
#3F3938
Fail
div ToMoviee AI1.51:14.5:1
#000000
#322B24
Fail
div All-in-One AI Creati…1.04:14.5:1
#000000
#070608
Fail
div UniConverter1.04:14.5:1
#000000
#070608
Fail
div High-Speed Media Con…1.04:14.5:1
#000000
#070608
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.

C
Lighthouse Accessibility Audits
Action
Score 76/100 — 7 failing, 23 passed
REVIEW
76

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
nav.wsc-header2020-navbar-master > div.wsc-header2020-container > div.wsc-header2020-navbar-content > button.wsc-header2020-navbar-collapse-toggle nav.wsc-header2020-navbar-master > div.wsc-header2020-container > div.wsc-header2020-navbar-content > button.wsc-header2020-navbar-collapse-toggle

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div#WSFD-container > iframe#WSFD-dom body > div#WSFD-container > iframe#WSFD-dom

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header.wsc-header2020 > nav.wsc-header2020-navbar-master > div.wsc-header2020-navbar-brand-ws > a header.wsc-header2020 > nav.wsc-header2020-navbar-master > div.wsc-header2020-navbar-brand-ws > a
div.wsc-footer2020-top-content > div.wsc-footer2020-nav > div > a.active_menu_a
div.wsc-footer2020-top-content > div.wsc-footer2020-nav > div > a.active_menu_a
div.wsc-footer2020-top-content > div.wsc-footer2020-nav > div > a.active_menu_a
div.wsc-footer2020-top-content > div.wsc-footer2020-nav > div > a.active_menu_a
div.wsc-footer2020-top-content > div.wsc-footer2020-nav > div > a.active_menu_a div.wsc-footer2020-top-content > div.wsc-footer2020-nav > div > a.active_menu_a

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
Accept All div.cmpboxbtns > span#cmpwelcomebtnyes > a.cmpboxbtn > span#cmpbntyestxt
Settings div.cmpboxinner > div.cmpboxbtns > div.cmpmore > a.cmpmorelink
Wondershare showcases at Gitex Morocco 2026, meet us at Hall 4, 4A-7A, Marrakec… div.h-100 > div.px-4 > div.px-md-0 > div.font-size-small

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Microsoft Xbox Research team uses Wondershare Filmora for a large group user st… div.text-container > div.unfold-box > div.text-content > h4.mb-2

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 6 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 7 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 8 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 9 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 10 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 1 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 1 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 6 div.text-center > div.d-xl-none > div.swiper-pagination > span.swiper-pagination-bullet

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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●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
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○`<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.
○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.
○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
Alt Text Quality
1 of 62 images have issues
PASS
1 of 62 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
4 decorative image(s) correctly marked
Info::
57 image(s) with good alt text
62 images 57 good alt text 4 decorative 1 missing
IssueCount
missing1 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

A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback