Atlassian

À examiner (27)

• Language switcher

  Échec65technique

  Visitors should move between locales without losing the current page.

  • mediumtechnical · 82 % de confiance

    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.

    Trouvé ici

    https://www.atlassian.com/

    Ce que nous avons constaté

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

    Comment le corriger

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

• hreflang

  Échec20technique

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

  • mediumtechnical · 95 % de confiance

    Missing hreflang self-reference

    The page lists hreflang alternates but does not include itself.

    Trouvé ici

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

    https://www.atlassian.com/

    Ce que nous avons constaté

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

    Comment le corriger

    Add a self-referencing hreflang alternate for this page.

  • lowtechnical · 95 % de confiance

    Missing x-default hreflang

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

    Trouvé ici

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

    https://www.atlassian.com/

    Ce que nous avons constaté

    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/

    Comment le corriger

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

• Localized SEO metadata

  Échec65technique

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

  • mediumtechnical · 95 % de confiance

    Page titles are not localized

    Sampled locales share the same document title.

    Trouvé ici

    Document head · <title>

    https://www.atlassian.com/

    Ce que nous avons constaté

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

    Comment le corriger

    Localize the document title for each page locale.

• Sitemap

  Échec60technique

  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 % de confiance

    Sitemap is missing localized URLs

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

    Trouvé ici

    Sitemap · sitemap.xml

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

    Ce que nous avons constaté

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

    Comment le corriger

    Include localized URLs in the sitemap for every published locale.

• Structured data

  Échec0technique

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

  • lowtechnical · 95 % de confiance

    Structured data omits inLanguage

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

    Trouvé ici

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

    https://www.atlassian.com/

    Ce que nous avons constaté

    Organization is present but inLanguage is missing

    Comment le corriger

    Set JSON-LD inLanguage to match each page locale.

• International formatting

  Échec50technique

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

  • infotechnical · 90 % de confiance

    Formatting coverage cannot be verified

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

    Ce que nous avons constaté

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

    Comment le corriger

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

• Accessibility localisation

  Échec72technique

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

  • infotechnical · 88 % de confiance

    Document language is localized

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

    Trouvé ici

    Document root · <html>

    https://www.atlassian.com/

    Ce que nous avons constaté

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

    Comment le corriger

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

  • mediumtechnical · 88 % de confiance

    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.

    Ce que nous avons constaté

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

    Comment le corriger

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

• Translation completeness

  Échec0linguistique

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

  • highlinguistic · 92 % de confiance

    Untranslated call to action

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

    Trouvé ici

    Pricing hero · <button>

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

    Ce que nous avons constaté

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

    Comment le corriger

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

  • highlinguistic · 95 % de confiance

    Page script does not match the locale

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

    Trouvé ici

    Page body · sampled copy

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

    Ce que nous avons constaté

    ___ 跳至内容 产品 精选 开发人员 产品经理 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/

    Comment le corriger

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

• Terminology consistency

  Échec40linguistique

  Important concepts should not be translated differently across pages.

  • mediumlinguistic · 95 % de confiance

    Terminology inconsistency

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

    Trouvé ici

    Header · <nav> or <button>

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

    Ce que nous avons constaté

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

    Comment le corriger

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

• Translation accuracy

  Échec88linguistique

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

  • infolinguistic · 78 % de confiance

    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.

    Trouvé ici

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

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

    Ce que nous avons constaté

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

• Fluency

  Échec88linguistique

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

  • infolinguistic · 78 % de confiance

    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.

    Trouvé ici

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

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

    Ce que nous avons constaté

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

• Brand voice

  Échec84linguistique

  Localized copy should preserve the intended tone of the source.

  • infolinguistic · 76 % de confiance

    Product-led, concise tone is retained

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

    Trouvé ici

    Featured apps and collections · <section>

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

    Ce que nous avons constaté

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

• Grammar and style

  Échec86linguistique

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

  • infolinguistic · 76 % de confiance

    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.

    Trouvé ici

    Navigation and headings · <nav>, <h2>

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

    Ce que nous avons constaté

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

• Cultural adaptation

  Échec55contextuel

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

  • infocontextual · 88 % de confiance

    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.

    Ce que nous avons constaté

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

    Comment le corriger

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

• UI context

  Échec88contextuel

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

  • infocontextual · 80 % de confiance

    Navigation and heading translations fit their UI roles

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

    Trouvé ici

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

    https://www.atlassian.com/

    Ce que nous avons constaté

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

• Product context

  Échec88contextuel

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

  • infocontextual · 80 % de confiance

    Product terminology remains recognizable and contextualized

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

    Trouvé ici

    Featured apps and collections · <section>

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

    Ce que nous avons constaté

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

    Comment le corriger

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

• Contextual meaning

  Échec86contextuel

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

  • infocontextual · 78 % de confiance

    Strings are supported by surrounding page context

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

    Trouvé ici

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

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

    Ce que nous avons constaté

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

• Audience context

  Échec88contextuel

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

  • infocontextual · 82 % de confiance

    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.

    Trouvé ici

    Primary navigation · <nav>

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

    Ce que nous avons constaté

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

• Text expansion

  Échec40visuel

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

  • mediumvisual · 88 % de confiance

    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.

    Trouvé ici

    Control · <button>

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

    Ce que nous avons constaté

    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/

    Comment le corriger

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

• Font and script support

  Échec48visuel

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

  • highvisual · 95 % de confiance

    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.

    Trouvé ici

    Page body · font-family

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

    Ce que nous avons constaté

    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/

    Comment le corriger

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

• CJK typography

  Échec72visuel

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

  • highvisual · 94 % de confiance

    Korean text uses word-break: break-all

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

    Trouvé ici

    CSS · word-break

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

    Ce que nous avons constaté

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

    Comment le corriger

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

• Localized images and assets

  Échec50visuel

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

  • infovisual · 90 % de confiance

    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.

    Ce que nous avons constaté

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

    Comment le corriger

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

• Visual hierarchy

  Échec76visuel

  Localization should not make headings or CTAs lose scanability.

  • lowvisual · 80 % de confiance

    Heading is excessively long

    A localized heading may crowd the visual hierarchy.

    Trouvé ici

    Page body · heading

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

    Ce que nous avons constaté

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

    Comment le corriger

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

• Component consistency

  Échec78visuel

  Repeated components should stay visually consistent across locales.

  • infovisual · 68 % de confiance

    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.

    Trouvé ici

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

    https://www.atlassian.com/

    Ce que nous avons constaté

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

    Comment le corriger

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

• Text overflow

  Échec74visuel

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

  • mediumvisual · 62 % de confiance

    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.

    Trouvé ici

    Header navigation · <nav>

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

    Ce que nous avons constaté

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

    Comment le corriger

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

• Layout breakage

  Échec76visuel

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

  • infovisual · 60 % de confiance

    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.

    Trouvé ici

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

    https://www.atlassian.com/

    Ce que nous avons constaté

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

    Comment le corriger

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

• Responsive localisation

  Échec74visuel

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

  • mediumvisual · 58 % de confiance

    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.

    Ce que nous avons constaté

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

    Comment le corriger

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