Lokaliseringsrapport
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.
Brandstemme: collaborative, creative, product-focused
Lokaliseringsscore
71/100
Kræver forbedringBrugerne kan opleve mærkbare lokaliseringsproblemer.
- 76Teknisk audit
- 71Sproglig kontrol
- 74Kontekstaudit
- 64Visuel revision
Udvalgte 15 sider på tværs af tekniske, sproglige, kontekstuelle og visuelle lokaliseringskrediteringer. Sådan bedømmer vi lokaliseringsaudits
Sådan ligger du i forhold til andre
Placering nr. 14 af 23 offentlige audits
Ret først
- 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
Revisionskriterier
5 passed · 10 to watch · 16 to fix · 4 not applicable
Kræver opmærksomhed (16)
Language switcher
Ikke bestået58tekniskVisitors should move between locales without losing the current page.
- hightechnical · 95% sikkerhed
Language links return to the homepage
Locale links were found, but they appear to drop the current page path.
Fundet her
Header · <nav> language links
https://www.figma.com/Hvad vi så
<a href="https://www.figma.com/ai/">AI workflows</a> drops the current page path
Sådan løser du det
Point language-switcher links at the equivalent localized path, not the locale homepage.
Structured data
Ikke bestået0tekniskJSON-LD inLanguage should match the page locale when structured data is present.
- lowtechnical · 95% sikkerhed
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Fundet her
JSON-LD · <script type="application/ld+json">
https://www.figma.com/Hvad vi så
Organization is present but inLanguage is missing
Sådan løser du det
Set JSON-LD inLanguage to match each page locale.
International formatting
Ikke bestået50tekniskDates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.
- infotechnical · 42% sikkerhed
Locale-sensitive values are not shown
The provided evidence contains no dates, numbers, currencies, or calendar values, so international formatting cannot be verified.
Hvad vi så
The preview shows page titles, buttons, headings, and cookie text, but no dates, numbers, currency amounts, or calendar values.
Sådan løser du det
Audit representative localized pages for date, number, currency, digit, and calendar formatting.
Terminology consistency
Ikke bestået40sprogligImportant concepts should not be translated differently across pages.
- mediumlinguistic · 95% sikkerhed
Terminology inconsistency
"Figma Socials" appears both untranslated and translated across de pages. Affects 11 sampled pages.
Fundet her
Header · <nav> or <button>
https://www.figma.com/de-de/Hvad vi så
"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/
Sådan løser du det
Use one translated label for "Figma Socials" across de pages.
Translation accuracy
Ikke bestået72sprogligTarget copy should preserve the source meaning, numbers, and product actions.
- mediumlinguistic · 67% sikkerhed
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.
Fundet her
Privacy controls · <button>
https://www.figma.com/de-de/Hvad vi så
English: "Opt-Out"; German: "Ausschluss"; German longer label: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
Sådan løser du det
Use established German consent terminology such as “Ablehnen” or “Opt-out” consistently, and validate it with German legal and UX reviewers.
Fluency
Ikke bestået70sprogligCopy should sound natural, without grammar issues or machine-translation artifacts.
- mediumlinguistic · 73% sikkerhed
German privacy copy reads awkwardly
The sampled German cookie notice contains an unnatural construction around selling and distributing behavioral advertising.
Fundet her
Cookie notice · <p>
https://www.figma.com/de-de/Hvad vi så
"Wir nutzen Cookies für Verkaufszwecke und Verteilung der verhaltensgebundenen Werbung oder für zielgerichtete Werbung."
Sådan løser du det
Rewrite the sentence in idiomatic German and have a native copy editor review the full privacy notice.
CTA intent
Ikke bestået72kontekstuelLocalized calls to action should communicate the intended product action.
- mediumcontextual · 76% sikkerhed
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.
Fundet her
Privacy controls · <button>
https://www.figma.com/de-de/Hvad vi så
Source button: "Opt-Out"; German button: "Ausschluss"; German extended button: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
Sådan løser du det
Replace “Ausschluss” with a clear action-oriented German label that explicitly conveys opting out of sale or sharing.
Cultural adaptation
Ikke bestået55kontekstuelCurrency, dates, addresses, and local examples should fit the market.
- infocontextual · 45% sikkerhed
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.
Hvad vi så
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.
Sådan løser du det
Review regional pages for market-appropriate formats, terminology, examples, and legal or privacy language.
Text expansion
Ikke bestået40visuelLonger translations should not create obvious length pressure versus the source UI.
- mediumvisual · 88% sikkerhed
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.
Fundet her
Heading · heading
https://www.figma.com/de-de/Hvad vi så
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/
Sådan løser du det
Shorten the translation or give the control more room so the longer copy does not overflow.
Font and script support
Ikke bestået62visuelTypography should support the target script without generic fallback-only stacks, tofu glyphs, or missing CJK fonts.
- highvisual · 95% sikkerhed
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.
Fundet her
Page body · font-family
https://www.figma.com/ja-jp/Hvad vi så
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/
Sådan løser du det
Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
Localized images and assets
Ikke bestået50visuelLanguage-specific images and alt text should match the page locale.
- infovisual · 35% sikkerhed
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.
Hvad vi så
The provided page preview lists titles, buttons, headings, and text, but contains no <img> markup or alt-text values.
Sådan løser du det
Inspect localized pages for image sources, embedded text, and alt attributes, then verify that language-specific assets and descriptions match each locale.
Visual hierarchy
Ikke bestået55visuelLocalization should not make headings or CTAs lose scanability.
- lowvisual · 80% sikkerhed
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 6 sampled pages.
Fundet her
Page body · heading
https://www.figma.com/de-de/Hvad vi så
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/
Sådan løser du det
Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
Ikke bestået70visuelRepeated components should stay visually consistent across locales.
- lowvisual · 95% sikkerhed
Repeated components differ across locales
Button counts differ between the source locale and ai.
Fundet her
Page body · <button>
https://www.figma.com/ai/Hvad vi så
Source locale has 7 buttons; ai has 13.
Sådan løser du det
Keep the same repeated controls across locales, or drop unused ones on purpose.
Text overflow
Ikke bestået68visuelText should not clip, truncate unexpectedly, or overflow buttons and navigation.
- lowvisual · 62% sikkerhed
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.
Fundet her
Privacy controls · <button>
https://www.figma.com/de-de/Hvad vi så
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" versus the English "Do Not Sell/Share My Personal Info + Opt-Out".
Sådan løser du det
Test the label at mobile and desktop widths; allow wrapping or expand the control instead of clipping or truncating text.
Layout breakage
Ikke bestået68visuelLocalized pages should not overlap, break grids, or overflow modals.
- lowvisual · 60% sikkerhed
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.
Fundet her
Privacy controls · <button>
https://www.figma.com/de-de/Hvad vi så
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" is shown as a button label.
Sådan løser du det
Check the privacy control and any consent modal at narrow widths, and support flexible button sizing and wrapping.
Responsive localisation
Ikke bestået68visuelLocalized layouts should hold up across mobile, tablet, and desktop widths.
- infovisual · 58% sikkerhed
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.
Fundet her
Privacy controls · <button>
https://www.figma.com/de-de/Hvad vi så
The evidence shows the long German label "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" but no viewport or layout output.
Sådan løser du det
Run mobile, tablet, and desktop visual checks for all locales with long navigation and privacy labels.
Worth a look (10)
Locale detection
Watch82tekniskPages should declare a correct html lang that matches the URL and content locale.
- hightechnical · 95% sikkerhed
URL locale and html lang disagree
Path locale ai expects html lang ai, but the page declares en.
Fundet her
Document head · <html lang>
https://www.figma.com/ai/Hvad vi så
<html lang="en"> while the path locale is ai
Sådan løser du det
Set html lang="ai" so it matches this page’s URL locale.
Sitemap
Watch88tekniskLike 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% sikkerhed
Sitemap omits some published locales
Locale-prefixed pages for ai do not appear in sampled sitemap URLs.
Fundet her
Sitemap · sitemap.xml
https://www.figma.com/sitemap.xmlHvad vi så
Sitemap locales in sample: id, de, es, fr, it, nl, pl, pt, hi, ja, ko, th; missing: ai
Sådan løser du det
Include URLs for every published locale prefix in the sitemap.
Accessibility localisation
Watch78teknisklang, aria-label, and alt text should match the page locale.
- infotechnical · 82% sikkerhed
Page language metadata matches sampled locales
The sampled German and Spanish pages expose matching htmlLang values, supporting correct language metadata.
Fundet her
Document root · <html>
https://www.figma.com/de-de/Hvad vi så
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
Watch82sprogligLocalized pages should not leave source-language copy in place, except brand names and URLs.
- highlinguistic · 92% sikkerhed
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
Fundet her
Pricing hero · <button>
https://www.figma.com/de-de/Hvad vi så
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/
Sådan løser du det
Translate leftover source-language CTAs to match the surrounding locale copy.
- infolinguistic · 84% sikkerhed
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.
Fundet her
Header · <nav>
https://www.figma.com/de-de/Hvad vi så
German buttons: "Produkte","Lösungen","Community","Ressourcen"; Spanish buttons: "Productos","Soluciones","Comunidad","Recursos".
Brand voice
Watch83sprogligLocalized copy should preserve the intended tone of the source.
Grammar and style
Watch76sprogligLocale-specific capitalization, punctuation, formality, and agreement should be correct.
- lowlinguistic · 70% sikkerhed
German terminology and capitalization need review
The privacy notice uses awkward nominal phrasing and borrowed terminology that may not align with polished German style.
Fundet her
Cookie notice · <p>
https://www.figma.com/de-de/Hvad vi så
"Diese Website verwendet Cookies, Zählpixel und lokale Speicherung zu Performance-, Personalisierungs- und Marketingzwecken."
Sådan løser du det
Review the sentence for idiomatic German, including terminology such as “Performance” and the construction after “Speicherung”.
UI context
Watch76kontekstuelTranslations should fit the UI component: button, nav, form, modal, or error.
- mediumcontextual · 70% sikkerhed
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.
Fundet her
Privacy controls · <button>
https://www.figma.com/de-de/Hvad vi så
German buttons include "Ausschluss" and "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
Sådan løser du det
Use a concise, recognizable consent action in the button and keep the longer explanation in supporting text or an accessible label.
Product context
Watch82kontekstuelLanguage should match product concepts such as plans, settings, and workflows.
Contextual meaning
Watch78kontekstuelStrings should be judged in surrounding page and component context, not in isolation.
Audience context
Watch82kontekstuelLanguage should fit the intended audience, such as consumer, enterprise, or developer.
Beståede audits (5)
Ikke relevant (4)
Registrerede lokaliteter
ai
URL path
tysk (Tyskland)
de-de · URL path
engelsk
en · page language
spansk (Argentina)
es-ar · hreflang
spansk (Bolivia)
es-bo · hreflang
spansk (Chile)
es-cl · hreflang
spansk (Colombia)
es-co · hreflang
spansk (Costa Rica)
es-cr · hreflang
spansk (Cuba)
es-cu · hreflang
spansk (Den Dominikanske Republik)
es-do · hreflang
spansk (Ecuador)
es-ec · hreflang
europæisk spansk
es-es · hreflang
spansk (Guatemala)
es-gt · hreflang
spansk (Honduras)
es-hn · hreflang
spansk (Laos)
es-la · URL path
mexicansk spansk
es-mx · hreflang
spansk (Nicaragua)
es-ni · hreflang
spansk (Panama)
es-pa · hreflang
spansk (Peru)
es-pe · hreflang
spansk (Puerto Rico)
es-pr · hreflang
spansk (Paraguay)
es-py · hreflang
spansk (El Salvador)
es-sv · hreflang
spansk (Uruguay)
es-uy · hreflang
spansk (Venezuela)
es-ve · hreflang
fransk (Frankrig)
fr-fr · URL path
hindi (Indien)
hi-in · URL path
indonesisk (Indonesien)
id-id · URL path
italiensk (Italien)
it-it · URL path
japansk (Japan)
ja-jp · URL path
koreansk (Sydkorea)
ko-kr · URL path
nederlandsk (Nederlandene)
nl-nl · URL path
polsk (Polen)
pl-pl · URL path
brasiliansk portugisisk
pt-br · hreflang
thai (Thailand)
th-th · URL path
Stikprøvekontrollerede sider
Næste skridt
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.