UXM UXMachine Real casesWhat UXMachine isTry it with a URLSign inESEN

Verifiable review

What we checked on this site

https://www.typeform.com/

Declared goal

A general review

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

September 26, 2026·evidence captured during the analysis

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

1

Diagnose

What we were able to measure

We reviewed 11 of the 107 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
What we checked and what was left outSee
The measurements, one by oneSee

We ran 6 checks. Complete: 1. Partial: 1. Not measured: 4. With that, we flag no 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.

There is no action we can support with what we measured. That does not mean the site is fine: it means the checks we completed point to nothing to fix.

What the evidence does not allow you to decide

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

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

    Anyone using a keyboard or a screen reader does not know whether the menu is open or closed.

    It appears on all 11 pages we reviewed. · only on mobile (390 px)

    Where: /, /platform-overview, /ai, /mcp, /growth, /research-flow, /blog-category/customer, /legal, /pricing, /enterprise, /enterprise/healthcare

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

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

    What we do not know about this check: Not measured. The cookie notice covered what needed measuring on every page, and we did not measure it.

    The evidence

  • On 8 of the 11 pages we reviewed, there are pieces of text that barely stand out from their background.

    Anyone reading in low light, on a screen in sunlight, or with tired eyes may not be able to tell this text from its background.

    It appears on 8 of the 11 pages we reviewed. · only on mobile (390 px)

    Where: /, /platform-overview, /ai, /mcp, /growth, /pricing, /enterprise, /enterprise/healthcare

    The measurement: 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.

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

    What we do not know about this check: Not measured. The cookie notice covered what needed measuring on every page, and we did not measure it.

    The evidence

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

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

    Neither a screen reader nor a search engine has anywhere to get the topic of the page from.

    It appears on 3 of the 11 pages we reviewed. · only on mobile (390 px)

    Where: /, /pricing, /enterprise

    The measurement: We found no <h1> on those pages.

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

    What we do not know about this check: Not measured. The cookie notice covered what needed measuring on every page, and we did not measure it.

    The evidence

3

Act

What to do, and in what order

This report proposes no changes. That does not mean there is nothing to change: it means we found none that the evidence in this report supports.

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.

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 107 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 September 26, 2026. We have 5 findings, in 4 groups.

How we chose which pages to read. We followed the links on www.typeform.com and found 140 anchors. 28 were repeated and 6 pointed outside the site.

We ran 6 checks. Complete: 1. Partial: 1. Not measured: 4.

  • https://www.typeform.com/
  • https://www.typeform.com/platform-overview
  • https://www.typeform.com/ai
  • https://www.typeform.com/mcp
  • https://www.typeform.com/growth
  • https://www.typeform.com/research-flow
  • https://www.typeform.com/blog-category/customer
  • https://www.typeform.com/legal
  • https://www.typeform.com/pricing
  • https://www.typeform.com/enterprise
  • https://www.typeform.com/enterprise/healthcare

We ran 6 checks. Complete: 1. Partial: 1. Not measured: 4.

With that, we flag no changes. In 3 cases, 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 any of the 11 pages we read. Since we could not see them without the notice in the way, we say nothing in this report about computed accessibility, navigation and links, or observed forms.

  • Computed accessibility

    Not measured. The cookie notice covered what needed measuring on every page, and we did not measure it.

  • Navigation and links

    Not measured. The cookie notice covered what needed measuring on every page, and we did not measure it.

  • Observed forms

    Not measured. The cookie notice covered what needed measuring on every page, and we did not measure it.

  • First screen and calls to action

    Not measured. A fixed layer sat over the first screen, and we cannot separate what is underneath.

  • Third parties and consent

    Partial. This check only covers the domains the page called while loading. We could not remove the cookie notice. 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.

  • 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 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: /, /platform-overview, /ai. Plus 8 more.

only on mobile (390 px)

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://www.typeform.com/ · 1
  • https://www.typeform.com/platform-overview · 1
  • https://www.typeform.com/ai · 1
  • https://www.typeform.com/mcp · 1
  • https://www.typeform.com/growth · 1
  • https://www.typeform.com/research-flow · 1
  • https://www.typeform.com/blog-category/customer · 1
  • https://www.typeform.com/legal · 1
  • https://www.typeform.com/pricing · 1
  • https://www.typeform.com/enterprise · 1
  • https://www.typeform.com/enterprise/healthcare · 1

Where it is

[aria-haspopup]

About this check: Not measured. The cookie notice covered what needed measuring on every page, and we did not measure it.

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 8 of the 11 pages we reviewed, there are pieces of text that barely stand out from their background.

