Rapport de localisation

Heidi

Healthcare AI

heidihealth.com

Produit: Heidi is an AI care partner for clinicians, supporting clinical documentation, note-taking, coding, evidence-based decisions, care gap outreach, and patient communications. It is designed to reduce administrative work across the care journey.

Voix de marque: Reassuring, practical, clinician-focused

Score de localisation

63/100

À améliorer

Les utilisateurs peuvent rencontrer des problèmes de localisation perceptibles.

77Audit technique
42Audit linguistique
73Audit contextuel
61Audit visuel

Audité: 8/17/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.

15 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 #16 sur 22 audits publics

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

Voir le classement complet

À corriger en priorité

highlinguistic · 92 % de confiance
Untranslated call to action
A fr-ca page still uses source-language CTA copy. Affects 5 sampled pages.
Trouvé ici
Primary action · <button>
https://www.heidihealth.com/fr-ca
Ce que nous avons constaté
Primary CTA: "Solutions" Seen on 5 pages, e.g. https://www.heidihealth.com/fr-ca, https://www.heidihealth.com/de-de, https://www.heidihealth.com/fr-fr
Comment le corriger
Translate leftover source-language CTAs to match the surrounding locale copy.
mediumtechnical · 88 % de confiance
Sitemap omits some published locales
Locale-prefixed pages for fr, de, es, it do not appear in sampled sitemap URLs.
Trouvé ici
Sitemap · sitemap.xml
https://www.heidihealth.com/sitemap-index.xml
Ce que nous avons constaté
Sitemap locales in sample: en; missing: fr, de, es, it
Comment le corriger
Include URLs for every published locale prefix in the sitemap.
mediumvisual · 88 % de confiance
Localized text is much longer than the source
A fr string is 171% the length of the source, which often causes overflow. Affects 27 sampled pages.
Trouvé ici
Heading · heading
https://www.heidihealth.com/fr-ca
Ce que nous avons constaté
EN "Relief in every visit" → FR "Heidi — Your AI Care PartnerHeidi AI" (171%) Seen on 5 pages, e.g. https://www.heidihealth.com/fr-ca, https://www.heidihealth.com/fr-fr, https://www.heidihealth.com/de-de
Comment le corriger
Shorten the translation or give the control more room so the longer copy does not overflow.

Critères d’audit

5 réussis · 22 à corriger · 8 non applicable

À examiner (22)

Language switcher
Échec55technique
Visitors should move between locales without losing the current page.
- mediumtechnical · 70 % de confiance
  Current-page preservation is not demonstrated
  The evidence lists many locale variants but only shows homepage URLs, so it does not verify that switching locales preserves a non-homepage path.
  Trouvé ici
  Header · language switcher
  https://www.heidihealth.com/en-us
  Ce que nous avons constaté
  "locales":["de-be","de-ch","de-de",...,"ja-jp"] and the shown page URLs include "https://www.heidihealth.com/en-us" and "https://www.heidihealth.com/en-gb".
  Comment le corriger
  Test the switcher from several non-homepage URLs and confirm that each locale links to the equivalent localized path.
Sitemap
Échec70technique
Like 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 % de confiance
  Sitemap omits some published locales
  Locale-prefixed pages for fr, de, es, it do not appear in sampled sitemap URLs.
  Trouvé ici
  Sitemap · sitemap.xml
  https://www.heidihealth.com/sitemap-index.xml
  Ce que nous avons constaté
  Sitemap locales in sample: en; missing: fr, de, es, it
  Comment le corriger
  Include URLs for every published locale prefix in the sitemap.
Structured data
Échec0technique
JSON-LD inLanguage should match the page locale when structured data is present.
- lowtechnical · 95 % de confiance
  Structured data omits inLanguage
  JSON-LD is present but does not declare inLanguage on sampled pages.
  Trouvé ici
  JSON-LD · <script type="application/ld+json">
  https://www.heidihealth.com/en-us
  Ce que nous avons constaté
  Organization is present but inLanguage is missing
  Comment le corriger
  Set JSON-LD inLanguage to match each page locale.
