Heidi

Needs attention (22)

• Language switcher

  Fail74technical

  Visitors should move between locales without losing the current page.

  • mediumtechnical · 62% confidence

    Current-page preservation is not demonstrated

    The evidence shows locale coverage and several homepage URLs, but does not explicitly verify switching between locales while retaining a non-homepage path.

    Found here

    Header · <nav>

    https://www.heidihealth.com/

    What we saw

    "locales":["de-be","de-ch","de-de",...,"ja-jp"] and homepage examples such as "https://www.heidihealth.com/", "https://www.heidihealth.com/en-us", and "https://www.heidihealth.com/en-gb"

    How to fix it

    Test the language switcher from representative inner pages and confirm that each locale preserves the equivalent path.

• Sitemap

  Fail76technical

  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% confidence

    Sitemap omits some published locales

    Locale-prefixed pages for fr, de do not appear in sampled sitemap URLs.

    Found here

    Sitemap · sitemap.xml

    https://www.heidihealth.com/sitemap-index.xml

    What we saw

    Sitemap locales in sample: en; missing: fr, de

    How to fix it

    Include URLs for every published locale prefix in the sitemap.

• Structured data

  Fail0technical

  JSON-LD inLanguage should match the page locale when structured data is present.

  • lowtechnical · 95% confidence

    Structured data omits inLanguage

    JSON-LD is present but does not declare inLanguage on sampled pages.

    Found here

    JSON-LD · <script type="application/ld+json">

    https://www.heidihealth.com/

    What we saw

    Organization is present but inLanguage is missing

    How to fix it

    Set JSON-LD inLanguage to match each page locale.

• Accessibility localisation

  Fail84technical

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

• Translation completeness

  Fail34linguistic

  Localized pages should not leave source-language copy in place, except brand names and URLs.

  • highlinguistic · 92% confidence

    Untranslated call to action

    A fr-ca page still uses source-language CTA copy. Affects 3 sampled pages.

    Found here

    Link · <a>

    https://www.heidihealth.com/fr-ca

    What we saw

    Primary CTA: "Skip to main content" Seen on 3 pages, e.g. https://www.heidihealth.com/fr-ca, https://www.heidihealth.com/de-de, https://www.heidihealth.com/fr-fr

    How to fix it

    Translate leftover source-language CTAs to match the surrounding locale copy.

• Terminology consistency

  Fail80linguistic

  Important concepts should not be translated differently across pages.

• Translation accuracy

  Fail72linguistic

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

• Fluency

  Fail86linguistic

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

• Brand voice

  Fail84linguistic

  Localized copy should preserve the intended tone of the source.

• Grammar and style

  Fail86linguistic

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

• CTA intent

  Fail89contextual

  Localized calls to action should communicate the intended product action.

• UI context

  Fail88contextual

  Translations should fit the UI component: button, nav, form, modal, or error.

• Product context

  Fail86contextual

  Language should match product concepts such as plans, settings, and workflows.

• Contextual meaning

  Fail87contextual

  Strings should be judged in surrounding page and component context, not in isolation.

• Audience context

  Fail89contextual

  Language should fit the intended audience, such as consumer, enterprise, or developer.

• Text expansion

  Fail40visual

  Longer translations should not create obvious length pressure versus the source UI.

  • mediumvisual · 88% confidence

    Localized text is much longer than the source

    A fr string is 171% the length of the source, which often causes overflow. Affects 13 sampled pages.

    Found here

    Heading · heading

    https://www.heidihealth.com/fr-ca

    What we saw

    EN "Relief in every visit" → FR "Heidi — Your AI Care PartnerHeidi AI" (171%) Seen on 3 pages, e.g. https://www.heidihealth.com/fr-ca, https://www.heidihealth.com/fr-fr, https://www.heidihealth.com/de-de

    How to fix it

    Shorten the translation or give the control more room so the longer copy does not overflow.

• Localized images and assets

  Fail74visual

  Language-specific images and alt text should match the page locale.

• Visual hierarchy

  Fail58visual

  Localization should not make headings or CTAs lose scanability.

  • lowvisual · 80% confidence

    Heading is excessively long

    A localized heading may crowd the visual hierarchy. Affects 4 sampled pages.

    Found here

    Page body · heading

    https://www.heidihealth.com/de-de

    What we saw

    „Seit ich Heidi benutze, kann ich mich dem Patienten besser zuwenden. Ich muss nicht mehr sofort alles stichpunktartig mitschreiben.” Seen on 2 pages, e.g. https://www.heidihealth.com/de-de, https://www.heidihealth.com/fr-fr

    How to fix it

    Shorten the heading so it does not crowd the visual hierarchy.

• Component consistency

  Fail70visual

  Repeated components should stay visually consistent across locales.

  • lowvisual · 95% confidence

    Repeated components differ across locales

    Button counts differ between the source locale and fr.

    Found here

    Page body · <button>

    https://www.heidihealth.com/fr-ca

    What we saw

    Source locale has 13 buttons; fr has 8.

    How to fix it

    Keep the same repeated controls across locales, or drop unused ones on purpose.

• Text overflow

  Fail76visual

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

• Layout breakage

  Fail76visual

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

• Responsive localisation

  Fail76visual

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