UXM UXMachine Real casesWhat UXMachine isTry it with a URLSign inESEN

Verifiable review

What we checked on this site

https://calendly.com

Declared goal

A general review

This report is written for whoever can change this site. If that is not you, pass it on.

October 11, 2026·evidence captured during the analysis

This is the report we issued on October 11, 2026. We have not edited it since.

Check your own site the same way

We open up to 11 pages of your site in a real browser, on desktop and mobile, and tell you what we observed, with its evidence and its limits.

Check a URL

If you change only one thing

Make the main action look different from the rest

When you change it, measure this site again: we will tell you whether we still observe it.

See the full order and why ↓

1

Diagnose

What we were able to measure

We reviewed 11 of the 73 linked pages, at 1280 px and 390 px. Everything we say below comes from these captures, and each statement has the measurement it comes from underneath it.

Screenshot of the first screen of the page, as it looked when we read it, in a 1280×800 window.
Screenshot of the first screen of the page, as it looked when we read it, in a 390×844 window.

First screen at 1280×800 and at 390×844, as it looked when we read it. Where the first screen ends depends on the window size. Open them at full size to see it.

First screen at 1280×800 and at 390×844, as it looked when we read it. Where the first screen ends depends on the window size. Open them at full size to see it.

What you can leave as it isSee
Other things we observed, none of which point to a problem.See
What its forms ask forSee
What we checked and what was left outSee
The measurements, one by oneSee

We ran 6 checks. Complete: 1. Partial: 5. Not measured: 0. With that, we flag 2 changes for you.

2

Decide

What you can decide

Each one is a change you can make, with the measurement it comes from and how to check that it is done. In stage 3 we tell you in what order we would make them.

We could not close this site’s cookie notice, and that notice is inside the page: it puts its own heading, its links and its checkboxes into what we measure. So we abstain on everything we cannot separate from it — the headings and the images, the menus and the links, the fields and the forms — and what depended on how things look, we measured with the notice on top, so it does not describe what someone who has already closed it sees. What we do stand behind: the metadata, and which external domains load on arrival.

They are not ordered by urgency. Which one you work on first is a decision this report does not make.

Found in the review, with no demonstrated relation to what you asked for.

  • Act

    Make one of these actions stand out from the others

    Why we say this —On the first screen of these pages there are actions that share the same background, text color and font size. It appears on 9 of the 11 pages we reviewed.

    Whoever arrives has to read them all to decide. When everything carries the same weight, nothing guides.

    You will know it is done whenthose actions no longer share all three at once.

    It appears on 9 of the 11 pages we reviewed.

    Where: /, /login, /app/login, /features/mobile-apps, /features/browser-extensions, /integration/zoom, /integration/gmail-workflows, /integration/google-meet, /integration/salesforce

    Check before you touch it: we do not measure this.

    What we do not know about this check: Partial. We stopped before finishing: of the visible links and buttons on this page, we stored 79 of 85.

    The evidence

  • Act

    Mark which of these fields are required

    Why we say this —On these pages we found at least one form that asks for details and does not mark which are required in a way we can read. It appears on 1 of the 11 pages we reviewed.

    Nobody knows what they can leave blank. Neither does the browser, so it cannot warn before sending: the warning comes late or not at all.

    You will know it is done whenthe required fields are declared as required.

    • One form asks for a single detail, and we found nothing that says whether it is required.

    It appears on 1 of the 11 pages we reviewed.

    Where: /login

    The measurement: We counted what the form asked for when it opened; it may ask for more as you go.

    Confirm it by looking at the form: the required fields stand out at a glance, and in the code they have required

    What we do not know about this check: Partial. On some pages the cookie notice covered what needed measuring, and there we did not measure it. On the rest, we did.

    The evidence

3

Act

What to do, and in what order

2 changes, in the order we would make them. If you are only going to change one thing, change the first one.

Where this order comes from: three things we measured — how much it overlaps with what you asked us for, whether we could check it fully or only partly, and on how many of the 11 reviewed pages it appears. What we checked fully goes before what we checked partly. We do not measure how much each change costs, so if the first is expensive and the third is one line, start with the third.

Make the main action look different from the rest

You check this yourself: we have no way of measuring whether it is done.

9 of the 11 pages · the card

Mark which details in this form are required

How to check it: Confirm it by looking at the form: the required fields stand out at a glance, and in the code they have required

1 of the 11 pages · the card

There are 5 more steps, in the same order

Declare the description of this page

How to check it: Confirm it in the page head: the meta description tag appears with its text

1 of the 11 pages · the card

Declare how this page looks when shared

How to check it: Confirm it in the page head: the Open Graph tags appear

1 of the 11 pages · the card

State whether these dropdowns are open or closed

How to check it: Confirm it in the menu code: it has aria-expanded, and its value changes when it is opened and closed