Accessibility localisation
Échec72technique
lang, aria-label, and alt text should match the page locale.
- infotechnical · 82 % de confiance
  Locale metadata is explicit for the sampled English pages
  The sampled pages expose locale-specific htmlLang values, but the evidence does not expose aria-label or alt attributes for verification.
  Trouvé ici
  Document · <html>
  https://www.heidihealth.com/en-us
  Ce que nous avons constaté
  "htmlLang":"en-us" and "htmlLang":"en-gb"
  Comment le corriger
  Audit aria-label and alt attributes across every locale and ensure their values are translated or otherwise appropriate for the page locale.
Translation completeness
Échec0linguistique
Localized pages should not leave source-language copy in place, except brand names and URLs.
- highlinguistic · 92 % de confiance
  Untranslated call to action
  A fr-ca page still uses source-language CTA copy. Affects 5 sampled pages.
  Trouvé ici
  Primary action · <button>
  https://www.heidihealth.com/fr-ca
  Ce que nous avons constaté
  Primary CTA: "Solutions" Seen on 5 pages, e.g. https://www.heidihealth.com/fr-ca, https://www.heidihealth.com/de-de, https://www.heidihealth.com/fr-fr
  Comment le corriger
  Translate leftover source-language CTAs to match the surrounding locale copy.
Terminology consistency
Échec50linguistique
Important concepts should not be translated differently across pages.
- infolinguistic · 95 % de confiance
  Cross-locale terminology cannot be assessed
  The supplied content shows only English page copy, so consistency of important concepts across translated locales is unverified.
  Trouvé ici
  https://www.heidihealth.com/en-us
  Ce que nous avons constaté
  The sampled page text includes English terms such as "Platform", "Solutions", "Research", and "Get Heidi free"; no translated counterpart is shown.
  Comment le corriger
  Compare repeated product terms across the German, Spanish, French, Italian, and Japanese pages and standardize their translations.
Translation accuracy
Échec50linguistique
Target copy should preserve the source meaning, numbers, and product actions.
- infolinguistic · 95 % de confiance
  Translation accuracy cannot be assessed
  No target-language copy or source-to-target comparison is provided in the evidence.
  Trouvé ici
  https://www.heidihealth.com/en-us
  Ce que nous avons constaté
  The shown titles, headings, buttons, and page text are English, including "The AI Care Partner for clinicians" and "Book a demo".
  Comment le corriger
  Provide paired source and localized strings for review, including all product actions and any numbers or other locale-sensitive content.
Fluency
Échec50linguistique
Copy should sound natural, without grammar issues or machine-translation artifacts.
- infolinguistic · 95 % de confiance
  Localized fluency cannot be assessed
  The evidence contains English copy only and does not show any translated text to evaluate for naturalness or machine-translation artifacts.
  Trouvé ici
  https://www.heidihealth.com/en-us
  Ce que nous avons constaté
  "Relief in every visit The AI Care Partner for clinicians"
  Comment le corriger
  Review rendered copy in each target locale with a native-language reviewer.
Brand voice
Échec50linguistique
Localized copy should preserve the intended tone of the source.
- infolinguistic · 95 % de confiance
  Localized brand voice cannot be assessed
  The English source demonstrates a concise, reassuring tone, but no localized copy is available to determine whether that tone is preserved.
  Trouvé ici
  Hero · <h1>
  https://www.heidihealth.com/en-us
  Ce que nous avons constaté
  "Relief in every visit" and "The AI Care Partner for clinicians"
  Comment le corriger
  Evaluate each localized hero, CTA, and supporting message against the source tone and revise wording that becomes overly formal, technical, or promotional.
Grammar and style
Échec50linguistique
Locale-specific capitalization, punctuation, formality, and agreement should be correct.
- infolinguistic · 95 % de confiance
  Locale-specific grammar and style cannot be assessed
  Only English page strings are shown, so capitalization, punctuation, formality, and agreement in other locales remain unverified.
  Trouvé ici
  https://www.heidihealth.com/en-us
  Ce que nous avons constaté
  The evidence shows English strings such as "Contact us", "Log in", and "Get Heidi free".
  Comment le corriger
  Proofread each locale for its own capitalization, punctuation, formality, and grammatical agreement conventions.
