Lokalisatierapport

Atlassian

Team collaboration software

atlassian.com

Product: Atlassian provides team collaboration software and AI-powered apps that help teams plan, organize, discuss, and complete shared work. Its products include Jira, Confluence, Loom, Bitbucket, and Jira Service Management.

Merkstem: Collaborative, confident, productivity-focused

Lokalisatiescore

69/100

Moet worden verbeterd

Gebruikers kunnen merkbare lokalisatieproblemen tegenkomen.

63Technische audit
64Taalkundige audit
83Contextuele audit
65Visuele audit

Gecontroleerd: 15 aug 2026Bereik: Openbare smart sample · credits voor techniek, taal, context en vormgevingBetrouwbaarheid: Indicatieve gezondheidscontrole op basis van steekproefpagina's — geen volledige crawl van de site.

Er zijn 15 pagina's steekproefsgewijs beoordeeld op technische, taalkundige, contextuele en visuele lokalisatiecredits. Hoe we lokalisatie-audits beoordelen

Hoe je je verhoudt

Rang #15 van 23 openbare audits

Ahead of 8 other public auditsPubliek gemiddelde: 70/100

Bekijk de volledige ranglijst

Eerst oplossen

1
high
Untranslated call to action
A fr page still uses source-language CTA copy. Affects 7 sampled pages.
See details
2
high
Page script does not match the locale
A zh page is dominated by Latin-script copy. Affects 2 sampled pages.
See details
3
high
No CJK-capable font detected
A ja page shows CJK text but the embedded/inline font stack has no known CJK typeface. Affects 3 sampled pages.
See details

Auditcriteria

4 passed · 11 to watch · 16 to fix · 4 not applicable

Vereist aandacht (16)

Language switcher
Mislukt65technisch
Visitors should move between locales without losing the current page.
- mediumtechnical · 82% zekerheid
  Locale routes are evidenced, but switching is not
  The evidence confirms separate locale URLs, but does not show a visible language switcher or preserve-current-page mapping.
  Hier gevonden
  https://www.atlassian.com/
  Wat we zagen
  "locales":["br","de","en","es","fr","it","ja","ko","nl","pl","pt-br","ru","zh"] and pages including "https://www.atlassian.com/", "https://www.atlassian.com/ja/", and "https://www.atlassian.com/fr/"
  Zo los je het op
  Add an explicit language selector to the shared header or footer. Make each locale option link to the equivalent current page where available.
hreflang
Mislukt20technisch
Localized versions should be linked with valid, reciprocal hreflang including self and x-default.
- mediumtechnical · 95% zekerheid
  Missing hreflang self-reference
  The page lists hreflang alternates but does not include itself.
  Hier gevonden
  Document head · <link rel="alternate" hreflang>
  https://www.atlassian.com/
  Wat we zagen
  <link rel="alternate" hreflang="ja" href="https://www.atlassian.com/ja/"> <link rel="alternate" hreflang="fr" href="https://www.atlassian.com/fr/"> <link rel="alternate" hreflang="de" href="https://www.atlassian.com/de/"> <link rel="alternate" hreflang="es" href="https://www.atla…
  Zo los je het op
  Add a self-referencing hreflang alternate for this page.
- lowtechnical · 95% zekerheid
  Missing x-default hreflang
  hreflang is present but does not declare an x-default fallback. Affects 12 sampled pages.
  Hier gevonden
  Document head · <link rel="alternate" hreflang>
  https://www.atlassian.com/
  Wat we zagen
  hreflang is present but none of the alternates use hreflang="x-default". Seen on 12 pages, e.g. https://www.atlassian.com/, https://www.atlassian.com/ja/, https://www.atlassian.com/fr/
  Zo los je het op
  Add an x-default hreflang fallback for users whose locale is not listed.
Localized SEO metadata
Mislukt65technisch
Titles, descriptions, and og:locale should be localized per locale.
- mediumtechnical · 95% zekerheid
  Page titles are not localized
  Sampled locales share the same document title.
  Hier gevonden
  Document head · <title>
  https://www.atlassian.com/
  Wat we zagen
  <title>Filter Icon</title> is reused across sampled locales
  Zo los je het op
  Localize the document title for each page locale.