All 11 pages · the card

Declare the main heading of this page

How to check it: Confirm it in the page code: the main title is inside an h1 tag

1 of the 11 pages · the card

Raise the contrast of this text against its background

How to check it: Confirm it with the eyedropper in the browser inspector: each of the color pairs listed in the full report now reaches its minimum

1 of the 11 pages · the card

What you can leave as it is

None of the checks we completed lets us say that something should stay as it is. That does not mean it is wrong: it means we do not have a complete check that certifies it.

Other things we observed, none of which point to a problem.

There are 9 facts.

  • We counted 211 images on the pages we reviewed. 168 of them are declared as decorative.
  • The main heading of /blog/new-calendly says: “Introducing the new Calendly”.
  • The main heading of /features/mobile-apps says: “Calendly for Mobile”.
  • The main heading of /features/browser-extensions says: “Calendly for Web Browsers”.
  • And 5 more.

What its forms ask for

A form without a title inside the form itself. If there is a heading just above it but outside it, we do not count it.

  • A form without a title of its own asks for 1 detail; we found no mark we can read that says whether it is required. It is on /login.
  • A form without a title of its own asks for 1 detail; we found no mark we can read that says whether it is required. It is on /app/login.

Why it matters: Every detail asked for before getting an answer is one more decision for whoever fills it in.

We counted what the form asked for when it opened; it may ask for more as you go. We only see the forms the page declares as forms.

What we checked and what was left out

This report looks at this site at 390 pixels wide, with the same checks we run on desktop. There are three things specific to mobile that we do not check yet: the size of what has to be tapped, whether the phone zooms in on the page when a field is tapped, and what text size is left afterwards. That we do not name them does not mean they are fine: it means we have not looked at them.

We read 11 pages on desktop, and all of them could also be read on mobile.

Consent notice: on all 11 pages of this review, we were able to establish whether there was one, either because we saw it or from the services the page loads.

We read 11 of the 73 pages we found linked from the one you gave us. We start with the pages in the main navigation; footer links go last. Besides the page you gave us, we read up to 10 more pages per diagnostic. Here we reached that limit.

What we did and on what

We read 11 pages on October 11, 2026. We have 9 findings, in 6 groups. There is 1 more that we only show with its evidence.

How we chose which pages to read. We followed the links on calendly.com and found 157 anchors. 71 were repeated and 14 pointed outside the site.

We ran 6 checks. Complete: 1. Partial: 5. Not measured: 0.

  • https://calendly.com/
  • https://calendly.com/blog/new-calendly
  • https://calendly.com/login
  • https://calendly.com/app/login
  • https://calendly.com/features/mobile-apps
  • https://calendly.com/features/browser-extensions
  • https://calendly.com/integration/zoom
  • https://calendly.com/help/how-to-connect-your-google-calendar
  • https://calendly.com/integration/gmail-workflows
  • https://calendly.com/integration/google-meet
  • https://calendly.com/integration/salesforce

We ran 6 checks. Complete: 1. Partial: 5. Not measured: 0.

With that, we flag 2 changes. In no case do we hold back.

Where we did not look

Each abstention with its cause and its scope. Absence of observation is not absence of the problem.

  • What we cannot separate from the cookie notice · throughout this report

    We could not close the cookie notice on 1 of the 11 pages we read. That is why we say nothing in this report about computed accessibility, navigation and links, or observed forms, not even on the pages where we did close it: what you see with the notice closed and with the notice on top is not the same, and mixing them would give a count that means nothing.

  • Computed accessibility

    Partial. Visible focus does not show in a still capture, so we did not check it.

  • Navigation and links

    Partial. We checked links with no declared destination, but we did not follow any, so we do not detect a link that leads to a page that does not exist.

  • Observed forms

    Partial. On some pages the cookie notice covered what needed measuring, and there we did not measure it. On the rest, we did.

  • First screen and calls to action

    Partial. We stopped before finishing: of the visible links and buttons on this page, we stored 79 of 85.

  • Third parties and consent

    Partial. This check only covers the domains the page called while loading. We removed the cookie notice by rejecting it. We do not judge whether what the page does with those domains is lawful.

  • Comparison with a reference population

    We do not yet compare this site with any reference corpus.

