UXM UXMachine Real casesWhat UXMachine isTry it with a URLSign inESEN

Verifiable review

What we checked on this site

https://atlassian.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

Declare the real type of this field

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 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
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: 2. Partial: 3. Not measured: 1. 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.

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

    Declare this field as an email address

    Why we say this —The “email” field is declared as text, and judging by its name it calls for an email address. It appears on all 11 pages we reviewed.

    On a phone the wrong keyboard comes up. Typing an email address with the normal keyboard is slower and produces more typos — and a typo in the email address is a customer who never reaches you.

    You will know it is done whenthat field is declared as an email address.

    It appears on 1 of the 11 pages we reviewed. · at both widths

    Where: /enterprise/contact?formType=product-features

    The measurement: The field is declared as type="text". We flag it because its name or its label mentions an email address; we do not check what is typed into it. For an email address, the value that declares it is type="email".

    Confirm it in the code of that field: its type is now email and not text

    What we do not know about this check: Complete across the pages we read.

    The evidence

  • Act

    Give these fields a label, as well as the text inside

    Why we say this —In 3 fields we found example text and no associated label: yourname@yourcompany.com, yourname@yourcompany.com, yourname@yourcompany.com. It appears on all 11 pages we reviewed.

    As soon as you start typing, the example disappears and the field is left without a name. Anyone who loses track has to delete everything to see it again.

    You will know it is done whenthose fields declare their label.

    It appears on 1 of the 11 pages we reviewed. · at both widths

    Where: /blog/state-of-teams-2026

    The measurement: We found no <label> tied to that field. The placeholder does not replace it: it disappears as you type.

    Confirm it by looking at the form: each field has its visible label above it or beside it, not only the gray text inside

    What we do not know about this check: Complete across the pages we read.

    The evidence

What the evidence does not allow you to decide

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

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

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

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

    Where: /, /enterprise/contact?formType=product-features

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

    What we do not know about this check: Not measured. A fixed layer sat over the first screen, and we cannot separate what is underneath.

    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.

Declare the real type of this field

How to check it: Confirm it in the code of that field: its type is now email and not text

1 of the 11 pages · the card

Give these fields a label of their own, as well as the text inside

How to check it: Confirm it by looking at the form: each field has its visible label above it or beside it, not only the gray text inside

1 of the 11 pages · the card

There are 6 more steps, in the same order

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

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

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

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

5 of the 11 pages · the card

Declare the alt text for these images

How to check it: Confirm it in the code: every image on those pages has its alt text

2 of the 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

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

  • We counted 497 images on the pages we reviewed. 197 of them are declared as decorative.
  • The main heading of / says: “Unleash your teams and their agents”.
  • The main heading of /collections/teamwork says: “The teamwork platform for the AI era”.
  • The main heading of /collections/strategy says: “AI-native strategic portfolio management”.
  • And 7 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, and it is required. It is on /collections/teamwork, /software/jira/dev y en /try/cloud/signup.
  • A form without a title of its own asks for 10 details. 9 of them are required. It is on /collections/strategy.
  • A form without a title of its own asks for 8 details. 6 of them are required. It is on /collections/service.
  • The “What tool(s) are you currently using to collect, manage, or analyze fe” form asks for 8 details. 4 of them are required. It is on /collections/product.
  • The “Cloud Products” form asks for 7 details; we found no mark we can read that says which are required. It is on /enterprise/contact?formType=product-features.
  • A form without a title of its own asks for 1 detail, and it is required. It is on /blog/state-of-teams-2026.
  • A form without a title of its own asks for 8 details. 4 of them are required. It is on /whitepapers/agentic-enterprise-guide.
  • 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 /whitepapers/agentic-enterprise-guide.

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 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 October 11, 2026. We have 11 findings, in 6 groups. There are 2 more that we only show with their evidence.

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

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

  • https://www.atlassian.com/
  • https://www.atlassian.com/collections/teamwork
  • https://www.atlassian.com/collections/strategy
  • https://www.atlassian.com/collections/service
  • https://www.atlassian.com/software/jira/dev
  • https://www.atlassian.com/collections/product
  • https://events.atlassian.com/teameurope-digital?utm_medium=event-web-referral&utm_source=cross-promo&utm_context=701qb00000j7fexyam&utm_campaign=K:event%7CH:any%7CN:team_europe_26%7CP:agnostic%7CO:event-marketing%7CF:pre-event%7CC:event-home&utm_content=events_wac_takeover&event_id=379053
  • https://www.atlassian.com/try/cloud/signup
  • https://www.atlassian.com/enterprise/contact?formType=product-features
  • https://www.atlassian.com/blog/state-of-teams-2026
  • https://www.atlassian.com/whitepapers/agentic-enterprise-guide

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

