Demander une démo

Rapport de localisation

Canva

Design software

canva.com

Produit: Canva appears to be a digital design service. The available page indicates users can create designs, but provides no further product details.

Voix de marque: reassuring, service-oriented

Score de localisation

39/100

Médiocre

Des lacunes importantes en matière de localisation affectent l’expérience.

  • 54Audit technique
  • 62Audit linguistique
  • 50Audit contextuel
  • 50Audit visuel
Audité: 8/15/2026Portée: Échantillon intelligent public · crédits techniques, linguistiques, contextuels et visuelsConfiance: Contrôle indicatif de l’état de santé à partir de pages échantillonnées — il ne s’agit pas d’une exploration complète du site.

2 pages échantillonnées parmi les crédits de localisation techniques, linguistiques, contextuels et visuels. Comment nous évaluons les audits de localisation

Comment vous vous comparez

Rang #22 sur 22 audits publics

Top 5 % des domaines auditésMoyenne publique : 68/100

À corriger en priorité

  • criticaltechnical · 100 % de confiance

    Could not inspect page language

    No successful HTML pages were available to check html lang.

    Trouvé ici

    Document head · <html lang>

    Ce que nous avons constaté

    The crawl returned no successful HTML pages to inspect.

    Comment le corriger

    Make the sampled localisation URLs return 200 HTML so html lang can be checked.

  • hightechnical · 100 % de confiance

    Page returned HTTP 403

    A sampled localisation URL did not return a successful HTML response. Affects 2 sampled pages.

    Trouvé ici

    Sampled page · document

    https://www.canva.com/

    Ce que nous avons constaté

    HTTP 403 Seen on 2 pages, e.g. https://www.canva.com/, https://www.canva.com/en/help/troubleshoot-cloudflare-error/

    Comment le corriger

    Fix the localized URL so it returns a successful HTML response.

  • mediumtechnical · 90 % de confiance

    Only one locale signal detected

    The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).

    Trouvé ici

    Sampled pages · document

    https://www.canva.com/

    Ce que nous avons constaté

    Detected locale signals: en

    Comment le corriger

    Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.

Critères d’audit

2 réussis · 15 à corriger · 18 non applicable