LIMITS OF THIS REVIEW

  • These observations are limited to the reviewed pages listed above.

  • The pages we did not read are not in these observations: nothing this report says refers to them.

  • What we count as a link or button: links, buttons, controls that submit a form, and anything that declares a link or button role. If something acts as a control without declaring itself one, we do not see it.

  • We measure contrast against the reference the check itself comes with: 4.5 to 1 for normal text and 3 to 1 for large text. It is not a threshold of our own. We do not measure text placed over an image or a gradient: the check cannot determine the background color, and those cases do not reach these observations.

  • This review looked at the site in its light version. If the site changes its appearance when the computer or phone is in dark mode, that version has not been looked at, and what we say here about contrast does not apply to it.

  • This review was done from the Netherlands, within the European Union. A visitor from outside the European Union may not see the same thing: some sites change depending on where they are requested from.

  • Fixed layers are measured in each of the windows used in this review. At another window size, the part of the first screen that is covered changes, and a layer that covers nothing in one window may cover something in another.

  • We do not count images declared as decorative: an image is declared decorative with alt="", and that is a choice made by whoever put it there. We trust that declaration; we do not check whether the image really is decorative.

  • When we review the declared type of a field, we go by its name and its label. We do not check what is typed into it, so a field whose name does not announce what it expects can go by without us flagging it.

  • We chose which pages to read by following the links on the first one, and the cookie notice we could not close was inside it, with its own links. We do not know whether any of the pages we read got onto the list because of the notice rather than because of your site.

  • You wrote “A general review” as your goal. We could not relate what you wrote to what we know how to check, so we ordered the report without taking it into account. That is a limit on our side.

  • This review abstains on 7 points. Each one, with its cause and its scope, is under “Where we did not look”.

The measurements, one by one

On 9 of the 11 pages we reviewed, the first screen has links and buttons that share the same background, text color and font size.

F4 · First screen and calls to action

Their appearance does not separate one action from another: someone arriving has no visual cue to choose by.

It appears on 9 of the 11 pages we reviewed. Among them: /, /login, /app/login. Plus 6 more.

The count for each page

  • https://calendly.com/ · 6
  • https://calendly.com/login · 5
  • https://calendly.com/app/login · 2
  • https://calendly.com/features/mobile-apps · 2
  • https://calendly.com/features/browser-extensions · 3
  • https://calendly.com/integration/zoom · 3
  • https://calendly.com/integration/gmail-workflows · 2
  • https://calendly.com/integration/google-meet · 2
  • https://calendly.com/integration/salesforce · 3

Where it is

a,button

About this check: Partial. We stopped before finishing: of the visible links and buttons on this page, we stored 79 of 85.

If you decide to change it: Change the style of whichever one should be the main action. We have not tested the change, so we do not know what else is affected.

One form asks for a single detail, and we found nothing that says whether it is required.

F3 · Observed forms

Why it matters: Whoever fills it in does not know what they can leave blank until they try to send it.

It is on /login.

We counted what the form asked for when it opened; it may ask for more as you go.

  • One form asks for a single detail, and we found nothing that says whether it is required.

Where it is

Continue with email§email:email

About this check: Partial. On some pages the cookie notice covered what needed measuring, and there we did not measure it. On the rest, we did.

If you decide to change it: Mark each required field in its label, and declare it on the field itself with the required attribute. We have not tested the change, so we do not know what else is affected.

We found no main heading on 1 of the 11 pages we reviewed.

F1 · Computed accessibility

We saw no level 1 element that says what the page is about.

It is on /login.

at both widths

We found no <h1> on those pages.

The count for each page

  • https://calendly.com/login · 1

Where it is

body

About this check: Partial. Visible focus does not show in a still capture, so we did not check it.

If you decide to change it: One tag around the title that already exists. We have not tested the change, so we do not know what else is affected.

There is one piece of text that barely stands out from its background.

F1 · Computed accessibility

Why it matters: It is hard to read against the color behind it.

It is on /help/how-to-connect-your-google-calendar.

only on desktop (1280 px)

We measure against the reference the check itself brings: 4.5 to 1 for normal text and 3 to 1 for large text. We did not set it. We do not measure text that sits on an image or a gradient: the check cannot work out the background color, and those cases never get this far.

The measured colors, with their page

  • 2.74The text is #8c959b on #f5f3ee · once on https://calendly.com/help/how-to-connect-your-google-calendar · it says “Categories”

About this check: Partial. Visible focus does not show in a still capture, so we did not check it.

If you decide to change it: Change one color in the stylesheet. We have not tested the change, so we do not know what else is affected.

We found no search engine description on 1 of the 11 pages we reviewed.

F5 · Metadata and shareability

Why it matters: Google chooses on its own which snippet to show under the title.

It is on /app/login.

at both widths

We found no <meta name="description"> tag on those pages.

The count for each page

  • https://calendly.com/app/login · 1

Where it is

head

If you decide to change it: One line in the page head. We have not tested the change, so we do not know what else is affected.

We found nothing on this page that says how it should look when shared.

F5 · Metadata and shareability

Why it matters: When the link is pasted into WhatsApp or LinkedIn, each one improvises the title and the image.

It is on /app/login.

at both widths

We found no Open Graph tags: og:title, og:description and og:image.

Where it is

head

If you decide to change it: Three lines in the page head. We have not tested the change, so we do not know what else is affected.

