Atlassian

Needs attention (27)

• Language switcher

  Fail65technical

  Visitors should move between locales without losing the current page.

  • mediumtechnical · 82% confidence

    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.

    Found here

    https://www.atlassian.com/

    What we saw

    "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/"

    How to fix it

    Add an explicit language selector to the shared header or footer. Make each locale option link to the equivalent current page where available.

• hreflang

  Fail20technical

  Localized versions should be linked with valid, reciprocal hreflang including self and x-default.

  • mediumtechnical · 95% confidence

    Missing hreflang self-reference

    The page lists hreflang alternates but does not include itself.

    Found here

    Document head · <link rel="alternate" hreflang>

    https://www.atlassian.com/

    What we saw

    <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.atlassian.com/es/">

    How to fix it

    Add a self-referencing hreflang alternate for this page.

  • lowtechnical · 95% confidence

    Missing x-default hreflang

    hreflang is present but does not declare an x-default fallback. Affects 12 sampled pages.

    Found here

    Document head · <link rel="alternate" hreflang>

    https://www.atlassian.com/

    What we saw

    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/

    How to fix it

    Add an x-default hreflang fallback for users whose locale is not listed.

• Localized SEO metadata

  Fail65technical

  Titles, descriptions, and og:locale should be localized per locale.

  • mediumtechnical · 95% confidence

    Page titles are not localized

    Sampled locales share the same document title.

    Found here

    Document head · <title>

    https://www.atlassian.com/

    What we saw

    <title>Filter Icon</title> is reused across sampled locales

    How to fix it

    Localize the document title for each page locale.

• Sitemap

  Fail60technical

  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% confidence

    Sitemap is missing localized URLs

    A sitemap was found, but sampled entries do not include locale-prefixed URLs.

    Found here

    Sitemap · sitemap.xml

    https://www.atlassian.com/blog/post-sitemap.xml

    What we saw

    Sitemap https://www.atlassian.com/blog/post-sitemap.xml has no locale-prefixed URLs in the sample

    How to fix it

    Include localized URLs in the sitemap for every published locale.

• Structured data

  Fail0technical

  JSON-LD inLanguage should match the page locale when structured data is present.

  • lowtechnical · 95% confidence

    Structured data omits inLanguage

    JSON-LD is present but does not declare inLanguage on sampled pages.

    Found here

    JSON-LD · <script type="application/ld+json">

    https://www.atlassian.com/

    What we saw

    Organization is present but inLanguage is missing

    How to fix it

    Set JSON-LD inLanguage to match each page locale.

• International formatting

  Fail50technical

  Dates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.

  • infotechnical · 90% confidence

    Formatting coverage cannot be verified

    The supplied page extracts contain no dates, numbers, currencies, addresses, or calendar examples to assess against locale conventions.

    What we saw

    The provided page text includes navigation and product descriptions such as "Featured apps" and "Flexible project management", but no dates, numbers, or currency values.

    How to fix it

    Audit localized pages containing prices, dates, quantities, and addresses with locale-aware formatting rules.

• Accessibility localisation

  Fail72technical

  lang, aria-label, and alt text should match the page locale.

  • infotechnical · 88% confidence

    Document language is localized

    The English, Japanese, and French page samples explicitly declare matching htmlLang values.

    Found here

    Document root · <html>

    https://www.atlassian.com/

    What we saw

    "htmlLang":"en" for "https://www.atlassian.com/", "htmlLang":"ja" for "https://www.atlassian.com/ja/", and "htmlLang":"fr" for "https://www.atlassian.com/fr/"

    How to fix it

    Keep the html lang value synchronized with the rendered locale on every localized route.

  • mediumtechnical · 88% confidence

    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.

    What we saw

    The preview lists buttons, headings, and text, but contains no "aria-label" or "alt" markup.

    How to fix it

    Review all accessible names and image alt attributes for untranslated or hard-coded source-language strings.

• Translation completeness

  Fail0linguistic

  Localized pages should not leave source-language copy in place, except brand names and URLs.

  • highlinguistic · 92% confidence

    Untranslated call to action

    A fr page still uses source-language CTA copy. Affects 7 sampled pages.

    Found here

    Pricing hero · <button>

    https://www.atlassian.com/fr/

    What we saw

    Primary CTA: "Solutions" Seen on 7 pages, e.g. https://www.atlassian.com/fr/, https://www.atlassian.com/de/, https://www.atlassian.com/es/

    How to fix it

    Translate leftover source-language CTAs to match the surrounding locale copy.

  • highlinguistic · 95% confidence

    Page script does not match the locale

    A zh page is dominated by Latin-script copy. Affects 2 sampled pages.

    Found here

    Page body · sampled copy

    https://www.atlassian.com/zh/

    What we saw

    ___ 跳至内容 产品 精选 开发人员 产品经理 IT 专业人员 业务团队 领导团队 查看所有应用 精选应用 Jira 灵活的项目管理 Confluence 知识，全部集中在一处 Jira Service Management 高速交付服务 Atlassian 集合 无缝地增强团队合作 Jira Confluence Loom 自信地优化策略与成果 Focus Talent Align 高速交付服务 Jira Service Management Customer Service Management Assets 快速交付优质的软件 Rovo Dev DX Pipelines Bitbucket 从容打造产品 Jira Product Discovery Feedback Rovo 技术支持 Rovo 人工智能支持的应用—由团队知识驱动。 Jira 灵活的项目管理 Bitbucket … Seen on 2 pages, e.g. https://www.atlassian.com/zh/, https://www.atlassian.com/ko/

    How to fix it

    Write this zh page in the expected script instead of leftover Latin-script copy.

