UXM UXMachine Real casesWhat UXMachine isTry it with a URLSign inESEN

Verifiable review

What we checked on this site

https://linear.app/

Declared goal

Make it usable by anyone

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

September 14, 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 47 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 we checked and what was left outSee
The measurements, one by oneSee

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

They are ordered by how they relate to what you chose, not by urgency. Which one you work on first is a decision this report does not make.

Related to what you asked for: Make it usable by anyone.

We could not check it fully.

  • Act

    Darken the text that does not reach the minimum against its background

    Why we say this —At least one piece of text on these pages falls below the minimum contrast that applies to it. It appears on 11 of the 11 pages we reviewed.

    In low light, in bright light or with tired eyes, this text blends into the background. Anyone who does not read it, does not read it.

    Lightening the background also works, or changing both. We give you one so you do not have to choose.

    You will know it is done wheneach pair reaches the minimum that applies to it.

    It appears on all 11 pages we reviewed.

    Where: /, /homepage, /signup, /browser-compatibility, /now/introducing-loops, /changelog/2026-09-03-priority-inbox, /changelog/2026-08-20-coding-environments, /changelog/2026-08-13-team-initiatives, /changelog/2026-07-30-coding-sessions-on-mobile, /intake, /plan

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

    The evidence

  • 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 10 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 10 of the 11 pages we reviewed. · at both widths

    Where: /, /homepage, /browser-compatibility, /now/introducing-loops, /changelog/2026-09-03-priority-inbox, /changelog/2026-08-20-coding-environments, /changelog/2026-08-13-team-initiatives, /changelog/2026-07-30-coding-sessions-on-mobile, /intake, /plan

    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 69 of 70.

    The evidence

  • Act

    Put a main heading on this page

    Why we say this —On these pages we found no h1. It appears on 4 of the 11 pages 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 4 of the 11 pages we reviewed. · at both widths

    Where: /changelog/2026-09-03-priority-inbox, /changelog/2026-08-20-coding-environments, /changelog/2026-08-13-team-initiatives, /changelog/2026-07-30-coding-sessions-on-mobile

    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. 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 /signup.

    at both widths

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

3

Act

What to do, and in what order

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

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

All 11 pages · overlaps with “Make it usable by anyone” · the card

Make the main action look different from the rest

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

10 of the 11 pages · overlaps with “Make it usable by anyone” · 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

4 of the 11 pages · overlaps with “Make it usable by anyone” · the card

There are 2 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

3 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

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 6 facts.

  • We counted 150 images on the pages we reviewed. 113 of them are declared as decorative.
  • The main heading of / says: “The product development system for teams and agents The product development system for teams and agents The product deve”.
  • The main heading of /homepage says: “The product development system for teams and agents The product development system for teams and agents The product deve”.
  • The main heading of /browser-compatibility says: “Incompatible Browser”.
  • And 4 more.
  • 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 11 pages on desktop, and all of them could also be read on mobile.

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

We read 11 of the 47 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 14, 2026. We have 6 findings, in 3 groups. There is 1 more that we only show with its evidence.

How we chose which pages to read. We followed the links on linear.app and found 74 anchors. 24 were repeated and 4 pointed outside the site.

We ran 6 checks. Complete: 2. Partial: 4. Not measured: 0.

  • https://linear.app/
  • https://linear.app/homepage
  • https://linear.app/browser-compatibility
  • https://linear.app/signup
  • https://linear.app/now/introducing-loops
  • https://linear.app/changelog/2026-09-03-priority-inbox
  • https://linear.app/changelog/2026-08-20-coding-environments
  • https://linear.app/changelog/2026-08-13-team-initiatives
  • https://linear.app/changelog/2026-07-30-coding-sessions-on-mobile
  • https://linear.app/intake
  • https://linear.app/plan

We ran 6 checks. Complete: 2. Partial: 4. Not measured: 0.

With that, we flag 3 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.

  • 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

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

  • 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

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

  • 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

