Rapport de localisation

Figma

Design and collaboration software

figma.com

Produit: 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.

Voix de marque: collaborative, creative, product-focused

Score de localisation

71/100

À améliorer

Les utilisateurs peuvent rencontrer des problèmes de localisation perceptibles.

76Audit technique
71Audit linguistique
74Audit contextuel
64Audit visuel

Audité: 8/15/2026Portée: Échantillon intelligent public · crédits techniques, linguistiques, contextuels et visuelsConfiance: Contrôle indicatif de l’état de santé à partir de pages échantillonnées — il ne s’agit pas d’une exploration complète du site.

15 pages échantillonnées parmi les crédits de localisation techniques, linguistiques, contextuels et visuels. Comment nous évaluons les audits de localisation

Comment vous vous comparez

Rang #10 sur 22 audits publics

Top 59 % des domaines auditésMoyenne publique : 68/100

Voir le classement complet

À corriger en priorité

hightechnical · 95 % de confiance
URL locale and html lang disagree
Path locale ai expects html lang ai, but the page declares en.
Trouvé ici
Document head · <html lang>
https://www.figma.com/ai/
Ce que nous avons constaté
<html lang="en"> while the path locale is ai
Comment le corriger
Set html lang="ai" so it matches this page’s URL locale.
hightechnical · 95 % de confiance
Language links return to the homepage
Locale links were found, but they appear to drop the current page path.
Trouvé ici
Header · <nav> language links
https://www.figma.com/
Ce que nous avons constaté
<a href="https://www.figma.com/ai/">AI workflows</a> drops the current page path
Comment le corriger
Point language-switcher links at the equivalent localized path, not the locale homepage.
highlinguistic · 92 % de confiance
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
Trouvé ici
Pricing hero · <button>
https://www.figma.com/de-de/
Ce que nous avons constaté
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/
Comment le corriger
Translate leftover source-language CTAs to match the surrounding locale copy.

Critères d’audit

5 réussis · 26 à corriger · 4 non applicable

À examiner (26)

Locale detection
Échec82technique
Pages should declare a correct html lang that matches the URL and content locale.
- hightechnical · 95 % de confiance
  URL locale and html lang disagree
  Path locale ai expects html lang ai, but the page declares en.
  Trouvé ici
  Document head · <html lang>
  https://www.figma.com/ai/
  Ce que nous avons constaté
  <html lang="en"> while the path locale is ai
  Comment le corriger
  Set html lang="ai" so it matches this page’s URL locale.
Language switcher
Échec58technique
Visitors should move between locales without losing the current page.
- hightechnical · 95 % de confiance
  Language links return to the homepage
  Locale links were found, but they appear to drop the current page path.
  Trouvé ici
  Header · <nav> language links
  https://www.figma.com/
  Ce que nous avons constaté
  <a href="https://www.figma.com/ai/">AI workflows</a> drops the current page path
  Comment le corriger
  Point language-switcher links at the equivalent localized path, not the locale homepage.
Sitemap
Échec88technique
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 % de confiance
  Sitemap omits some published locales
  Locale-prefixed pages for ai do not appear in sampled sitemap URLs.
  Trouvé ici
  Sitemap · sitemap.xml
  https://www.figma.com/sitemap.xml
  Ce que nous avons constaté
  Sitemap locales in sample: id, de, es, fr, it, nl, pl, pt, hi, ja, ko, th; missing: ai
  Comment le corriger
  Include URLs for every published locale prefix in the sitemap.
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.figma.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 · 42 % de confiance
  Locale-sensitive values are not shown
  The provided evidence contains no dates, numbers, currencies, or calendar values, so international formatting cannot be verified.
  Ce que nous avons constaté
  The preview shows page titles, buttons, headings, and cookie text, but no dates, numbers, currency amounts, or calendar values.
  Comment le corriger
  Audit representative localized pages for date, number, currency, digit, and calendar formatting.
