Localisation report
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.
Brand voice: collaborative, creative, product-focused
Localisation score
71/100
Needs improvementUsers may encounter noticeable localisation problems.
Sampled 15 pages across technical, linguistic, contextual, and visual localisation credits. How we score localisation audits
Rank #14 of 24 public audits
URL locale and html lang disagree
Path locale ai expects html lang ai, but the page declares en.
Found here
Document head · <html lang>
https://www.figma.com/ai/What we saw
<html lang="en"> while the path locale is ai
How to fix it
Set html lang="ai" so it matches this page’s URL locale.
Language links return to the homepage
Locale links were found, but they appear to drop the current page path.
Found here
Header · <nav> language links
https://www.figma.com/What we saw
<a href="https://www.figma.com/ai/">AI workflows</a> drops the current page path
How to fix it
Point language-switcher links at the equivalent localized path, not the locale homepage.
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
Found here
Pricing hero · <button>
https://www.figma.com/de-de/What we saw
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/
How to fix it
Translate leftover source-language CTAs to match the surrounding locale copy.
5 passed · 26 to fix · 4 not applicable
Locale detection
Fail82technicalPages should declare a correct html lang that matches the URL and content locale.
URL locale and html lang disagree
Path locale ai expects html lang ai, but the page declares en.
Found here
Document head · <html lang>
https://www.figma.com/ai/What we saw
<html lang="en"> while the path locale is ai
How to fix it
Set html lang="ai" so it matches this page’s URL locale.
Language switcher
Fail58technicalVisitors should move between locales without losing the current page.
Language links return to the homepage
Locale links were found, but they appear to drop the current page path.
Found here
Header · <nav> language links
https://www.figma.com/What we saw
<a href="https://www.figma.com/ai/">AI workflows</a> drops the current page path
How to fix it
Point language-switcher links at the equivalent localized path, not the locale homepage.
Sitemap
Fail88technicalLike 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.
Sitemap omits some published locales
Locale-prefixed pages for ai do not appear in sampled sitemap URLs.
Found here
Sitemap · sitemap.xml
https://www.figma.com/sitemap.xmlWhat we saw
Sitemap locales in sample: id, de, es, fr, it, nl, pl, pt, hi, ja, ko, th; missing: ai
How to fix it
Include URLs for every published locale prefix in the sitemap.
Structured data
Fail0technicalJSON-LD inLanguage should match the page locale when structured data is present.
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Found here
JSON-LD · <script type="application/ld+json">
https://www.figma.com/What we saw
Organization is present but inLanguage is missing
How to fix it
Set JSON-LD inLanguage to match each page locale.
International formatting
Fail50technicalDates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.
Locale-sensitive values are not shown
The provided evidence contains no dates, numbers, currencies, or calendar values, so international formatting cannot be verified.
What we saw
The preview shows page titles, buttons, headings, and cookie text, but no dates, numbers, currency amounts, or calendar values.
How to fix it
Audit representative localized pages for date, number, currency, digit, and calendar formatting.
Accessibility localisation
Fail78technicallang, aria-label, and alt text should match the page locale.
Page language metadata matches sampled locales
The sampled German and Spanish pages expose matching htmlLang values, supporting correct language metadata.
Found here
Document root · <html>
https://www.figma.com/de-de/What we saw
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
Fail82linguisticLocalized pages should not leave source-language copy in place, except brand names and URLs.
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
Found here
Pricing hero · <button>
https://www.figma.com/de-de/What we saw
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/
How to fix it
Translate leftover source-language CTAs to match the surrounding locale copy.
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.
Found here
Header · <nav>
https://www.figma.com/de-de/What we saw
German buttons: "Produkte","Lösungen","Community","Ressourcen"; Spanish buttons: "Productos","Soluciones","Comunidad","Recursos".
Terminology consistency
Fail40linguisticImportant concepts should not be translated differently across pages.
Terminology inconsistency
"Figma Socials" appears both untranslated and translated across de pages. Affects 11 sampled pages.
Found here
Header · <nav> or <button>
https://www.figma.com/de-de/What we saw
"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/
How to fix it
Use one translated label for "Figma Socials" across de pages.
Translation accuracy
Fail72linguisticTarget copy should preserve the source meaning, numbers, and product actions.
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.
Found here
Privacy controls · <button>
https://www.figma.com/de-de/What we saw
English: "Opt-Out"; German: "Ausschluss"; German longer label: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
How to fix it
Use established German consent terminology such as “Ablehnen” or “Opt-out” consistently, and validate it with German legal and UX reviewers.
Fluency
Fail70linguisticCopy should sound natural, without grammar issues or machine-translation artifacts.
German privacy copy reads awkwardly
The sampled German cookie notice contains an unnatural construction around selling and distributing behavioral advertising.
Found here
Cookie notice · <p>
https://www.figma.com/de-de/What we saw
"Wir nutzen Cookies für Verkaufszwecke und Verteilung der verhaltensgebundenen Werbung oder für zielgerichtete Werbung."
How to fix it
Rewrite the sentence in idiomatic German and have a native copy editor review the full privacy notice.
Brand voice
Fail83linguisticLocalized copy should preserve the intended tone of the source.
Grammar and style
Fail76linguisticLocale-specific capitalization, punctuation, formality, and agreement should be correct.
German terminology and capitalization need review
The privacy notice uses awkward nominal phrasing and borrowed terminology that may not align with polished German style.
Found here
Cookie notice · <p>
https://www.figma.com/de-de/What we saw
"Diese Website verwendet Cookies, Zählpixel und lokale Speicherung zu Performance-, Personalisierungs- und Marketingzwecken."
How to fix it
Review the sentence for idiomatic German, including terminology such as “Performance” and the construction after “Speicherung”.
CTA intent
Fail72contextualLocalized calls to action should communicate the intended product action.
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.
Found here
Privacy controls · <button>
https://www.figma.com/de-de/What we saw
Source button: "Opt-Out"; German button: "Ausschluss"; German extended button: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
How to fix it
Replace “Ausschluss” with a clear action-oriented German label that explicitly conveys opting out of sale or sharing.
Cultural adaptation
Fail55contextualCurrency, dates, addresses, and local examples should fit the market.
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.
What we saw
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.
How to fix it
Review regional pages for market-appropriate formats, terminology, examples, and legal or privacy language.
UI context
Fail76contextualTranslations should fit the UI component: button, nav, form, modal, or error.
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.
Found here
Privacy controls · <button>
https://www.figma.com/de-de/What we saw
German buttons include "Ausschluss" and "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
How to fix it
Use a concise, recognizable consent action in the button and keep the longer explanation in supporting text or an accessible label.
Product context
Fail82contextualLanguage should match product concepts such as plans, settings, and workflows.
Contextual meaning
Fail78contextualStrings should be judged in surrounding page and component context, not in isolation.
Audience context
Fail82contextualLanguage should fit the intended audience, such as consumer, enterprise, or developer.
Text expansion
Fail40visualLonger translations should not create obvious length pressure versus the source UI.
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.
Found here
Heading · heading
https://www.figma.com/de-de/What we saw
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/
How to fix it
Shorten the translation or give the control more room so the longer copy does not overflow.
Font and script support
Fail62visualTypography should support the target script without generic fallback-only stacks, tofu glyphs, or missing CJK fonts.
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.
Found here
Page body · font-family
https://www.figma.com/ja-jp/What we saw
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/
How to fix it
Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
Localized images and assets
Fail50visualLanguage-specific images and alt text should match the page locale.
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.
What we saw
The provided page preview lists titles, buttons, headings, and text, but contains no <img> markup or alt-text values.
How to fix it
Inspect localized pages for image sources, embedded text, and alt attributes, then verify that language-specific assets and descriptions match each locale.
Visual hierarchy
Fail55visualLocalization should not make headings or CTAs lose scanability.
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 6 sampled pages.
Found here
Page body · heading
https://www.figma.com/de-de/What we saw
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/
How to fix it
Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
Fail70visualRepeated components should stay visually consistent across locales.
Repeated components differ across locales
Button counts differ between the source locale and ai.
Found here
Page body · <button>
https://www.figma.com/ai/What we saw
Source locale has 7 buttons; ai has 13.
How to fix it
Keep the same repeated controls across locales, or drop unused ones on purpose.
Text overflow
Fail68visualText should not clip, truncate unexpectedly, or overflow buttons and navigation.
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.
Found here
Privacy controls · <button>
https://www.figma.com/de-de/What we saw
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" versus the English "Do Not Sell/Share My Personal Info + Opt-Out".
How to fix it
Test the label at mobile and desktop widths; allow wrapping or expand the control instead of clipping or truncating text.
Layout breakage
Fail68visualLocalized pages should not overlap, break grids, or overflow modals.
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.
Found here
Privacy controls · <button>
https://www.figma.com/de-de/What we saw
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" is shown as a button label.
How to fix it
Check the privacy control and any consent modal at narrow widths, and support flexible button sizing and wrapping.
Responsive localisation
Fail68visualLocalized layouts should hold up across mobile, tablet, and desktop widths.
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.
Found here
Privacy controls · <button>
https://www.figma.com/de-de/What we saw
The evidence shows the long German label "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" but no viewport or layout output.
How to fix it
Run mobile, tablet, and desktop visual checks for all locales with long navigation and privacy labels.
URL locale and html lang disagree
Path locale ai expects html lang ai, but the page declares en.
Found here
Document head · <html lang>
https://www.figma.com/ai/What we saw
<html lang="en"> while the path locale is ai
How to fix it
Set html lang="ai" so it matches this page’s URL locale.
Language links return to the homepage
Locale links were found, but they appear to drop the current page path.
Found here
Header · <nav> language links
https://www.figma.com/What we saw
<a href="https://www.figma.com/ai/">AI workflows</a> drops the current page path
How to fix it
Point language-switcher links at the equivalent localized path, not the locale homepage.
Sitemap omits some published locales
Locale-prefixed pages for ai do not appear in sampled sitemap URLs.
Found here
Sitemap · sitemap.xml
https://www.figma.com/sitemap.xmlWhat we saw
Sitemap locales in sample: id, de, es, fr, it, nl, pl, pt, hi, ja, ko, th; missing: ai
How to fix it
Include URLs for every published locale prefix in the sitemap.
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Found here
JSON-LD · <script type="application/ld+json">
https://www.figma.com/What we saw
Organization is present but inLanguage is missing
How to fix it
Set JSON-LD inLanguage to match each page locale.
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
Found here
Pricing hero · <button>
https://www.figma.com/de-de/What we saw
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/
How to fix it
Translate leftover source-language CTAs to match the surrounding locale copy.
Terminology inconsistency
"Figma Socials" appears both untranslated and translated across de pages. Affects 11 sampled pages.
Found here
Header · <nav> or <button>
https://www.figma.com/de-de/What we saw
"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/
How to fix it
Use one translated label for "Figma Socials" across de pages.
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.
Found here
Heading · heading
https://www.figma.com/de-de/What we saw
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/
How to fix it
Shorten the translation or give the control more room so the longer copy does not overflow.
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.
Found here
Page body · font-family
https://www.figma.com/ja-jp/What we saw
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/
How to fix it
Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 6 sampled pages.
Found here
Page body · heading
https://www.figma.com/de-de/What we saw
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/
How to fix it
Shorten the heading so it does not crowd the visual hierarchy.
Repeated components differ across locales
Button counts differ between the source locale and ai.
Found here
Page body · <button>
https://www.figma.com/ai/What we saw
Source locale has 7 buttons; ai has 13.
How to fix it
Keep the same repeated controls across locales, or drop unused ones on purpose.
Locale-sensitive values are not shown
The provided evidence contains no dates, numbers, currencies, or calendar values, so international formatting cannot be verified.
What we saw
The preview shows page titles, buttons, headings, and cookie text, but no dates, numbers, currency amounts, or calendar values.
How to fix it
Audit representative localized pages for date, number, currency, digit, and calendar formatting.
Page language metadata matches sampled locales
The sampled German and Spanish pages expose matching htmlLang values, supporting correct language metadata.
Found here
Document root · <html>
https://www.figma.com/de-de/What we saw
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".
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.
Found here
Header · <nav>
https://www.figma.com/de-de/What we saw
German buttons: "Produkte","Lösungen","Community","Ressourcen"; Spanish buttons: "Productos","Soluciones","Comunidad","Recursos".
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.
Found here
Privacy controls · <button>
https://www.figma.com/de-de/What we saw
English: "Opt-Out"; German: "Ausschluss"; German longer label: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
How to fix it
Use established German consent terminology such as “Ablehnen” or “Opt-out” consistently, and validate it with German legal and UX reviewers.
German privacy copy reads awkwardly
The sampled German cookie notice contains an unnatural construction around selling and distributing behavioral advertising.
Found here
Cookie notice · <p>
https://www.figma.com/de-de/What we saw
"Wir nutzen Cookies für Verkaufszwecke und Verteilung der verhaltensgebundenen Werbung oder für zielgerichtete Werbung."
How to fix it
Rewrite the sentence in idiomatic German and have a native copy editor review the full privacy notice.
German terminology and capitalization need review
The privacy notice uses awkward nominal phrasing and borrowed terminology that may not align with polished German style.
Found here
Cookie notice · <p>
https://www.figma.com/de-de/What we saw
"Diese Website verwendet Cookies, Zählpixel und lokale Speicherung zu Performance-, Personalisierungs- und Marketingzwecken."
How to fix it
Review the sentence for idiomatic German, including terminology such as “Performance” and the construction after “Speicherung”.
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.
Found here
Privacy controls · <button>
https://www.figma.com/de-de/What we saw
Source button: "Opt-Out"; German button: "Ausschluss"; German extended button: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
How to fix it
Replace “Ausschluss” with a clear action-oriented German label that explicitly conveys opting out of sale or sharing.
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.
What we saw
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.
How to fix it
Review regional pages for market-appropriate formats, terminology, examples, and legal or privacy language.
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.
Found here
Privacy controls · <button>
https://www.figma.com/de-de/What we saw
German buttons include "Ausschluss" and "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
How to fix it
Use a concise, recognizable consent action in the button and keep the longer explanation in supporting text or an accessible label.
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.
What we saw
The provided page preview lists titles, buttons, headings, and text, but contains no <img> markup or alt-text values.
How to fix it
Inspect localized pages for image sources, embedded text, and alt attributes, then verify that language-specific assets and descriptions match each locale.
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.
Found here
Privacy controls · <button>
https://www.figma.com/de-de/What we saw
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" versus the English "Do Not Sell/Share My Personal Info + Opt-Out".
How to fix it
Test the label at mobile and desktop widths; allow wrapping or expand the control instead of clipping or truncating text.
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.
Found here
Privacy controls · <button>
https://www.figma.com/de-de/What we saw
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" is shown as a button label.
How to fix it
Check the privacy control and any consent modal at narrow widths, and support flexible button sizing and wrapping.
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.
Found here
Privacy controls · <button>
https://www.figma.com/de-de/What we saw
The evidence shows the long German label "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" but no viewport or layout output.
How to fix it
Run mobile, tablet, and desktop visual checks for all locales with long navigation and privacy labels.
Optional. Enter your work email and we will send a concise summary of this public report.
Solid baseline with room to improve. Create a workspace for continuous locale monitoring, or book an audit review.
