Skip to content
https://jll.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-rz0un7
404 Page Quality Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://jll.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://jll.com/manifest.json

Manifest contains invalid JSON.

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::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 6 <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
Form Accessibility
Action
9 of 9 controls have issues
REVIEW
9 of 9 controls have issues
Critical::
9 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>
9 controls
0 labeled
0 placeholder only
9 unlabeled
ControlTypeLabelMethod
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none

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

<select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>

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

C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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'>.
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA 3 pass AA only
a Contact us
3.77:1
#000000
on
#686868
needs 4.5:1 (normal text)
16px · top of page (header area)
span Properties
3.50:1
#000000
on
#676262
needs 4.5:1 (normal text)
16px · above the fold
span Services
3.19:1
#000000
on
#605C5F
needs 4.5:1 (normal text)
16px · above the fold
span Technology
3.26:1
#000000
on
#5C5F61
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Explore a brighter w…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Our latest insights5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Careers at JLL5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Our real estate solu…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Properties for sale …5.24:13.0:1
#000000
#7F7F7F
Pass
h2 More to explore5.24:13.0:1
#000000
#7F7F7F
Pass
h2 The Video Cloud vide…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Spotlight stories5.24:13.0:1
#000000
#7F7F7F
Pass
h3 JLL Foundation deplo…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Watch as JLL rings t…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 JLL acquires renewab…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 At JLL, women inspir…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 How the pandemic res…5.24:13.0:1
#000000
#7F7F7F
Pass
title JLL | Commercial Rea…5.24:14.5:1
#000000
#7F7F7F
Pass
a Skip to main content5.24:14.5:1
#000000
#7F7F7F
Pass
div United States5.24:14.5:1
#000000
#7F7F7F
Pass
a Contact us3.77:14.5:1
#000000
#686868
Fail
span Properties3.50:14.5:1
#000000
#676262
Fail
span Services3.19:14.5:1
#000000
#605C5F
Fail
span Technology3.26:14.5:1
#000000
#5C5F61
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 27 passed
REVIEW
88

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
How can we help? div.react-container-fluid > div.row > div.col-mobile-small-2 > div.c-accordion__item
Careers div.react-container-fluid > div.row > div.col-mobile-small-2 > div.c-accordion__item
Corporate Information div.react-container-fluid > div.row > div.col-mobile-small-2 > div.c-accordion__item
Legal div.react-container-fluid > div.row > div.col-mobile-small-2 > div.c-accordion__item

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
future div.featured-card__title-wrapper > h2.l-title-2-default > span > span.jll-red
live and work div.featured-card__title-wrapper > h2.l-title-2-default > span > span.jll-red
insights div.featured-card__title-wrapper > h2.l-title-2-default > span > span.jll-red

These are opportunities to improve the legibility of your content.

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.cta > div.cta__content > div.cta__links > a.link div.cta > div.cta__content > div.cta__links > a.link

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
United States div.row > div.max-laptop-sm:w-full > div.max-laptop-sm:[&_.sol-button]:h-9 > button.sol-button
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>`
`[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
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
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.
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.
`[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
`<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
`<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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
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.
A+
Landmark Structure
16 landmarks
PASS
16 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation" MAIN CONTENTINFO footer
A+
Heading Hierarchy
21 headings
PASS
21 headings
Info::
Single H1 present
  • H4 Join our Global Real Estate Perspective webinar
  • H4 Seeing opportunity in change
  • H4 Webinar: Balance inspiring office design with cost-effective fit outs
  • H4 Shaping the future of real estate for a better world
  • H3 Spotlight stories
  • H4 Join our Global Real Estate Perspective webinar
  • H1 Explore a brighter way
  • H2 Our latest insights
  • H2 Careers at JLL
  • H2 Our real estate solutions
  • H2 Properties for sale or lease
  • H2 AI advances the future of real estate
  • H2 Brighter places to live and work
  • H2 Illuminating insights for every sector and industry
  • H2 More to explore
  • H3 JLL Foundation deploys record $5.1M to climate startups in 2025
  • H3 Watch as JLL rings the closing bell at the New York Stock Exchange
  • H3 JLL acquires renewable energy investment firm, Javelin Capital
  • H2 The Video Cloud video was not found.
  • H3 At JLL, women inspire
  • H3 How the pandemic reshaped work forever
A
Alt Text Quality
4 of 26 images have issues
PASS
4 of 26 images have issues
Warning::
4 image(s) with generic alt text
Info::
17 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
26 images 5 good alt text 17 decorative 4 generic
IssueCount
generic4 image(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback