Localisation report
yourquarter.au
Product: Quarter is software for owners corporations, committees, developers and building service teams to manage building operations. It supports proposals, decisions, budgets, levies, maintenance, documents, compliance and communication with neighbours and managers.
Brand voice: Practical, clear, collaborative, reassuring
Localisation score
72/100
Needs improvementUsers may encounter noticeable localisation problems.
Sampled 15 pages across technical, linguistic, contextual, and visual localisation credits. How we score localisation audits
Rank #12 of 24 public audits
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.
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.xmlWhat 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.
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/ownersWhat 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.
4 passed · 12 to fix · 19 not applicable
Locale detection
Fail40technicalPages should declare a correct html lang that matches the URL and content locale.
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
Fail62technicalVisitors should move between locales without losing the current page.
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/ownersWhat 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
Fail60technicalLike 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.
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.xmlWhat 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
Fail88linguisticImportant concepts should not be translated differently across pages.
Translation accuracy
Fail86linguisticTarget copy should preserve the source meaning, numbers, and product actions.
Fluency
Fail88linguisticCopy should sound natural, without grammar issues or machine-translation artifacts.
Brand voice
Fail88linguisticLocalized copy should preserve the intended tone of the source.
Grammar and style
Fail82linguisticLocale-specific capitalization, punctuation, formality, and agreement should be correct.
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
Fail88visualLanguage-specific images and alt text should match the page locale.
Text overflow
Fail84visualText should not clip, truncate unexpectedly, or overflow buttons and navigation.
Layout breakage
Fail84visualLocalized pages should not overlap, break grids, or overflow modals.
Responsive localisation
Fail82visualLocalized layouts should hold up across mobile, tablet, and desktop widths.
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.
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.xmlWhat 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.
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/ownersWhat 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.
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.
Optional. Enter your work email and we will send a concise summary of this public report.
Solid baseline with room to improve. Create a workspace for continuous locale monitoring, or book an audit review.
You can re-run this audit once a day. Next run Sep 8, 2026, 1:23 PM.