À examiner (15)

  • Locale detection

    Échec0technique

    Pages should declare a correct html lang that matches the URL and content locale.

    • criticaltechnical · 100 % de confiance

      Could not inspect page language

      No successful HTML pages were available to check html lang.

      Trouvé ici

      Document head · <html lang>

      Ce que nous avons constaté

      The crawl returned no successful HTML pages to inspect.

      Comment le corriger

      Make the sampled localisation URLs return 200 HTML so html lang can be checked.

  • Locale routing

    Échec48technique

    Localized pages should use a consistent URL structure and resolve successfully.

    • hightechnical · 100 % de confiance

      Page returned HTTP 403

      A sampled localisation URL did not return a successful HTML response. Affects 2 sampled pages.

      Trouvé ici

      Sampled page · document

      https://www.canva.com/

      Ce que nous avons constaté

      HTTP 403 Seen on 2 pages, e.g. https://www.canva.com/, https://www.canva.com/en/help/troubleshoot-cloudflare-error/

      Comment le corriger

      Fix the localized URL so it returns a successful HTML response.

    • mediumtechnical · 90 % de confiance

      Only one locale signal detected

      The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).

      Trouvé ici

      Sampled pages · document

      https://www.canva.com/

      Ce que nous avons constaté

      Detected locale signals: en

      Comment le corriger

      Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.

  • Canonical URLs

    Échec72technique

    Canonical URLs should represent the localized page, not a different locale.

    • mediumtechnical · 95 % de confiance

      Canonical URLs are missing

      Sampled pages did not declare a canonical URL.

      Trouvé ici

      Document head · <link rel="canonical">

      Ce que nous avons constaté

      No <link rel="canonical"> was found on sampled pages.

      Comment le corriger

      Add a canonical URL that points at this locale’s own page.

  • International formatting

    Échec50technique

    Dates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.

    • infotechnical · 92 % de confiance

      Formatting examples unavailable

      Both sampled URLs return a Cloudflare verification page, so dates, numbers, currencies, and calendar conventions cannot be assessed.

      Trouvé ici

      Page response · <html>

      https://www.canva.com/

      Ce que nous avons constaté

      "status":403,"reason":"no_formatting_examples"

      Comment le corriger

      Review the rendered localized pages and test representative dates, numbers, currencies, and calendar values.

  • Accessibility localisation

    Échec55technique

    lang, aria-label, and alt text should match the page locale.

    • infotechnical · 88 % de confiance

      Accessible names unavailable

      The page declares English and left-to-right direction, but the 403 response exposes no buttons, alt text, or ARIA labels for review.

      Trouvé ici

      Document root · <html>

      https://www.canva.com/

      Ce que nous avons constaté

      "htmlLang":"en","dir":"ltr","buttons":[]

      Comment le corriger

      Review rendered controls, images, and landmarks to verify that accessible names and alternative text are in English.

  • Terminology consistency

    Échec50linguistique

    Important concepts should not be translated differently across pages.

    • infolinguistic · 93 % de confiance

      No term comparison possible

      The available responses contain only a Cloudflare verification message and provide no clear cross-page terminology clusters.

      Trouvé ici

      Page body · <body>

      https://www.canva.com/

      Ce que nous avons constaté

      "reason":"no_clear_term_clusters"

      Comment le corriger

      Compare repeated product, navigation, and support terms across accessible localized pages.

  • Translation accuracy

    Échec50linguistique

    Target copy should preserve the source meaning, numbers, and product actions.

    • infolinguistic · 94 % de confiance

      Source-target accuracy cannot be verified

      Only an English verification message is available; there is no source copy or translated product content to compare.

      Trouvé ici

      Page body · <body>

      https://www.canva.com/

      Ce que nous avons constaté

      "status":403,"title":"Just a moment..."

      Comment le corriger

      Restore access to the localized content and compare headings, actions, numbers, and meaning against the source copy.

  • Fluency

    Échec60linguistique

    Copy should sound natural, without grammar issues or machine-translation artifacts.

    • infolinguistic · 72 % de confiance

      Limited copy sample

      The exposed verification text reads naturally enough, but it is system text rather than representative localized website copy.

      Trouvé ici

      Verification message · <h1>

      https://www.canva.com/

      Ce que nous avons constaté

      We’ll have you designing again soon

      Comment le corriger

      Evaluate fluency using the rendered product and help content, not only the access-verification message.

  • Brand voice

    Échec50linguistique

    Localized copy should preserve the intended tone of the source.

    • infolinguistic · 91 % de confiance

      Brand voice unavailable

      The responses expose only a generic verification page, so the intended localized brand tone cannot be compared or assessed.

      Trouvé ici

      Verification page · <body>

      https://www.canva.com/

      Ce que nous avons constaté

      "headings":["We’ll have you designing again soon"]

      Comment le corriger

      Review accessible marketing, product, and support copy for consistency with Canva’s intended localized voice.

  • Grammar and style

    Échec60linguistique

    Locale-specific capitalization, punctuation, formality, and agreement should be correct.

    • infolinguistic · 74 % de confiance

      Insufficient locale copy

      The short English verification message shows no obvious grammar issue, but it is insufficient to assess broader capitalization, punctuation, formality, or agreement.

      Trouvé ici

      Verification message · <h1>

      https://www.canva.com/

      Ce que nous avons constaté

      We’ll have you designing again soon

      Comment le corriger

      Check complete localized page content for locale-specific punctuation, capitalization, formality, and grammatical agreement.

  • Cultural adaptation

    Échec50contextuel

    Currency, dates, addresses, and local examples should fit the market.

    • infocontextual · 93 % de confiance

      Cultural signals unavailable

      No localized currency, date, address, market example, or other cultural content is visible in the 403 responses.

      Trouvé ici

      Page body · <body>

      https://www.canva.com/

      Ce que nous avons constaté

      "reason":"no_cultural_signals"

      Comment le corriger

      Review market-specific examples, formats, and references on accessible localized pages.

  • Visual hierarchy

    Échec50visuel

    Localization should not make headings or CTAs lose scanability.

    • infovisual · 70 % de confiance

      Hierarchy cannot be assessed

      The response exposes only one verification heading and no localized navigation or CTA structure, so hierarchy in the actual site is unknown.

      Trouvé ici

      Verification message · <h1>

      https://www.canva.com/

      Ce que nous avons constaté

      "headings":["We’ll have you designing again soon"]

      Comment le corriger

      Inspect the rendered localized pages to verify heading levels, CTA prominence, and scanability.

  • Text overflow

    Échec50visuel

    Text should not clip, truncate unexpectedly, or overflow buttons and navigation.

    • infovisual · 65 % de confiance

      Rendered layout unavailable

      No rendered layout or localized controls are available, so clipping and text overflow cannot be verified.

      Trouvé ici

      Page layout · <body>

      https://www.canva.com/

      Ce que nous avons constaté

      "reason":"no_rendered_layout"

      Comment le corriger

      Test localized headings, buttons, navigation labels, and form fields at representative viewport sizes.

  • Layout breakage

    Échec50visuel

    Localized pages should not overlap, break grids, or overflow modals.

    • infovisual · 65 % de confiance

      Layout integrity cannot be assessed

      Both sampled pages return status 403 and provide no rendered localized layout for checking overlap, grids, or modals.

      Trouvé ici

      Page layout · <body>

      https://www.canva.com/

      Ce que nous avons constaté

      "status":403,"reason":"no_rendered_layout"

      Comment le corriger

      Load the localized pages successfully and test grids, overlays, modals, and long translated strings.

  • Responsive localisation

    Échec50visuel

    Localized layouts should hold up across mobile, tablet, and desktop widths.

    • infovisual · 65 % de confiance

      Responsive behavior unavailable

      The evidence contains no rendered layouts or viewport comparisons, so mobile, tablet, and desktop behavior cannot be assessed.

      Trouvé ici

      Responsive layout · <body>

      https://www.canva.com/

      Ce que nous avons constaté

      "reason":"no_rendered_layout"

      Comment le corriger

      Compare accessible localized pages at mobile, tablet, and desktop widths using representative long strings.