Accessibility localisation
Échec78technique
lang, aria-label, and alt text should match the page locale.
- infotechnical · 82 % de confiance
  Page language metadata matches sampled locales
  The sampled German and Spanish pages expose matching htmlLang values, supporting correct language metadata.
  Trouvé ici
  Document root · <html>
  https://www.figma.com/de-de/
  Ce que nous avons constaté
  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
Échec82linguistique
Localized pages should not leave source-language copy in place, except brand names and URLs.
- highlinguistic · 92 % de confiance
  Untranslated call to action
  A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
  Trouvé ici
  Pricing hero · <button>
  https://www.figma.com/de-de/
  Ce que nous avons constaté
  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/
  Comment le corriger
  Translate leftover source-language CTAs to match the surrounding locale copy.
- infolinguistic · 84 % de confiance
  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.
  Trouvé ici
  Header · <nav>
  https://www.figma.com/de-de/
  Ce que nous avons constaté
  German buttons: "Produkte","Lösungen","Community","Ressourcen"; Spanish buttons: "Productos","Soluciones","Comunidad","Recursos".
Terminology consistency
Échec40linguistique
Important concepts should not be translated differently across pages.
- mediumlinguistic · 95 % de confiance
  Terminology inconsistency
  "Figma Socials" appears both untranslated and translated across de pages. Affects 11 sampled pages.
  Trouvé ici
  Header · <nav> or <button>
  https://www.figma.com/de-de/
  Ce que nous avons constaté
  "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/
  Comment le corriger
  Use one translated label for "Figma Socials" across de pages.
Translation accuracy
Échec72linguistique
Target copy should preserve the source meaning, numbers, and product actions.
- mediumlinguistic · 67 % de confiance
  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.
  Trouvé ici
  Privacy controls · <button>
  https://www.figma.com/de-de/
  Ce que nous avons constaté
  English: "Opt-Out"; German: "Ausschluss"; German longer label: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
  Comment le corriger
  Use established German consent terminology such as “Ablehnen” or “Opt-out” consistently, and validate it with German legal and UX reviewers.
Fluency
Échec70linguistique
Copy should sound natural, without grammar issues or machine-translation artifacts.
- mediumlinguistic · 73 % de confiance
  German privacy copy reads awkwardly
  The sampled German cookie notice contains an unnatural construction around selling and distributing behavioral advertising.
  Trouvé ici
  Cookie notice · <p>
  https://www.figma.com/de-de/
  Ce que nous avons constaté
  "Wir nutzen Cookies für Verkaufszwecke und Verteilung der verhaltensgebundenen Werbung oder für zielgerichtete Werbung."
  Comment le corriger
  Rewrite the sentence in idiomatic German and have a native copy editor review the full privacy notice.
Brand voice
Échec83linguistique
Localized copy should preserve the intended tone of the source.
Grammar and style
Échec76linguistique
Locale-specific capitalization, punctuation, formality, and agreement should be correct.
- lowlinguistic · 70 % de confiance
  German terminology and capitalization need review
  The privacy notice uses awkward nominal phrasing and borrowed terminology that may not align with polished German style.
  Trouvé ici
  Cookie notice · <p>
  https://www.figma.com/de-de/
  Ce que nous avons constaté
  "Diese Website verwendet Cookies, Zählpixel und lokale Speicherung zu Performance-, Personalisierungs- und Marketingzwecken."
  Comment le corriger
  Review the sentence for idiomatic German, including terminology such as “Performance” and the construction after “Speicherung”.
CTA intent
Échec72contextuel
Localized calls to action should communicate the intended product action.
- mediumcontextual · 76 % de confiance
  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.
  Trouvé ici
  Privacy controls · <button>
  https://www.figma.com/de-de/
  Ce que nous avons constaté
  Source button: "Opt-Out"; German button: "Ausschluss"; German extended button: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
  Comment le corriger
  Replace “Ausschluss” with a clear action-oriented German label that explicitly conveys opting out of sale or sharing.
