• Overall
  • All institutional pages must use the approved CMS and templates within
  • All institutional pages must follow the style guide
  • Do not use copyrighted material unless you have written notification from the copyright holder
  • All (X)HTML code must pass validation (error pass required, not warning pass) at http://validator.w3.org/
  • All pages must pass 508 validation (error pass required, not warning pass) at http://wave.webaim.org/ (note: validator of choice may change based on input from tech committee)
  • Template-based navigation system must be used by all sites; creation of a complete separate navigation system within the body is not permitted (such as adding left navigation to all pages in our site)
• Color
  • Use colors found on the UVU Color Palette in the Marketing Logo Style Guide (pdf) (accent colors should be used sparingly)
  • Ensure your site content works for those who are color blind (in particular ensure those who are color blind can 'see' links. This can be checked at http://www.vischeck.com/vischeck/vischeckURL.php 
• Text
  • Always use web-safe fonts (Arial, Sans-serif, Verdana, Times New Roman, Courier, Courier New, Impact)
  • Use text colors that are in high contrast to background
  • Do not underline text unless it is a link
  • Use relative font sizes between xx-small and xx-large
• Navigation
  • All departmental navigation must have an index.html file for every 'tab'.
  • This index.html file must have any navigation listed in the drop navigation on that page along with any other content deemed appropriate by the department.
• Links
  • Use underline for links (either on hover or as default active/not-visited)
  • Ensure words that are linked are descriptive for search engine optimization
  • Do not use the words "click here" as your links (approved 1/2011 by Communications Committee). For rationale see W3C Quality Assurance Tips for Webmasters
    
  • Links to PDF or other non (X)HTML documents need to have the file extension listed (5/2011: Pending Communications Committee approval)
    Sample:   2011 Getting Started Brochure (pdf)
• Images
  • If you put text on top of an image make sure it remains legible
  • Make images 72 dpi (maximum quality on the Web)
  • Ensure images are sized exactly as it will be displayed on the page
  • Use jpg (pictures), gif (graphics), or png (with script for IE6 operability) formats
  • Image maps should not be used
• Multimedia
  • Video and audio clips must have an accessibility alternative, and should facilitate easy searching
  • All Javascript must be accessible or have an accessibility alternative
  • All Flash or similar multimedia must either have 'cosmetic' content or must have an accessible alternative
  • Video, in most cases, should be housed on UVU's YouTube account at http://www.youtube.com/utahvalleyuniversity/
  • For video to be posted on http://www.youtube.com/utahvalleyuniversity/  the YouTube Web Presence Guidelines need to be followed.

Other recommendations

• Overall
  • Navigation & layout should be focused on user (users don't usually care about organizational structure)
  • Subtitles in the main header should be links
• Body
  • Use spaces between paragraphs
  • Generally limit the number of text colors to 3 or less
  • Generally, text should be left justified or full
  • Generally, avoid putting all content in one long scrolling page
  • Do not use the term 'under construction' or anything similar; if we do not have content we should not have a page until we do.  You can instead say something like 'contact [name and contact information here] for additional information'
• Text
  • Do not use italic, except for within APA guideline standards, as they are not as legible on the Web
• Links
  • Generally, use the CSS default
• Images
  • Use clipart sparingly
  • Use images that appeal to your target audience (age, gender, style, color, etc)
  • Use people when possible
  • Use animated gifs sparingly
  • If an image is used as a link it should have a mouseover effect (visible difference on mouseover)
• Multimedia
  • Use Flash sparingly and code for easy search when used