Quarter

Needs attention (12)

• Locale detection

  Fail40technical

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

  • hightechnical · 95% confidence

    Missing language declaration

    15 sampled pages do not set html lang, so browsers and assistive tech cannot identify the locale.

    Found here

    Document head · <html lang>

    https://yourquarter.au/

    What we saw

    html lang is missing on 15 pages, e.g. https://yourquarter.au/, https://yourquarter.au/owners, https://yourquarter.au/committees

    How to fix it

    Set html lang to a BCP 47 language tag for each page locale, such as en, fr-FR, or es-419.

• Language switcher

  Fail62technical

  Visitors should move between locales without losing the current page.

  • mediumtechnical · 84% confidence

    Current-page locale switching is not evidenced

    The evidence shows a New Zealand link, but does not demonstrate that visitors can switch to the equivalent locale while preserving the current path.

    Found here

    Header or locale navigation · <nav>

    https://yourquarter.au/owners

    What we saw

    "In New Zealand? Visit quarter.nz for body corporates."; listed locales: ["en-au","en-nz"]

    How to fix it

    Provide explicit locale links for each page and map the current path to its equivalent locale path, not only to the locale homepage.

• Sitemap

  Fail60technical

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

    Sitemap is missing localized URLs

    A sitemap was found, but sampled entries do not include locale-prefixed URLs.

    Found here

    Sitemap · sitemap.xml

    https://yourquarter.au/sitemap.xml

    What we saw

    Sitemap https://yourquarter.au/sitemap.xml has no locale-prefixed URLs in the sample

    How to fix it

    Include localized URLs in the sitemap for every published locale.

• Terminology consistency

  Fail88linguistic

  Important concepts should not be translated differently across pages.

• Translation accuracy

  Fail86linguistic

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

• Fluency

  Fail88linguistic

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

• Brand voice

  Fail88linguistic

  Localized copy should preserve the intended tone of the source.

• Grammar and style

  Fail82linguistic

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

  • mediumlinguistic · 78% confidence

    Missing HTML language metadata

    The inspected pages have no declared HTML language, so locale-specific language and assistive-technology behavior cannot be reliably established.

    Found here

    Document metadata · <html>

    https://yourquarter.au/

    What we saw

    "htmlLang":null

    How to fix it

    Set the root <html lang> value to the page locale, such as `en-AU` or `en-NZ`, on every localized page.

• Localized images and assets

  Fail88visual

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

• Text overflow

  Fail84visual

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

• Layout breakage

  Fail84visual

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

• Responsive localisation

  Fail82visual

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