Lokalisierungsbericht
Figma
Design and collaboration softwarefigma.com
Produkt: 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.
Markenstimme: collaborative, creative, product-focused
Lokalisierungsbewertung
71/100
VerbesserungsbedarfNutzer können auf auffällige Lokalisierungsprobleme stoßen.
- 76Technische Prüfung
- 71Sprachprüfung
- 74Kontextbezogene Prüfung
- 64Visuelle Prüfung
Es wurden 15 Seiten aus den Bereichen technische, sprachliche, kontextuelle und visuelle Lokalisierung als Stichprobe untersucht. So bewerten wir Lokalisierungsprüfungen
So schneiden Sie im Vergleich ab
Rang #10 von 22 öffentlichen Audits
Zuerst beheben
- hightechnical · 95% Vertrauen
URL locale and html lang disagree
Path locale ai expects html lang ai, but the page declares en.
Hier gefunden
Document head · <html lang>
https://www.figma.com/ai/Was wir gesehen haben
<html lang="en"> while the path locale is ai
So beheben Sie das
Set html lang="ai" so it matches this page’s URL locale.
- hightechnical · 95% Vertrauen
Language links return to the homepage
Locale links were found, but they appear to drop the current page path.
Hier gefunden
Header · <nav> language links
https://www.figma.com/Was wir gesehen haben
<a href="https://www.figma.com/ai/">AI workflows</a> drops the current page path
So beheben Sie das
Point language-switcher links at the equivalent localized path, not the locale homepage.
- highlinguistic · 92% Vertrauen
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
Hier gefunden
Pricing hero · <button>
https://www.figma.com/de-de/Was wir gesehen haben
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/
So beheben Sie das
Translate leftover source-language CTAs to match the surrounding locale copy.
Prüfkriterien
5 bestanden · 26 zu beheben · 4 nicht zutreffend
Erfordert Aufmerksamkeit (26)
Locale detection
Fehlgeschlagen82technischPages should declare a correct html lang that matches the URL and content locale.
- hightechnical · 95% Vertrauen
URL locale and html lang disagree
Path locale ai expects html lang ai, but the page declares en.
Hier gefunden
Document head · <html lang>
https://www.figma.com/ai/Was wir gesehen haben
<html lang="en"> while the path locale is ai
So beheben Sie das
Set html lang="ai" so it matches this page’s URL locale.
Language switcher
Fehlgeschlagen58technischVisitors should move between locales without losing the current page.
- hightechnical · 95% Vertrauen
Language links return to the homepage
Locale links were found, but they appear to drop the current page path.
Hier gefunden
Header · <nav> language links
https://www.figma.com/Was wir gesehen haben
<a href="https://www.figma.com/ai/">AI workflows</a> drops the current page path
So beheben Sie das
Point language-switcher links at the equivalent localized path, not the locale homepage.
Sitemap
Fehlgeschlagen88technischLike 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% Vertrauen
Sitemap omits some published locales
Locale-prefixed pages for ai do not appear in sampled sitemap URLs.
Hier gefunden
Sitemap · sitemap.xml
https://www.figma.com/sitemap.xmlWas wir gesehen haben
Sitemap locales in sample: id, de, es, fr, it, nl, pl, pt, hi, ja, ko, th; missing: ai
So beheben Sie das
Include URLs for every published locale prefix in the sitemap.
Structured data
Fehlgeschlagen0technischJSON-LD inLanguage should match the page locale when structured data is present.
- lowtechnical · 95% Vertrauen
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Hier gefunden
JSON-LD · <script type="application/ld+json">
https://www.figma.com/Was wir gesehen haben
Organization is present but inLanguage is missing
So beheben Sie das
Set JSON-LD inLanguage to match each page locale.
International formatting
Fehlgeschlagen50technischDates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.
- infotechnical · 42% Vertrauen
Locale-sensitive values are not shown
The provided evidence contains no dates, numbers, currencies, or calendar values, so international formatting cannot be verified.
Was wir gesehen haben
The preview shows page titles, buttons, headings, and cookie text, but no dates, numbers, currency amounts, or calendar values.
So beheben Sie das
Audit representative localized pages for date, number, currency, digit, and calendar formatting.
Accessibility localisation
Fehlgeschlagen78technischlang, aria-label, and alt text should match the page locale.
- infotechnical · 82% Vertrauen
Page language metadata matches sampled locales
The sampled German and Spanish pages expose matching htmlLang values, supporting correct language metadata.
Hier gefunden
Document root · <html>
https://www.figma.com/de-de/Was wir gesehen haben
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
Fehlgeschlagen82sprachlichLocalized pages should not leave source-language copy in place, except brand names and URLs.
- highlinguistic · 92% Vertrauen
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
Hier gefunden
Pricing hero · <button>
https://www.figma.com/de-de/Was wir gesehen haben
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/
So beheben Sie das
Translate leftover source-language CTAs to match the surrounding locale copy.
- infolinguistic · 84% Vertrauen
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.
Hier gefunden
Header · <nav>
https://www.figma.com/de-de/Was wir gesehen haben
German buttons: "Produkte","Lösungen","Community","Ressourcen"; Spanish buttons: "Productos","Soluciones","Comunidad","Recursos".
Terminology consistency
Fehlgeschlagen40sprachlichImportant concepts should not be translated differently across pages.
- mediumlinguistic · 95% Vertrauen
Terminology inconsistency
"Figma Socials" appears both untranslated and translated across de pages. Affects 11 sampled pages.
Hier gefunden
Header · <nav> or <button>
https://www.figma.com/de-de/Was wir gesehen haben
"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/
So beheben Sie das
Use one translated label for "Figma Socials" across de pages.
Translation accuracy
Fehlgeschlagen72sprachlichTarget copy should preserve the source meaning, numbers, and product actions.
- mediumlinguistic · 67% Vertrauen
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.
Hier gefunden
Privacy controls · <button>
https://www.figma.com/de-de/Was wir gesehen haben
English: "Opt-Out"; German: "Ausschluss"; German longer label: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
So beheben Sie das
Use established German consent terminology such as “Ablehnen” or “Opt-out” consistently, and validate it with German legal and UX reviewers.
Fluency
Fehlgeschlagen70sprachlichCopy should sound natural, without grammar issues or machine-translation artifacts.
- mediumlinguistic · 73% Vertrauen
German privacy copy reads awkwardly
The sampled German cookie notice contains an unnatural construction around selling and distributing behavioral advertising.
Hier gefunden
Cookie notice · <p>
https://www.figma.com/de-de/Was wir gesehen haben
"Wir nutzen Cookies für Verkaufszwecke und Verteilung der verhaltensgebundenen Werbung oder für zielgerichtete Werbung."
So beheben Sie das
Rewrite the sentence in idiomatic German and have a native copy editor review the full privacy notice.
Brand voice
Fehlgeschlagen83sprachlichLocalized copy should preserve the intended tone of the source.
Grammar and style
Fehlgeschlagen76sprachlichLocale-specific capitalization, punctuation, formality, and agreement should be correct.
- lowlinguistic · 70% Vertrauen
German terminology and capitalization need review
The privacy notice uses awkward nominal phrasing and borrowed terminology that may not align with polished German style.
Hier gefunden
Cookie notice · <p>
https://www.figma.com/de-de/Was wir gesehen haben
"Diese Website verwendet Cookies, Zählpixel und lokale Speicherung zu Performance-, Personalisierungs- und Marketingzwecken."
So beheben Sie das
Review the sentence for idiomatic German, including terminology such as “Performance” and the construction after “Speicherung”.
CTA intent
Fehlgeschlagen72kontextbezogenLocalized calls to action should communicate the intended product action.
- mediumcontextual · 76% Vertrauen
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.
Hier gefunden
Privacy controls · <button>
https://www.figma.com/de-de/Was wir gesehen haben
Source button: "Opt-Out"; German button: "Ausschluss"; German extended button: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
So beheben Sie das
Replace “Ausschluss” with a clear action-oriented German label that explicitly conveys opting out of sale or sharing.
Cultural adaptation
Fehlgeschlagen55kontextbezogenCurrency, dates, addresses, and local examples should fit the market.
- infocontextual · 45% Vertrauen
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.
Was wir gesehen haben
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.
So beheben Sie das
Review regional pages for market-appropriate formats, terminology, examples, and legal or privacy language.
UI context
Fehlgeschlagen76kontextbezogenTranslations should fit the UI component: button, nav, form, modal, or error.
- mediumcontextual · 70% Vertrauen
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.
Hier gefunden
Privacy controls · <button>
https://www.figma.com/de-de/Was wir gesehen haben
German buttons include "Ausschluss" and "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
So beheben Sie das
Use a concise, recognizable consent action in the button and keep the longer explanation in supporting text or an accessible label.
Product context
Fehlgeschlagen82kontextbezogenLanguage should match product concepts such as plans, settings, and workflows.
Contextual meaning
Fehlgeschlagen78kontextbezogenStrings should be judged in surrounding page and component context, not in isolation.
Audience context
Fehlgeschlagen82kontextbezogenLanguage should fit the intended audience, such as consumer, enterprise, or developer.
Text expansion
Fehlgeschlagen40visuellLonger translations should not create obvious length pressure versus the source UI.
- mediumvisual · 88% Vertrauen
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.
Hier gefunden
Heading · heading
https://www.figma.com/de-de/Was wir gesehen haben
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/
So beheben Sie das
Shorten the translation or give the control more room so the longer copy does not overflow.
Font and script support
Fehlgeschlagen62visuellTypography should support the target script without generic fallback-only stacks, tofu glyphs, or missing CJK fonts.
- highvisual · 95% Vertrauen
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.
Hier gefunden
Page body · font-family
https://www.figma.com/ja-jp/Was wir gesehen haben
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/
So beheben Sie das
Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
Localized images and assets
Fehlgeschlagen50visuellLanguage-specific images and alt text should match the page locale.
- infovisual · 35% Vertrauen
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.
Was wir gesehen haben
The provided page preview lists titles, buttons, headings, and text, but contains no <img> markup or alt-text values.
So beheben Sie das
Inspect localized pages for image sources, embedded text, and alt attributes, then verify that language-specific assets and descriptions match each locale.
Visual hierarchy
Fehlgeschlagen55visuellLocalization should not make headings or CTAs lose scanability.
- lowvisual · 80% Vertrauen
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 6 sampled pages.
Hier gefunden
Page body · heading
https://www.figma.com/de-de/Was wir gesehen haben
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/
So beheben Sie das
Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
Fehlgeschlagen70visuellRepeated components should stay visually consistent across locales.
- lowvisual · 95% Vertrauen
Repeated components differ across locales
Button counts differ between the source locale and ai.
Hier gefunden
Page body · <button>
https://www.figma.com/ai/Was wir gesehen haben
Source locale has 7 buttons; ai has 13.
So beheben Sie das
Keep the same repeated controls across locales, or drop unused ones on purpose.
Text overflow
Fehlgeschlagen68visuellText should not clip, truncate unexpectedly, or overflow buttons and navigation.
- lowvisual · 62% Vertrauen
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.
Hier gefunden
Privacy controls · <button>
https://www.figma.com/de-de/Was wir gesehen haben
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" versus the English "Do Not Sell/Share My Personal Info + Opt-Out".
So beheben Sie das
Test the label at mobile and desktop widths; allow wrapping or expand the control instead of clipping or truncating text.
Layout breakage
Fehlgeschlagen68visuellLocalized pages should not overlap, break grids, or overflow modals.
- lowvisual · 60% Vertrauen
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.
Hier gefunden
Privacy controls · <button>
https://www.figma.com/de-de/Was wir gesehen haben
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" is shown as a button label.
So beheben Sie das
Check the privacy control and any consent modal at narrow widths, and support flexible button sizing and wrapping.
Responsive localisation
Fehlgeschlagen68visuellLocalized layouts should hold up across mobile, tablet, and desktop widths.
- infovisual · 58% Vertrauen
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.
Hier gefunden
Privacy controls · <button>
https://www.figma.com/de-de/Was wir gesehen haben
The evidence shows the long German label "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" but no viewport or layout output.
So beheben Sie das
Run mobile, tablet, and desktop visual checks for all locales with long navigation and privacy labels.
Bestandene Prüfungen (5)
Nicht zutreffend (4)
Erkannte Gebietsschemas
Vollständige Ergebnisse
- hightechnical · 95% Vertrauen
URL locale and html lang disagree
Path locale ai expects html lang ai, but the page declares en.
Hier gefunden
Document head · <html lang>
https://www.figma.com/ai/Was wir gesehen haben
<html lang="en"> while the path locale is ai
So beheben Sie das
Set html lang="ai" so it matches this page’s URL locale.
- hightechnical · 95% Vertrauen
Language links return to the homepage
Locale links were found, but they appear to drop the current page path.
Hier gefunden
Header · <nav> language links
https://www.figma.com/Was wir gesehen haben
<a href="https://www.figma.com/ai/">AI workflows</a> drops the current page path
So beheben Sie das
Point language-switcher links at the equivalent localized path, not the locale homepage.
- mediumtechnical · 88% Vertrauen
Sitemap omits some published locales
Locale-prefixed pages for ai do not appear in sampled sitemap URLs.
Hier gefunden
Sitemap · sitemap.xml
https://www.figma.com/sitemap.xmlWas wir gesehen haben
Sitemap locales in sample: id, de, es, fr, it, nl, pl, pt, hi, ja, ko, th; missing: ai
So beheben Sie das
Include URLs for every published locale prefix in the sitemap.
- lowtechnical · 95% Vertrauen
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Hier gefunden
JSON-LD · <script type="application/ld+json">
https://www.figma.com/Was wir gesehen haben
Organization is present but inLanguage is missing
So beheben Sie das
Set JSON-LD inLanguage to match each page locale.
- highlinguistic · 92% Vertrauen
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
Hier gefunden
Pricing hero · <button>
https://www.figma.com/de-de/Was wir gesehen haben
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/
So beheben Sie das
Translate leftover source-language CTAs to match the surrounding locale copy.
- mediumlinguistic · 95% Vertrauen
Terminology inconsistency
"Figma Socials" appears both untranslated and translated across de pages. Affects 11 sampled pages.
Hier gefunden
Header · <nav> or <button>
https://www.figma.com/de-de/Was wir gesehen haben
"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/
So beheben Sie das
Use one translated label for "Figma Socials" across de pages.
- mediumvisual · 88% Vertrauen
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.
Hier gefunden
Heading · heading
https://www.figma.com/de-de/Was wir gesehen haben
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/
So beheben Sie das
Shorten the translation or give the control more room so the longer copy does not overflow.
- highvisual · 95% Vertrauen
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.
Hier gefunden
Page body · font-family
https://www.figma.com/ja-jp/Was wir gesehen haben
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/
So beheben Sie das
Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
- lowvisual · 80% Vertrauen
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 6 sampled pages.
Hier gefunden
Page body · heading
https://www.figma.com/de-de/Was wir gesehen haben
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/
So beheben Sie das
Shorten the heading so it does not crowd the visual hierarchy.
- lowvisual · 95% Vertrauen
Repeated components differ across locales
Button counts differ between the source locale and ai.
Hier gefunden
Page body · <button>
https://www.figma.com/ai/Was wir gesehen haben
Source locale has 7 buttons; ai has 13.
So beheben Sie das
Keep the same repeated controls across locales, or drop unused ones on purpose.
- infotechnical · 42% Vertrauen
Locale-sensitive values are not shown
The provided evidence contains no dates, numbers, currencies, or calendar values, so international formatting cannot be verified.
Was wir gesehen haben
The preview shows page titles, buttons, headings, and cookie text, but no dates, numbers, currency amounts, or calendar values.
So beheben Sie das
Audit representative localized pages for date, number, currency, digit, and calendar formatting.
- infotechnical · 82% Vertrauen
Page language metadata matches sampled locales
The sampled German and Spanish pages expose matching htmlLang values, supporting correct language metadata.
Hier gefunden
Document root · <html>
https://www.figma.com/de-de/Was wir gesehen haben
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% Vertrauen
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.
Hier gefunden
Header · <nav>
https://www.figma.com/de-de/Was wir gesehen haben
German buttons: "Produkte","Lösungen","Community","Ressourcen"; Spanish buttons: "Productos","Soluciones","Comunidad","Recursos".
- mediumlinguistic · 67% Vertrauen
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.
Hier gefunden
Privacy controls · <button>
https://www.figma.com/de-de/Was wir gesehen haben
English: "Opt-Out"; German: "Ausschluss"; German longer label: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
So beheben Sie das
Use established German consent terminology such as “Ablehnen” or “Opt-out” consistently, and validate it with German legal and UX reviewers.
- mediumlinguistic · 73% Vertrauen
German privacy copy reads awkwardly
The sampled German cookie notice contains an unnatural construction around selling and distributing behavioral advertising.
Hier gefunden
Cookie notice · <p>
https://www.figma.com/de-de/Was wir gesehen haben
"Wir nutzen Cookies für Verkaufszwecke und Verteilung der verhaltensgebundenen Werbung oder für zielgerichtete Werbung."
So beheben Sie das
Rewrite the sentence in idiomatic German and have a native copy editor review the full privacy notice.
- lowlinguistic · 70% Vertrauen
German terminology and capitalization need review
The privacy notice uses awkward nominal phrasing and borrowed terminology that may not align with polished German style.
Hier gefunden
Cookie notice · <p>
https://www.figma.com/de-de/Was wir gesehen haben
"Diese Website verwendet Cookies, Zählpixel und lokale Speicherung zu Performance-, Personalisierungs- und Marketingzwecken."
So beheben Sie das
Review the sentence for idiomatic German, including terminology such as “Performance” and the construction after “Speicherung”.
- mediumcontextual · 76% Vertrauen
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.
Hier gefunden
Privacy controls · <button>
https://www.figma.com/de-de/Was wir gesehen haben
Source button: "Opt-Out"; German button: "Ausschluss"; German extended button: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
So beheben Sie das
Replace “Ausschluss” with a clear action-oriented German label that explicitly conveys opting out of sale or sharing.
- infocontextual · 45% Vertrauen
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.
Was wir gesehen haben
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.
So beheben Sie das
Review regional pages for market-appropriate formats, terminology, examples, and legal or privacy language.
- mediumcontextual · 70% Vertrauen
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.
Hier gefunden
Privacy controls · <button>
https://www.figma.com/de-de/Was wir gesehen haben
German buttons include "Ausschluss" and "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
So beheben Sie das
Use a concise, recognizable consent action in the button and keep the longer explanation in supporting text or an accessible label.
- infovisual · 35% Vertrauen
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.
Was wir gesehen haben
The provided page preview lists titles, buttons, headings, and text, but contains no <img> markup or alt-text values.
So beheben Sie das
Inspect localized pages for image sources, embedded text, and alt attributes, then verify that language-specific assets and descriptions match each locale.
- lowvisual · 62% Vertrauen
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.
Hier gefunden
Privacy controls · <button>
https://www.figma.com/de-de/Was wir gesehen haben
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" versus the English "Do Not Sell/Share My Personal Info + Opt-Out".
So beheben Sie das
Test the label at mobile and desktop widths; allow wrapping or expand the control instead of clipping or truncating text.
- lowvisual · 60% Vertrauen
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.
Hier gefunden
Privacy controls · <button>
https://www.figma.com/de-de/Was wir gesehen haben
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" is shown as a button label.
So beheben Sie das
Check the privacy control and any consent modal at narrow widths, and support flexible button sizing and wrapping.
- infovisual · 58% Vertrauen
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.
Hier gefunden
Privacy controls · <button>
https://www.figma.com/de-de/Was wir gesehen haben
The evidence shows the long German label "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" but no viewport or layout output.
So beheben Sie das
Run mobile, tablet, and desktop visual checks for all locales with long navigation and privacy labels.
Stichprobenartig geprüfte Seiten
- 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
Senden Sie mir eine Zusammenfassung per E-Mail
Optional. Geben Sie Ihre geschäftliche E-Mail-Adresse ein, und wir senden Ihnen eine kurze Zusammenfassung dieses öffentlichen Berichts.
Nächster Schritt
Solide Grundlage mit Verbesserungspotenzial. Erstellen Sie einen Workspace zur kontinuierlichen Überwachung der Lokalisierung oder buchen Sie eine Audit-Besprechung.