F1 · Computed accessibility

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

It appears on 8 of the 11 pages we reviewed. Among them: /, /platform-overview, /ai. Plus 5 more.

only on mobile (390 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

  • 4.09The text is #a25fba on #faf9fb · once on https://www.typeform.com/ · it says “INTELLIGENT forms”
  • 4.18The text is #f9f2fd on #a057bb · 2 times on https://www.typeform.com/ · it says “NEW”
  • 4.09The text is #a25fba on #faf9fb · 5 times on https://www.typeform.com/platform-overview · it says “platform overview”
  • 4.3The text is #a25fba on #ffffff · once on https://www.typeform.com/platform-overview · it says “Integrations”
  • 3.58The text is #a25fba on #2a222b · once on https://www.typeform.com/ai · it says “TYPEFORM AI”
  • 4.09The text is #a25fba on #faf9fb · once on https://www.typeform.com/ai · it says “DATA COLLECTION”
  • 4.18The text is #f9f2fd on #a057bb · 2 times on https://www.typeform.com/ai · it says “Coming Soon”
  • 4.09The text is #a25fba on #faf9fb · once on https://www.typeform.com/mcp · it says “What is the Typeform MCP server?”
  • 3.38The text is #ffffff on #b96dd5 · 5 times on https://www.typeform.com/mcp · it says “Create forms”
  • 4.09The text is #a25fba on #faf9fb · once on https://www.typeform.com/growth · it says “Customer Acquisition and Automation”
  • 3.58The text is #a25fba on #2a222b · once on https://www.typeform.com/growth · it says “Product demo”
  • 2.64The text is #a49da6 on #ffffff · once on https://www.typeform.com/pricing · it says “242”
  • 4.09The text is #faf9fb on #a25fba · 5 times on https://www.typeform.com/pricing · it says “Free trial”
  • 3.51The text is #837a85 on #eeecee · 9 times on https://www.typeform.com/pricing · it says “Enterprise only”
  • 4.3The text is #a25fba on #ffffff · once on https://www.typeform.com/enterprise · it says “Integrations”
  • 2.51The text is #a49da6 on #faf9fb · once on https://www.typeform.com/enterprise/healthcare · it says “242”
  • 4.09The text is #faf9fb on #a25fba · once on https://www.typeform.com/enterprise/healthcare · it says “Free trial”

About this check: Not measured. The cookie notice covered what needed measuring on every page, and we did not measure 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 main heading on 3 of the 11 pages we reviewed.

F1 · Computed accessibility

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

It appears on 3 of the 11 pages we reviewed. Among them: /, /pricing, /enterprise.

only on mobile (390 px)

We found no <h1> on those pages.

The count for each page

  • https://www.typeform.com/ · 1
  • https://www.typeform.com/pricing · 1
  • https://www.typeform.com/enterprise · 1

Where it is

body

About this check: Not measured. The cookie notice covered what needed measuring on every page, and we did not measure 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.

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

F6 · Third parties and consent

They showed up in the first load. We could not determine whether this page shows a consent notice, so we do not know whether any of this would have changed after answering it. If that matters for what you are going to decide, check it by hand before acting.

Among them: ade.googlesyndication.com, ajax.googleapis.com, api.marker.io. Plus 34 more.

It appears on 11 of the 11 pages we reviewed. Among them: /, /platform-overview, /ai. Plus 8 more.

at both widths

The count for each page

  • https://www.typeform.com/ · 23
  • https://www.typeform.com/platform-overview · 23
  • https://www.typeform.com/ai · 23
  • https://www.typeform.com/mcp · 21
  • https://www.typeform.com/growth · 25
  • https://www.typeform.com/research-flow · 29
  • https://www.typeform.com/blog-category/customer · 21
  • https://www.typeform.com/legal · 21
  • https://www.typeform.com/pricing · 23
  • https://www.typeform.com/enterprise · 25
  • https://www.typeform.com/enterprise/healthcare · 21

Where it is

network

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

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

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 /platform-overview.

at both widths

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

The count for each page

  • https://www.typeform.com/platform-overview · 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.

All cases

The other cases: Attio · Linear · Notion · Paddle · PostHog · Simple Analytics · Umami

Provenance

The instrument this review was written with.

Artifact versionartifact.v12
Resolution baseCaptured
Captured2026-09-26T11:42:42.103Z
Page setcs-e447fea7-2751-4190-8c65-663783de023d
Instrumentcopy-informe.v1 · spine seis-secciones.v1 · surface superficie.v1
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://www.typeform.com/
ReadingRead on September 26, 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.