With that, we flag 2 changes. In 1 case, 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.

  • Links whose destination we could not determine · on 11 pages we read

    We cannot tell which are links that lead nowhere and which are buttons that work — tabs and dropdowns are written the same way. We do not claim that any of them is broken.

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

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

The measurements, one by one

On 2 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 2 of the 11 pages we reviewed. Among them: /, /enterprise/contact?formType=product-features.

only on mobile (390 px)

The count for each page

  • https://www.atlassian.com/ · 2
  • https://www.atlassian.com/enterprise/contact?formType=product-features · 2

Where it is

a,button

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

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.

The “email” field is declared as text. Judging by its name, it calls for an email address.

F3 · Observed forms

Why it matters: On a phone the right keyboard does not appear and the browser cannot autofill it.

It is on /enterprise/contact?formType=product-features.

at both widths

The field is declared as type="text". We flag it because its name or its label mentions an email address; we do not check what is typed into it. For an email address, the value that declares it is type="email".

Where it is

input

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

We found 3 fields in the form that are only explained by the text inside.

F3 · Observed forms

Why it matters: That text disappears as soon as you start typing. The fields are: yourname@yourcompany.com, yourname@yourcompany.com, yourname@yourcompany.com.

It is on /blog/state-of-teams-2026.

at both widths

We found no <label> tied to that field. The placeholder does not replace it: it disappears as you type.

Where it is

input[placeholder]

If you decide to change it: One visible label per field. 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 /enterprise/contact?formType=product-features.

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

Cloud Products§checkbox:consent|text:company|text:email|text:firstName|text:lastName|text:opportunity_Description__c|text:title

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.

On 5 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 5 of the 11 pages we reviewed. Among them: /collections/strategy, /collections/service, /collections/teamwork. Plus 2 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.9The text is #7d818a on #ffffff · 2 times on https://www.atlassian.com/collections/strategy · it says “Please enter your work email.”
  • 3.9The text is #7d818a on #ffffff · 2 times on https://www.atlassian.com/collections/service · it says “Please enter your work email.”
  • 1.11The text is #ececec on #f8f8f8 · once on https://www.atlassian.com/collections/teamwork · it says “Search”
  • 1.37The text is #d5d6d7 on #f8f8f8 · once on https://www.atlassian.com/collections/service · it says “Search”
  • 1.57The text is #c7c8c9 on #f8f8f8 · once on https://www.atlassian.com/collections/product · it says “Search”
  • 3.35The text is #85888c on #f8f8f8 · once on https://www.atlassian.com/enterprise/contact?formType=product-features · it says “Search”

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.

On 2 of the 11 pages we reviewed, we found images without alt text.

F1 · Computed accessibility

Why it matters: A screen reader cannot describe them.

It appears on 2 of the 11 pages we reviewed. Among them: https://events.atlassian.com/teameurope-digital?utm_medium=event-web-referral&utm_source=cross-promo&utm_context=701qb00000j7fexyam&utm_campaign=K:event|H:any|N:team_europe_26|P:agnostic|O:event-marketing|F:pre-event|C:event-home&utm_content=events_wac_takeover&event_id=379053, /blog/state-of-teams-2026.

at both widths

We found no alt attribute on those images. A decorative image is declared with alt="", and we do not count those here.

The count for each page

  • https://events.atlassian.com/teameurope-digital?utm_medium=event-web-referral&utm_source=cross-promo&utm_context=701qb00000j7fexyam&utm_campaign=K:event%7CH:any%7CN:team_europe_26%7CP:agnostic%7CO:event-marketing%7CF:pre-event%7CC:event-home&utm_content=events_wac_takeover&event_id=379053 · 2
  • https://www.atlassian.com/blog/state-of-teams-2026 · 30

Where it is

img

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 attribute per image. 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 /enterprise/contact?formType=product-features.

at both widths

We found no <h1> on those pages.

The count for each page

  • https://www.atlassian.com/enterprise/contact?formType=product-features · 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.

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 https://events.atlassian.com/teameurope-digital?utm_medium=event-web-referral&utm_source=cross-promo&utm_context=701qb00000j7fexyam&utm_campaign=K:event|H:any|N:team_europe_26|P:agnostic|O:event-marketing|F:pre-event|C:event-home&utm_content=events_wac_takeover&event_id=379053.

