Site Review Tips
Mistakes to Avoid
There are simple issues we tend to encounter when reviewing websites which can prolong the review process. Please look over the list of common mistakes below prior to beginning work on your website to help speed up the launch process.
Working on sites under review
Once the site is submitted for review, it is important to no longer edit the site. Continuing to edit the site while it's in the launch process will increase the length of the review time. This is the equivalent of working on a submitted assignment while a professor is reviewing it.
- If this behavior is identified and not ceased, we will stop the review and work on the next submitted site before coming back to yours, regardless of launch deadlines. It's important that site managers plan ahead and only submit sites to us once they are completed.
- Site editors should only work on items sent back from our team for correction.
For convenience, editors will often copy and paste content into Gato pages to save on time. While this is allowed, we often find that this results in a couple common issues, listed below:
- Outdated content tends to be included in text. This could include names of previous employees, contact information, deadlines and links. Try to avoid copying and pasting older content and always carefully review material being added to new pages.
- Outside formatting is not cleared. Gato sites are expected to maintain consistent formatting across all sites. Sites will not be cleared for launch until all excess formatting is removed. To be safe, always select pasted material and remove formatting using the format stripping tool found in either the text and image or rich editor content types.
One of the most common issues we tend to find is incomplete form properties being entered, such as:
- A confirmation page is not internally linked. Always remember to include a confirmation page somewhere in your site to link to. This will prevent users from selecting the submit button and being directed to a 404 page.
- Always be sure to hide confirmation pages from navigation.
- Ensure that the confirmation page matches the form, if applicable.
- Linking multiple forms to a single generic confirmation page is allowed, but it needs to be appropriate for all forms linking to it. For example, a user who submits an application form would find it awkward to be linked to a "Thank you for your feedback" page. Instead, a form mentioning "Thank you for your submission. We will contact you within 3 business days" could work for many different forms.
- The auto-email response option is not set up (situational). If editors are going to include an email field with "This is the form submitter's email address" selected, the auto-email response tab needs to be filled out.
There are many different form fields which can be added in forms.
- Ensure that the requested information matches the field type option. For example, if requesting an email address, editors will need to select the email address field from the field properties.
- Do not request sensitive information.
- If possible, avoid requesting A#'s as these are also considered sensitive information.
We review the form properties and every form field in each form. Any issues found will be sent back to site managers for correction.
- Always use internal linking when pointing to a page in the same website.
- Always use external linking if pointing to a separate website.
- If an editor has access to multiple websites, the ability to select a page from another website appears when setting up an internal link. While it appears possible to do so, this will result in a broken link once the site becomes live.
- Do not use gato-edit or gato-public URLs as external links
- If working on a sandbox page, do not create an external link to the original live site. This may work if the URL pathway remains the same, but can result in link issues in the future if pages are ever re-arranged.
- Use appropriately sized images. If selecting a smaller image to be portrayed in a larger space, it will appear blurry. Blurry images such as these are required to be fixed/replaced before a site can go live.
- Review each picture carefully to ensure that it is appropriate to be portrayed on your website. If the image is questionable, it's likely that it has be replaced.
- Ensure that all images contain alt text, and that the text is appropriate. Do not use the same alt text for different images on the same page. For questions relating to alt text, please visit the Images and Alt Text page within the Digital Accessibility website for more information.
- Do not use images to portray text information.
- We often see sites add organizational charts as images. The text within these images cannot be read by a screen reader, so a text version of these images would have to be provided.
Page Names and Titles
- Ensure that all the page names are short (one to three words), simple (no need for a bunch of dashes or underscores), and lower-case. Page names are found in the left-most column in Gato.
- All pages must have titles. Titles should be short and to the point, and should never be a full sentence in length. Titles must also encompass the whole idea of the page.
Sites containing a mix of both TXST Standard and Calico templates will not be reviewed and will be immediately returned. Sites must either be 100% in Calico, or 100% in TXST Standard. For more information relating to the use of the Calico template, visit the Calico Template Guidelines page.
Avoid using headings as regular text. In the past, we've seen editors attempt to aesthetically improve text on a page by turning all of that text into a title or subtitle.
Site's found doing this will not move forward until this is corrected. All headings should be used appropriately, and should be short and to the point. For more information on headings in Gato, please visit the Headers page within the Digital Accessibility website. You can also visit the Automatic Header Adjusting page to view how Gato helps auto-adjust your headings.