UXM UXMachine Real casesWhat UXMachine isTry it with a URLSign inESEN

Verifiable review

What we checked on the Zero site

https://why.zero.university/

Declared goal

A general review

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

October 18, 2026·evidence captured during the analysis

UX memory

Want this for your site?

Measure your site and keep it in your UX memory: every time you measure again, we tell you what appeared, what is still there and what came back.

Measure my site →

If you change only one thing

Declare the main heading of this page

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 a single page, 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 we checked and what was left outSee
The measurements, one by oneSee

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

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

    Put a main heading on this page

    Why we say this —On these pages we found no h1. It appears on the only page we reviewed.

    Anyone navigating by headings with a screen reader has no starting point. And you lose the clearest signal of what the page is about.

    You will know it is done whenthe page declares a main heading.

    It appears on the only page we reviewed. · at both widths

    Where: /

    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: Partial. Visible focus does not show in a still capture, so we did not check it.

    The evidence

What gets in the way most

Computed accessibility

  • Let this page be zoomed in on a phone

    This site asks the browser not to allow zooming in on a phone.

    The viewport tag declares user-scalable=no y maximum-scale=1.0. Some browsers ignore that request and others respect it.

    Anyone who needs to zoom in to read cannot do it on their phone.

    It is on /.

    at both widths

    It is in the viewport tag, in maximum-scale=1 or in user-scalable=no.

What the evidence does not allow you to decide

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

  • 3 external domains load before anyone touches anything.

    They showed up in the first load. We report this as an observation: we make no judgment about legal compliance.

    These external domains are contacted before anyone has been able to answer the notice.

    They are: fonts.googleapis.com, region1.google-analytics.com, www.googletagmanager.com.

    It appears on the only page we reviewed. · at both widths

    Where: /

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

    What we do not know about this check: Partial. This check only covers the domains the page called while loading. We do not judge whether what the page does with those domains is lawful.

    The evidence

3

Act

What to do, and in what order

A single change. It is the one we would make.

Where this order comes from: two things we measured — how much it overlaps with what you asked us for, and whether we could check it fully or only partly. With a single page there is no count to order anything by. 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.

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

the card

What you can leave as it is

We looked at this in full and found nothing to fix.

  • Metadata and shareability

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

There are 4 facts.

  • We counted 1 image on the pages we reviewed.
  • The only page we reviewed has a title, a description and sharing data.

  • Metadata and shareability

    We looked at it on the only page we read and found nothing to flag.
  • We saw no forms on the pages we read.

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 1 page on desktop, and it could also be read on mobile.

Consent notice: on the only page of this review, we could not determine whether there was one. What we describe is what loaded before we responded to anything; if the notice exists, content that only appears afterwards may be missing.

We found no link leading to another page of this site.

What we did and on what

We read 1 page on October 18, 2026. We have 3 findings, in 2 groups.

We ran 6 checks. Complete: 2. Partial: 3. Not measured: 1.

  • https://why.zero.university/

We ran 6 checks. Complete: 2. Partial: 3. Not measured: 1.

With that, we flag 1 change. In 1 case, the evidence does not allow you to decide.

Where we did not look

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

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

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

  • Only this page has been looked at. The rest of the site has not been seen, nor what happens on click, nor how it behaves with real data. The images above show the first screen; what was checked is the full page.

  • 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 follow the links the page declares as links. If something leads to another page without being a link, we do not see it.

  • 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 5 points. Each one, with its cause and its scope, is under “Where we did not look”.

The measurements, one by one

This site asks the browser not to allow zooming in on a phone.

F1 · Computed accessibility

The viewport tag declares user-scalable=no y maximum-scale=1.0. Some browsers ignore that request and others respect it.

It is on /.

at both widths

It is in the viewport tag, in maximum-scale=1 or in user-scalable=no.

Where it is

meta[name=viewport]

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: Remove that value from one line. We have not tested the change, so we do not know what else is affected.

We found no main heading on the only page we reviewed.

F1 · Computed accessibility

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

It is on /.

at both widths

We found no <h1> on those pages.

The count for each page

  • https://why.zero.university/ · 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.

3 external domains load before anyone touches anything.

F6 · Third parties and consent

They showed up in the first load. We report this as an observation: we make no judgment about legal compliance.

They are: fonts.googleapis.com, region1.google-analytics.com, www.googletagmanager.com.

It is on /.

at both widths

Where it is

network

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

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

All cases

The other cases: Airbnb · Atlassian · Attio · Basecamp · Calendly · Cerebrium · Dropbox · Duolingo · Fourmula.ai · GitHub · Intercom · Linear · Loom · Made With Gsap · Miro · Notion · Paddle · PostHog · Shift5 · Shopify · Simple Analytics · Typeform · Umami · Vercel · Waabi · 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 18, 2026, 20:21 UTC
Page setcs-dee1bda3-6823-4f09-a7d4-6ae5cd544551
Instrumentcopy-familias.v32 · spine seis-secciones.v1 · surface superficie:007ae10d8b9a78af
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://why.zero.university/
ReadingRead on October 18, 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