When should you use Logo used correctly?
logo-usage · visual · required
When should you use this check?
Run this on any page a customer might land on cold, where the header is doing the work of saying whose site this is. It earns its place most on sites with several templates or sub-brands, because the header is a shared component and a change to it either fixes or breaks every page at once. Include it in scheduled runs on key landing pages, since logos break through asset moves and stylesheet changes far more often than through anyone editing the header.
When should you not?
Skip it on pages that deliberately have no logo — an embedded widget, an iframe destination, a whitelabelled surface, a print stylesheet. It is also not the right check for brand-guideline questions it cannot see, like whether the correct colour variant was used against a given background, or whether clear-space rules were respected to the millimetre. Those need a human against the brand book; this check answers whether the mark is present, whole and readable.
What does it inspect?
Verify logo is present and follows brand guidelines
What does a failure mean?
A failure says what was wrong with the mark: absent, distorted, cropped, or too small or low-contrast to read. The common cause is not a designer's choice but an inherited one — a width or height set on one axis, a container that changed size, an asset that moved and now resolves to nothing. Because the header is shared, a failure here usually describes how every page in that template currently greets its visitors.
What are the Standard defaults — and why?
One parameter carries the check: `logoRequirement`, a written rule rather than a number. Its Standard default asks that a brand or company logo be present, clearly visible, and readable in the header or primary brand area — deliberately broad, because "correct logo usage" differs by brand and a universal numeric rule would be wrong for most of them. There is no threshold to tune; the requirement sentence is what the check judges against.
How does an agent call it?
{
"type": "url",
"url": "https://example.com",
"validations": [
"logo-usage"
]
}
Who governs the Standard?
Schemafirst.org publishes community-governed standards for digital QA. ArbiterQA is a sponsor and commercial licensee of those standards; citation does not mean Schemafirst operates ArbiterQA.
Author ArbiterQA · Reviewed by ArbiterQA · 2026-08-14