On all 11 pages we reviewed, we found menus that open and close without saying which of the two states they are in.

F2 · Navigation and links

Why it matters: Someone using a screen reader cannot tell whether it is expanded.

It appears on 11 of the 11 pages we reviewed. Among them: /, /blog/new-calendly, /login. Plus 8 more.

We found no aria-expanded attribute on the control that opens it, nor anything that changes it from false to true when it opens.

The count for each page

  • https://calendly.com/ · 1
  • https://calendly.com/blog/new-calendly · 1
  • https://calendly.com/login · 1
  • https://calendly.com/app/login · 1
  • https://calendly.com/features/mobile-apps · 1
  • https://calendly.com/features/browser-extensions · 1
  • https://calendly.com/integration/zoom · 1
  • https://calendly.com/help/how-to-connect-your-google-calendar · 1
  • https://calendly.com/integration/gmail-workflows · 1
  • https://calendly.com/integration/google-meet · 1
  • https://calendly.com/integration/salesforce · 1

Where it is

[aria-haspopup]

About this check: Partial. We checked links with no declared destination, but we did not follow any, so we do not detect a link that leads to a page that does not exist.

If you decide to change it: One attribute per menu. We have not tested the change, so we do not know what else is affected.

On all 11 pages we reviewed, there are external domains that load before anyone touches anything. On the page with the most, there are 14.

F6 · Third parties and consent

They showed up in the first load, before we answered the cookie notice on 10 of the 11 pages in this review. It is what someone finds when they arrive at the site and have not answered yet.

Among them: cdn.calendlycms.com, cdn.cookielaw.org, geolocation.onetrust.com. Plus 16 more.

It appears on 11 of the 11 pages we reviewed. Among them: /, /blog/new-calendly, /login. Plus 8 more.

at both widths

The count for each page

  • https://calendly.com/ · 9
  • https://calendly.com/blog/new-calendly · 8
  • https://calendly.com/login · 8
  • https://calendly.com/app/login · 6
  • https://calendly.com/features/mobile-apps · 8
  • https://calendly.com/features/browser-extensions · 8
  • https://calendly.com/integration/zoom · 14
  • https://calendly.com/help/how-to-connect-your-google-calendar · 7
  • https://calendly.com/integration/gmail-workflows · 8
  • https://calendly.com/integration/google-meet · 14
  • https://calendly.com/integration/salesforce · 14

Where it is

network

About this check: Partial. This check only covers the domains the page called while loading. We removed the cookie notice by rejecting it. We do not judge whether what the page does with those domains is lawful.

No fix proposed: this is a decision worth consulting on.

The headings on each page skip levels once.

F1 · Computed accessibility

Why it matters: Anyone navigating by headings loses the thread of the document.

It appears on 5 of the 11 pages we reviewed. Among them: /integration/zoom, /help/how-to-connect-your-google-calendar, /integration/gmail-workflows. Plus 2 more.

at both widths

We look at the order of the heading levels (h1, h2, h3…) as they appear in the document, and here there is a skip between levels. We do not judge what each heading says.

Where it is

h1..h6

About this check: Partial. Visible focus does not show in a still capture, so we did not check it.

If you decide to change it: Change the level of the tag, not how it looks. We have not tested the change, so we do not know what else is affected.

All cases

The other cases: Airbnb · Atlassian · Attio · Basecamp · Dropbox · Duolingo · GitHub · Intercom · Linear · Loom · Miro · Notion · Paddle · PostHog · Shopify · Simple Analytics · Typeform · Umami · Vercel · Zoom

Check your own site the same way

We open up to 11 pages of your site in a real browser, on desktop and mobile, and tell you what we observed, with its evidence and its limits.

Check a URL

Provenance

The instrument this review was written with.

Artifact versionartifact.v15
Resolution baseCaptured
CapturedOctober 11, 2026, 12:45 UTC
Page setcs-6b28db39-5f46-478d-ab92-65594616fe60
Instrumentcopy-familias.v32 · spine seis-secciones.v1 · surface superficie:47f340120276a76a
Field definitioncenso-de-formularios.v1 · we do not count: hidden, submit, button, reset, image and the anti-spam tokens · the fields marked aria-hidden · the search fields: they do not ask for details about the person; they are a navigation control · the fields that appear while typing or in later steps: they are not guessed
Selection rulenot recorded

These versions identify the instrument, not the exact wording: the same version can cover later wording corrections.

Requested addresshttps://calendly.com
Final addresshttps://calendly.com/
ReadingRead on October 11, 2026. Sites change.

Examples made on public home pages. They imply no commercial relationship, engagement, validation or approval on the part of the brands analyzed.

If you own one of these sites and do not want its report here, write to us and we will take it down the same day. You do not have to explain why.

UXMachine would like to use Google to measure visits and which ads bring them. Without your permission, we do not load those tools. Details

Settings