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

4 icon(s) detected

FIX

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

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

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

Heading Hierarchy

14 headings

REVIEW

14 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Corporate Real Estate
H3 Make smarter big picture decisions with digital twins.
H2 Property Marketing
H3 Increase buyer and seller confidence with digital twins.
H2 Facilities Management
H3 Revolutionize operations with digital twins.
H2 Design & Construction
H3 Stay on time and budget with digital twins.
H3 Corporate Real Estate
H3 Design & Construction
H3 Facilities Management
H3 Property Marketing
H3 My Cart
H3 Total

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Alt Text Quality

Action

4 of 31 images have issues

REVIEW

4 of 31 images have issues

4 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 decorative image(s) correctly marked

25 image(s) with good alt text

31 images 25 good alt text 2 decorative 4 missing

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

Link & Button Quality

Action

5 issue(s) across 25 links and 14 buttons

REVIEW

5 issue(s) across 25 links and 14 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#main-content

1 link(s) with generic text

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

Got: /solutions/corporate-real-estate ("Learn More")

3 button(s) with no accessible text

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

Got: button.Button_Button__o21gk (#127 on page); button.Button_Button__o21gk (#235 on page); button.Button_Button__o21gk (#237 on page)

23 link(s) with descriptive text

25 links

1 empty

1 generic text

0 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
/solutions/corporate-real-estate	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Corporate Real Estate
<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

34 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#main-content

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

/solutions/corporate-real-estate ("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

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

button.Button_Button__o21gk (#127 on page); button.Button_Button__o21gk (#235 on page); button.Button_Button__o21gk (#237 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

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: This page could not be found | Matterport ✓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.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA

h2 Property Marketing

1.32:1

#000000

#222222

needs 3.0:1 (large text)

24px · mid-page

h2 Facilities Management

1.32:1

#000000

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Design & Construction

1.32:1

#000000

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Corporate Real Estate

1.32:1

#000000

#222222

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Design & Construction

1.32:1

#000000

#222222

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Facilities Management

1.32:1

#000000

#222222

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Property Marketing

1.32:1

#000000

#222222

needs 3.0:1 (large text)

19px · bottom of viewport

h3 My Cart

1.32:1

#000000

#222222

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Total

1.32:1

#000000

#222222

needs 3.0:1 (large text)

19px · bottom of viewport

span Search

1.02:1

#000000

#010305

needs 4.5:1 (normal text)

16px · top of page (header area)

a Contact Us

1.02:1

#000000

#020405

needs 4.5:1 (normal text)

16px · top of page (header area)

span Cart

1.02:1

#000000

#010405

needs 4.5:1 (normal text)

16px · above the fold

span Solutions

1.03:1

#000000

#060508

needs 4.5:1 (normal text)

16px · above the fold

span Products

1.04:1

#000000

#070707

needs 4.5:1 (normal text)

16px · above the fold

span Pricing

1.05:1

#000000

#080808

needs 4.5:1 (normal text)

16px · above the fold

span Resources

1.10:1

#000000

#0F0F0F

needs 4.5:1 (normal text)

16px · above the fold

span What's New

1.22:1

#000000

#1B1B1B

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Corporate Real Estat…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Property Marketing	1.32:1	3.0:1	#000000	#222222	Fail
h2 Facilities Managemen…	1.32:1	3.0:1	#000000	#222222	Fail
h2 Design & Constructio…	1.32:1	3.0:1	#000000	#222222	Fail
h3 Corporate Real Estat…	1.32:1	3.0:1	#000000	#222222	Fail
h3 Design & Constructio…	1.32:1	3.0:1	#000000	#222222	Fail
h3 Facilities Managemen…	1.32:1	3.0:1	#000000	#222222	Fail
h3 Property Marketing	1.32:1	3.0:1	#000000	#222222	Fail
h3 My Cart	1.32:1	3.0:1	#000000	#222222	Fail
h3 Total	1.32:1	3.0:1	#000000	#222222	Fail
title Capture, share, and …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Search	1.02:1	4.5:1	#000000	#010305	Fail
a Contact Us	1.02:1	4.5:1	#000000	#020405	Fail
span Cart	1.02:1	4.5:1	#000000	#010405	Fail
span Solutions	1.03:1	4.5:1	#000000	#060508	Fail
span Products	1.04:1	4.5:1	#000000	#070707	Fail
span Pricing	1.05:1	4.5:1	#000000	#080808	Fail
span Resources	1.10:1	4.5:1	#000000	#0F0F0F	Fail
span What's New	1.22:1	4.5:1	#000000	#1B1B1B	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+

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#promo-form	text	Promo Code	for/id

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 25 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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AI assistant `body.www-page > q-focus-sentinel > div`
After AI assistant `body.www-page > q-focus-sentinel > div`
AI assistant, start `div#qualified-multimodal-host > div`
AI assistant, end `div#qualified-multimodal-host > div`

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.

○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

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

●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 are distinguishable without relying on color.

●Links have a discernible name

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

●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

○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

○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

○Form elements have associated labels

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

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

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