Lokaliseringsrapport

Atlassian

Team collaboration software

atlassian.com

Produkt: 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.

Brandstemme: Collaborative, confident, productivity-focused

Lokaliseringsscore

69/100

Kræver forbedring

Brugerne kan opleve mærkbare lokaliseringsproblemer.

63Teknisk audit
64Sproglig kontrol
83Kontekstaudit
65Visuel revision

Auditeret: 15. aug. 2026Omfang: Offentlig smart prøve · tekniske, sproglige, kontekstuelle og visuelle creditsSikkerhed: Vejledende sundhedstjek baseret på udvalgte sider — ikke en fuld gennemgang af webstedet.

Udvalgte 15 sider på tværs af tekniske, sproglige, kontekstuelle og visuelle lokaliseringskrediteringer. Sådan bedømmer vi lokaliseringsaudits

Sådan ligger du i forhold til andre

Placering nr. 15 af 23 offentlige audits

Ahead of 8 other public auditsOffentligt gennemsnit: 70/100

Se hele ranglisten

Ret først

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

Revisionskriterier

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

Kræver opmærksomhed (16)

Language switcher
Ikke bestået65teknisk
Visitors should move between locales without losing the current page.
- mediumtechnical · 82% sikkerhed
  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.
  Fundet her
  https://www.atlassian.com/
  Hvad vi så
  "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/"
  Sådan løser du det
  Add an explicit language selector to the shared header or footer. Make each locale option link to the equivalent current page where available.
hreflang
Ikke bestået20teknisk
Localized versions should be linked with valid, reciprocal hreflang including self and x-default.
- mediumtechnical · 95% sikkerhed
  Missing hreflang self-reference
  The page lists hreflang alternates but does not include itself.
  Fundet her
  Document head · <link rel="alternate" hreflang>
  https://www.atlassian.com/
  Hvad vi så
  <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…
  Sådan løser du det
  Add a self-referencing hreflang alternate for this page.
- lowtechnical · 95% sikkerhed
  Missing x-default hreflang
  hreflang is present but does not declare an x-default fallback. Affects 12 sampled pages.
  Fundet her
  Document head · <link rel="alternate" hreflang>
  https://www.atlassian.com/
  Hvad vi så
  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/
  Sådan løser du det
  Add an x-default hreflang fallback for users whose locale is not listed.
Localized SEO metadata
Ikke bestået65teknisk
Titles, descriptions, and og:locale should be localized per locale.
- mediumtechnical · 95% sikkerhed
  Page titles are not localized
  Sampled locales share the same document title.
  Fundet her
  Document head · <title>
  https://www.atlassian.com/
  Hvad vi så
  <title>Filter Icon</title> is reused across sampled locales
  Sådan løser du det
  Localize the document title for each page locale.
Sitemap
Ikke bestået60teknisk
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% sikkerhed
  Sitemap is missing localized URLs
  A sitemap was found, but sampled entries do not include locale-prefixed URLs.
  Fundet her
  Sitemap · sitemap.xml
  https://www.atlassian.com/blog/post-sitemap.xml
  Hvad vi så
  Sitemap https://www.atlassian.com/blog/post-sitemap.xml has no locale-prefixed URLs in the sample
  Sådan løser du det
  Include localized URLs in the sitemap for every published locale.
Structured data
Ikke bestået0teknisk
JSON-LD inLanguage should match the page locale when structured data is present.
- lowtechnical · 95% sikkerhed
  Structured data omits inLanguage
  JSON-LD is present but does not declare inLanguage on sampled pages.
  Fundet her
  JSON-LD · <script type="application/ld+json">
  https://www.atlassian.com/
  Hvad vi så
  Organization is present but inLanguage is missing
  Sådan løser du det
  Set JSON-LD inLanguage to match each page locale.
International formatting
Ikke bestået50teknisk
Dates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.
- infotechnical · 90% sikkerhed
  Formatting coverage cannot be verified
  The supplied page extracts contain no dates, numbers, currencies, addresses, or calendar examples to assess against locale conventions.
  Hvad vi så
  The provided page text includes navigation and product descriptions such as "Featured apps" and "Flexible project management", but no dates, numbers, or currency values.
  Sådan løser du det
  Audit localized pages containing prices, dates, quantities, and addresses with locale-aware formatting rules.
