Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 REVIEW 4 FIX

Link & Button Quality

Action

9 issue(s) across 270 links and 33 buttons

FIX

9 issue(s) across 270 links and 33 buttons

7 link(s) with generic text

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

Got: https://www.visme.co/templates/ ("More"); https://www.visme.co/graph-maker/ ("Learn more"); https://www.visme.co/templates/ ("Learn more"); https://www.visme.co/brand-design-tool/ ("Learn more"); https://www.visme.co/social-media-scheduler/ ("Learn more"); https://www.visme.co/icon-finder/ ("Learn more"); https://www.visme.co/animation-interactivity/ ("Learn more")

27 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://dashboard.visme.co/login; https://visme.co/blog/recruitment-strategies/; https://visme.co/blog/denver-broncos-use-visme/; https://visme.co/blog/case-study-visme-interactive-reports/; https://visme.co/blog/visme-insurance-company-case-study/; https://visme.co/blog/case-study-visme-cross-departmentally/; https://visme.co/blog/visme-case-study-presentation-creation-time/; https://visme.co/blog/recruitment-strategies/; https://dashboard.visme.co/v2/create/presentations?action=openVismeDesignGene…; https://www.capterra.com/p/153139/Visme/ (+17 more)

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.v-toggle (#105 on page); button.vismecookie__button (#1820 on page)

236 link(s) with descriptive text

270 links

0 empty

7 generic text

27 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://dashboard.visme.co/login	Login	new tab	Add '(opens in new tab)' to text
https://www.visme.co/templates/	More	generic text	Replace with descriptive text
Before: More Suggested: Templates
https://visme.co/blog/recruitment-strate…	Read this case study	new tab	Add '(opens in new tab)' to text
https://visme.co/blog/denver-broncos-use…	Read this case study	new tab	Add '(opens in new tab)' to text
https://visme.co/blog/case-study-visme-i…	Read this case study	new tab	Add '(opens in new tab)' to text
https://visme.co/blog/visme-insurance-co…	Read this case study	new tab	Add '(opens in new tab)' to text
https://visme.co/blog/case-study-visme-c…	Read this case study	new tab	Add '(opens in new tab)' to text
https://visme.co/blog/visme-case-study-p…	Read this case study	new tab	Add '(opens in new tab)' to text
https://visme.co/blog/recruitment-strate…	Read this case study	new tab	Add '(opens in new tab)' to text
https://dashboard.visme.co/v2/create/pre…	Try it free	new tab	Add '(opens in new tab)' to text
https://www.visme.co/graph-maker/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Graph Maker
https://www.visme.co/templates/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Templates
https://www.visme.co/brand-design-tool/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Brand Design Tool
https://www.visme.co/social-media-schedu…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Social Media Scheduler
https://www.visme.co/icon-finder/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Icon Finder
https://www.visme.co/animation-interacti…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Animation Interactivity
https://www.capterra.com/p/153139/Visme/	Capterra	new tab	Add '(opens in new tab)' to text
https://www.g2.com/products/visme/review…	G2 - Leader	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/c/VismeApp?sub_c…	YouTube	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/vismeapp	Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/visme	LinkedIn	new tab	Add '(opens in new tab)' to text
https://twitter.com/vismeapp	Twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/vismeapp/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/VismeApp/	Pinterest	new tab	Add '(opens in new tab)' to text
https://visme.co/blog/recruitment-strate…	How IBM Uses Infographics to A…	new tab	Add '(opens in new tab)' to text
https://visme.co/blog/	More from our blog >	new tab	Add '(opens in new tab)' to text
https://www.capterra.com/p/153139/Visme/	Capterra	new tab	Add '(opens in new tab)' to text
https://www.g2.com/products/visme/review…	G2 - Leader	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/c/VismeApp?sub_c…	YouTube	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/vismeapp	Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/visme	LinkedIn	new tab	Add '(opens in new tab)' to text
https://twitter.com/vismeapp	Twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/vismeapp/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/VismeApp/	Pinterest	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

267 links and buttons have descriptive text

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

https://www.visme.co/templates/ ("More"); https://www.visme.co/graph-maker/ ("Learn more"); https://www.visme.co/templates/ ("Learn more"); https://www.visme.co/brand-design-tool/ ("Learn more"); https://www.visme.co/social-media-scheduler/ ("Learn more"); https://www.visme.co/icon-finder/ ("Learn more"); https://www.visme.co/animation-interactivity/ ("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

Add '(opens in new tab)' to link text or aria-label.

https://dashboard.visme.co/login; https://visme.co/blog/recruitment-strategies/; https://visme.co/blog/denver-broncos-use-visme/; https://visme.co/blog/case-study-visme-interactive-reports/; https://visme.co/blog/visme-insurance-company-case-study/; https://visme.co/blog/case-study-visme-cross-departmentally/; https://visme.co/blog/visme-case-study-presentation-creation-time/; https://visme.co/blog/recruitment-strategies/; https://dashboard.visme.co/v2/create/presentations?action=openVismeDesignGene…; https://www.capterra.com/p/153139/Visme/ (+17 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.v-toggle (#105 on page); button.vismecookie__button (#1820 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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

1 navigation landmark(s) detected

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 1 <nav> element(s)

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.

Form Accessibility

Action

3 of 3 controls have issues

REVIEW

3 of 3 controls have issues

3 control(s) without accessible label

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

Got: <input type="checkbox" id="vismecookie-analytics-toggle">; <input type="checkbox" id="vismecookie-advertisement-toggle">; <input type="checkbox" id="vismecookie-functionality-toggle">

3 controls

0 labeled

0 placeholder only

3 unlabeled

Control	Type	Label	Method
#vismecookie-analytics-toggle	checkbox	(none)	none
#vismecookie-advertisement-toggle	checkbox	(none)	none
#vismecookie-functionality-toggle	checkbox	(none)	none

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

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

404 Error Page

Action

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

7 icon(s) detected

REVIEW

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Visme

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name Visme ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Name Visme Display Mode standalone Theme Color #2b3140 Background Color #2b3140 Icons 2 icon(s)

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

33 headings, 1 skip(s)

PASS

33 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H1 Create high-converting, engaging, branded content — faster
H2 Start creating today, no design experience required
H2 Presentations
H2 Documents
H2 Data visualizations
H2 Social media graphics
H2 Videos
H2 Wireframes & mockups
H2 Learn how major businesses leveled up content with Visme
H2 Experience more design capabilities at your fingertips
H3 Generate ready-to-use designs with Visme AI Designer
H3 Turn statistics and figures into beautiful visuals
H3 Choose from thousands of customizable templates
H3 End-to-end branded content creation in a fraction of the time
H3 Create, schedule and publish your content all from one place
H3 Millions of unique photos & icons to set your work apart
H3 Engage your audience with interactivity and animations
H2 Collaborate with teammates
H3 Collaboration
H3 Precise communication
H3 Asset management
H2 Unlock creativity from branded visuals to interactive content
H2 Discover what Visme can do for you
H3 Create content faster
H3 Choose from thousands of templates
H3 Create content faster
H3 Choose from thousands of templates
H3 Manage projects in style
H3 Create and track engagement
H3 Manage projects in style
H3 Create and track engagement
H2 Connect with the tools you already use
H4 Manage cookies skipped

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

Alt Text Quality

1 of 91 images have issues

PASS

1 of 91 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

90 image(s) with good alt text

91 images 90 good alt text 1 missing

Issue	Count
missing	1 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+

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)

