ローカライズレポート

Atlassian

Team collaboration software

atlassian.com

製品: 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.

ブランドボイス: Collaborative, confident, productivity-focused

ローカライズスコア

69/100

改善が必要

ユーザーは、目立つローカライズの問題に遭遇する可能性があります。

63技術監査
64言語監査
83コンテキスト監査
65ビジュアル監査

監査日: 2026/08/15範囲: 公開スマートサンプル · 技術・言語・文脈・ビジュアルの各クレジット信頼度: サンプルページに基づく参考用のヘルスチェック — サイト全体をクロールしたものではありません。

技術面、言語面、文脈面、視覚面の各ローカライズ評価項目にわたり、15 ページをサンプリングしました。ローカライゼーション監査の評価方法

他の人との比較

公開監査23件中#15位

Ahead of 8 other public audits公開平均: 70/100

リーダーボード全体を見る

最初に修正する項目

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

監査基準

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

要対応 (16)

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

合格した監査項目 (4)

該当なし（4）

Other findings

Findings not listed under a criterion above.

infocontextual · 84% の確信度
Sign-in action is clearly localized
The sampled sign-in control communicates the same authentication action across English, Japanese, French, and German.
こちらで見つかりました
Header · <button>
https://www.atlassian.com/
確認されたこと
English: "Sign in"; Japanese: "サインイン"; French: "Connexion"; German: "Einloggen"

検出されたロケール

ブルトン語
br · page language
ドイツ語
de · hreflang
英語
en · page language
スペイン語
es · hreflang
フランス語
fr · hreflang
イタリア語
it · hreflang
日本語
ja · hreflang
韓国語
ko · hreflang
オランダ語
nl · hreflang
ポーランド語
pl · hreflang
ポルトガル語 (ブラジル)
pt-br · hreflang
ロシア語
ru · hreflang
中国語
zh · page language

サンプル対象のページ

次のステップ

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

監査レビューを予約する

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.