Accessibility localisation
Ikke bestået72teknisk
lang, aria-label, and alt text should match the page locale.
- infotechnical · 88% sikkerhed
  Document language is localized
  The English, Japanese, and French page samples explicitly declare matching htmlLang values.
  Fundet her
  Document root · <html>
  https://www.atlassian.com/
  Hvad vi så
  "htmlLang":"en" for "https://www.atlassian.com/", "htmlLang":"ja" for "https://www.atlassian.com/ja/", and "htmlLang":"fr" for "https://www.atlassian.com/fr/"
  Sådan løser du det
  Keep the html lang value synchronized with the rendered locale on every localized route.
- mediumtechnical · 88% sikkerhed
  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.
  Hvad vi så
  The preview lists buttons, headings, and text, but contains no "aria-label" or "alt" markup.
  Sådan løser du det
  Review all accessible names and image alt attributes for untranslated or hard-coded source-language strings.
Translation completeness
Ikke bestået0sproglig
Localized pages should not leave source-language copy in place, except brand names and URLs.
- highlinguistic · 92% sikkerhed
  Untranslated call to action
  A fr page still uses source-language CTA copy. Affects 7 sampled pages.
  Fundet her
  Pricing hero · <button>
  https://www.atlassian.com/fr/
  Hvad vi så
  Primary CTA: "Solutions" Seen on 7 pages, e.g. https://www.atlassian.com/fr/, https://www.atlassian.com/de/, https://www.atlassian.com/es/
  Sådan løser du det
  Translate leftover source-language CTAs to match the surrounding locale copy.
- highlinguistic · 95% sikkerhed
  Page script does not match the locale
  A zh page is dominated by Latin-script copy. Affects 2 sampled pages.
  Fundet her
  Page body · sampled copy
  https://www.atlassian.com/zh/
  Hvad vi så
  ___ 跳至内容产品精选开发人员产品经理 IT 专业人员业务团队领导团队查看所有应用精选应用 Jira 灵活的项目管理 Confluence 知识，全部集中在一处 Jira Service Management 高速交付服务 Atlassian 集合无缝地增强团队合作 Jira Confluence Loom 自信地优化策略与成果 Focus Talent Align 高速交付服务 Jira Service Management Customer Service Management Assets 快速交付优质的软件 Rovo Dev…
  Sådan løser du det
  Write this zh page in the expected script instead of leftover Latin-script copy.
Terminology consistency
Ikke bestået40sproglig
Important concepts should not be translated differently across pages.
- mediumlinguistic · 95% sikkerhed
  Terminology inconsistency
  "Manage preferences" appears both untranslated and translated across ja pages. Affects 26 sampled pages.
  Fundet her
  Header · <nav> or <button>
  https://www.atlassian.com/ja/
  Hvad vi så
  "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/
  Sådan løser du det
  Use one translated label for "Manage preferences" across ja pages.
Cultural adaptation
Ikke bestået55kontekstuel
Currency, dates, addresses, and local examples should fit the market.
- infocontextual · 88% sikkerhed
  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.
  Hvad vi så
  The samples show product and audience labels such as "Atlassian Collections", "By Use Case", and "By Team", with no local market data or examples.
  Sådan løser du det
  Review pricing, date, address, legal, and example content separately for each target market.
Text expansion
Ikke bestået40visuel
Longer translations should not create obvious length pressure versus the source UI.
- mediumvisual · 88% sikkerhed
  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.
  Fundet her
  Control · <button>
  https://www.atlassian.com/fr/
  Hvad vi så
  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/
  Sådan løser du det
  Shorten the translation or give the control more room so the longer copy does not overflow.
Font and script support
Ikke bestået48visuel
Typography should support the target script without generic fallback-only stacks, tofu glyphs, or missing CJK fonts.
- highvisual · 95% sikkerhed
  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.
  Fundet her
  Page body · font-family
  https://www.atlassian.com/ja/
  Hvad vi så
  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…
  Sådan løser du det
  Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