Audits réussis (2)

Non applicable (18)

Paramètres régionaux détectés

en (html_lang)

Résultats complets

  • criticaltechnical · 100 % de confiance

    Could not inspect page language

    No successful HTML pages were available to check html lang.

    Trouvé ici

    Document head · <html lang>

    Ce que nous avons constaté

    The crawl returned no successful HTML pages to inspect.

    Comment le corriger

    Make the sampled localisation URLs return 200 HTML so html lang can be checked.

  • hightechnical · 100 % de confiance

    Page returned HTTP 403

    A sampled localisation URL did not return a successful HTML response. Affects 2 sampled pages.

    Trouvé ici

    Sampled page · document

    https://www.canva.com/

    Ce que nous avons constaté

    HTTP 403 Seen on 2 pages, e.g. https://www.canva.com/, https://www.canva.com/en/help/troubleshoot-cloudflare-error/

    Comment le corriger

    Fix the localized URL so it returns a successful HTML response.

  • mediumtechnical · 90 % de confiance

    Only one locale signal detected

    The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).

    Trouvé ici

    Sampled pages · document

    https://www.canva.com/

    Ce que nous avons constaté

    Detected locale signals: en

    Comment le corriger

    Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.

  • mediumtechnical · 95 % de confiance

    Canonical URLs are missing

    Sampled pages did not declare a canonical URL.

    Trouvé ici

    Document head · <link rel="canonical">

    Ce que nous avons constaté

    No <link rel="canonical"> was found on sampled pages.

    Comment le corriger

    Add a canonical URL that points at this locale’s own page.

  • infotechnical · 92 % de confiance

    Formatting examples unavailable

    Both sampled URLs return a Cloudflare verification page, so dates, numbers, currencies, and calendar conventions cannot be assessed.

    Trouvé ici

    Page response · <html>

    https://www.canva.com/

    Ce que nous avons constaté

    "status":403,"reason":"no_formatting_examples"

    Comment le corriger

    Review the rendered localized pages and test representative dates, numbers, currencies, and calendar values.

  • infotechnical · 88 % de confiance

    Accessible names unavailable

    The page declares English and left-to-right direction, but the 403 response exposes no buttons, alt text, or ARIA labels for review.

    Trouvé ici

    Document root · <html>

    https://www.canva.com/

    Ce que nous avons constaté

    "htmlLang":"en","dir":"ltr","buttons":[]

    Comment le corriger

    Review rendered controls, images, and landmarks to verify that accessible names and alternative text are in English.

  • infolinguistic · 93 % de confiance

    No term comparison possible

    The available responses contain only a Cloudflare verification message and provide no clear cross-page terminology clusters.

    Trouvé ici

    Page body · <body>

    https://www.canva.com/

    Ce que nous avons constaté

    "reason":"no_clear_term_clusters"

    Comment le corriger

    Compare repeated product, navigation, and support terms across accessible localized pages.

  • infolinguistic · 94 % de confiance

    Source-target accuracy cannot be verified

    Only an English verification message is available; there is no source copy or translated product content to compare.

    Trouvé ici

    Page body · <body>

    https://www.canva.com/

    Ce que nous avons constaté

    "status":403,"title":"Just a moment..."

    Comment le corriger

    Restore access to the localized content and compare headings, actions, numbers, and meaning against the source copy.

  • infolinguistic · 72 % de confiance

    Limited copy sample

    The exposed verification text reads naturally enough, but it is system text rather than representative localized website copy.

    Trouvé ici

    Verification message · <h1>

    https://www.canva.com/

    Ce que nous avons constaté

    We’ll have you designing again soon

    Comment le corriger

    Evaluate fluency using the rendered product and help content, not only the access-verification message.

  • infolinguistic · 91 % de confiance

    Brand voice unavailable

    The responses expose only a generic verification page, so the intended localized brand tone cannot be compared or assessed.

    Trouvé ici

    Verification page · <body>

    https://www.canva.com/

    Ce que nous avons constaté

    "headings":["We’ll have you designing again soon"]

    Comment le corriger

    Review accessible marketing, product, and support copy for consistency with Canva’s intended localized voice.

  • infolinguistic · 74 % de confiance

    Insufficient locale copy

    The short English verification message shows no obvious grammar issue, but it is insufficient to assess broader capitalization, punctuation, formality, or agreement.

    Trouvé ici

    Verification message · <h1>

    https://www.canva.com/

    Ce que nous avons constaté

    We’ll have you designing again soon

    Comment le corriger

    Check complete localized page content for locale-specific punctuation, capitalization, formality, and grammatical agreement.

  • infocontextual · 93 % de confiance

    Cultural signals unavailable

    No localized currency, date, address, market example, or other cultural content is visible in the 403 responses.

    Trouvé ici

    Page body · <body>

    https://www.canva.com/

    Ce que nous avons constaté

    "reason":"no_cultural_signals"

    Comment le corriger

    Review market-specific examples, formats, and references on accessible localized pages.

  • infovisual · 70 % de confiance

    Hierarchy cannot be assessed

    The response exposes only one verification heading and no localized navigation or CTA structure, so hierarchy in the actual site is unknown.

    Trouvé ici

    Verification message · <h1>

    https://www.canva.com/

    Ce que nous avons constaté

    "headings":["We’ll have you designing again soon"]

    Comment le corriger

    Inspect the rendered localized pages to verify heading levels, CTA prominence, and scanability.

  • infovisual · 65 % de confiance

    Rendered layout unavailable

    No rendered layout or localized controls are available, so clipping and text overflow cannot be verified.

    Trouvé ici

    Page layout · <body>

    https://www.canva.com/

    Ce que nous avons constaté

    "reason":"no_rendered_layout"

    Comment le corriger

    Test localized headings, buttons, navigation labels, and form fields at representative viewport sizes.

  • infovisual · 65 % de confiance

    Layout integrity cannot be assessed

    Both sampled pages return status 403 and provide no rendered localized layout for checking overlap, grids, or modals.

    Trouvé ici

    Page layout · <body>

    https://www.canva.com/

    Ce que nous avons constaté

    "status":403,"reason":"no_rendered_layout"

    Comment le corriger

    Load the localized pages successfully and test grids, overlays, modals, and long translated strings.

  • infovisual · 65 % de confiance

    Responsive behavior unavailable

    The evidence contains no rendered layouts or viewport comparisons, so mobile, tablet, and desktop behavior cannot be assessed.

    Trouvé ici

    Responsive layout · <body>

    https://www.canva.com/

    Ce que nous avons constaté

    "reason":"no_rendered_layout"

    Comment le corriger

    Compare accessible localized pages at mobile, tablet, and desktop widths using representative long strings.

Pages échantillonnées

  • 403 · https://www.canva.com/ · lang=en
  • 403 · https://www.canva.com/en/help/troubleshoot-cloudflare-error/ · lang=en

Envoyez-moi un récapitulatif par e-mail

Facultatif. Saisissez votre adresse e-mail professionnelle et nous vous enverrons un résumé concis de ce rapport public.

Étape suivante

Des lacunes critiques ont été détectées. Créez un espace de travail pour effectuer un audit enregistré plus approfondi, ou réservez une revue avec notre équipe.