CTA intent
Échec72contextuel
Localized calls to action should communicate the intended product action.
- infocontextual · 82 % de confiance
  English CTA intent is clear in the sampled page
  The sampled English page exposes distinct acquisition and sales actions, but localized CTA intent is not shown for comparison.
  Trouvé ici
  Hero · CTA buttons
  https://www.heidihealth.com/en-us
  Ce que nous avons constaté
  "Get Heidi free" and "Book a demo"
  Comment le corriger
  Verify that every locale preserves the distinction between starting access and requesting a sales demonstration.
UI context
Échec72contextuel
Translations should fit the UI component: button, nav, form, modal, or error.
- infocontextual · 82 % de confiance
  English UI contexts are identifiable
  The evidence identifies navigation controls, search-related controls, and CTAs in English, but provides no translated UI strings for review.
  Trouvé ici
  Header · <nav>
  https://www.heidihealth.com/en-us
  Ce que nous avons constaté
  "Platform", "Solutions", "Resources", "⌘K", "Look up", and "Research"
  Comment le corriger
  Review each translated string in its actual button, navigation, search, or form component and adjust wording to fit the control.
Product context
Échec72contextuel
Language should match product concepts such as plans, settings, and workflows.
- infocontextual · 82 % de confiance
  Product context is clear in the sampled English copy
  The page consistently presents Heidi as an AI care partner for clinicians, but translated product terminology is not provided.
  Trouvé ici
  Hero · <h1>
  https://www.heidihealth.com/en-us
  Ce que nous avons constaté
  "Heidi | Your AI Care Partner for Modern Clinical Practice" and "The AI Care Partner for clinicians"
  Comment le corriger
  Preserve the clinician-focused product meaning and established product terms in every localized workflow and CTA.
Contextual meaning
Échec72contextuel
Strings should be judged in surrounding page and component context, not in isolation.
- infocontextual · 82 % de confiance
  English strings have visible page context
  The evidence places the sampled copy in navigation, hero, and CTA contexts, but does not provide target-language renderings for contextual review.
  Trouvé ici
  Hero · <h1>
  https://www.heidihealth.com/en-us
  Ce que nous avons constaté
  "Relief in every visit", "Get Heidi free", and "Book a demo" appear together in the sampled page text.
  Comment le corriger
  Review localized strings in their surrounding sections and components rather than approving them as isolated translation units.
Audience context
Échec78contextuel
Language should fit the intended audience, such as consumer, enterprise, or developer.
- infocontextual · 88 % de confiance
  The sampled page clearly targets clinicians
  The English title and hero explicitly frame the product for clinical practice and clinicians; localized audience fit is not shown.
  Trouvé ici
  Hero · <h1>
  https://www.heidihealth.com/en-us
  Ce que nous avons constaté
  "Your AI Care Partner for Modern Clinical Practice" and "The AI Care Partner for clinicians"
  Comment le corriger
  Keep clinician-facing terminology and professional positioning consistent across all target locales.
Text expansion
Échec40visuel
Longer translations should not create obvious length pressure versus the source UI.
- mediumvisual · 88 % de confiance
  Localized text is much longer than the source
  A fr string is 171% the length of the source, which often causes overflow. Affects 27 sampled pages.
  Trouvé ici
  Heading · heading
  https://www.heidihealth.com/fr-ca
  Ce que nous avons constaté
  EN "Relief in every visit" → FR "Heidi — Your AI Care PartnerHeidi AI" (171%) Seen on 5 pages, e.g. https://www.heidihealth.com/fr-ca, https://www.heidihealth.com/fr-fr, https://www.heidihealth.com/de-de
  Comment le corriger
  Shorten the translation or give the control more room so the longer copy does not overflow.
Localized images and assets
Échec50visuel
Language-specific images and alt text should match the page locale.
- infovisual · 65 % de confiance
  Localized assets cannot be verified
  The supplied preview does not include image markup, asset names, or alt text, so locale-specific imagery and accessibility text remain unverified.
  Trouvé ici
  https://www.heidihealth.com/en-us
  Comment le corriger
  Inspect image elements and asset variants on each locale page, including their alt attributes, for language and cultural appropriateness.