CJK typography
Ikke bestået72visuel
Korean pages should avoid word-break: break-all and prefer word-break: keep-all; CJK forms should use local name-field conventions.
- highvisual · 94% sikkerhed
  Korean text uses word-break: break-all
  break-all can split Hangul mid-word and makes Korean body copy harder to read.
  Fundet her
  CSS · word-break
  https://www.atlassian.com/ko/
  Hvad vi så
  word-break: break-all, break-word, keep-all, normal, unset
  Sådan løser du det
  Use word-break: keep-all for Korean text instead of break-all.
Localized images and assets
Ikke bestået50visuel
Language-specific images and alt text should match the page locale.
- infovisual · 90% sikkerhed
  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.
  Hvad vi så
  The preview includes buttons, headings, and text fields but no "<img>" fragment, asset URL, or "alt" attribute.
  Sådan løser du det
  Audit image assets and their alt text on every locale, replacing embedded source-language text where necessary.
Text overflow
Ikke bestået74visuel
Text should not clip, truncate unexpectedly, or overflow buttons and navigation.
- mediumvisual · 62% sikkerhed
  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.
  Fundet her
  Header navigation · <nav>
  https://www.atlassian.com/fr/
  Hvad vi så
  French labels include "Professionnels de l'informatique" and "Équipes de direction"; Japanese includes "IT プロフェッショナル" and "ビジネス・チーム".
  Sådan løser du det
  Test long labels at narrow widths and allow wrapping, flexible button widths, or a collapsed navigation pattern instead of clipping.
Responsive localisation
Ikke bestået74visuel
Localized layouts should hold up across mobile, tablet, and desktop widths.
- mediumvisual · 58% sikkerhed
  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.
  Hvad vi så
  The supplied preview lists page URLs and extracted text only; it contains no viewport dimensions or responsive layout results.
  Sådan løser du det
  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
Watch88sproglig
Target copy should preserve the source meaning, numbers, and product actions.
- infolinguistic · 78% sikkerhed
  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.
  Fundet her
  Primary navigation and featured apps · <nav>, <h2>
  https://www.atlassian.com/fr/
  Hvad vi så
  English: "Featured apps" and "Flexible project management"; Japanese: "おすすめのアプリ" and "柔軟なプロジェクト管理"; French: "Apps recommandées" and "Gestion de projet flexible"
Fluency
Watch88sproglig
Copy should sound natural, without grammar issues or machine-translation artifacts.
- infolinguistic · 78% sikkerhed
  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.
  Fundet her
  Navigation and featured apps · <nav>, <section>
  https://www.atlassian.com/ja/
  Hvad vi så
  French: "Apps recommandées", "Collections Atlassian", and "Par cas d’usage"; Japanese: "おすすめのアプリ", "ユースケース別", and "チーム別"
Brand voice
Watch84sproglig
Localized copy should preserve the intended tone of the source.
- infolinguistic · 76% sikkerhed
  Product-led, concise tone is retained
  Localized labels preserve the concise, professional tone of the English source while keeping the Atlassian product naming intact.
  Fundet her
  Featured apps and collections · <section>
  https://www.atlassian.com/fr/
  Hvad vi så
  English: "Knowledge, all in one place"; Japanese: "すべての知識を 1 か所に"; French: "Les connaissances réunies au même endroit"
Grammar and style
Watch86sproglig
Locale-specific capitalization, punctuation, formality, and agreement should be correct.
- infolinguistic · 76% sikkerhed
  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.
  Fundet her
  Navigation and headings · <nav>, <h2>
  https://www.atlassian.com/fr/
  Hvad vi så
  French: "Responsables produit", "Professionnels de l'informatique", and "Équipes métier"; Japanese: "プロダクトマネージャー" and "ビジネス・チーム"
UI context
Watch88kontekstuel
Translations should fit the UI component: button, nav, form, modal, or error.
- infocontextual · 80% sikkerhed
  Navigation and heading translations fit their UI roles
  The evidence distinguishes localized buttons from headings and shows role-appropriate short labels in multiple locales.
  Fundet her
  Header and page sections · <button>, <h2>
  https://www.atlassian.com/
  Hvad vi så
  Buttons include "Sign in", "サインイン", "Connexion", and "Einloggen"; headings include "Featured apps", "おすすめのアプリ", and "Apps recommandées"