Sitemap
Mislukt60technisch
Like Lighthouse: a valid XML sitemap must be discoverable, robots.txt should reference it with an absolute Sitemap: URL, and localized URLs should appear for published locales.
- mediumtechnical · 90% zekerheid
  Sitemap is missing localized URLs
  A sitemap was found, but sampled entries do not include locale-prefixed URLs.
  Hier gevonden
  Sitemap · sitemap.xml
  https://www.atlassian.com/blog/post-sitemap.xml
  Wat we zagen
  Sitemap https://www.atlassian.com/blog/post-sitemap.xml has no locale-prefixed URLs in the sample
  Zo los je het op
  Include localized URLs in the sitemap for every published locale.
Structured data
Mislukt0technisch
JSON-LD inLanguage should match the page locale when structured data is present.
- lowtechnical · 95% zekerheid
  Structured data omits inLanguage
  JSON-LD is present but does not declare inLanguage on sampled pages.
  Hier gevonden
  JSON-LD · <script type="application/ld+json">
  https://www.atlassian.com/
  Wat we zagen
  Organization is present but inLanguage is missing
  Zo los je het op
  Set JSON-LD inLanguage to match each page locale.
International formatting
Mislukt50technisch
Dates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.
- infotechnical · 90% zekerheid
  Formatting coverage cannot be verified
  The supplied page extracts contain no dates, numbers, currencies, addresses, or calendar examples to assess against locale conventions.
  Wat we zagen
  The provided page text includes navigation and product descriptions such as "Featured apps" and "Flexible project management", but no dates, numbers, or currency values.
  Zo los je het op
  Audit localized pages containing prices, dates, quantities, and addresses with locale-aware formatting rules.
Accessibility localisation
Mislukt72technisch
lang, aria-label, and alt text should match the page locale.
- infotechnical · 88% zekerheid
  Document language is localized
  The English, Japanese, and French page samples explicitly declare matching htmlLang values.
  Hier gevonden
  Document root · <html>
  https://www.atlassian.com/
  Wat we zagen
  "htmlLang":"en" for "https://www.atlassian.com/", "htmlLang":"ja" for "https://www.atlassian.com/ja/", and "htmlLang":"fr" for "https://www.atlassian.com/fr/"
  Zo los je het op
  Keep the html lang value synchronized with the rendered locale on every localized route.
- mediumtechnical · 88% zekerheid
  ARIA labels and alt text are not shown
  The truncated evidence does not include aria-label attributes or image alt text, so accessibility localization cannot be confirmed.
  Wat we zagen
  The preview lists buttons, headings, and text, but contains no "aria-label" or "alt" markup.
  Zo los je het op
  Review all accessible names and image alt attributes for untranslated or hard-coded source-language strings.
Translation completeness
Mislukt0taalkundig
Localized pages should not leave source-language copy in place, except brand names and URLs.
- highlinguistic · 92% zekerheid
  Untranslated call to action
  A fr page still uses source-language CTA copy. Affects 7 sampled pages.
  Hier gevonden
  Pricing hero · <button>
  https://www.atlassian.com/fr/
  Wat we zagen
  Primary CTA: "Solutions" Seen on 7 pages, e.g. https://www.atlassian.com/fr/, https://www.atlassian.com/de/, https://www.atlassian.com/es/
  Zo los je het op
  Translate leftover source-language CTAs to match the surrounding locale copy.
- highlinguistic · 95% zekerheid
  Page script does not match the locale
  A zh page is dominated by Latin-script copy. Affects 2 sampled pages.
  Hier gevonden
  Page body · sampled copy
  https://www.atlassian.com/zh/
  Wat we zagen
  ___ 跳至内容产品精选开发人员产品经理 IT 专业人员业务团队领导团队查看所有应用精选应用 Jira 灵活的项目管理 Confluence 知识，全部集中在一处 Jira Service Management 高速交付服务 Atlassian 集合无缝地增强团队合作 Jira Confluence Loom 自信地优化策略与成果 Focus Talent Align 高速交付服务 Jira Service Management Customer Service Management Assets 快速交付优质的软件 Rovo Dev…
  Zo los je het op
  Write this zh page in the expected script instead of leftover Latin-script copy.