Visual hierarchy
Échec55visuel
Localization should not make headings or CTAs lose scanability.
- lowvisual · 80 % de confiance
  Heading is excessively long
  A localized heading may crowd the visual hierarchy. Affects 5 sampled pages.
  Trouvé ici
  Page body · heading
  https://www.heidihealth.com/de-de
  Ce que nous avons constaté
  „Seit ich Heidi benutze, kann ich mich dem Patienten besser zuwenden. Ich muss nicht mehr sofort alles stichpunktartig mitschreiben.” Seen on 3 pages, e.g. https://www.heidihealth.com/de-de, https://www.heidihealth.com/fr-fr, https://www.heidihealth.com/it-it
  Comment le corriger
  Shorten the heading so it does not crowd the visual hierarchy.
Component consistency
Échec70visuel
Repeated components should stay visually consistent across locales.
- lowvisual · 95 % de confiance
  Repeated components differ across locales
  Button counts differ between the source locale and fr.
  Trouvé ici
  Page body · <button>
  https://www.heidihealth.com/fr-ca
  Ce que nous avons constaté
  Source locale has 14 buttons; fr has 8.
  Comment le corriger
  Keep the same repeated controls across locales, or drop unused ones on purpose.
Text overflow
Échec70visuel
Text should not clip, truncate unexpectedly, or overflow buttons and navigation.
Layout breakage
Échec70visuel
Localized pages should not overlap, break grids, or overflow modals.
Responsive localisation
Échec70visuel
Localized layouts should hold up across mobile, tablet, and desktop widths.

Audits réussis (5)

Non applicable (8)

Paramètres régionaux détectés

de-be (hreflang)de-ch (hreflang)de-de (hreflang)de-lu (hreflang)en-au (hreflang)en-ca (hreflang)en-gb (hreflang)en-hk (hreflang)en-ie (hreflang)en-my (hreflang)en-nz (hreflang)en-sg (hreflang)en-us (html_lang)en-za (hreflang)es-ar (hreflang)es-es (hreflang)es-mx (hreflang)fr-be (hreflang)fr-ca (hreflang)fr-ch (hreflang)fr-fr (hreflang)fr-lu (hreflang)it-it (hreflang)ja-jp (hreflang)

Résultats complets

