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

3 <nav> landmark(s) found

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

Alt Text Quality

Action

2 of 45 images have issues

FIX

2 of 45 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

An image inside a link with no alt creates an empty link.

43 image(s) with good alt text

45 images 43 good alt text 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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: #000000

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

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

Lighthouse Accessibility Audits

Action

Score 65/100 — 6 failing, 11 passed

FIX

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.

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
JOIN NOW! `ul.header-pane > li.tagline > div.ctas > a.join`
LEARN MORE `ul.header-pane > li.tagline > div.ctas > a.explore`
PRO `div.module > div.text > p > a.pro`
BUSINESS `div.module > div.text > p > a.pro`
WATCH INTRO VIDEO `article.modular > div.module > div.text > span.mbtn`
PRO `div.module > div.text > p > a.pro`
BUSINESS `div.module > div.text > p > a.pro`
LEARN MORE `article.modular > div.module > div.text > a.mbtn`
JOIN NOW `article.modular > div.module > div.text > a.mbtn`
Ben Claremont `div.module > div.testimonial > p > a.user`
VirtualTourPro `div.module > div.testimonial > p > a.link`
Michael Ty `div.module > div.testimonial > p > a.user`
360rumors `div.module > div.testimonial > p > a.link`
Martin Kulhavy `div.module > div.testimonial > p > a.user`
www.martin.kulhavy.info `div.module > div.testimonial > p > a.link`
MORE TESTIMONIALS `div.about-wrapper > article.modular > div.module > a.mbtn`
JOIN NOW! `div.about-wrapper > article.modular > div.module > a.mbtn`
EXPLORE `div.about-wrapper > article.modular > div.module > a.mbtn`
More info `div.blog-post > a > p > span.continue`
More info `div.blog-post > a > p > span.continue`
More info `div.blog-post > a > p > span.continue`
KUULA BLOG `div.about-wrapper > article.modular > div.module > a.mbtn`
Read our guide `div.blog-post > a > p > span.continue`
Here's how `div.blog-post > a > p > span.continue`
PRO `div.blog-post > a > div.head-title > span.pro`
PRO `div.blog-post > a > p > span.pro`
See features and pricing `div.blog-post > a > p > span.continue`
ALL TUTORIALS `div.about-wrapper > article.modular > div.module > a.mbtn`
Get in touch! `div.content-pane > ul.social > li.head > a.grey`
We're social `footer > div.content-pane > ul.social > li.head`
Blog `div.content-pane > ul.other > li > a`
Support `div.content-pane > ul.other > li > a`
Change Log `div.content-pane > ul.other > li > a`
Debug Page `div.content-pane > ul.other > li > a`
Status `div.content-pane > ul.other > li > a`
Terms `div.content-pane > ul.legal > li > a`
Privacy Policy `div.content-pane > ul.legal > li > a`
GDPR `div.content-pane > ul.legal > li > a`
© 2016-2026 Kuula Inc. All Rights Reserved \| Build 866r22 TH `body > footer > div.copyright > span._ert`
Artwork by Flaticon & EmojiOne `body > footer > div.copyright > span`
Flaticon `footer > div.copyright > span > a`
EmojiOne `footer > div.copyright > span > a`
Register `body > nav.bar > a.lout > span.text`

These are opportunities to improve the legibility of your content.

