ローカライズレポート

Figma

Design and collaboration software

figma.com

製品: Figma is a collaborative canvas bringing design, code, and AI together, helping teams move from initial ideas to shipped products in one place. Its offerings include design, prototyping, developer handoff, whiteboarding, presentations, and related creative workflows.

ブランドボイス: collaborative, creative, product-focused

ローカライズスコア

71/100

改善が必要

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

76技術監査
71言語監査
74コンテキスト監査
64ビジュアル監査

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

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

他の人との比較

公開監査23件中#14位

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

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

最初に修正する項目

1
high
URL locale and html lang disagree
Path locale ai expects html lang ai, but the page declares en.
See details
2
high
Language links return to the homepage
Locale links were found, but they appear to drop the current page path.
See details
3
high
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
See details

監査基準

5 passed · 10 to watch · 16 to fix · 4 not applicable

要対応 (16)

Language switcher
不合格58技術的
Visitors should move between locales without losing the current page.
- hightechnical · 95% の確信度
  Language links return to the homepage
  Locale links were found, but they appear to drop the current page path.
  こちらで見つかりました
  Header · <nav> language links
  https://www.figma.com/
  確認されたこと
  <a href="https://www.figma.com/ai/">AI workflows</a> drops the current page path
  修正方法
  Point language-switcher links at the equivalent localized path, not the locale homepage.
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.figma.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 · 42% の確信度
  Locale-sensitive values are not shown
  The provided evidence contains no dates, numbers, currencies, or calendar values, so international formatting cannot be verified.
  確認されたこと
  The preview shows page titles, buttons, headings, and cookie text, but no dates, numbers, currency amounts, or calendar values.
  修正方法
  Audit representative localized pages for date, number, currency, digit, and calendar formatting.
Terminology consistency
不合格40言語
Important concepts should not be translated differently across pages.
- mediumlinguistic · 95% の確信度
  Terminology inconsistency
  "Figma Socials" appears both untranslated and translated across de pages. Affects 11 sampled pages.
  こちらで見つかりました
  Header · <nav> or <button>
  https://www.figma.com/de-de/
  確認されたこと
  "Figma Socials" appears untranslated on some de pages and translated on others Seen on 5 pages, e.g. https://www.figma.com/de-de/, https://www.figma.com/fr-fr/, https://www.figma.com/it-it/
  修正方法
  Use one translated label for "Figma Socials" across de pages.
Translation accuracy
不合格72言語
Target copy should preserve the source meaning, numbers, and product actions.
- mediumlinguistic · 67% の確信度
  Opt-out wording may not preserve the source action
  The German translation "Ausschluss" does not clearly communicate the consent-management action expressed by the English "Opt-Out" and may be semantically inaccurate in this UI context.
  こちらで見つかりました
  Privacy controls · <button>
  https://www.figma.com/de-de/
  確認されたこと
  English: "Opt-Out"; German: "Ausschluss"; German longer label: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
  修正方法
  Use established German consent terminology such as “Ablehnen” or “Opt-out” consistently, and validate it with German legal and UX reviewers.
Fluency
不合格70言語
Copy should sound natural, without grammar issues or machine-translation artifacts.
- mediumlinguistic · 73% の確信度
  German privacy copy reads awkwardly
  The sampled German cookie notice contains an unnatural construction around selling and distributing behavioral advertising.
  こちらで見つかりました
  Cookie notice · <p>
  https://www.figma.com/de-de/
  確認されたこと
  "Wir nutzen Cookies für Verkaufszwecke und Verteilung der verhaltensgebundenen Werbung oder für zielgerichtete Werbung."
  修正方法
  Rewrite the sentence in idiomatic German and have a native copy editor review the full privacy notice.
CTA intent
不合格72文脈に即した
Localized calls to action should communicate the intended product action.
- mediumcontextual · 76% の確信度
  German opt-out CTA is ambiguous
  The German CTA "Ausschluss" does not clearly tell users that they can opt out of selling or sharing personal information.
  こちらで見つかりました
  Privacy controls · <button>
  https://www.figma.com/de-de/
  確認されたこと
  Source button: "Opt-Out"; German button: "Ausschluss"; German extended button: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
  修正方法
  Replace “Ausschluss” with a clear action-oriented German label that explicitly conveys opting out of sale or sharing.
Cultural adaptation
不合格55文脈に即した
Currency, dates, addresses, and local examples should fit the market.
- infocontextual · 45% の確信度
  Market-specific adaptation is not evidenced
  The preview identifies many regional Spanish locales but does not show localized currencies, dates, addresses, examples, or market-specific content.
  確認されたこと
  The locale list includes regional variants such as "es-ar", "es-mx", and "es-es", while the visible page evidence contains only general product and privacy copy.
  修正方法
  Review regional pages for market-appropriate formats, terminology, examples, and legal or privacy language.
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 de string is 167% the length of the source, which often causes overflow. Affects 26 sampled pages.
  こちらで見つかりました
  Heading · heading
  https://www.figma.com/de-de/
  確認されたこと
  EN "Use cases" → DE "Anwendungsfälle" (167%) Seen on 9 pages, e.g. https://www.figma.com/de-de/, https://www.figma.com/es-es/, https://www.figma.com/es-la/
  修正方法
  Shorten the translation or give the control more room so the longer copy does not overflow.