Cultural adaptation
Échec55contextuel
Currency, dates, addresses, and local examples should fit the market.
- infocontextual · 45 % de confiance
  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.
  Ce que nous avons constaté
  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.
  Comment le corriger
  Review regional pages for market-appropriate formats, terminology, examples, and legal or privacy language.
UI context
Échec76contextuel
Translations should fit the UI component: button, nav, form, modal, or error.
- mediumcontextual · 70 % de confiance
  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.
  Trouvé ici
  Privacy controls · <button>
  https://www.figma.com/de-de/
  Ce que nous avons constaté
  German buttons include "Ausschluss" and "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
  Comment le corriger
  Use a concise, recognizable consent action in the button and keep the longer explanation in supporting text or an accessible label.
Product context
Échec82contextuel
Language should match product concepts such as plans, settings, and workflows.
Contextual meaning
Échec78contextuel
Strings should be judged in surrounding page and component context, not in isolation.
Audience context
Échec82contextuel
Language should fit the intended audience, such as consumer, enterprise, or developer.
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 de string is 167% the length of the source, which often causes overflow. Affects 26 sampled pages.
  Trouvé ici
  Heading · heading
  https://www.figma.com/de-de/
  Ce que nous avons constaté
  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/
  Comment le corriger
  Shorten the translation or give the control more room so the longer copy does not overflow.
Font and script support
Échec62visuel
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-jp page shows CJK text but the embedded/inline font stack has no known CJK typeface. Affects 2 sampled pages.
  Trouvé ici
  Page body · font-family
  https://www.figma.com/ja-jp/
  Ce que nous avons constaté
  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/
  Comment le corriger
  Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
Localized images and assets
Échec50visuel
Language-specific images and alt text should match the page locale.
- infovisual · 35 % de confiance
  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.
  Ce que nous avons constaté
  The provided page preview lists titles, buttons, headings, and text, but contains no <img> markup or alt-text values.
  Comment le corriger
  Inspect localized pages for image sources, embedded text, and alt attributes, then verify that language-specific assets and descriptions match each locale.
Visual hierarchy
Échec55visuel
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. Affects 6 sampled pages.
  Trouvé ici
  Page body · heading
  https://www.figma.com/de-de/
  Ce que nous avons constaté
  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/
  Comment le corriger
  Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
Échec70visuel
Repeated components should stay visually consistent across locales.
- lowvisual · 95 % de confiance
  Repeated components differ across locales
  Button counts differ between the source locale and ai.
  Trouvé ici
  Page body · <button>
  https://www.figma.com/ai/
  Ce que nous avons constaté
  Source locale has 7 buttons; ai has 13.
  Comment le corriger
  Keep the same repeated controls across locales, or drop unused ones on purpose.
Text overflow
Échec68visuel
Text should not clip, truncate unexpectedly, or overflow buttons and navigation.
- lowvisual · 62 % de confiance
  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.
  Trouvé ici
  Privacy controls · <button>
  https://www.figma.com/de-de/
  Ce que nous avons constaté
  "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" versus the English "Do Not Sell/Share My Personal Info + Opt-Out".
  Comment le corriger
  Test the label at mobile and desktop widths; allow wrapping or expand the control instead of clipping or truncating text.
Layout breakage
Échec68visuel
Localized pages should not overlap, break grids, or overflow modals.
- lowvisual · 60 % de confiance
  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.
  Trouvé ici
  Privacy controls · <button>
  https://www.figma.com/de-de/
  Ce que nous avons constaté
  "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" is shown as a button label.
  Comment le corriger
  Check the privacy control and any consent modal at narrow widths, and support flexible button sizing and wrapping.
Responsive localisation
Échec68visuel
Localized layouts should hold up across mobile, tablet, and desktop widths.
- infovisual · 58 % de confiance
  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.
  Trouvé ici
  Privacy controls · <button>
  https://www.figma.com/de-de/
  Ce que nous avons constaté
  The evidence shows the long German label "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" but no viewport or layout output.
  Comment le corriger
  Run mobile, tablet, and desktop visual checks for all locales with long navigation and privacy labels.