• Terminology consistency

  Fail40linguistic

  Important concepts should not be translated differently across pages.

  • mediumlinguistic · 95% confidence

    Terminology inconsistency

    "Manage preferences" appears both untranslated and translated across ja pages. Affects 26 sampled pages.

    Found here

    Header · <nav> or <button>

    https://www.atlassian.com/ja/

    What we saw

    "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/

    How to fix it

    Use one translated label for "Manage preferences" across ja pages.

• Translation accuracy

  Fail88linguistic

  Target copy should preserve the source meaning, numbers, and product actions.

  • infolinguistic · 78% confidence

    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.

    Found here

    Primary navigation and featured apps · <nav>, <h2>

    https://www.atlassian.com/fr/

    What we saw

    English: "Featured apps" and "Flexible project management"; Japanese: "おすすめのアプリ" and "柔軟なプロジェクト管理"; French: "Apps recommandées" and "Gestion de projet flexible"

• Fluency

  Fail88linguistic

  Copy should sound natural, without grammar issues or machine-translation artifacts.

  • infolinguistic · 78% confidence

    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.

    Found here

    Navigation and featured apps · <nav>, <section>

    https://www.atlassian.com/ja/

    What we saw

    French: "Apps recommandées", "Collections Atlassian", and "Par cas d’usage"; Japanese: "おすすめのアプリ", "ユース ケース別", and "チーム別"

• Brand voice

  Fail84linguistic

  Localized copy should preserve the intended tone of the source.

  • infolinguistic · 76% confidence

    Product-led, concise tone is retained

    Localized labels preserve the concise, professional tone of the English source while keeping the Atlassian product naming intact.

    Found here

    Featured apps and collections · <section>

    https://www.atlassian.com/fr/

    What we saw

    English: "Knowledge, all in one place"; Japanese: "すべての知識を 1 か所に"; French: "Les connaissances réunies au même endroit"

• Grammar and style

  Fail86linguistic

  Locale-specific capitalization, punctuation, formality, and agreement should be correct.

  • infolinguistic · 76% confidence

    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.

    Found here

    Navigation and headings · <nav>, <h2>

    https://www.atlassian.com/fr/

    What we saw

    French: "Responsables produit", "Professionnels de l'informatique", and "Équipes métier"; Japanese: "プロダクト マネージャー" and "ビジネス・チーム"

• Cultural adaptation

  Fail55contextual

  Currency, dates, addresses, and local examples should fit the market.

  • infocontextual · 88% confidence

    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.

    What we saw

    The samples show product and audience labels such as "Atlassian Collections", "By Use Case", and "By Team", with no local market data or examples.

    How to fix it

    Review pricing, date, address, legal, and example content separately for each target market.

• UI context

  Fail88contextual

  Translations should fit the UI component: button, nav, form, modal, or error.

  • infocontextual · 80% confidence

    Navigation and heading translations fit their UI roles

    The evidence distinguishes localized buttons from headings and shows role-appropriate short labels in multiple locales.

    Found here

    Header and page sections · <button>, <h2>

    https://www.atlassian.com/

    What we saw

    Buttons include "Sign in", "サインイン", "Connexion", and "Einloggen"; headings include "Featured apps", "おすすめのアプリ", and "Apps recommandées"

• Product context

  Fail88contextual

  Language should match product concepts such as plans, settings, and workflows.

  • infocontextual · 80% confidence

    Product terminology remains recognizable and contextualized

    Product names remain unchanged while surrounding descriptions are translated for the locale.

    Found here

    Featured apps and collections · <section>

    https://www.atlassian.com/ja/

    What we saw

    The extracts retain "Jira", "Confluence", "Jira Service Management", "Atlassian Collections", and "Focus Talent Align" alongside localized descriptions.

    How to fix it

    Maintain an approved glossary for product names and product-specific concepts across all locales.