Font and script support
不合格62視覚的
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-jp page shows CJK text but the embedded/inline font stack has no known CJK typeface. Affects 2 sampled pages.
  こちらで見つかりました
  Page body · font-family
  https://www.figma.com/ja-jp/
  確認されたこと
  font-family: monospace, inherit, var(--global-font-sans, var(--global-font-mono Seen on 2 pages, e.g. https://www.figma.com/ja-jp/, https://www.figma.com/ko-kr/
  修正方法
  Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
Localized images and assets
不合格50視覚的
Language-specific images and alt text should match the page locale.
- infovisual · 35% の確信度
  Images and alt text are not included in the evidence
  The preview provides no image elements, asset references, or alt text, so localized visual assets cannot be verified.
  確認されたこと
  The provided page preview lists titles, buttons, headings, and text, but contains no <img> markup or alt-text values.
  修正方法
  Inspect localized pages for image sources, embedded text, and alt attributes, then verify that language-specific assets and descriptions match each locale.
Visual hierarchy
不合格55視覚的
Localization should not make headings or CTAs lose scanability.
- lowvisual · 80% の確信度
  Heading is excessively long
  A localized heading may crowd the visual hierarchy. Affects 6 sampled pages.
  こちらで見つかりました
  Page body · heading
  https://www.figma.com/de-de/
  確認されたこと
  Mache rasch Fortschritte in die richtige Richtung auf einer KI-nativen Arbeitsfläche. Seen on 5 pages, e.g. https://www.figma.com/de-de/, https://www.figma.com/fr-fr/, https://www.figma.com/id-id/
  修正方法
  Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
不合格70視覚的
Repeated components should stay visually consistent across locales.
- lowvisual · 95% の確信度
  Repeated components differ across locales
  Button counts differ between the source locale and ai.
  こちらで見つかりました
  Page body · <button>
  https://www.figma.com/ai/
  確認されたこと
  Source locale has 7 buttons; ai has 13.
  修正方法
  Keep the same repeated controls across locales, or drop unused ones on purpose.
Text overflow
不合格68視覚的
Text should not clip, truncate unexpectedly, or overflow buttons and navigation.
- lowvisual · 62% の確信度
  Long localized privacy labels may require overflow testing
  The extended German privacy button is substantially longer than the English source and could stress fixed-width controls; no screenshot or layout measurements are provided.
  こちらで見つかりました
  Privacy controls · <button>
  https://www.figma.com/de-de/
  確認されたこと
  "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" versus the English "Do Not Sell/Share My Personal Info + Opt-Out".
  修正方法
  Test the label at mobile and desktop widths; allow wrapping or expand the control instead of clipping or truncating text.
Layout breakage
不合格68視覚的
Localized pages should not overlap, break grids, or overflow modals.
- lowvisual · 60% の確信度
  Long privacy CTA warrants layout testing
  The longer German privacy control may affect button width or modal layout, but the evidence contains no visual capture confirming a breakage.
  こちらで見つかりました
  Privacy controls · <button>
  https://www.figma.com/de-de/
  確認されたこと
  "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" is shown as a button label.
  修正方法
  Check the privacy control and any consent modal at narrow widths, and support flexible button sizing and wrapping.
Responsive localisation
不合格68視覚的
Localized layouts should hold up across mobile, tablet, and desktop widths.
- infovisual · 58% の確信度
  Responsive behavior is not directly evidenced
  The preview contains no screenshots, viewport measurements, or responsive DOM details; the longer localized CTA should therefore be treated as a test risk rather than a confirmed defect.
  こちらで見つかりました
  Privacy controls · <button>
  https://www.figma.com/de-de/
  確認されたこと
  The evidence shows the long German label "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" but no viewport or layout output.
  修正方法
  Run mobile, tablet, and desktop visual checks for all locales with long navigation and privacy labels.

Worth a look (10)

Locale detection
Watch82技術的
Pages should declare a correct html lang that matches the URL and content locale.
- hightechnical · 95% の確信度
  URL locale and html lang disagree
  Path locale ai expects html lang ai, but the page declares en.
  こちらで見つかりました
  Document head · <html lang>
  https://www.figma.com/ai/
  確認されたこと
  <html lang="en"> while the path locale is ai
  修正方法
  Set html lang="ai" so it matches this page’s URL locale.
Sitemap
Watch88技術的
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 · 88% の確信度
  Sitemap omits some published locales
  Locale-prefixed pages for ai do not appear in sampled sitemap URLs.
  こちらで見つかりました
  Sitemap · sitemap.xml
  https://www.figma.com/sitemap.xml
  確認されたこと
  Sitemap locales in sample: id, de, es, fr, it, nl, pl, pt, hi, ja, ko, th; missing: ai
  修正方法
  Include URLs for every published locale prefix in the sitemap.
Accessibility localisation
Watch78技術的
lang, aria-label, and alt text should match the page locale.
- infotechnical · 82% の確信度
  Page language metadata matches sampled locales
  The sampled German and Spanish pages expose matching htmlLang values, supporting correct language metadata.
  こちらで見つかりました
  Document root · <html>
  https://www.figma.com/de-de/
  確認されたこと
  German page: "htmlLang":"de" with title "Figma: kollaborative Arbeitsfläche für Design, Code und KI"; Spanish page: "htmlLang":"es-es" with title "Figma: El lienzo colaborativo para diseño, código e IA".
Translation completeness
Watch82言語
Localized pages should not leave source-language copy in place, except brand names and URLs.
- highlinguistic · 92% の確信度
  Untranslated call to action
  A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
  こちらで見つかりました
  Pricing hero · <button>
  https://www.figma.com/de-de/
  確認されたこと
  Primary CTA: "Community" Seen on 10 pages, e.g. https://www.figma.com/de-de/, https://www.figma.com/es-es/, https://www.figma.com/es-la/
  修正方法
  Translate leftover source-language CTAs to match the surrounding locale copy.
- infolinguistic · 84% の確信度
  Sampled navigation and headings are localized
  The German and Spanish samples translate page titles, navigation labels, and headings rather than retaining the English source copy.
  こちらで見つかりました
  Header · <nav>
  https://www.figma.com/de-de/
  確認されたこと
  German buttons: "Produkte","Lösungen","Community","Ressourcen"; Spanish buttons: "Productos","Soluciones","Comunidad","Recursos".
Brand voice
Watch83言語
Localized copy should preserve the intended tone of the source.
Grammar and style
Watch76言語
Locale-specific capitalization, punctuation, formality, and agreement should be correct.
- lowlinguistic · 70% の確信度
  German terminology and capitalization need review
  The privacy notice uses awkward nominal phrasing and borrowed terminology that may not align with polished German style.
  こちらで見つかりました
  Cookie notice · <p>
  https://www.figma.com/de-de/
  確認されたこと
  "Diese Website verwendet Cookies, Zählpixel und lokale Speicherung zu Performance-, Personalisierungs- und Marketingzwecken."
  修正方法
  Review the sentence for idiomatic German, including terminology such as “Performance” and the construction after “Speicherung”.
UI context
Watch76文脈に即した
Translations should fit the UI component: button, nav, form, modal, or error.
- mediumcontextual · 70% の確信度
  Privacy CTA context is unclear in German
  The short label "Ausschluss" is difficult to interpret as a button action, especially when paired with a longer personal-data opt-out label.
  こちらで見つかりました
  Privacy controls · <button>
  https://www.figma.com/de-de/
  確認されたこと
  German buttons include "Ausschluss" and "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
  修正方法
  Use a concise, recognizable consent action in the button and keep the longer explanation in supporting text or an accessible label.
Product context
Watch82文脈に即した
Language should match product concepts such as plans, settings, and workflows.
Contextual meaning
Watch78文脈に即した
Strings should be judged in surrounding page and component context, not in isolation.
Audience context
Watch82文脈に即した
Language should fit the intended audience, such as consumer, enterprise, or developer.

合格した監査項目 (5)

該当なし（4）

検出されたロケール

ai
URL path
ドイツ語 (ドイツ)
de-de · URL path
英語
en · page language
スペイン語 (アルゼンチン)
es-ar · hreflang
スペイン語 (ボリビア)
es-bo · hreflang
スペイン語 (チリ)
es-cl · hreflang
スペイン語 (コロンビア)
es-co · hreflang
スペイン語 (コスタリカ)
es-cr · hreflang
スペイン語 (キューバ)
es-cu · hreflang
スペイン語 (ドミニカ共和国)
es-do · hreflang
スペイン語 (エクアドル)
es-ec · hreflang
スペイン語 (イベリア半島)
es-es · hreflang
スペイン語 (グアテマラ)
es-gt · hreflang
スペイン語 (ホンジュラス)
es-hn · hreflang
スペイン語 (ラオス)
es-la · URL path
スペイン語 (メキシコ)
es-mx · hreflang
スペイン語 (ニカラグア)
es-ni · hreflang
スペイン語 (パナマ)
es-pa · hreflang
スペイン語 (ペルー)
es-pe · hreflang
スペイン語 (プエルトリコ)
es-pr · hreflang
スペイン語 (パラグアイ)
es-py · hreflang
スペイン語 (エルサルバドル)
es-sv · hreflang
スペイン語 (ウルグアイ)
es-uy · hreflang
スペイン語 (ベネズエラ)
es-ve · hreflang
フランス語 (フランス)
fr-fr · URL path
ヒンディー語 (インド)
hi-in · URL path
インドネシア語 (インドネシア)
id-id · URL path
イタリア語 (イタリア)
it-it · URL path
日本語 (日本)
ja-jp · URL path
韓国語 (韓国)
ko-kr · URL path
オランダ語 (オランダ)
nl-nl · URL path
ポーランド語 (ポーランド)
pl-pl · URL path
ポルトガル語 (ブラジル)
pt-br · hreflang
タイ語 (タイ)
th-th · URL path

サンプル対象のページ

次のステップ

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.