Báo cáo bản địa hóa
Figma
Design and collaboration softwarefigma.com
Sản phẩm: 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.
Giọng điệu thương hiệu: collaborative, creative, product-focused
Điểm bản địa hóa
71/100
Cần cải thiệnNgười dùng có thể gặp phải các vấn đề bản địa hóa đáng chú ý.
- 76Kiểm tra kỹ thuật
- 71Kiểm tra ngôn ngữ
- 74Kiểm tra theo ngữ cảnh
- 64Kiểm tra trực quan
Đã lấy mẫu 15 trang dựa trên các tiêu chí tín dụng bản địa hóa về kỹ thuật, ngôn ngữ, ngữ cảnh và hình ảnh. Cách chúng tôi chấm điểm các cuộc kiểm tra bản địa hóa
Bạn so sánh như thế nào
Xếp hạng #10 trong số 22 cuộc kiểm tra công khai
Khắc phục trước
- hightechnical · 95% độ tin cậy
URL locale and html lang disagree
Path locale ai expects html lang ai, but the page declares en.
Tìm thấy tại đây
Document head · <html lang>
https://www.figma.com/ai/Điều chúng tôi nhận thấy
<html lang="en"> while the path locale is ai
Cách khắc phục
Set html lang="ai" so it matches this page’s URL locale.
- hightechnical · 95% độ tin cậy
Language links return to the homepage
Locale links were found, but they appear to drop the current page path.
Tìm thấy tại đây
Header · <nav> language links
https://www.figma.com/Điều chúng tôi nhận thấy
<a href="https://www.figma.com/ai/">AI workflows</a> drops the current page path
Cách khắc phục
Point language-switcher links at the equivalent localized path, not the locale homepage.
- highlinguistic · 92% độ tin cậy
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
Tìm thấy tại đây
Pricing hero · <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
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/
Cách khắc phục
Translate leftover source-language CTAs to match the surrounding locale copy.
Tiêu chí kiểm tra
5 đạt · 26 cần sửa · 4 không áp dụng
Cần chú ý (26)
Locale detection
Fail82kỹ thuậtPages should declare a correct html lang that matches the URL and content locale.
- hightechnical · 95% độ tin cậy
URL locale and html lang disagree
Path locale ai expects html lang ai, but the page declares en.
Tìm thấy tại đây
Document head · <html lang>
https://www.figma.com/ai/Điều chúng tôi nhận thấy
<html lang="en"> while the path locale is ai
Cách khắc phục
Set html lang="ai" so it matches this page’s URL locale.
Language switcher
Fail58kỹ thuậtVisitors should move between locales without losing the current page.
- hightechnical · 95% độ tin cậy
Language links return to the homepage
Locale links were found, but they appear to drop the current page path.
Tìm thấy tại đây
Header · <nav> language links
https://www.figma.com/Điều chúng tôi nhận thấy
<a href="https://www.figma.com/ai/">AI workflows</a> drops the current page path
Cách khắc phục
Point language-switcher links at the equivalent localized path, not the locale homepage.
Sitemap
Fail88kỹ thuậtLike 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% độ tin cậy
Sitemap omits some published locales
Locale-prefixed pages for ai do not appear in sampled sitemap URLs.
Tìm thấy tại đây
Sitemap · sitemap.xml
https://www.figma.com/sitemap.xmlĐiều chúng tôi nhận thấy
Sitemap locales in sample: id, de, es, fr, it, nl, pl, pt, hi, ja, ko, th; missing: ai
Cách khắc phục
Include URLs for every published locale prefix in the sitemap.
Structured data
Fail0kỹ thuậtJSON-LD inLanguage should match the page locale when structured data is present.
- lowtechnical · 95% độ tin cậy
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Tìm thấy tại đây
JSON-LD · <script type="application/ld+json">
https://www.figma.com/Điều chúng tôi nhận thấy
Organization is present but inLanguage is missing
Cách khắc phục
Set JSON-LD inLanguage to match each page locale.
International formatting
Fail50kỹ thuậtDates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.
- infotechnical · 42% độ tin cậy
Locale-sensitive values are not shown
The provided evidence contains no dates, numbers, currencies, or calendar values, so international formatting cannot be verified.
Điều chúng tôi nhận thấy
The preview shows page titles, buttons, headings, and cookie text, but no dates, numbers, currency amounts, or calendar values.
Cách khắc phục
Audit representative localized pages for date, number, currency, digit, and calendar formatting.
Accessibility localisation
Fail78kỹ thuậtlang, aria-label, and alt text should match the page locale.
- infotechnical · 82% độ tin cậy
Page language metadata matches sampled locales
The sampled German and Spanish pages expose matching htmlLang values, supporting correct language metadata.
Tìm thấy tại đây
Document root · <html>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
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.
- highlinguistic · 92% độ tin cậy
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
Tìm thấy tại đây
Pricing hero · <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
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/
Cách khắc phục
Translate leftover source-language CTAs to match the surrounding locale copy.
- infolinguistic · 84% độ tin cậy
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.
Tìm thấy tại đây
Header · <nav>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
German buttons: "Produkte","Lösungen","Community","Ressourcen"; Spanish buttons: "Productos","Soluciones","Comunidad","Recursos".
Terminology consistency
Fail40linguisticImportant concepts should not be translated differently across pages.
- mediumlinguistic · 95% độ tin cậy
Terminology inconsistency
"Figma Socials" appears both untranslated and translated across de pages. Affects 11 sampled pages.
Tìm thấy tại đây
Header · <nav> or <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
"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/
Cách khắc phục
Use one translated label for "Figma Socials" across de pages.
Translation accuracy
Fail72linguisticTarget copy should preserve the source meaning, numbers, and product actions.
- mediumlinguistic · 67% độ tin cậy
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.
Tìm thấy tại đây
Privacy controls · <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
English: "Opt-Out"; German: "Ausschluss"; German longer label: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
Cách khắc phục
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.
- mediumlinguistic · 73% độ tin cậy
German privacy copy reads awkwardly
The sampled German cookie notice contains an unnatural construction around selling and distributing behavioral advertising.
Tìm thấy tại đây
Cookie notice · <p>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
"Wir nutzen Cookies für Verkaufszwecke und Verteilung der verhaltensgebundenen Werbung oder für zielgerichtete Werbung."
Cách khắc phục
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.
- lowlinguistic · 70% độ tin cậy
German terminology and capitalization need review
The privacy notice uses awkward nominal phrasing and borrowed terminology that may not align with polished German style.
Tìm thấy tại đây
Cookie notice · <p>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
"Diese Website verwendet Cookies, Zählpixel und lokale Speicherung zu Performance-, Personalisierungs- und Marketingzwecken."
Cách khắc phục
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.
- mediumcontextual · 76% độ tin cậy
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.
Tìm thấy tại đây
Privacy controls · <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
Source button: "Opt-Out"; German button: "Ausschluss"; German extended button: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
Cách khắc phục
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.
- infocontextual · 45% độ tin cậy
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.
Điều chúng tôi nhận thấy
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.
Cách khắc phục
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.
- mediumcontextual · 70% độ tin cậy
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.
Tìm thấy tại đây
Privacy controls · <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
German buttons include "Ausschluss" and "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
Cách khắc phục
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
Fail40trực quanLonger translations should not create obvious length pressure versus the source UI.
- mediumvisual · 88% độ tin cậy
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.
Tìm thấy tại đây
Heading · heading
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
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/
Cách khắc phục
Shorten the translation or give the control more room so the longer copy does not overflow.
Font and script support
Fail62trực quanTypography should support the target script without generic fallback-only stacks, tofu glyphs, or missing CJK fonts.
- highvisual · 95% độ tin cậy
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.
Tìm thấy tại đây
Page body · font-family
https://www.figma.com/ja-jp/Điều chúng tôi nhận thấy
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/
Cách khắc phục
Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
Localized images and assets
Fail50trực quanLanguage-specific images and alt text should match the page locale.
- infovisual · 35% độ tin cậy
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.
Điều chúng tôi nhận thấy
The provided page preview lists titles, buttons, headings, and text, but contains no <img> markup or alt-text values.
Cách khắc phục
Inspect localized pages for image sources, embedded text, and alt attributes, then verify that language-specific assets and descriptions match each locale.
Visual hierarchy
Fail55trực quanLocalization should not make headings or CTAs lose scanability.
- lowvisual · 80% độ tin cậy
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 6 sampled pages.
Tìm thấy tại đây
Page body · heading
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
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/
Cách khắc phục
Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
Fail70trực quanRepeated components should stay visually consistent across locales.
- lowvisual · 95% độ tin cậy
Repeated components differ across locales
Button counts differ between the source locale and ai.
Tìm thấy tại đây
Page body · <button>
https://www.figma.com/ai/Điều chúng tôi nhận thấy
Source locale has 7 buttons; ai has 13.
Cách khắc phục
Keep the same repeated controls across locales, or drop unused ones on purpose.
Text overflow
Fail68trực quanText should not clip, truncate unexpectedly, or overflow buttons and navigation.
- lowvisual · 62% độ tin cậy
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.
Tìm thấy tại đây
Privacy controls · <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" versus the English "Do Not Sell/Share My Personal Info + Opt-Out".
Cách khắc phục
Test the label at mobile and desktop widths; allow wrapping or expand the control instead of clipping or truncating text.
Layout breakage
Fail68trực quanLocalized pages should not overlap, break grids, or overflow modals.
- lowvisual · 60% độ tin cậy
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.
Tìm thấy tại đây
Privacy controls · <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" is shown as a button label.
Cách khắc phục
Check the privacy control and any consent modal at narrow widths, and support flexible button sizing and wrapping.
Responsive localisation
Fail68trực quanLocalized layouts should hold up across mobile, tablet, and desktop widths.
- infovisual · 58% độ tin cậy
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.
Tìm thấy tại đây
Privacy controls · <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
The evidence shows the long German label "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" but no viewport or layout output.
Cách khắc phục
Run mobile, tablet, and desktop visual checks for all locales with long navigation and privacy labels.
Các kiểm tra đã đạt (5)
Không áp dụng (4)
Các ngôn ngữ được phát hiện
Toàn bộ phát hiện
- hightechnical · 95% độ tin cậy
URL locale and html lang disagree
Path locale ai expects html lang ai, but the page declares en.
Tìm thấy tại đây
Document head · <html lang>
https://www.figma.com/ai/Điều chúng tôi nhận thấy
<html lang="en"> while the path locale is ai
Cách khắc phục
Set html lang="ai" so it matches this page’s URL locale.
- hightechnical · 95% độ tin cậy
Language links return to the homepage
Locale links were found, but they appear to drop the current page path.
Tìm thấy tại đây
Header · <nav> language links
https://www.figma.com/Điều chúng tôi nhận thấy
<a href="https://www.figma.com/ai/">AI workflows</a> drops the current page path
Cách khắc phục
Point language-switcher links at the equivalent localized path, not the locale homepage.
- mediumtechnical · 88% độ tin cậy
Sitemap omits some published locales
Locale-prefixed pages for ai do not appear in sampled sitemap URLs.
Tìm thấy tại đây
Sitemap · sitemap.xml
https://www.figma.com/sitemap.xmlĐiều chúng tôi nhận thấy
Sitemap locales in sample: id, de, es, fr, it, nl, pl, pt, hi, ja, ko, th; missing: ai
Cách khắc phục
Include URLs for every published locale prefix in the sitemap.
- lowtechnical · 95% độ tin cậy
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Tìm thấy tại đây
JSON-LD · <script type="application/ld+json">
https://www.figma.com/Điều chúng tôi nhận thấy
Organization is present but inLanguage is missing
Cách khắc phục
Set JSON-LD inLanguage to match each page locale.
- highlinguistic · 92% độ tin cậy
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 10 sampled pages.
Tìm thấy tại đây
Pricing hero · <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
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/
Cách khắc phục
Translate leftover source-language CTAs to match the surrounding locale copy.
- mediumlinguistic · 95% độ tin cậy
Terminology inconsistency
"Figma Socials" appears both untranslated and translated across de pages. Affects 11 sampled pages.
Tìm thấy tại đây
Header · <nav> or <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
"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/
Cách khắc phục
Use one translated label for "Figma Socials" across de pages.
- mediumvisual · 88% độ tin cậy
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.
Tìm thấy tại đây
Heading · heading
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
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/
Cách khắc phục
Shorten the translation or give the control more room so the longer copy does not overflow.
- highvisual · 95% độ tin cậy
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.
Tìm thấy tại đây
Page body · font-family
https://www.figma.com/ja-jp/Điều chúng tôi nhận thấy
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/
Cách khắc phục
Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
- lowvisual · 80% độ tin cậy
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 6 sampled pages.
Tìm thấy tại đây
Page body · heading
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
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/
Cách khắc phục
Shorten the heading so it does not crowd the visual hierarchy.
- lowvisual · 95% độ tin cậy
Repeated components differ across locales
Button counts differ between the source locale and ai.
Tìm thấy tại đây
Page body · <button>
https://www.figma.com/ai/Điều chúng tôi nhận thấy
Source locale has 7 buttons; ai has 13.
Cách khắc phục
Keep the same repeated controls across locales, or drop unused ones on purpose.
- infotechnical · 42% độ tin cậy
Locale-sensitive values are not shown
The provided evidence contains no dates, numbers, currencies, or calendar values, so international formatting cannot be verified.
Điều chúng tôi nhận thấy
The preview shows page titles, buttons, headings, and cookie text, but no dates, numbers, currency amounts, or calendar values.
Cách khắc phục
Audit representative localized pages for date, number, currency, digit, and calendar formatting.
- infotechnical · 82% độ tin cậy
Page language metadata matches sampled locales
The sampled German and Spanish pages expose matching htmlLang values, supporting correct language metadata.
Tìm thấy tại đây
Document root · <html>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
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% độ tin cậy
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.
Tìm thấy tại đây
Header · <nav>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
German buttons: "Produkte","Lösungen","Community","Ressourcen"; Spanish buttons: "Productos","Soluciones","Comunidad","Recursos".
- mediumlinguistic · 67% độ tin cậy
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.
Tìm thấy tại đây
Privacy controls · <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
English: "Opt-Out"; German: "Ausschluss"; German longer label: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
Cách khắc phục
Use established German consent terminology such as “Ablehnen” or “Opt-out” consistently, and validate it with German legal and UX reviewers.
- mediumlinguistic · 73% độ tin cậy
German privacy copy reads awkwardly
The sampled German cookie notice contains an unnatural construction around selling and distributing behavioral advertising.
Tìm thấy tại đây
Cookie notice · <p>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
"Wir nutzen Cookies für Verkaufszwecke und Verteilung der verhaltensgebundenen Werbung oder für zielgerichtete Werbung."
Cách khắc phục
Rewrite the sentence in idiomatic German and have a native copy editor review the full privacy notice.
- lowlinguistic · 70% độ tin cậy
German terminology and capitalization need review
The privacy notice uses awkward nominal phrasing and borrowed terminology that may not align with polished German style.
Tìm thấy tại đây
Cookie notice · <p>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
"Diese Website verwendet Cookies, Zählpixel und lokale Speicherung zu Performance-, Personalisierungs- und Marketingzwecken."
Cách khắc phục
Review the sentence for idiomatic German, including terminology such as “Performance” and the construction after “Speicherung”.
- mediumcontextual · 76% độ tin cậy
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.
Tìm thấy tại đây
Privacy controls · <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
Source button: "Opt-Out"; German button: "Ausschluss"; German extended button: "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
Cách khắc phục
Replace “Ausschluss” with a clear action-oriented German label that explicitly conveys opting out of sale or sharing.
- infocontextual · 45% độ tin cậy
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.
Điều chúng tôi nhận thấy
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.
Cách khắc phục
Review regional pages for market-appropriate formats, terminology, examples, and legal or privacy language.
- mediumcontextual · 70% độ tin cậy
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.
Tìm thấy tại đây
Privacy controls · <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
German buttons include "Ausschluss" and "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss".
Cách khắc phục
Use a concise, recognizable consent action in the button and keep the longer explanation in supporting text or an accessible label.
- infovisual · 35% độ tin cậy
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.
Điều chúng tôi nhận thấy
The provided page preview lists titles, buttons, headings, and text, but contains no <img> markup or alt-text values.
Cách khắc phục
Inspect localized pages for image sources, embedded text, and alt attributes, then verify that language-specific assets and descriptions match each locale.
- lowvisual · 62% độ tin cậy
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.
Tìm thấy tại đây
Privacy controls · <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" versus the English "Do Not Sell/Share My Personal Info + Opt-Out".
Cách khắc phục
Test the label at mobile and desktop widths; allow wrapping or expand the control instead of clipping or truncating text.
- lowvisual · 60% độ tin cậy
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.
Tìm thấy tại đây
Privacy controls · <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
"Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" is shown as a button label.
Cách khắc phục
Check the privacy control and any consent modal at narrow widths, and support flexible button sizing and wrapping.
- infovisual · 58% độ tin cậy
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.
Tìm thấy tại đây
Privacy controls · <button>
https://www.figma.com/de-de/Điều chúng tôi nhận thấy
The evidence shows the long German label "Meine persönlichen Daten nicht verkaufen/weitergeben + Ausschluss" but no viewport or layout output.
Cách khắc phục
Run mobile, tablet, and desktop visual checks for all locales with long navigation and privacy labels.
Các trang được lấy mẫu
- 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
Gửi cho tôi bản tóm tắt qua email
Không bắt buộc. Nhập email công việc của bạn và chúng tôi sẽ gửi cho bạn bản tóm tắt ngắn gọn về báo cáo công khai này.
Bước tiếp theo
Nền tảng vững chắc nhưng vẫn còn dư địa để cải thiện. Hãy tạo một không gian làm việc để liên tục theo dõi bản địa hóa hoặc đặt lịch đánh giá kiểm tra.