Brand Compliance

Brand Compliance

Brand Compliance aims to detect deviations in corporate guidelines and standards, with regards to HTML documents.

This policy category is broken down into 8 policies.


Valid Corporate Logos

Aims to detect HTML documents that do not use a valid corporate logo, in a specified location. This policy will look to find a specified image in a specific location, or the use of a valid css class that renders the corporate logo.

Any document that does not use the specified corporate logo correctly will generate a policy exception.


Valid CSS Styles

This policy will detect HTML documents that use cascading style sheets, CSS that are not regarded as valid in relation to corporate guidelines. Any document that references CSS that are not approved will generate a policy exception.


Using Embedded Stylesheets

Any document that uses embedded stylesheets within the HTML mark-up will generate a policy exception. All stylesheets should be held within their own document, not embedded in a HTML document.

The following code snippet would result in a policy exception being generated.

<head>
    ....
    <style type="text/css">
            h1 {color:red}
            p {color:blue}
       </style>
</head>


Using Embeded Styles

Any document that uses style attributes on a HTML element will generate a policy exception. These style attributes should be contained within a referenced stylesheet, not inline to the HTML document.

The following paragraph element would be invalid and would generate a policy exception.

<p style="background-color: red;">This paragraph has a style attached and is invalid</p>


Valid Favicon Used

This policy aims to ensure only a valid favourite icon is used within the document. The following would generate a policy exception, if the valid icon name was 'valid_icon.gif'.

<head>
    <link rel="icon" href="our_wrong_favicon.gif" type="image/gif" />
    ....
</head>


Use Of Font Tags

No inline font tags should be used within the HTML document. This policy checks that no inline font tags are used, if any font tags are found a policy exception is generated.

All fonts should be removed from the document and held within CSS files. The following code snippet would be invalid.

<p>
    <font face="verdana" color="green">This is some text wrapped in a font!</font>
</p>


Common Corporate Naming Errors

This policy aims to detect common spelling errors in corporate naming conventions. For example searching for the name 'Vamsoa' would generate a policy exception when given the following code snippet.

<h1>Vamsoa Content Migrator</h1>


8.Common Product Naming Errors

This policy aims to detect common spelling errors in product naming conventions. For example searching for the name 'Vamosa Content Migrater' would generate a policy exception when given the following code snippet.

<h1>Vamosa Content Migrater</h1>