Localisation report
canva.com
Product: Canva appears to be a digital design service. The available page indicates users can create designs, but provides no further product details.
Brand voice: reassuring, service-oriented
Localisation score
39/100
PoorSignificant localisation gaps are affecting the experience.
Sampled 2 pages across technical, linguistic, contextual, and visual localisation credits. How we score localisation audits
Rank #24 of 24 public audits
Could not inspect page language
No successful HTML pages were available to check html lang.
Found here
Document head · <html lang>
What we saw
The crawl returned no successful HTML pages to inspect.
How to fix it
Make the sampled localisation URLs return 200 HTML so html lang can be checked.
Page returned HTTP 403
A sampled localisation URL did not return a successful HTML response. Affects 2 sampled pages.
Found here
Sampled page · document
https://www.canva.com/What we saw
HTTP 403 Seen on 2 pages, e.g. https://www.canva.com/, https://www.canva.com/en/help/troubleshoot-cloudflare-error/
How to fix it
Fix the localized URL so it returns a successful HTML response.
Only one locale signal detected
The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
Found here
Sampled pages · document
https://www.canva.com/What we saw
Detected locale signals: en
How to fix it
Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.
2 passed · 15 to fix · 18 not applicable
Locale detection
Fail0technicalPages should declare a correct html lang that matches the URL and content locale.
Could not inspect page language
No successful HTML pages were available to check html lang.
Found here
Document head · <html lang>
What we saw
The crawl returned no successful HTML pages to inspect.
How to fix it
Make the sampled localisation URLs return 200 HTML so html lang can be checked.
Locale routing
Fail48technicalLocalized pages should use a consistent URL structure and resolve successfully.
Page returned HTTP 403
A sampled localisation URL did not return a successful HTML response. Affects 2 sampled pages.
Found here
Sampled page · document
https://www.canva.com/What we saw
HTTP 403 Seen on 2 pages, e.g. https://www.canva.com/, https://www.canva.com/en/help/troubleshoot-cloudflare-error/
How to fix it
Fix the localized URL so it returns a successful HTML response.
Only one locale signal detected
The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
Found here
Sampled pages · document
https://www.canva.com/What we saw
Detected locale signals: en
How to fix it
Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.
Canonical URLs
Fail72technicalCanonical URLs should represent the localized page, not a different locale.
Canonical URLs are missing
Sampled pages did not declare a canonical URL.
Found here
Document head · <link rel="canonical">
What we saw
No <link rel="canonical"> was found on sampled pages.
How to fix it
Add a canonical URL that points at this locale’s own page.
International formatting
Fail50technicalDates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.
Formatting examples unavailable
Both sampled URLs return a Cloudflare verification page, so dates, numbers, currencies, and calendar conventions cannot be assessed.
Found here
Page response · <html>
https://www.canva.com/What we saw
"status":403,"reason":"no_formatting_examples"
How to fix it
Review the rendered localized pages and test representative dates, numbers, currencies, and calendar values.
Accessibility localisation
Fail55technicallang, aria-label, and alt text should match the page locale.
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.
Found here
Document root · <html>
https://www.canva.com/What we saw
"htmlLang":"en","dir":"ltr","buttons":[]
How to fix it
Review rendered controls, images, and landmarks to verify that accessible names and alternative text are in English.
Terminology consistency
Fail50linguisticImportant concepts should not be translated differently across pages.
No term comparison possible
The available responses contain only a Cloudflare verification message and provide no clear cross-page terminology clusters.
Found here
Page body · <body>
https://www.canva.com/What we saw
"reason":"no_clear_term_clusters"
How to fix it
Compare repeated product, navigation, and support terms across accessible localized pages.
Translation accuracy
Fail50linguisticTarget copy should preserve the source meaning, numbers, and product actions.
Source-target accuracy cannot be verified
Only an English verification message is available; there is no source copy or translated product content to compare.
Found here
Page body · <body>
https://www.canva.com/What we saw
"status":403,"title":"Just a moment..."
How to fix it
Restore access to the localized content and compare headings, actions, numbers, and meaning against the source copy.
Fluency
Fail60linguisticCopy should sound natural, without grammar issues or machine-translation artifacts.
Limited copy sample
The exposed verification text reads naturally enough, but it is system text rather than representative localized website copy.
Found here
Verification message · <h1>
https://www.canva.com/What we saw
We’ll have you designing again soon
How to fix it
Evaluate fluency using the rendered product and help content, not only the access-verification message.
Brand voice
Fail50linguisticLocalized copy should preserve the intended tone of the source.
Brand voice unavailable
The responses expose only a generic verification page, so the intended localized brand tone cannot be compared or assessed.
Found here
Verification page · <body>
https://www.canva.com/What we saw
"headings":["We’ll have you designing again soon"]
How to fix it
Review accessible marketing, product, and support copy for consistency with Canva’s intended localized voice.
Grammar and style
Fail60linguisticLocale-specific capitalization, punctuation, formality, and agreement should be correct.
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.
Found here
Verification message · <h1>
https://www.canva.com/What we saw
We’ll have you designing again soon
How to fix it
Check complete localized page content for locale-specific punctuation, capitalization, formality, and grammatical agreement.
Cultural adaptation
Fail50contextualCurrency, dates, addresses, and local examples should fit the market.
Cultural signals unavailable
No localized currency, date, address, market example, or other cultural content is visible in the 403 responses.
Found here
Page body · <body>
https://www.canva.com/What we saw
"reason":"no_cultural_signals"
How to fix it
Review market-specific examples, formats, and references on accessible localized pages.
Visual hierarchy
Fail50visualLocalization should not make headings or CTAs lose scanability.
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.
Found here
Verification message · <h1>
https://www.canva.com/What we saw
"headings":["We’ll have you designing again soon"]
How to fix it
Inspect the rendered localized pages to verify heading levels, CTA prominence, and scanability.
Text overflow
Fail50visualText should not clip, truncate unexpectedly, or overflow buttons and navigation.
Rendered layout unavailable
No rendered layout or localized controls are available, so clipping and text overflow cannot be verified.
Found here
Page layout · <body>
https://www.canva.com/What we saw
"reason":"no_rendered_layout"
How to fix it
Test localized headings, buttons, navigation labels, and form fields at representative viewport sizes.
Layout breakage
Fail50visualLocalized pages should not overlap, break grids, or overflow modals.
Layout integrity cannot be assessed
Both sampled pages return status 403 and provide no rendered localized layout for checking overlap, grids, or modals.
Found here
Page layout · <body>
https://www.canva.com/What we saw
"status":403,"reason":"no_rendered_layout"
How to fix it
Load the localized pages successfully and test grids, overlays, modals, and long translated strings.
Responsive localisation
Fail50visualLocalized layouts should hold up across mobile, tablet, and desktop widths.
Responsive behavior unavailable
The evidence contains no rendered layouts or viewport comparisons, so mobile, tablet, and desktop behavior cannot be assessed.
Found here
Responsive layout · <body>
https://www.canva.com/What we saw
"reason":"no_rendered_layout"
How to fix it
Compare accessible localized pages at mobile, tablet, and desktop widths using representative long strings.
Could not inspect page language
No successful HTML pages were available to check html lang.
Found here
Document head · <html lang>
What we saw
The crawl returned no successful HTML pages to inspect.
How to fix it
Make the sampled localisation URLs return 200 HTML so html lang can be checked.
Page returned HTTP 403
A sampled localisation URL did not return a successful HTML response. Affects 2 sampled pages.
Found here
Sampled page · document
https://www.canva.com/What we saw
HTTP 403 Seen on 2 pages, e.g. https://www.canva.com/, https://www.canva.com/en/help/troubleshoot-cloudflare-error/
How to fix it
Fix the localized URL so it returns a successful HTML response.
Only one locale signal detected
The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
Found here
Sampled pages · document
https://www.canva.com/What we saw
Detected locale signals: en
How to fix it
Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.
Canonical URLs are missing
Sampled pages did not declare a canonical URL.
Found here
Document head · <link rel="canonical">
What we saw
No <link rel="canonical"> was found on sampled pages.
How to fix it
Add a canonical URL that points at this locale’s own page.
Formatting examples unavailable
Both sampled URLs return a Cloudflare verification page, so dates, numbers, currencies, and calendar conventions cannot be assessed.
Found here
Page response · <html>
https://www.canva.com/What we saw
"status":403,"reason":"no_formatting_examples"
How to fix it
Review the rendered localized pages and test representative dates, numbers, currencies, and calendar values.
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.
Found here
Document root · <html>
https://www.canva.com/What we saw
"htmlLang":"en","dir":"ltr","buttons":[]
How to fix it
Review rendered controls, images, and landmarks to verify that accessible names and alternative text are in English.
No term comparison possible
The available responses contain only a Cloudflare verification message and provide no clear cross-page terminology clusters.
Found here
Page body · <body>
https://www.canva.com/What we saw
"reason":"no_clear_term_clusters"
How to fix it
Compare repeated product, navigation, and support terms across accessible localized pages.
Source-target accuracy cannot be verified
Only an English verification message is available; there is no source copy or translated product content to compare.
Found here
Page body · <body>
https://www.canva.com/What we saw
"status":403,"title":"Just a moment..."
How to fix it
Restore access to the localized content and compare headings, actions, numbers, and meaning against the source copy.
Limited copy sample
The exposed verification text reads naturally enough, but it is system text rather than representative localized website copy.
Found here
Verification message · <h1>
https://www.canva.com/What we saw
We’ll have you designing again soon
How to fix it
Evaluate fluency using the rendered product and help content, not only the access-verification message.
Brand voice unavailable
The responses expose only a generic verification page, so the intended localized brand tone cannot be compared or assessed.
Found here
Verification page · <body>
https://www.canva.com/What we saw
"headings":["We’ll have you designing again soon"]
How to fix it
Review accessible marketing, product, and support copy for consistency with Canva’s intended localized voice.
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.
Found here
Verification message · <h1>
https://www.canva.com/What we saw
We’ll have you designing again soon
How to fix it
Check complete localized page content for locale-specific punctuation, capitalization, formality, and grammatical agreement.
Cultural signals unavailable
No localized currency, date, address, market example, or other cultural content is visible in the 403 responses.
Found here
Page body · <body>
https://www.canva.com/What we saw
"reason":"no_cultural_signals"
How to fix it
Review market-specific examples, formats, and references on accessible localized pages.
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.
Found here
Verification message · <h1>
https://www.canva.com/What we saw
"headings":["We’ll have you designing again soon"]
How to fix it
Inspect the rendered localized pages to verify heading levels, CTA prominence, and scanability.
Rendered layout unavailable
No rendered layout or localized controls are available, so clipping and text overflow cannot be verified.
Found here
Page layout · <body>
https://www.canva.com/What we saw
"reason":"no_rendered_layout"
How to fix it
Test localized headings, buttons, navigation labels, and form fields at representative viewport sizes.
Layout integrity cannot be assessed
Both sampled pages return status 403 and provide no rendered localized layout for checking overlap, grids, or modals.
Found here
Page layout · <body>
https://www.canva.com/What we saw
"status":403,"reason":"no_rendered_layout"
How to fix it
Load the localized pages successfully and test grids, overlays, modals, and long translated strings.
Responsive behavior unavailable
The evidence contains no rendered layouts or viewport comparisons, so mobile, tablet, and desktop behavior cannot be assessed.
Found here
Responsive layout · <body>
https://www.canva.com/What we saw
"reason":"no_rendered_layout"
How to fix it
Compare accessible localized pages at mobile, tablet, and desktop widths using representative long strings.
Optional. Enter your work email and we will send a concise summary of this public report.
Critical gaps showed up. Create a workspace to run a deeper registered audit, or book a review with our team.