Product context
Watch88kontekstuel
Language should match product concepts such as plans, settings, and workflows.
- infocontextual · 80% sikkerhed
  Product terminology remains recognizable and contextualized
  Product names remain unchanged while surrounding descriptions are translated for the locale.
  Fundet her
  Featured apps and collections · <section>
  https://www.atlassian.com/ja/
  Hvad vi så
  The extracts retain "Jira", "Confluence", "Jira Service Management", "Atlassian Collections", and "Focus Talent Align" alongside localized descriptions.
  Sådan løser du det
  Maintain an approved glossary for product names and product-specific concepts across all locales.
Contextual meaning
Watch86kontekstuel
Strings should be judged in surrounding page and component context, not in isolation.
- infocontextual · 78% sikkerhed
  Strings are supported by surrounding page context
  The samples provide consistent relationships between navigation labels, section headings, product names, and descriptions across locales.
  Fundet her
  Page navigation and featured apps · <nav>, <section>
  https://www.atlassian.com/ja/
  Hvad vi så
  English groups "Featured apps", "Atlassian Collections", "By Use Case", and "By Team"; Japanese groups "おすすめのアプリ", "Atlassian Collections", "ユースケース別", and "チーム別".
Audience context
Watch88kontekstuel
Language should fit the intended audience, such as consumer, enterprise, or developer.
- infocontextual · 82% sikkerhed
  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.
  Fundet her
  Primary navigation · <nav>
  https://www.atlassian.com/fr/
  Hvad vi så
  English: "Developers", "Product Managers", "IT professionals", and "Business Teams"; French: "Développeurs", "Responsables produit", "Professionnels de l'informatique", and "Équipes métier"
Visual hierarchy
Watch76visuel
Localization should not make headings or CTAs lose scanability.
- lowvisual · 80% sikkerhed
  Heading is excessively long
  A localized heading may crowd the visual hierarchy.
  Fundet her
  Page body · heading
  https://www.atlassian.com/pl/
  Hvad vi så
  Ponad 350 000 zespołów nie do zatrzymania wykorzystuje potencjał sztucznej inteligencji
  Sådan løser du det
  Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
Watch78visuel
Repeated components should stay visually consistent across locales.
- infovisual · 68% sikkerhed
  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.
  Fundet her
  Header and section components · <button>, <h2>
  https://www.atlassian.com/
  Hvad vi så
  Each sample exposes localized button arrays and corresponding headings, including "Sign in"/"サインイン"/"Connexion"/"Einloggen" and translated featured-app headings.
  Sådan løser du det
  Run visual regression tests across locales to confirm spacing, typography, and component dimensions remain consistent.
Layout breakage
Watch76visuel
Localized pages should not overlap, break grids, or overflow modals.
- infovisual · 60% sikkerhed
  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.
  Fundet her
  Page shell and featured sections · <header>, <section>
  https://www.atlassian.com/
  Hvad vi så
  The samples expose the same broad page structure: navigation, featured apps, Atlassian Collections, use-case, and team sections across English, Japanese, and French.
  Sådan løser du det
  Capture localized screenshots and test grids, menus, and dialogs at representative desktop and mobile widths.

Beståede audits (4)

Ikke relevant (4)

Other findings

Findings not listed under a criterion above.

infocontextual · 84% sikkerhed
Sign-in action is clearly localized
The sampled sign-in control communicates the same authentication action across English, Japanese, French, and German.
Fundet her
Header · <button>
https://www.atlassian.com/
Hvad vi så
English: "Sign in"; Japanese: "サインイン"; French: "Connexion"; German: "Einloggen"

Registrerede lokaliteter

bretonsk
br · page language
tysk
de · hreflang
engelsk
en · page language
spansk
es · hreflang
fransk
fr · hreflang
italiensk
it · hreflang
japansk
ja · hreflang
koreansk
ko · hreflang
nederlandsk
nl · hreflang
polsk
pl · hreflang
brasiliansk portugisisk
pt-br · hreflang
russisk
ru · hreflang
kinesisk
zh · page language

Stikprøvekontrollerede sider

Næste skridt

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

Book en gennemgang af lokaliseringen-аudit

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.