Terminology consistency
Mislukt40taalkundig
Important concepts should not be translated differently across pages.
- mediumlinguistic · 95% zekerheid
  Terminology inconsistency
  "Manage preferences" appears both untranslated and translated across ja pages. Affects 26 sampled pages.
  Hier gevonden
  Header · <nav> or <button>
  https://www.atlassian.com/ja/
  Wat we zagen
  "Manage preferences" appears untranslated on some ja pages and translated on others Seen on 11 pages, e.g. https://www.atlassian.com/ja/, https://www.atlassian.com/fr/, https://www.atlassian.com/de/
  Zo los je het op
  Use one translated label for "Manage preferences" across ja pages.
Cultural adaptation
Mislukt55contextueel
Currency, dates, addresses, and local examples should fit the market.
- infocontextual · 88% zekerheid
  No market-specific adaptation is evidenced
  The supplied extracts contain global product navigation and descriptions but no local currencies, dates, addresses, or market-specific examples to assess.
  Wat we zagen
  The samples show product and audience labels such as "Atlassian Collections", "By Use Case", and "By Team", with no local market data or examples.
  Zo los je het op
  Review pricing, date, address, legal, and example content separately for each target market.
Text expansion
Mislukt40visueel
Longer translations should not create obvious length pressure versus the source UI.
- mediumvisual · 88% zekerheid
  Localized text is much longer than the source
  A fr string is 200% the length of the source, which often causes overflow. Affects 37 sampled pages.
  Hier gevonden
  Control · <button>
  https://www.atlassian.com/fr/
  Wat we zagen
  EN "IT professionals" → FR "Professionnels de l'informatique" (200%) Seen on 9 pages, e.g. https://www.atlassian.com/fr/, https://www.atlassian.com/de/, https://www.atlassian.com/es/
  Zo los je het op
  Shorten the translation or give the control more room so the longer copy does not overflow.