• Contextual meaning

  Fail86contextual

  Strings should be judged in surrounding page and component context, not in isolation.

  • infocontextual · 78% confidence

    Strings are supported by surrounding page context

    The samples provide consistent relationships between navigation labels, section headings, product names, and descriptions across locales.

    Found here

    Page navigation and featured apps · <nav>, <section>

    https://www.atlassian.com/ja/

    What we saw

    English groups "Featured apps", "Atlassian Collections", "By Use Case", and "By Team"; Japanese groups "おすすめのアプリ", "Atlassian Collections", "ユース ケース別", and "チーム別".

• Audience context

  Fail88contextual

  Language should fit the intended audience, such as consumer, enterprise, or developer.

  • infocontextual · 82% confidence

    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.

    Found here

    Primary navigation · <nav>

    https://www.atlassian.com/fr/

    What we saw

    English: "Developers", "Product Managers", "IT professionals", and "Business Teams"; French: "Développeurs", "Responsables produit", "Professionnels de l'informatique", and "Équipes métier"

• Text expansion

  Fail40visual

  Longer translations should not create obvious length pressure versus the source UI.

  • mediumvisual · 88% confidence

    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.

    Found here

    Control · <button>

    https://www.atlassian.com/fr/

    What we saw

    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/

    How to fix it

    Shorten the translation or give the control more room so the longer copy does not overflow.

• Font and script support

  Fail48visual

  Typography should support the target script without generic fallback-only stacks, tofu glyphs, or missing CJK fonts.

  • highvisual · 95% confidence

    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.

    Found here

    Page body · font-family

    https://www.atlassian.com/ja/

    What we saw

    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. https://www.atlassian.com/ja/, https://www.atlassian.com/zh/, https://www.atlassian.com/ko/

    How to fix it

    Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.

• CJK typography

  Fail72visual

  Korean pages should avoid word-break: break-all and prefer word-break: keep-all; CJK forms should use local name-field conventions.

  • highvisual · 94% confidence

    Korean text uses word-break: break-all

    break-all can split Hangul mid-word and makes Korean body copy harder to read.

    Found here

    CSS · word-break

    https://www.atlassian.com/ko/

    What we saw

    word-break: break-all, break-word, keep-all, normal, unset

    How to fix it

    Use word-break: keep-all for Korean text instead of break-all.

• Localized images and assets

  Fail50visual

  Language-specific images and alt text should match the page locale.

  • infovisual · 90% confidence

    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.

    What we saw

    The preview includes buttons, headings, and text fields but no "<img>" fragment, asset URL, or "alt" attribute.

    How to fix it

    Audit image assets and their alt text on every locale, replacing embedded source-language text where necessary.

• Visual hierarchy

  Fail76visual

  Localization should not make headings or CTAs lose scanability.

  • lowvisual · 80% confidence

    Heading is excessively long

    A localized heading may crowd the visual hierarchy.

    Found here

    Page body · heading

    https://www.atlassian.com/pl/

    What we saw

    Ponad 350 000 zespołów nie do zatrzymania wykorzystuje potencjał sztucznej inteligencji

    How to fix it

    Shorten the heading so it does not crowd the visual hierarchy.

• Component consistency

  Fail78visual

  Repeated components should stay visually consistent across locales.

  • infovisual · 68% confidence

    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.

    Found here

    Header and section components · <button>, <h2>

    https://www.atlassian.com/

    What we saw

    Each sample exposes localized button arrays and corresponding headings, including "Sign in"/"サインイン"/"Connexion"/"Einloggen" and translated featured-app headings.

    How to fix it

    Run visual regression tests across locales to confirm spacing, typography, and component dimensions remain consistent.

• Text overflow

  Fail74visual

  Text should not clip, truncate unexpectedly, or overflow buttons and navigation.

  • mediumvisual · 62% confidence

    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.

    Found here

    Header navigation · <nav>

    https://www.atlassian.com/fr/

    What we saw

    French labels include "Professionnels de l'informatique" and "Équipes de direction"; Japanese includes "IT プロフェッショナル" and "ビジネス・チーム".

    How to fix it

    Test long labels at narrow widths and allow wrapping, flexible button widths, or a collapsed navigation pattern instead of clipping.

• Layout breakage

  Fail76visual

  Localized pages should not overlap, break grids, or overflow modals.

  • infovisual · 60% confidence

    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.

    Found here

    Page shell and featured sections · <header>, <section>

    https://www.atlassian.com/

    What we saw

    The samples expose the same broad page structure: navigation, featured apps, Atlassian Collections, use-case, and team sections across English, Japanese, and French.

    How to fix it

    Capture localized screenshots and test grids, menus, and dialogs at representative desktop and mobile widths.

• Responsive localisation

  Fail74visual

  Localized layouts should hold up across mobile, tablet, and desktop widths.

  • mediumvisual · 58% confidence

    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.

    What we saw

    The supplied preview lists page URLs and extracted text only; it contains no viewport dimensions or responsive layout results.

    How to fix it

    Perform responsive checks for every supported locale, prioritizing long labels such as "Professionnels de l'informatique" and translated header navigation.