현지화 보고서

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