Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 6 REVIEW 4 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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

6 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 6 <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

9 landmarks

REVIEW

9 landmarks

<main> landmark present

6 <nav> landmark(s) found

5 of 6 <nav> elements are unlabeled

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

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

Heading Hierarchy

22 headings, 2 skip(s)

REVIEW

22 headings, 2 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H2 → H5 (missing H3)

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

H4 The State of Video Live Show
H1 Video marketing platform
H3 Trusted by over 440,000 customers skipped
H2 Tired of tool overload?
H3 Video hosting & management
H3 Webinars
H3 Recording & editing
H3 Actionable insights
H2 Wistia syncs with your tech stack
H2 Like what you see?
H2 Read all about it
H3 2026 State of Video Live Show
H3 AI Video Marketing Trends
H3 Choosing between Wistia & Vimeo?
H3 Top-notch customer support
H2 We think you’ll love Wistia, but don’t take our word for it.
H2 Ready to take Wistia for a spin?
H5 Product skipped
H5 Learning Center
H5 Video Series
H5 Support
H5 Company

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Link & Button Quality

4 issue(s) across 151 links and 1 buttons

REVIEW

4 issue(s) across 151 links and 1 buttons

4 link(s) with generic text

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

Got: /product/hosting ("Learn more"); /product/webinar-hosting ("Learn more"); /product/video-recording ("Learn more"); /product/analytics ("Learn more")

147 link(s) with descriptive text

151 links

0 empty

4 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/product/hosting	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Hosting
/product/webinar-hosting	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Webinar Hosting
/product/video-recording	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Video Recording
/product/analytics	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Analytics

148 links and buttons have descriptive text

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

/product/hosting ("Learn more"); /product/webinar-hosting ("Learn more"); /product/video-recording ("Learn more"); /product/analytics ("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

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 Facebook icon ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

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 hsla(0, 0%, 100%, 0.25) ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA 1 pass AA only

title The Video Marketing Platform for Busines…

3.14:1

#000000

#2948E4

needs 4.5:1 (normal text)

16px · top of page (header area)

p Wed, Apr 22 @ 11 AM EDT

3.14:1

#000000

#2948E4

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Video marketing plat…	14.53:1	3.0:1	#000000	#CCD5FF	Pass
h2 Tired of tool overlo…	14.53:1	3.0:1	#000000	#CCD5FF	Pass
h2 Wistia syncs with yo…	14.53:1	3.0:1	#000000	#CCD5FF	Pass
h2 Like what you see?	14.53:1	3.0:1	#000000	#CCD5FF	Pass
h2 Read all about it	14.53:1	3.0:1	#000000	#CCD5FF	Pass
h2 We think you’ll lo…	14.53:1	3.0:1	#000000	#CCD5FF	Pass
h2 Ready to take Wistia…	14.53:1	3.0:1	#000000	#CCD5FF	Pass
h3 Trusted by over 440,…	14.53:1	3.0:1	#000000	#CCD5FF	Pass
h3 Video hosting & mana…	14.53:1	3.0:1	#000000	#CCD5FF	Pass
h3 Webinars	14.53:1	3.0:1	#000000	#CCD5FF	Pass
h3 Recording & editing	14.53:1	3.0:1	#000000	#CCD5FF	Pass
h3 Actionable insights	14.53:1	3.0:1	#000000	#CCD5FF	Pass
h3 2026 State of Video …	14.53:1	3.0:1	#000000	#CCD5FF	Pass
h3 AI Video Marketing T…	14.53:1	3.0:1	#000000	#CCD5FF	Pass
h3 Choosing between Wis…	14.53:1	3.0:1	#000000	#CCD5FF	Pass
h3 Top-notch customer s…	14.53:1	3.0:1	#000000	#CCD5FF	Pass
title The Video Marketing …	3.14:1	4.5:1	#000000	#2948E4	Fail
p Wed, Apr 22 @ 11 AM…	3.14:1	4.5:1	#000000	#2948E4	Fail
h4 The State of Video L…	3.14:1	3.0:1	#000000	#2948E4	Pass
a Product	21.00:1	4.5:1	#000000	#FFFFFF	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.

Alt Text Quality

1 of 25 images have issues

PASS

1 of 25 images have issues

1 image(s) with generic alt text

4 image(s) with alt text over 125 characters

20 image(s) with good alt text

25 images 20 good alt text 1 generic

Issue	Count
generic	1 image(s)
too long	4 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 27 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.w-bottom-bar-right-inner > div.w-css-reset > div.w-vulcan-button-wrapper > button.w-vulcan-v2-button `div.w-bottom-bar-right-inner > div.w-css-reset > div.w-vulcan-button-wrapper > button.w-vulcan-v2-button`

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.

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
TRUSTED BY OVER 440,000 CUSTOMERS `div.Section__SectionContent-sc-e1c007ce-1 > div.HeroSplit__HeroContainer-sc-bde179c7-0 > div.SocialProof__SocialProofContainer-sc-d5fbdc16-0 > h3.styles__Eyebrow-sc-f6571d14-1`
Product `div.Section__SectionContent-sc-e1c007ce-1 > div.Footer__FooterSections-sc-883ca9c6-2 > nav.Footer__FooterNavSection-sc-883ca9c6-4 > h5`

These are opportunities to improve keyboard navigation in your application.

○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

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

●ARIA input fields have accessible names

●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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

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

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