Hyperlocalise 徽标
申请演示

本地化报告

Figma

Design and collaboration software

figma.com

Product: 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视觉审计
Audited: 8/15/2026Scope: 公开智能示例 · 技术、语言、上下文和视觉鸣谢Confidence: 来自抽样页面的指示性健康检查结果 — 并非完整的网站爬取。

在技术、语言、上下文和视觉本地化方面抽样检查了 15 个页面。 我们如何评估本地化审核

你的比较情况

在 22 个公开审计中排名第 #10

受审核域名中排名前 59%公开平均分：68/100
查看完整排行榜

首先修复

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

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

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

审核标准

5 项通过 · 26 项待修复 · 4 不适用

需要注意（26）

  • Locale detection

    Fail82technical

    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.

  • Language switcher

    Fail58technical

    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.

  • Sitemap

    Fail88technical

    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.

  • Structured data

    Fail0technical

    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

    Fail50technical

    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.

  • Accessibility localisation

    Fail78technical

    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

    Fail82linguistic

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

  • Terminology consistency

    Fail40linguistic

    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

    Fail72linguistic

    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

    Fail70linguistic

    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.

  • Brand voice

    Fail83linguistic

    Localized copy should preserve the intended tone of the source.

  • Grammar and style

    Fail76linguistic

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

  • CTA intent

    Fail72contextual

    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

    Fail55contextual

    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.

  • UI context

    Fail76contextual

    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

    Fail82contextual

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

  • Contextual meaning

    Fail78contextual

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

  • Audience context

    Fail82contextual

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

  • Text expansion

    Fail40visual

    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

    Fail62visual

    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

    Fail50visual

    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

    Fail55visual

    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

    Fail70visual

    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

    Fail68visual

    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

    Fail68visual

    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

    Fail68visual

    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.

已通过的审核（5）

不适用（4）

检测到的语言区域

ai (url_prefix)de-de (url_prefix)en (html_lang)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_prefix)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_prefix)hi-in (url_prefix)id-id (url_prefix)it-it (url_prefix)ja-jp (url_prefix)ko-kr (url_prefix)nl-nl (url_prefix)pl-pl (url_prefix)pt-br (hreflang)th-th (url_prefix)

完整发现

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

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

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

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

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

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

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

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

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

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

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

  • 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".

  • 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".

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

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

  • 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”.

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

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

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

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

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

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

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

抽样页面

  • 200 · https://www.figma.com/ · lang=en
  • 200 · https://www.figma.com/de-de/ · lang=de
  • 200 · https://www.figma.com/es-es/ · lang=es-es
  • 200 · https://www.figma.com/es-la/ · lang=es
  • 200 · https://www.figma.com/fr-fr/ · lang=fr
  • 200 · https://www.figma.com/hi-in/ · lang=hi
  • 200 · https://www.figma.com/id-id/ · lang=id
  • 200 · https://www.figma.com/it-it/ · lang=it
  • 200 · https://www.figma.com/ja-jp/ · lang=ja
  • 200 · https://www.figma.com/ko-kr/ · lang=ko
  • 200 · https://www.figma.com/nl-nl/ · lang=nl
  • 200 · https://www.figma.com/pl-pl/ · lang=pl
  • 200 · https://www.figma.com/pt-br/ · lang=pt-BR
  • 200 · https://www.figma.com/th-th/ · lang=th
  • 200 · https://www.figma.com/ai/ · lang=en

将摘要发送到我的邮箱

可选。输入您的工作邮箱，我们将向您发送这份公开报告的简明摘要。

下一步

基础扎实，但仍有提升空间。创建一个工作区以持续监控本地化状态，或预约审核。

预约审核评估