Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 6 FIX

Landmark Structure

Action

5 landmarks

FIX

5 landmarks

No <main> landmark found

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

2 <nav> landmark(s) found

2 of 2 <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

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

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

Link & Button Quality

Action

6 issue(s) across 163 links and 17 buttons

FIX

6 issue(s) across 163 links and 17 buttons

6 link(s) with generic text

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

Got: https://miro.com/ai/ai-overview ("Learn more"); https://miro.com/intelligent-canvas ("Learn more"); https://miro.com/intelligent-canvas/#formats ("Learn more"); https://miro.com/capabilities/blueprints ("Learn more"); https://miro.com/enterprise-security ("Learn more"); https://miro.com/integrations ("Learn more")

6 image-only link(s) without alt text

17 link(s) open in new tab without warning

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

Got: https://canvas.miro.com/?utm_campaign=glb-27q1-nsp-he-c1_sdmp-canvas_26_inperson&utm_source=weblink&utm_medium=redirect&utm_content=hosted%20event&utm_term=homepage-reg-live&src=-weblink_glb; https://miro.com/blog/asos-agile-shopping-experience/; https://trust.miro.com/; https://trust.miro.com/; https://trust.miro.com/; https://trust.miro.com/; https://www.capterra.com/p/128955/Miro/; https://www.g2.com/products/miro/; https://www.trustradius.com/products/miro/reviews; https://twitter.com/mirohq (+7 more)

134 link(s) with descriptive text

163 links

0 empty

6 generic text

17 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://canvas.miro.com/?utm_campaign=gl…	SAVE YOUR SPOT	new tab	Add '(opens in new tab)' to text
https://miro.com/blog/asos-agile-shoppin…	Read Customer Study	new tab	Add '(opens in new tab)' to text
https://miro.com/ai/ai-overview	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Ai Overview
https://miro.com/intelligent-canvas	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Intelligent Canvas
https://miro.com/intelligent-canvas/#for…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: #Formats
https://miro.com/capabilities/blueprints	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Blueprints
https://miro.com/enterprise-security	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Enterprise Security
https://miro.com/integrations	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Integrations
https://miro.com/pricing	PricingSelect a plan	img no alt	Add alt attribute to the image
https://miro.com/templates	TemplatesGet started fast	img no alt	Add alt attribute to the image
https://miro.com/find-a-partner	Solution PartnersExplore the n…	img no alt	Add alt attribute to the image
https://community.miro.com/	CommunityConnect with Miro use…	img no alt	Add alt attribute to the image
https://miro.com/blog	BlogDive in to ways of working	img no alt	Add alt attribute to the image
https://academy.miro.com/	AcademyGet started with Miro	img no alt	Add alt attribute to the image
https://trust.miro.com/	ISO 42001 READY	new tab	Add '(opens in new tab)' to text
https://trust.miro.com/	ISO 27001 CERTIFIED	new tab	Add '(opens in new tab)' to text
https://trust.miro.com/	SOC 2 COMPLIANT	new tab	Add '(opens in new tab)' to text
https://trust.miro.com/	GDPR COMPLIANT	new tab	Add '(opens in new tab)' to text
https://www.capterra.com/p/128955/Miro/	Trust Capterra	new tab	Add '(opens in new tab)' to text
https://www.g2.com/products/miro/	Trust G2	new tab	Add '(opens in new tab)' to text
https://www.trustradius.com/products/mir…	Trust TR	new tab	Add '(opens in new tab)' to text
https://twitter.com/mirohq	Miro Twitter	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/TryMiro	Miro Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/mirohq	Miro LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/mirohq/	Miro Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/RealtimeBoa…	Miro YouTube	new tab	Add '(opens in new tab)' to text
https://www.reddit.com/r/miro/	Miro Reddit	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/us/app/miro-colla…	Download on the App Store	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Download on Google Play	new tab	Add '(opens in new tab)' to text

151 links and buttons have descriptive text

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

https://miro.com/ai/ai-overview ("Learn more"); https://miro.com/intelligent-canvas ("Learn more"); https://miro.com/intelligent-canvas/#formats ("Learn more"); https://miro.com/capabilities/blueprints ("Learn more"); https://miro.com/enterprise-security ("Learn more"); https://miro.com/integrations ("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://canvas.miro.com/?utm_campaign=glb-27q1-nsp-he-c1_sdmp-canvas_26_inperson&utm_source=weblink&utm_medium=redirect&utm_content=hosted%20event&utm_term=homepage-reg-live&src=-weblink_glb; https://miro.com/blog/asos-agile-shopping-experience/; https://trust.miro.com/; https://trust.miro.com/; https://trust.miro.com/; https://trust.miro.com/; https://www.capterra.com/p/128955/Miro/; https://www.g2.com/products/miro/; https://www.trustradius.com/products/miro/reviews; https://twitter.com/mirohq (+7 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

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

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

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

Alt Text Quality

2 of 69 images have issues

REVIEW

2 of 69 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

50 decorative image(s) correctly marked

17 image(s) with good alt text

69 images 17 good alt text 50 decorative 2 missing

Issue	Count
missing	2 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

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

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Heading Hierarchy

22 headings, 1 skip(s)

PASS

22 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H5 (missing H2)

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

H1 Get from brainstorm to breakthrough with Miro
H5 More than 100M users and 250,000companies are collaborating on the canvas skipped
H2 The only thing more important than moving fast is moving the needle
H2 100M+
H2 250+
H2 6,000+
H2 Flow from idea to outcome in seconds
H2 Experience the Innovation Workspace
H3 AI
H3 Intelligent Canvas
H3 Formats
H3 Blueprints
H3 Enterprise Security & Scale
H3 Integrations
H2 Introducing Miro for Product Acceleration
H2 Need help getting started?
H3 Select a plan
H3 Get started fast
H3 Explore the network
H3 Connect with Miro users
H3 Dive in to ways of working
H3 Get started with Miro

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

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="email">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	email	(Enter your work email)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

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

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 Get from brainstorm …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The only thing more …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 than moving fast is …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 100M+	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 250+	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 6,000+	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Experience the Innov…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Introducing Miro for…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Need help getting st…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Intelligent Canvas	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Formats	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Blueprints	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Enterprise Security …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Integrations	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Select a plan	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Get started fast	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Explore the network	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Connect with	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Miro users	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Dive in to ways of w…	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.

A+

Lighthouse Accessibility Audits

Score 95/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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookies Settings `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-pc-btn-handler`
Reject All `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-reject-all-handler`
Accept All Cookies `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-accept-btn-handler`

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
More than 100M users and 250,000 companies are collaborating on the canvas `div.framer-17ox8cb > div.framer-am0iu1 > div.framer-3qyfb9 > h5.framer-text`

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

●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

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

●Touch targets have sufficient size and spacing.

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

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

○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

○Links are distinguishable without relying on color.

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.