Skip to content
https://techsmith.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Landmark Structure
Action
7 landmarks
REVIEW
7 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation" MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | TechSmith ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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 Missing
✓ Multiple Sizes Present
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 Smarter screen capture and recording sta…
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
32px · bottom of viewport
h2 AI-powered tools that support your workf…
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
24px · bottom of viewport
h2 We’re always building something better
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
24px · bottom of viewport
h2 invented screen capture
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Turn knowledge into action
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Crowd faves
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Privacy Preference Center
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Editor
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Snagit
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Audiate
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Rev Media Now Editable on Timeline (Beta…
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Single Window or Application Recording
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Instantly Turn Clicks Into Step-by-Step …
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Instantly Redact Sensitive Information f…
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Eliminate Distractions with AI Backgroun…
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Make Cursor Movements Look Cinematic wit…
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sync Generate Avatar Updates from Audiat…
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Easily Stitch Multiple Videos Together
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Technical documentation
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Corporate training
1.59:1
#000000
on
#2A3137
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Smarter screen captu…1.59:13.0:1
#000000
#2A3137
Fail
h2 AI-powered tools tha…1.59:13.0:1
#000000
#2A3137
Fail
h2 We’re always build…1.59:13.0:1
#000000
#2A3137
Fail
h2 invented screen capt…1.59:13.0:1
#000000
#2A3137
Fail
h2 Turn knowledge into …1.59:13.0:1
#000000
#2A3137
Fail
h2 Crowd faves1.59:13.0:1
#000000
#2A3137
Fail
h2 Privacy Preference C…1.59:13.0:1
#000000
#2A3137
Fail
h3 Editor1.59:13.0:1
#000000
#2A3137
Fail
h3 Snagit1.59:13.0:1
#000000
#2A3137
Fail
h3 Audiate1.59:13.0:1
#000000
#2A3137
Fail
h3 Rev Media Now Editab…1.59:13.0:1
#000000
#2A3137
Fail
h3 Single Window or App…1.59:13.0:1
#000000
#2A3137
Fail
h3 Instantly Turn Click…1.59:13.0:1
#000000
#2A3137
Fail
h3 Instantly Redact Sen…1.59:13.0:1
#000000
#2A3137
Fail
h3 Eliminate Distractio…1.59:13.0:1
#000000
#2A3137
Fail
h3 Make Cursor Movement…1.59:13.0:1
#000000
#2A3137
Fail
h3 Sync Generate Avatar…1.59:13.0:1
#000000
#2A3137
Fail
h3 Easily Stitch Multip…1.59:13.0:1
#000000
#2A3137
Fail
h3 Technical documentat…1.59:13.0:1
#000000
#2A3137
Fail
h3 Corporate training1.59:13.0:1
#000000
#2A3137
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
29 headings
PASS
29 headings
Info::
Single H1 present
  • H3 Editor
  • H3 Snagit
  • H3 Audiate
  • H1 Smarter screen capture and recording starts here
  • H2 AI-powered tools that support your workflow
  • H2 We’re always building something better
  • H3 Rev Media Now Editable on Timeline (Beta)
  • H3 Single Window or Application Recording
  • H3 Instantly Turn Clicks Into Step-by-Step Guides
  • H3 Instantly Redact Sensitive Information from Screenshots
  • H3 Eliminate Distractions with AI Background Noise Removal
  • H3 Make Cursor Movements Look Cinematic with New Effects
  • H3 Sync Generate Avatar Updates from Audiate
  • H3 Easily Stitch Multiple Videos Together
  • H2 We literally invented screen capture
  • H2 Turn knowledge into action
  • H3 Technical documentation
  • H3 Corporate training
  • H3 Team communication
  • H2 Crowd faves
  • H3 Snagit
  • H3 Camtasia
  • H2 Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies
  • H5 Performance Cookies
  • H5 Functional Cookies
  • H4 Targeting Cookies
  • H3 Performance Cookies
A
Alt Text Quality
1 of 111 images have issues
PASS
1 of 111 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 image(s) with alt text over 125 characters
Info::
34 decorative image(s) correctly marked
Info::
75 image(s) with good alt text
111 images 75 good alt text 34 decorative 1 missing
IssueCount
missing1 image(s)
too long1 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
All 6 controls labeled
PASS
All 6 controls labeled
Info::
6 control(s) properly labeled
6 controls
6 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextVendor Searchfor/id
#storage-access-groupcheckboxInformation storage and accessfor/id
#select-all-vendor-leg-handlercheckboxSelect All Vendorsfor/id
#select-all-vendor-groups-handlercheckboxSelect All Vendorsfor/id
#select-all-hosts-groups-handlercheckboxAll Consent Allowedfor/id
A
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 29 passed
PASS
92

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.

ARIA

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English ul > li.wpml-ls-slot-footer > a.wpml-ls-link > span.wpml-ls-native

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

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
div.feature-box > div.feature-box-footer > div.feature-box-footer-inner > a.feature-box-footer-arrow div.feature-box > div.feature-box-footer > div.feature-box-footer-inner > a.feature-box-footer-arrow
div.feature-box > div.feature-box-footer > div.feature-box-footer-inner > a.feature-box-footer-arrow div.feature-box > div.feature-box-footer > div.feature-box-footer-inner > a.feature-box-footer-arrow
div.feature-box > div.feature-box-footer > div.feature-box-footer-inner > a.feature-box-footer-arrow div.feature-box > div.feature-box-footer > div.feature-box-footer-inner > a.feature-box-footer-arrow

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.

○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]` 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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`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
●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
●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.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○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.
○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.
○`<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.
○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