at both widths

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

The count for each page

  • https://events.atlassian.com/teameurope-digital?utm_medium=event-web-referral&utm_source=cross-promo&utm_context=701qb00000j7fexyam&utm_campaign=K:event%7CH:any%7CN:team_europe_26%7CP:agnostic%7CO:event-marketing%7CF:pre-event%7CC:event-home&utm_content=events_wac_takeover&event_id=379053 · 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.

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: /, /collections/teamwork, /collections/strategy. 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://www.atlassian.com/ · 1
  • https://www.atlassian.com/collections/teamwork · 1
  • https://www.atlassian.com/collections/strategy · 1
  • https://www.atlassian.com/collections/service · 1
  • https://www.atlassian.com/collections/product · 1
  • https://events.atlassian.com/teameurope-digital?utm_medium=event-web-referral&utm_source=cross-promo&utm_context=701qb00000j7fexyam&utm_campaign=K:event%7CH:any%7CN:team_europe_26%7CP:agnostic%7CO:event-marketing%7CF:pre-event%7CC:event-home&utm_content=events_wac_takeover&event_id=379053 · 1
  • https://www.atlassian.com/try/cloud/signup · 1
  • https://www.atlassian.com/enterprise/contact?formType=product-features · 1
  • https://www.atlassian.com/blog/state-of-teams-2026 · 2
  • https://www.atlassian.com/whitepapers/agentic-enterprise-guide · 1
  • https://www.atlassian.com/software/jira/dev · 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 21.

F6 · Third parties and consent

They showed up in the first load, before we answered the cookie notice on 11 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.cookielaw.org, cdn.jsdelivr.net, dam-cdn.atl.orangelogic.com. Plus 34 more.

It appears on 11 of the 11 pages we reviewed. Among them: /, /collections/teamwork, /collections/strategy. Plus 8 more.

at both widths

The count for each page

  • https://www.atlassian.com/ · 12
  • https://www.atlassian.com/collections/teamwork · 12
  • https://www.atlassian.com/collections/strategy · 12
  • https://www.atlassian.com/collections/service · 12
  • https://www.atlassian.com/software/jira/dev · 11
  • https://www.atlassian.com/collections/product · 12
  • https://events.atlassian.com/teameurope-digital?utm_medium=event-web-referral&utm_source=cross-promo&utm_context=701qb00000j7fexyam&utm_campaign=K:event%7CH:any%7CN:team_europe_26%7CP:agnostic%7CO:event-marketing%7CF:pre-event%7CC:event-home&utm_content=events_wac_takeover&event_id=379053 · 21
  • https://www.atlassian.com/try/cloud/signup · 10
  • https://www.atlassian.com/enterprise/contact?formType=product-features · 11
  • https://www.atlassian.com/blog/state-of-teams-2026 · 11
  • https://www.atlassian.com/whitepapers/agentic-enterprise-guide · 11

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.

On 10 of the 11 pages we reviewed, there are headings that skip levels.

F1 · Computed accessibility

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

It appears on 10 of the 11 pages we reviewed. Among them: /, /collections/teamwork, /collections/strategy. Plus 7 more.

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.

The count for each page

  • https://www.atlassian.com/ · 1
  • https://www.atlassian.com/collections/teamwork · 1
  • https://www.atlassian.com/collections/strategy · 2
  • https://www.atlassian.com/collections/service · 1
  • https://www.atlassian.com/collections/product · 1
  • https://events.atlassian.com/teameurope-digital?utm_medium=event-web-referral&utm_source=cross-promo&utm_context=701qb00000j7fexyam&utm_campaign=K:event%7CH:any%7CN:team_europe_26%7CP:agnostic%7CO:event-marketing%7CF:pre-event%7CC:event-home&utm_content=events_wac_takeover&event_id=379053 · 5
  • https://www.atlassian.com/try/cloud/signup · 1
  • https://www.atlassian.com/enterprise/contact?formType=product-features · 1
  • https://www.atlassian.com/whitepapers/agentic-enterprise-guide · 13
  • https://www.atlassian.com/software/jira/dev · 1

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 · Attio · Basecamp · Calendly · 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:40 UTC
Page setcs-1969f5a5-0b30-4158-a883-f52857f8e3ef
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://atlassian.com
Final addresshttps://www.atlassian.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