mediumtechnical · 88 % de confiance
Sitemap omits some published locales
Locale-prefixed pages for fr, de, es, it do not appear in sampled sitemap URLs.
Trouvé ici
Sitemap · sitemap.xml
https://www.heidihealth.com/sitemap-index.xml
Ce que nous avons constaté
Sitemap locales in sample: en; missing: fr, de, es, it
Comment le corriger
Include URLs for every published locale prefix in the sitemap.
lowtechnical · 95 % de confiance
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Trouvé ici
JSON-LD · <script type="application/ld+json">
https://www.heidihealth.com/en-us
Ce que nous avons constaté
Organization is present but inLanguage is missing
Comment le corriger
Set JSON-LD inLanguage to match each page locale.
highlinguistic · 92 % de confiance
Untranslated call to action
A fr-ca page still uses source-language CTA copy. Affects 5 sampled pages.
Trouvé ici
Primary action · <button>
https://www.heidihealth.com/fr-ca
Ce que nous avons constaté
Primary CTA: "Solutions" Seen on 5 pages, e.g. https://www.heidihealth.com/fr-ca, https://www.heidihealth.com/de-de, https://www.heidihealth.com/fr-fr
Comment le corriger
Translate leftover source-language CTAs to match the surrounding locale copy.
mediumvisual · 88 % de confiance
Localized text is much longer than the source
A fr string is 171% the length of the source, which often causes overflow. Affects 27 sampled pages.
Trouvé ici
Heading · heading
https://www.heidihealth.com/fr-ca
Ce que nous avons constaté
EN "Relief in every visit" → FR "Heidi — Your AI Care PartnerHeidi AI" (171%) Seen on 5 pages, e.g. https://www.heidihealth.com/fr-ca, https://www.heidihealth.com/fr-fr, https://www.heidihealth.com/de-de
Comment le corriger
Shorten the translation or give the control more room so the longer copy does not overflow.
lowvisual · 80 % de confiance
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 5 sampled pages.
Trouvé ici
Page body · heading
https://www.heidihealth.com/de-de
Ce que nous avons constaté
„Seit ich Heidi benutze, kann ich mich dem Patienten besser zuwenden. Ich muss nicht mehr sofort alles stichpunktartig mitschreiben.” Seen on 3 pages, e.g. https://www.heidihealth.com/de-de, https://www.heidihealth.com/fr-fr, https://www.heidihealth.com/it-it
Comment le corriger
Shorten the heading so it does not crowd the visual hierarchy.
lowvisual · 95 % de confiance
Repeated components differ across locales
Button counts differ between the source locale and fr.
Trouvé ici
Page body · <button>
https://www.heidihealth.com/fr-ca
Ce que nous avons constaté
Source locale has 14 buttons; fr has 8.
Comment le corriger
Keep the same repeated controls across locales, or drop unused ones on purpose.
mediumtechnical · 70 % de confiance
Current-page preservation is not demonstrated
The evidence lists many locale variants but only shows homepage URLs, so it does not verify that switching locales preserves a non-homepage path.
Trouvé ici
Header · language switcher
https://www.heidihealth.com/en-us
Ce que nous avons constaté
"locales":["de-be","de-ch","de-de",...,"ja-jp"] and the shown page URLs include "https://www.heidihealth.com/en-us" and "https://www.heidihealth.com/en-gb".
Comment le corriger
Test the switcher from several non-homepage URLs and confirm that each locale links to the equivalent localized path.
infotechnical · 82 % de confiance
Locale metadata is explicit for the sampled English pages
The sampled pages expose locale-specific htmlLang values, but the evidence does not expose aria-label or alt attributes for verification.
Trouvé ici
Document · <html>
https://www.heidihealth.com/en-us
Ce que nous avons constaté
"htmlLang":"en-us" and "htmlLang":"en-gb"
Comment le corriger
Audit aria-label and alt attributes across every locale and ensure their values are translated or otherwise appropriate for the page locale.
infolinguistic · 95 % de confiance
Cross-locale terminology cannot be assessed
The supplied content shows only English page copy, so consistency of important concepts across translated locales is unverified.
Trouvé ici
https://www.heidihealth.com/en-us
Ce que nous avons constaté
The sampled page text includes English terms such as "Platform", "Solutions", "Research", and "Get Heidi free"; no translated counterpart is shown.
Comment le corriger
Compare repeated product terms across the German, Spanish, French, Italian, and Japanese pages and standardize their translations.
infolinguistic · 95 % de confiance
Translation accuracy cannot be assessed
No target-language copy or source-to-target comparison is provided in the evidence.
Trouvé ici
https://www.heidihealth.com/en-us
Ce que nous avons constaté
The shown titles, headings, buttons, and page text are English, including "The AI Care Partner for clinicians" and "Book a demo".
Comment le corriger
Provide paired source and localized strings for review, including all product actions and any numbers or other locale-sensitive content.
infolinguistic · 95 % de confiance
Localized fluency cannot be assessed
The evidence contains English copy only and does not show any translated text to evaluate for naturalness or machine-translation artifacts.
Trouvé ici
https://www.heidihealth.com/en-us
Ce que nous avons constaté
"Relief in every visit The AI Care Partner for clinicians"
Comment le corriger
Review rendered copy in each target locale with a native-language reviewer.
infolinguistic · 95 % de confiance
Localized brand voice cannot be assessed
The English source demonstrates a concise, reassuring tone, but no localized copy is available to determine whether that tone is preserved.
Trouvé ici
Hero · <h1>
https://www.heidihealth.com/en-us
Ce que nous avons constaté
"Relief in every visit" and "The AI Care Partner for clinicians"
Comment le corriger
Evaluate each localized hero, CTA, and supporting message against the source tone and revise wording that becomes overly formal, technical, or promotional.
infolinguistic · 95 % de confiance
Locale-specific grammar and style cannot be assessed
Only English page strings are shown, so capitalization, punctuation, formality, and agreement in other locales remain unverified.
Trouvé ici
https://www.heidihealth.com/en-us
Ce que nous avons constaté
The evidence shows English strings such as "Contact us", "Log in", and "Get Heidi free".
Comment le corriger
Proofread each locale for its own capitalization, punctuation, formality, and grammatical agreement conventions.
infocontextual · 82 % de confiance
English CTA intent is clear in the sampled page
The sampled English page exposes distinct acquisition and sales actions, but localized CTA intent is not shown for comparison.
Trouvé ici
Hero · CTA buttons
https://www.heidihealth.com/en-us
Ce que nous avons constaté
"Get Heidi free" and "Book a demo"
Comment le corriger
Verify that every locale preserves the distinction between starting access and requesting a sales demonstration.
infocontextual · 82 % de confiance
English UI contexts are identifiable
The evidence identifies navigation controls, search-related controls, and CTAs in English, but provides no translated UI strings for review.
Trouvé ici
Header · <nav>
https://www.heidihealth.com/en-us
Ce que nous avons constaté
"Platform", "Solutions", "Resources", "⌘K", "Look up", and "Research"
Comment le corriger
Review each translated string in its actual button, navigation, search, or form component and adjust wording to fit the control.
infocontextual · 82 % de confiance
Product context is clear in the sampled English copy
The page consistently presents Heidi as an AI care partner for clinicians, but translated product terminology is not provided.
Trouvé ici
Hero · <h1>
https://www.heidihealth.com/en-us
Ce que nous avons constaté
"Heidi | Your AI Care Partner for Modern Clinical Practice" and "The AI Care Partner for clinicians"
Comment le corriger
Preserve the clinician-focused product meaning and established product terms in every localized workflow and CTA.
infocontextual · 82 % de confiance
English strings have visible page context
The evidence places the sampled copy in navigation, hero, and CTA contexts, but does not provide target-language renderings for contextual review.
Trouvé ici
Hero · <h1>
https://www.heidihealth.com/en-us
Ce que nous avons constaté
"Relief in every visit", "Get Heidi free", and "Book a demo" appear together in the sampled page text.
Comment le corriger
Review localized strings in their surrounding sections and components rather than approving them as isolated translation units.
infocontextual · 88 % de confiance
The sampled page clearly targets clinicians
The English title and hero explicitly frame the product for clinical practice and clinicians; localized audience fit is not shown.
Trouvé ici
Hero · <h1>
https://www.heidihealth.com/en-us
Ce que nous avons constaté
"Your AI Care Partner for Modern Clinical Practice" and "The AI Care Partner for clinicians"
Comment le corriger
Keep clinician-facing terminology and professional positioning consistent across all target locales.
infovisual · 65 % de confiance
Localized assets cannot be verified
The supplied preview does not include image markup, asset names, or alt text, so locale-specific imagery and accessibility text remain unverified.
Trouvé ici
https://www.heidihealth.com/en-us
Comment le corriger
Inspect image elements and asset variants on each locale page, including their alt attributes, for language and cultural appropriateness.

Pages échantillonnées

200 · https://www.heidihealth.com/en-us · lang=en-us
200 · https://www.heidihealth.com/en-us · lang=en-us
200 · https://www.heidihealth.com/en-gb · lang=en-gb
200 · https://www.heidihealth.com/en-ca · lang=en-ca
200 · https://www.heidihealth.com/fr-ca · lang=fr-ca
200 · https://www.heidihealth.com/en-au · lang=en-au
200 · https://www.heidihealth.com/en-nz · lang=en-nz
200 · https://www.heidihealth.com/en-ie · lang=en-ie
200 · https://www.heidihealth.com/en-hk · lang=en-hk
200 · https://www.heidihealth.com/en-za · lang=en-za
200 · https://www.heidihealth.com/en-sg · lang=en-sg
200 · https://www.heidihealth.com/de-de · lang=de-de
200 · https://www.heidihealth.com/fr-fr · lang=fr-fr
200 · https://www.heidihealth.com/es-es · lang=es-es
200 · https://www.heidihealth.com/it-it · lang=it-it

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

Bonne base, avec une marge d’amélioration. Créez un espace de travail pour un suivi continu de la localisation, ou réservez une revue d’audit.

Réserver un examen d’audit