Technical Audit Checklist

When you send your website content out for review, your content goes through a "Technical Audit" prior to being published live. The following is a general checklist of what will be checked for in each review.

URL Review

Review the URL path (website address) to make sure that:

  • a URL has been added and is human-readable
  • the URL is in the correct context
  • the URL doesn’t start with a slash (/)
  • the URL doesn’t use special characters and that spaces are replaced with a dash (-)

Menu Review

If this content has been added to a menu, check that:

  • it has been added to an appropriate menu (and parent item if applicable) for the context of the content.
  • the menu link title clearly describes the content that it is associated with
  • the menu weight is appropriate for where this content should appear on the menu

Filename Review

If files are being used on the content, check that:

  • downloadable files (Word, PDF etc.) have appropriate file names
    • no special characters or spaces
    • not longer than 31 characters
    • file name has context and is understandable
    • does not contain working language like “draft” or “final”
    • does not contain internal language like “uc” or “sem”
  • image files have appropriate file names
    • no special characters or spaces
    • not longer than 31 characters

Accessibility Review

Review the content area(s) of the website content to ensure adherence to the Website Content Accessibility Guidelines, check that:

  • all images have ALT tags and are they appropriate
  • if headings are used, are they used correctly
  • links that are used on the page clearly indicate where they are going and don’t use language like “click here” or “more info”…
  • images do not contain information that is too complex to be described in the ALT text (some exceptions may be permissible.

Mobile Friendliness Review

Content will be reviewed to ensure that it has been created in a way that will work well on mobile devices such as tablets and phones, check that:

  • image sizes are appropriate — this includes both file sizes and pixel dimensions
  • content that has been added without the use of the WYSIWYG editor (copy/pasted in) is appropriate and will work on a mobile device

Note: We will also complete a basic qualitative review of how the content has been laid out and if the WYSIWYG tools have been used appropriately. This review will check that:

  • the content is laid out in a clear way and does not use/overuse WYSIWYG styles in a confusing way
  • there is no attempt to override the styles of the built in WYSIWYG editor – this could include bolding headings, trying to change colours, adding additional style code, adding JavaScript etc.
  • the content is laid out like a web page rather than a poster or word document