Font and script support
Mislukt48visueel
Typography should support the target script without generic fallback-only stacks, tofu glyphs, or missing CJK fonts.
- highvisual · 95% zekerheid
  No CJK-capable font detected
  A ja page shows CJK text but the embedded/inline font stack has no known CJK typeface. Affects 3 sampled pages.
  Hier gevonden
  Page body · font-family
  https://www.atlassian.com/ja/
  Wat we zagen
  font-family: Charlie Display, Charlie Text, Atlassian Sans, var(--bxp-charlie-text-font-family), var(--bxp-charlie-display-font-family), inherit, var(--_bs1jwf), var(--_1vugql0), var(--ds-font-family-code, var(--ds-font-family-body, unset, SFMono-MediumItalic Seen on 3 pages, e.g…
  Zo los je het op
  Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
CJK typography
Mislukt72visueel
Korean pages should avoid word-break: break-all and prefer word-break: keep-all; CJK forms should use local name-field conventions.
- highvisual · 94% zekerheid
  Korean text uses word-break: break-all
  break-all can split Hangul mid-word and makes Korean body copy harder to read.
  Hier gevonden
  CSS · word-break
  https://www.atlassian.com/ko/
  Wat we zagen
  word-break: break-all, break-word, keep-all, normal, unset
  Zo los je het op
  Use word-break: keep-all for Korean text instead of break-all.
Localized images and assets
Mislukt50visueel
Language-specific images and alt text should match the page locale.
- infovisual · 90% zekerheid
  Localized assets and image alt text are not evidenced
  The truncated page extracts contain no image markup, asset references, or alt attributes, so image localization cannot be assessed.
  Wat we zagen
  The preview includes buttons, headings, and text fields but no "<img>" fragment, asset URL, or "alt" attribute.
  Zo los je het op
  Audit image assets and their alt text on every locale, replacing embedded source-language text where necessary.
Text overflow
Mislukt74visueel
Text should not clip, truncate unexpectedly, or overflow buttons and navigation.
- mediumvisual · 62% zekerheid
  Long localized labels may require overflow testing
  The evidence includes comparatively long navigation labels, but provides no viewport measurements or screenshots to confirm whether text clips or overflows.
  Hier gevonden
  Header navigation · <nav>
  https://www.atlassian.com/fr/
  Wat we zagen
  French labels include "Professionnels de l'informatique" and "Équipes de direction"; Japanese includes "IT プロフェッショナル" and "ビジネス・チーム".
  Zo los je het op
  Test long labels at narrow widths and allow wrapping, flexible button widths, or a collapsed navigation pattern instead of clipping.
Responsive localisation
Mislukt74visueel
Localized layouts should hold up across mobile, tablet, and desktop widths.
- mediumvisual · 58% zekerheid
  Responsive behavior is unverified
  The evidence confirms locale-specific pages but contains no mobile, tablet, or desktop screenshots and no viewport-specific markup or measurements.
  Wat we zagen
  The supplied preview lists page URLs and extracted text only; it contains no viewport dimensions or responsive layout results.
  Zo los je het op
  Perform responsive checks for every supported locale, prioritizing long labels such as "Professionnels de l'informatique" and translated header navigation.

Worth a look (11)

Translation accuracy
Watch88taalkundig
Target copy should preserve the source meaning, numbers, and product actions.
- infolinguistic · 78% zekerheid
  Core navigation and product descriptions preserve meaning
  The Japanese and French extracts correspond to the English navigation and product sections while retaining product names such as Jira and Confluence.
  Hier gevonden
  Primary navigation and featured apps · <nav>, <h2>
  https://www.atlassian.com/fr/
  Wat we zagen
  English: "Featured apps" and "Flexible project management"; Japanese: "おすすめのアプリ" and "柔軟なプロジェクト管理"; French: "Apps recommandées" and "Gestion de projet flexible"
Fluency
Watch88taalkundig
Copy should sound natural, without grammar issues or machine-translation artifacts.
- infolinguistic · 78% zekerheid
  Sampled localized copy reads naturally
  The provided Japanese and French navigation and product labels appear coherent and idiomatic, with no explicit machine-translation artifacts in the sample.
  Hier gevonden
  Navigation and featured apps · <nav>, <section>
  https://www.atlassian.com/ja/
  Wat we zagen
  French: "Apps recommandées", "Collections Atlassian", and "Par cas d’usage"; Japanese: "おすすめのアプリ", "ユースケース別", and "チーム別"
Brand voice
Watch84taalkundig
Localized copy should preserve the intended tone of the source.
- infolinguistic · 76% zekerheid
  Product-led, concise tone is retained
  Localized labels preserve the concise, professional tone of the English source while keeping the Atlassian product naming intact.
  Hier gevonden
  Featured apps and collections · <section>
  https://www.atlassian.com/fr/
  Wat we zagen
  English: "Knowledge, all in one place"; Japanese: "すべての知識を 1 か所に"; French: "Les connaissances réunies au même endroit"
Grammar and style
Watch86taalkundig
Locale-specific capitalization, punctuation, formality, and agreement should be correct.
- infolinguistic · 76% zekerheid
  Sampled locale grammar and capitalization are consistent
  The extracted French and Japanese headings and navigation labels follow coherent locale-specific conventions in the sampled content.
  Hier gevonden
  Navigation and headings · <nav>, <h2>
  https://www.atlassian.com/fr/
  Wat we zagen
  French: "Responsables produit", "Professionnels de l'informatique", and "Équipes métier"; Japanese: "プロダクトマネージャー" and "ビジネス・チーム"
UI context
Watch88contextueel
Translations should fit the UI component: button, nav, form, modal, or error.
- infocontextual · 80% zekerheid
  Navigation and heading translations fit their UI roles
  The evidence distinguishes localized buttons from headings and shows role-appropriate short labels in multiple locales.
  Hier gevonden
  Header and page sections · <button>, <h2>
  https://www.atlassian.com/
  Wat we zagen
  Buttons include "Sign in", "サインイン", "Connexion", and "Einloggen"; headings include "Featured apps", "おすすめのアプリ", and "Apps recommandées"
Product context
Watch88contextueel
Language should match product concepts such as plans, settings, and workflows.
- infocontextual · 80% zekerheid
  Product terminology remains recognizable and contextualized
  Product names remain unchanged while surrounding descriptions are translated for the locale.
  Hier gevonden
  Featured apps and collections · <section>
  https://www.atlassian.com/ja/
  Wat we zagen
  The extracts retain "Jira", "Confluence", "Jira Service Management", "Atlassian Collections", and "Focus Talent Align" alongside localized descriptions.
  Zo los je het op
  Maintain an approved glossary for product names and product-specific concepts across all locales.
Contextual meaning
Watch86contextueel
Strings should be judged in surrounding page and component context, not in isolation.
- infocontextual · 78% zekerheid
  Strings are supported by surrounding page context
  The samples provide consistent relationships between navigation labels, section headings, product names, and descriptions across locales.
  Hier gevonden
  Page navigation and featured apps · <nav>, <section>
  https://www.atlassian.com/ja/
  Wat we zagen
  English groups "Featured apps", "Atlassian Collections", "By Use Case", and "By Team"; Japanese groups "おすすめのアプリ", "Atlassian Collections", "ユースケース別", and "チーム別".
Audience context
Watch88contextueel
Language should fit the intended audience, such as consumer, enterprise, or developer.
- infocontextual · 82% zekerheid
  Professional audience segments are localized
  Audience-oriented navigation labels for developers, product managers, IT professionals, business teams, and leadership teams are represented in localized samples.
  Hier gevonden
  Primary navigation · <nav>
  https://www.atlassian.com/fr/
  Wat we zagen
  English: "Developers", "Product Managers", "IT professionals", and "Business Teams"; French: "Développeurs", "Responsables produit", "Professionnels de l'informatique", and "Équipes métier"
Visual hierarchy
Watch76visueel
Localization should not make headings or CTAs lose scanability.
- lowvisual · 80% zekerheid
  Heading is excessively long
  A localized heading may crowd the visual hierarchy.
  Hier gevonden
  Page body · heading
  https://www.atlassian.com/pl/
  Wat we zagen
  Ponad 350 000 zespołów nie do zatrzymania wykorzystuje potencjał sztucznej inteligencji
  Zo los je het op
  Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
Watch78visueel
Repeated components should stay visually consistent across locales.
- infovisual · 68% zekerheid
  Repeated text components appear structurally consistent
  The same button and heading categories are present across the English, Japanese, French, and German extracts, but screenshots or computed styles are not provided.
  Hier gevonden
  Header and section components · <button>, <h2>
  https://www.atlassian.com/
  Wat we zagen
  Each sample exposes localized button arrays and corresponding headings, including "Sign in"/"サインイン"/"Connexion"/"Einloggen" and translated featured-app headings.
  Zo los je het op
  Run visual regression tests across locales to confirm spacing, typography, and component dimensions remain consistent.
Layout breakage
Watch76visueel
Localized pages should not overlap, break grids, or overflow modals.
- infovisual · 60% zekerheid
  No layout failure is visible in the supplied markup extract
  The page extracts show matching navigation and section structures across locales, but markup-only evidence cannot establish whether grids or overlays break visually.
  Hier gevonden
  Page shell and featured sections · <header>, <section>
  https://www.atlassian.com/
  Wat we zagen
  The samples expose the same broad page structure: navigation, featured apps, Atlassian Collections, use-case, and team sections across English, Japanese, and French.
  Zo los je het op
  Capture localized screenshots and test grids, menus, and dialogs at representative desktop and mobile widths.

Geslaagde controles (4)

Niet van toepassing (4)

Other findings

Findings not listed under a criterion above.

infocontextual · 84% zekerheid
Sign-in action is clearly localized
The sampled sign-in control communicates the same authentication action across English, Japanese, French, and German.
Hier gevonden
Header · <button>
https://www.atlassian.com/
Wat we zagen
English: "Sign in"; Japanese: "サインイン"; French: "Connexion"; German: "Einloggen"

Gedetecteerde talen

Bretons
br · page language
Duits
de · hreflang
Engels
en · page language
Spaans
es · hreflang
Frans
fr · hreflang
Italiaans
it · hreflang
Japans
ja · hreflang
Koreaans
ko · hreflang
Nederlands
nl · hreflang
Pools
pl · hreflang
Portugees (Brazilië)
pt-br · hreflang
Russisch
ru · hreflang
Chinees
zh · page language

Pagina’s bemonsterd

Volgende stap

Solid baseline with room to improve. Claim this domain to monitor locales as you ship, or book an audit review.

Boek een auditbeoordeling

Send this to your team

We'll email a short summary — score, top fixes, and a link back to this report — so it's easy to forward.