On all 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 11 of the 11 pages we reviewed. Among them: /, /homepage, /signup. Plus 8 more.

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

  • 3.45The text is #62666d on #08090a · 12 times on https://linear.app/ · it says “Powering the companies building the future”
  • 3.45The text is #62666d on #08090a · 12 times on https://linear.app/homepage · it says “Powering the companies building the future”
  • 3.93The text is #fefeff on #6d78d5 · once on https://linear.app/signup · it says “Continue with Google”
  • 1.88The text is #3c3f43 on #08090a · 2 times on https://linear.app/ · it says “Fig 0.1”
  • 1.88The text is #3c3f43 on #08090a · 2 times on https://linear.app/homepage · it says “Fig 0.1”
  • 3.45The text is #62666d on #08090a · 4 times on https://linear.app/browser-compatibility · it says “Privacy”
  • 3.45The text is #62666d on #08090a · 4 times on https://linear.app/now/introducing-loops · it says “Privacy”
  • 3.45The text is #62666d on #08090a · 4 times on https://linear.app/changelog/2026-09-03-priority-inbox · it says “Privacy”
  • 3.45The text is #62666d on #08090a · 4 times on https://linear.app/changelog/2026-08-20-coding-environments · it says “Privacy”
  • 3.45The text is #62666d on #08090a · 4 times on https://linear.app/changelog/2026-08-13-team-initiatives · it says “Privacy”
  • 3.45The text is #62666d on #08090a · 4 times on https://linear.app/changelog/2026-07-30-coding-sessions-on-mobile · it says “Privacy”
  • 3.45The text is #62666d on #08090a · 4 times on https://linear.app/intake · it says “Privacy”
  • 2.92The text is #585b60 on #08090a · 3 times on https://linear.app/plan · it says “Product pipeline”
  • 1.88The text is #3c3f43 on #08090a · 3 times on https://linear.app/plan · it says “Monitor delivery stages across initiatives”
  • 3.45The text is #62666d on #08090a · 4 times on https://linear.app/plan · it says “Privacy”

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.

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. Some browsers ignore that request and others respect it.

It is on /signup.

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 4 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 4 of the 11 pages we reviewed. Among them: /changelog/2026-09-03-priority-inbox, /changelog/2026-08-20-coding-environments, /changelog/2026-08-13-team-initiatives. Plus 1 more.

at both widths

We found no <h1> on those pages.

The count for each page

  • https://linear.app/changelog/2026-09-03-priority-inbox · 1
  • https://linear.app/changelog/2026-08-20-coding-environments · 1
  • https://linear.app/changelog/2026-08-13-team-initiatives · 1
  • https://linear.app/changelog/2026-07-30-coding-sessions-on-mobile · 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.

On 10 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 10 of the 11 pages we reviewed. Among them: /, /homepage, /browser-compatibility. Plus 7 more.

at both widths

The count for each page

  • https://linear.app/ · 10
  • https://linear.app/homepage · 10
  • https://linear.app/browser-compatibility · 6
  • https://linear.app/now/introducing-loops · 3
  • https://linear.app/changelog/2026-09-03-priority-inbox · 4
  • https://linear.app/changelog/2026-08-20-coding-environments · 4
  • https://linear.app/changelog/2026-08-13-team-initiatives · 4
  • https://linear.app/changelog/2026-07-30-coding-sessions-on-mobile · 4
  • https://linear.app/intake · 2
  • https://linear.app/plan · 2

Where it is

a,button

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

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.

We found no search engine description on 3 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 appears on 3 of the 11 pages we reviewed. Among them: /browser-compatibility, /signup, /now/introducing-loops.

at both widths

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

The count for each page

  • https://linear.app/browser-compatibility · 1
  • https://linear.app/signup · 1
  • https://linear.app/now/introducing-loops · 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 /signup.

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.

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 4 of the 11 pages we reviewed. Among them: /, /homepage, /browser-compatibility. Plus 1 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: Attio · Notion · Paddle · PostHog · Simple Analytics · Typeform · Umami

Provenance

The instrument this review was written with.

Artifact versionartifact.v12
Resolution baseCaptured
Captured2026-09-14T08:13:00.920Z
Page setcs-4072cd8d-6cbe-42f4-92d0-2b6e326e4d24
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://linear.app/
ReadingRead on September 14, 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.