Element	Ratio	Required	FG	BG	Result
h1 Create high-converti…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 branded content — …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Start creating today…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Learn how major busi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Experience more desi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Collaborate with tea…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Unlock creativity fr…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Discover what Visme …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Connect with the too…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 you already use	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Generate ready-to-us…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Turn statistics and …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Choose from thousand…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 End-to-end branded c…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Create, schedule and…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Millions of unique p…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Engage your audience…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Collaboration	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Precise communicatio…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Asset management	21.00:1	3.0: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.

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 23 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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
“In this digital age, social media is playing an increasingly larger role in th… `div.visme-testimonial-slider > div.flickity-viewport > div.flickity-slider > div.visme-testimonial-slider__slide`
“At the Broncos, we recommend Visme to other teams, brands, or organizations lo… `div.visme-testimonial-slider > div.flickity-viewport > div.flickity-slider > div.visme-testimonial-slider__slide`
“We use Visme not just for reporting but also for engaging our stakeholders and… `div.visme-testimonial-slider > div.flickity-viewport > div.flickity-slider > div.visme-testimonial-slider__slide`
“The hours saved each month from meeting time, working back and forth between t… `div.visme-testimonial-slider > div.flickity-viewport > div.flickity-slider > div.visme-testimonial-slider__slide`
“It’s easy to create something in Visme quickly that looks like we sent it out … `div.visme-testimonial-slider > div.flickity-viewport > div.flickity-slider > div.visme-testimonial-slider__slide`
“I absolutely recommend Visme due to its dynamic functionality and ability to i… `div.visme-testimonial-slider > div.flickity-viewport > div.flickity-slider > div.visme-testimonial-slider__slide`
“Visme is something that I would highly recommend. It made us look a lot better… `div.visme-testimonial-slider > div.flickity-viewport > div.flickity-slider > div.visme-testimonial-slider__slide`

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.

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
Sign up free `div.hero > div.container > button.d-inline-block > span`
CASE STUDIES `main.has-sticky-menu > section.pt-5 > div.container > p.user-select-none`
Read this case study `div > div.visme-testimonial-slider__slide-author > p.ps-1 > a.visme-testimonial-slider__slide-button`
FEATURES `main.has-sticky-menu > section.pt-5 > div.container > p.text-center`
TEAMWORK `main.has-sticky-menu > section.pt-5 > div.container > p.text-center`
CREATE FROM A TO Z `main.has-sticky-menu > section.pt-5 > div.container > p.text-center`
SOLUTIONS FOR EVERYONE `main.has-sticky-menu > section.pt-5 > div.container > p.text-center`
INTEGRATIONS `main.has-sticky-menu > section.pt-5 > div.container > p.text-center`
CREATE `div.footer-container > div.block-menus-container > div.menus-container > strong.heading`
USE CASES `div.footer-container > div.block-menus-container > div.menus-container > strong.heading`
RESOURCES `div.footer-container > div.block-menus-container > div.menus-container > strong.heading`
COMPANY `div.footer-container > div.block-menus-container > div.menus-container > strong.heading`
SUPPORT `div.footer-container > div.block-menus-container > div.menus-container > strong.heading`
RECENT FEATURES & ARTICLES `footer.footer-21-v1 > div.footer-container > div.block-blog-container > strong.heading`
Copyright 2026 Easy WebContent, LLC. (DBA Visme). All rights reserved. Proudly … `footer.footer-21-v1 > div.footer-container > div.block-menus-container > p.copyright`

These are opportunities to improve the legibility of your content.

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

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

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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

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

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

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

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