Audits réussis (5)

Non applicable (4)

Paramètres régionaux détectés

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)

Résultats complets

hightechnical · 95 % de confiance
URL locale and html lang disagree
Path locale ai expects html lang ai, but the page declares en.
Trouvé ici
Document head · <html lang>
https://www.figma.com/ai/
Ce que nous avons constaté
<html lang="en"> while the path locale is ai
Comment le corriger
Set html lang="ai" so it matches this page’s URL locale.
hightechnical · 95 % de confiance
Language links return to the homepage
Locale links were found, but they appear to drop the current page path.
Trouvé ici
Header · <nav> language links
https://www.figma.com/
Ce que nous avons constaté
<a href="https://www.figma.com/ai/">AI workflows</a> drops the current page path
Comment le corriger
Point language-switcher links at the equivalent localized path, not the locale homepage.
mediumtechnical · 88 % de confiance
Sitemap omits some published locales
Locale-prefixed pages for ai do not appear in sampled sitemap URLs.
Trouvé ici
Sitemap · sitemap.xml
https://www.figma.com/sitemap.xml
Ce que nous avons constaté
Sitemap locales in sample: id, de, es, fr, it, nl, pl, pt, hi, ja, ko, th; missing: ai
Comment le corriger
Include URLs for every published locale prefix in the sitemap.
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.figma.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.
highlinguistic · 92 % de confiance
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
Trouvé ici
Pricing hero · <button>
https://www.figma.com/de-de/
Ce que nous avons constaté
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/
Comment le corriger
Translate leftover source-language CTAs to match the surrounding locale copy.
mediumlinguistic · 95 % de confiance
Terminology inconsistency
"Figma Socials" appears both untranslated and translated across de pages. Affects 11 sampled pages.
Trouvé ici
Header · <nav> or <button>
https://www.figma.com/de-de/
Ce que nous avons constaté
"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/
Comment le corriger
Use one translated label for "Figma Socials" across de pages.
mediumvisual · 88 % de confiance
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.
Trouvé ici
Heading · heading
https://www.figma.com/de-de/
Ce que nous avons constaté
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/
Comment le corriger
Shorten the translation or give the control more room so the longer copy does not overflow.
highvisual · 95 % de confiance
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.
Trouvé ici
Page body · font-family
https://www.figma.com/ja-jp/
Ce que nous avons constaté
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/
Comment le corriger
Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
lowvisual · 80 % de confiance
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 6 sampled pages.
Trouvé ici
Page body · heading
https://www.figma.com/de-de/
Ce que nous avons constaté
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/
Comment le corriger
Shorten the heading so it does not crowd the visual hierarchy.
lowvisual · 95 % de confiance
Repeated components differ across locales
Button counts differ between the source locale and ai.
Trouvé ici
Page body · <button>
https://www.figma.com/ai/
Ce que nous avons constaté
Source locale has 7 buttons; ai has 13.
Comment le corriger
Keep the same repeated controls across locales, or drop unused ones on purpose.
infotechnical · 42 % de confiance
Locale-sensitive values are not shown
The provided evidence contains no dates, numbers, currencies, or calendar values, so international formatting cannot be verified.
Ce que nous avons constaté
The preview shows page titles, buttons, headings, and cookie text, but no dates, numbers, currency amounts, or calendar values.
Comment le corriger
Audit representative localized pages for date, number, currency, digit, and calendar formatting.
infotechnical · 82 % de confiance
Page language metadata matches sampled locales
The sampled German and Spanish pages expose matching htmlLang values, supporting correct language metadata.
Trouvé ici
Document root · <html>
https://www.figma.com/de-de/
Ce que nous avons constaté
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 % de confiance
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.
Trouvé ici
Header · <nav>
https://www.figma.com/de-de/
Ce que nous avons constaté
German buttons: "Produkte","Lösungen","Community","Ressourcen"; Spanish buttons: "Productos","Soluciones","Comunidad","Recursos".
mediumlinguistic · 67 % de confiance
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.
Trouvé ici
Privacy controls · <button>
https://www.figma.com/de-de/
Ce que nous avons constaté
English: "Opt-Out"; German: "Ausschluss"; German longer label: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
Comment le corriger
Use established German consent terminology such as “Ablehnen” or “Opt-out” consistently, and validate it with German legal and UX reviewers.
mediumlinguistic · 73 % de confiance
German privacy copy reads awkwardly
The sampled German cookie notice contains an unnatural construction around selling and distributing behavioral advertising.
Trouvé ici
Cookie notice · <p>
https://www.figma.com/de-de/
Ce que nous avons constaté
"Wir nutzen Cookies für Verkaufszwecke und Verteilung der verhaltensgebundenen Werbung oder für zielgerichtete Werbung."
Comment le corriger
Rewrite the sentence in idiomatic German and have a native copy editor review the full privacy notice.
lowlinguistic · 70 % de confiance
German terminology and capitalization need review
The privacy notice uses awkward nominal phrasing and borrowed terminology that may not align with polished German style.
Trouvé ici
Cookie notice · <p>
https://www.figma.com/de-de/
Ce que nous avons constaté
"Diese Website verwendet Cookies, Zählpixel und lokale Speicherung zu Performance-, Personalisierungs- und Marketingzwecken."
Comment le corriger
Review the sentence for idiomatic German, including terminology such as “Performance” and the construction after “Speicherung”.
mediumcontextual · 76 % de confiance
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.
Trouvé ici
Privacy controls · <button>
https://www.figma.com/de-de/
Ce que nous avons constaté
Source button: "Opt-Out"; German button: "Ausschluss"; German extended button: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
Comment le corriger
Replace “Ausschluss” with a clear action-oriented German label that explicitly conveys opting out of sale or sharing.
infocontextual · 45 % de confiance
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.
Ce que nous avons constaté
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.
Comment le corriger
Review regional pages for market-appropriate formats, terminology, examples, and legal or privacy language.
mediumcontextual · 70 % de confiance
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.
Trouvé ici
Privacy controls · <button>
https://www.figma.com/de-de/
Ce que nous avons constaté
German buttons include "Ausschluss" and "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
Comment le corriger
Use a concise, recognizable consent action in the button and keep the longer explanation in supporting text or an accessible label.
infovisual · 35 % de confiance
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.
Ce que nous avons constaté
The provided page preview lists titles, buttons, headings, and text, but contains no <img> markup or alt-text values.
Comment le corriger
Inspect localized pages for image sources, embedded text, and alt attributes, then verify that language-specific assets and descriptions match each locale.
lowvisual · 62 % de confiance
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.
Trouvé ici
Privacy controls · <button>
https://www.figma.com/de-de/
Ce que nous avons constaté
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" versus the English "Do Not Sell/Share My Personal Info + Opt-Out".
Comment le corriger
Test the label at mobile and desktop widths; allow wrapping or expand the control instead of clipping or truncating text.
lowvisual · 60 % de confiance
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.
Trouvé ici
Privacy controls · <button>
https://www.figma.com/de-de/
Ce que nous avons constaté
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" is shown as a button label.
Comment le corriger
Check the privacy control and any consent modal at narrow widths, and support flexible button sizing and wrapping.
infovisual · 58 % de confiance
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.
Trouvé ici
Privacy controls · <button>
https://www.figma.com/de-de/
Ce que nous avons constaté
The evidence shows the long German label "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" but no viewport or layout output.
Comment le corriger
Run mobile, tablet, and desktop visual checks for all locales with long navigation and privacy labels.

Pages échantillonnées

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

Envoyez-moi un récapitulatif par e-mail

Facultatif. Saisissez votre adresse e-mail professionnelle et nous vous enverrons un résumé concis de ce rapport public.

Étape suivante

Bonne base, avec une marge d’amélioration. Créez un espace de travail pour un suivi continu de la localisation, ou réservez une revue d’audit.

Réserver un examen d’audit