Names and labels

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
div.about-wrapper > header > div.splash > iframe `div.about-wrapper > header > div.splash > iframe`

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
750,000+ `div.module > ul > li > h4`

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
Ben Claremont `div.module > div.testimonial > p > a.user`
VirtualTourPro `div.module > div.testimonial > p > a.link`
Michael Ty `div.module > div.testimonial > p > a.user`
360rumors `div.module > div.testimonial > p > a.link`
Martin Kulhavy `div.module > div.testimonial > p > a.user`
www.martin.kulhavy.info `div.module > div.testimonial > p > a.link`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js `html.js`

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-hidden="true"]` is not present on the document `<body>`

●Image elements have `[alt]` attributes

●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

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

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

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

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

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

Heading Hierarchy

22 headings, 1 skip(s)

REVIEW

22 headings, 1 skip(s)

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H2 → H4 (missing H3)

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

H1 Virtual Tours made easy. Create, edit, share.
H2 Kuula is the most popular virtual tour software to create 3D 360 tours for real estate, architecture, construction, art galleries, education and more.
H4 750,000+ skipped
H4 21 million+
H4 2 million+
H4 2.2 billion+
H4 Trusted by teams at:
H3 Create Virtual Toursthat engage your audience
H3 The smoothest and most efficient3D 360 Virtual Tour player on the web
H3 Easily share, embed and add to listings
H3 Let your virtual tours shine on mobile
H3 Enter the world of Virtual Reality
H3 Reach anyone, anywhere
H3 All cameras supported!
H3 A worldwide community
H4 What users say about Kuula
H4 Kuula and our images have been featured on
H4 Are you ready to start building virtual tours?
H3 About Kuula
H4 What's new?
H4 Articles and tutorials
H1 Oups! duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

Link & Button Quality

Action

5 issue(s) across 88 links and 6 buttons

REVIEW

5 issue(s) across 88 links and 6 buttons

2 link(s) with generic text

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

Got: ("LEARN MORE"); page/pro ("Learn More")

21 link(s) open in new tab without warning

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

Got: post/n1/collection/7PNXK; tinyplanet/7YyzN; https://www.virtualtourpro.com/; https://www.virtualtourpro.com/; http://360rumors.com; http://360rumors.com; https://kuula.co/profile/MartinKulhavy; https://kuula.co/profile/MartinKulhavy; https://blog.kuula.co?utm_name=kuula&utm_source=home&utm_medium=website; about?utm_source=sug (+11 more)

3 button(s) with no accessible text

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

Got: button (#313 on page); button (#315 on page); button.close (#410 on page)

65 link(s) with descriptive text

88 links

0 empty

2 generic text

21 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: Home page
post/n1/collection/7PNXK	Virtual Tour by PostRain	new tab	Add '(opens in new tab)' to text
page/pro	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Pro
tinyplanet/7YyzN	Honolulu, HI by Island Imaging	new tab	Add '(opens in new tab)' to text
https://www.virtualtourpro.com/	Ben Claremont	new tab	Add '(opens in new tab)' to text
https://www.virtualtourpro.com/	VirtualTourPro	new tab	Add '(opens in new tab)' to text
http://360rumors.com	Michael Ty	new tab	Add '(opens in new tab)' to text
http://360rumors.com	360rumors	new tab	Add '(opens in new tab)' to text
https://kuula.co/profile/MartinKulhavy	Martin Kulhavy	new tab	Add '(opens in new tab)' to text
https://kuula.co/profile/MartinKulhavy	www.martin.kulhavy.info	new tab	Add '(opens in new tab)' to text
https://blog.kuula.co?utm_name=kuula&utm…	KUULA BLOG	new tab	Add '(opens in new tab)' to text
about?utm_source=sug	#1 Virtual Tour EditorThe most…	new tab	Add '(opens in new tab)' to text
page/pro?utm_source=sug	Upgrade to PROKuula PRO offer…	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/kuulapic	Facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/c/kuulapic	Youtube	new tab	Add '(opens in new tab)' to text
https://twitter.com/kuulapic	Twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/kuula	LinkedIn	new tab	Add '(opens in new tab)' to text
https://instagram.com/kuulapic	Instagram	new tab	Add '(opens in new tab)' to text
/test	Debug Page	new tab	Add '(opens in new tab)' to text
https://stats.uptimerobot.com/0nWR3fJJOn	Status	new tab	Add '(opens in new tab)' to text
http://stripe.com	Powered by Stripe	new tab	Add '(opens in new tab)' to text
https://www.flaticon.com	Flaticon	new tab	Add '(opens in new tab)' to text
https://www.emojione.com/	EmojiOne	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
<button>	(empty)	empty	Add button text or aria-label

68 links and buttons have descriptive text

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

("LEARN MORE"); page/pro ("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.

post/n1/collection/7PNXK; tinyplanet/7YyzN; https://www.virtualtourpro.com/; https://www.virtualtourpro.com/; http://360rumors.com; http://360rumors.com; https://kuula.co/profile/MartinKulhavy; https://kuula.co/profile/MartinKulhavy; https://blog.kuula.co?utm_name=kuula&utm_source=home&utm_medium=website; about?utm_source=sug (+11 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 (#313 on page); button (#315 on page); button.close (#410 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

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Kuula | Not found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Favicon & Branding

12 icon(s) detected

REVIEW

12 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

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Kuula

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Kuula ✓192×192 icon ✓512×512 icon ✓Start URL https://kuula.co/feed?utm_source=pwapp ✓Display Mode standalone ✓

Name Kuula Display Mode standalone Background Color #4092b4 Icons 5 icon(s)

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 Virtual Tours made e…	11.42:1	3.0:1	#000000	#BFBFBF	Pass
h1 Oups!	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Kuula is the most po…	8.61:1	3.0:1	#000000	#A5A6A7	Pass
h2 to create 3D 360 tou…	7.56:1	3.0:1	#000000	#9B9B9C	Pass
h3 Create Virtual Tours	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 that engage your aud…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The smoothest and mo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 3D 360 Virtual Tour …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Easily share, embed …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Let your virtual tou…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Enter the world of V…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Reach anyone, anywhe…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 All cameras supporte…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 A worldwide communit…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 About Kuula	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Kuula: #1 Virtual To…	19.93:1	4.5:1	#000000	#F9F9F8	Pass
strong virtual tour softwar…	7.56:1	3.0:1	#000000	#9B9B9C	Pass
a JOIN NOW!	7.56:1	4.5:1	#000000	#9B9B9B	Pass
a LEARN MORE	7.46:1	4.5:1	#000000	#9A9A9A	Pass
p It takes less than 3…	7.46:1	4.5:1	#000000	#9A9A9A	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.

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