Lokalisatierapport
Figma
Design and collaboration softwarefigma.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.
Merkstem: collaborative, creative, product-focused
Lokalisatiescore
71/100
Moet worden verbeterdGebruikers kunnen merkbare lokalisatieproblemen tegenkomen.
- 76Technische audit
- 71Taalkundige audit
- 74Contextuele audit
- 64Visuele audit
Er zijn 15 pagina's steekproefsgewijs beoordeeld op technische, taalkundige, contextuele en visuele lokalisatiecredits. Hoe we lokalisatie-audits beoordelen
Hoe je je verhoudt
Rang #14 van 23 openbare audits
Eerst oplossen
- 1high
URL locale and html lang disagree
Path locale ai expects html lang ai, but the page declares en.
See details - 2high
Language links return to the homepage
Locale links were found, but they appear to drop the current page path.
See details - 3high
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
See details
Auditcriteria
5 passed · 10 to watch · 16 to fix · 4 not applicable
Vereist aandacht (16)
Language switcher
Mislukt58technischVisitors should move between locales without losing the current page.
- hightechnical · 95% zekerheid
Language links return to the homepage
Locale links were found, but they appear to drop the current page path.
Hier gevonden
Header · <nav> language links
https://www.figma.com/Wat we zagen
<a href="https://www.figma.com/ai/">AI workflows</a> drops the current page path
Zo los je het op
Point language-switcher links at the equivalent localized path, not the locale homepage.
Structured data
Mislukt0technischJSON-LD inLanguage should match the page locale when structured data is present.
- lowtechnical · 95% zekerheid
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Hier gevonden
JSON-LD · <script type="application/ld+json">
https://www.figma.com/Wat we zagen
Organization is present but inLanguage is missing
Zo los je het op
Set JSON-LD inLanguage to match each page locale.
International formatting
Mislukt50technischDates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.
- infotechnical · 42% zekerheid
Locale-sensitive values are not shown
The provided evidence contains no dates, numbers, currencies, or calendar values, so international formatting cannot be verified.
Wat we zagen
The preview shows page titles, buttons, headings, and cookie text, but no dates, numbers, currency amounts, or calendar values.
Zo los je het op
Audit representative localized pages for date, number, currency, digit, and calendar formatting.
Terminology consistency
Mislukt40taalkundigImportant concepts should not be translated differently across pages.
- mediumlinguistic · 95% zekerheid
Terminology inconsistency
"Figma Socials" appears both untranslated and translated across de pages. Affects 11 sampled pages.
Hier gevonden
Header · <nav> or <button>
https://www.figma.com/de-de/Wat we zagen
"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/
Zo los je het op
Use one translated label for "Figma Socials" across de pages.
Translation accuracy
Mislukt72taalkundigTarget copy should preserve the source meaning, numbers, and product actions.
- mediumlinguistic · 67% zekerheid
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 gevonden
Privacy controls · <button>
https://www.figma.com/de-de/Wat we zagen
English: "Opt-Out"; German: "Ausschluss"; German longer label: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
Zo los je het op
Use established German consent terminology such as “Ablehnen” or “Opt-out” consistently, and validate it with German legal and UX reviewers.
Fluency
Mislukt70taalkundigCopy should sound natural, without grammar issues or machine-translation artifacts.
- mediumlinguistic · 73% zekerheid
German privacy copy reads awkwardly
The sampled German cookie notice contains an unnatural construction around selling and distributing behavioral advertising.
Hier gevonden
Cookie notice · <p>
https://www.figma.com/de-de/Wat we zagen
"Wir nutzen Cookies für Verkaufszwecke und Verteilung der verhaltensgebundenen Werbung oder für zielgerichtete Werbung."
Zo los je het op
Rewrite the sentence in idiomatic German and have a native copy editor review the full privacy notice.
CTA intent
Mislukt72contextueelLocalized calls to action should communicate the intended product action.
- mediumcontextual · 76% zekerheid
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 gevonden
Privacy controls · <button>
https://www.figma.com/de-de/Wat we zagen
Source button: "Opt-Out"; German button: "Ausschluss"; German extended button: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
Zo los je het op
Replace “Ausschluss” with a clear action-oriented German label that explicitly conveys opting out of sale or sharing.
Cultural adaptation
Mislukt55contextueelCurrency, dates, addresses, and local examples should fit the market.
- infocontextual · 45% zekerheid
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.
Wat we zagen
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.
Zo los je het op
Review regional pages for market-appropriate formats, terminology, examples, and legal or privacy language.
Text expansion
Mislukt40visueelLonger translations should not create obvious length pressure versus the source UI.
- mediumvisual · 88% zekerheid
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 gevonden
Heading · heading
https://www.figma.com/de-de/Wat we zagen
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/
Zo los je het op
Shorten the translation or give the control more room so the longer copy does not overflow.
Font and script support
Mislukt62visueelTypography should support the target script without generic fallback-only stacks, tofu glyphs, or missing CJK fonts.
- highvisual · 95% zekerheid
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 gevonden
Page body · font-family
https://www.figma.com/ja-jp/Wat we zagen
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/
Zo los je het op
Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
Localized images and assets
Mislukt50visueelLanguage-specific images and alt text should match the page locale.
- infovisual · 35% zekerheid
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.
Wat we zagen
The provided page preview lists titles, buttons, headings, and text, but contains no <img> markup or alt-text values.
Zo los je het op
Inspect localized pages for image sources, embedded text, and alt attributes, then verify that language-specific assets and descriptions match each locale.
Visual hierarchy
Mislukt55visueelLocalization should not make headings or CTAs lose scanability.
- lowvisual · 80% zekerheid
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 6 sampled pages.
Hier gevonden
Page body · heading
https://www.figma.com/de-de/Wat we zagen
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/
Zo los je het op
Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
Mislukt70visueelRepeated components should stay visually consistent across locales.
- lowvisual · 95% zekerheid
Repeated components differ across locales
Button counts differ between the source locale and ai.
Hier gevonden
Page body · <button>
https://www.figma.com/ai/Wat we zagen
Source locale has 7 buttons; ai has 13.
Zo los je het op
Keep the same repeated controls across locales, or drop unused ones on purpose.
Text overflow
Mislukt68visueelText should not clip, truncate unexpectedly, or overflow buttons and navigation.
- lowvisual · 62% zekerheid
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 gevonden
Privacy controls · <button>
https://www.figma.com/de-de/Wat we zagen
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" versus the English "Do Not Sell/Share My Personal Info + Opt-Out".
Zo los je het op
Test the label at mobile and desktop widths; allow wrapping or expand the control instead of clipping or truncating text.
Layout breakage
Mislukt68visueelLocalized pages should not overlap, break grids, or overflow modals.
- lowvisual · 60% zekerheid
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 gevonden
Privacy controls · <button>
https://www.figma.com/de-de/Wat we zagen
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" is shown as a button label.
Zo los je het op
Check the privacy control and any consent modal at narrow widths, and support flexible button sizing and wrapping.
Responsive localisation
Mislukt68visueelLocalized layouts should hold up across mobile, tablet, and desktop widths.
- infovisual · 58% zekerheid
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 gevonden
Privacy controls · <button>
https://www.figma.com/de-de/Wat we zagen
The evidence shows the long German label "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" but no viewport or layout output.
Zo los je het op
Run mobile, tablet, and desktop visual checks for all locales with long navigation and privacy labels.
Worth a look (10)
Locale detection
Watch82technischPages should declare a correct html lang that matches the URL and content locale.
- hightechnical · 95% zekerheid
URL locale and html lang disagree
Path locale ai expects html lang ai, but the page declares en.
Hier gevonden
Document head · <html lang>
https://www.figma.com/ai/Wat we zagen
<html lang="en"> while the path locale is ai
Zo los je het op
Set html lang="ai" so it matches this page’s URL locale.
Sitemap
Watch88technischLike 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% zekerheid
Sitemap omits some published locales
Locale-prefixed pages for ai do not appear in sampled sitemap URLs.
Hier gevonden
Sitemap · sitemap.xml
https://www.figma.com/sitemap.xmlWat we zagen
Sitemap locales in sample: id, de, es, fr, it, nl, pl, pt, hi, ja, ko, th; missing: ai
Zo los je het op
Include URLs for every published locale prefix in the sitemap.
Accessibility localisation
Watch78technischlang, aria-label, and alt text should match the page locale.
- infotechnical · 82% zekerheid
Page language metadata matches sampled locales
The sampled German and Spanish pages expose matching htmlLang values, supporting correct language metadata.
Hier gevonden
Document root · <html>
https://www.figma.com/de-de/Wat we zagen
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
Watch82taalkundigLocalized pages should not leave source-language copy in place, except brand names and URLs.
- highlinguistic · 92% zekerheid
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
Hier gevonden
Pricing hero · <button>
https://www.figma.com/de-de/Wat we zagen
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/
Zo los je het op
Translate leftover source-language CTAs to match the surrounding locale copy.
- infolinguistic · 84% zekerheid
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 gevonden
Header · <nav>
https://www.figma.com/de-de/Wat we zagen
German buttons: "Produkte","Lösungen","Community","Ressourcen"; Spanish buttons: "Productos","Soluciones","Comunidad","Recursos".
Brand voice
Watch83taalkundigLocalized copy should preserve the intended tone of the source.
Grammar and style
Watch76taalkundigLocale-specific capitalization, punctuation, formality, and agreement should be correct.
- lowlinguistic · 70% zekerheid
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 gevonden
Cookie notice · <p>
https://www.figma.com/de-de/Wat we zagen
"Diese Website verwendet Cookies, Zählpixel und lokale Speicherung zu Performance-, Personalisierungs- und Marketingzwecken."
Zo los je het op
Review the sentence for idiomatic German, including terminology such as “Performance” and the construction after “Speicherung”.
UI context
Watch76contextueelTranslations should fit the UI component: button, nav, form, modal, or error.
- mediumcontextual · 70% zekerheid
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 gevonden
Privacy controls · <button>
https://www.figma.com/de-de/Wat we zagen
German buttons include "Ausschluss" and "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
Zo los je het op
Use a concise, recognizable consent action in the button and keep the longer explanation in supporting text or an accessible label.
Product context
Watch82contextueelLanguage should match product concepts such as plans, settings, and workflows.
Contextual meaning
Watch78contextueelStrings should be judged in surrounding page and component context, not in isolation.
Audience context
Watch82contextueelLanguage should fit the intended audience, such as consumer, enterprise, or developer.
Geslaagde controles (5)
Niet van toepassing (4)
Gedetecteerde talen
ai
URL path
Duits (Duitsland)
de-de · URL path
Engels
en · page language
Spaans (Argentinië)
es-ar · hreflang
Spaans (Bolivia)
es-bo · hreflang
Spaans (Chili)
es-cl · hreflang
Spaans (Colombia)
es-co · hreflang
Spaans (Costa Rica)
es-cr · hreflang
Spaans (Cuba)
es-cu · hreflang
Spaans (Dominicaanse Republiek)
es-do · hreflang
Spaans (Ecuador)
es-ec · hreflang
Spaans (Spanje)
es-es · hreflang
Spaans (Guatemala)
es-gt · hreflang
Spaans (Honduras)
es-hn · hreflang
Spaans (Laos)
es-la · URL path
Spaans (Mexico)
es-mx · hreflang
Spaans (Nicaragua)
es-ni · hreflang
Spaans (Panama)
es-pa · hreflang
Spaans (Peru)
es-pe · hreflang
Spaans (Puerto Rico)
es-pr · hreflang
Spaans (Paraguay)
es-py · hreflang
Spaans (El Salvador)
es-sv · hreflang
Spaans (Uruguay)
es-uy · hreflang
Spaans (Venezuela)
es-ve · hreflang
Frans (Frankrijk)
fr-fr · URL path
Hindi (India)
hi-in · URL path
Indonesisch (Indonesië)
id-id · URL path
Italiaans (Italië)
it-it · URL path
Japans (Japan)
ja-jp · URL path
Koreaans (Zuid-Korea)
ko-kr · URL path
Nederlands (Nederland)
nl-nl · URL path
Pools (Polen)
pl-pl · URL path
Portugees (Brazilië)
pt-br · hreflang
Thai (Thailand)
th-th · URL path
Pagina’s bemonsterd
Volgende stap
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.