Campus Web Header and Footer Guidelines

Campus Header

Campus Header

The campus header is used only on the main CSU, Chico website (pages within www.csuchico.edu) and web apps developed on campus (ex., Directory, University Catalog). It indicates to users that the page is part of an official university website. The header also provides sites with consistent CSU, Chico branding and creates a more intuitive experience navigating through the campus web.

Positioning

The campus header is the topmost element on every campus web page.

Header Elements

Below are the required elements in the Global Header. No other elements may be added to the Global Header.

  • The web signature
    • Provides a link back to the university homepage. 
    • May not to be combined with other logos, elements, or typefaces
    • See more information on this and other University logos in the University Communicators Guide.
  • Links to the top campus services, as determined by analytics 
    • Portal
    • Email 
    • Catalog 
    • Class Schedule 
    • Campus Map 
    • Directory
    • Library
  • Search Box element 
    • Campus search is maintained by Web Services with relevant results. Associated web apps that modify the search box functionality are responsible for providing users relevant search results.

Header Updates

While the header is relatively static, it does require occasional updates such as link changes or color contrast adjustments. When Web Services changes the campus header, it is automatically updated across sites in the Cascade WCMS. Associated web apps like the Directory and Class Schedule require a manual change made by departments outside of Web Services. These departments are notified through the IRES technotice.

Issues within the global header can be reported via a ticket to Web Services.

Campus Footer

The following image shows the components of the campus footer as described below.

complete footer with subfooter, site footer and global footer

Global Footer

Every page within the Campus Web is required to use the global footer. The purpose of the footer is to further identify official CSU, Chico web pages as well as provide required links and easy access to help and contact information on each page.

Positioning

The campus footer is the bottommost element on every Campus Web page. It may be used alone on simple landing pages, microsites, and web applications. On department and other more complex subsites, it must be used in conjunction with a site footer and/or subfooter.

Footer Elements

  • “Contact Us” link 
  • “Need Help?” link
    • Goes to Help page with contact information for ITSS, service ticket links, Chico information, search tips, and more
  • University social media links
    • Facebook, Twitter, and Instagram
  • “Report an accessibility issue” link
    • Goes to Campus Web Accessibility Statement and link to issue-reporting form
    • Required by CSU Accessible Technology Initiative, supported by Executive Order 1111
  • “Report a broken link” link
    • Allows users to identify broken links on any webpage 
    • Goes to issue-reporting form that generates a TeamDynamix ticket
  • “Title IX” link
    • Goes to Title IX website with “Notice of Non-Discrimination on the Basis of Gender or Sex”
    • Required by CSU Executive Order 1095
  • CSU, Chico address
  • Copyright information
    • Includes current year

Global Footer Updates

While the footer is relatively static, it does require occasional updates such as copyright date changes. When Web Services changes the campus footer, it is automatically updated across  sites in the Cascade WCMS. Associated web apps like the Directory and Class Schedule require a manual change made by departments outside of Web Services. These departments are notified through the IRES technotice.

Issues within the global footer can be reported via a ticket to Web Services.

Site Footer

Most Campus Web subsites have a site footer that helps users orient that department or office within the larger university context. Every department or office within a unit uses the same site footer. Content is determined by Web Services in conjunction with the parent division, college, or unit. Office hours, contact information, navigation links, giving buttons, and other main content should remain in a subsite’s main content areas, where Campus Web users expect them to be.

Some campus subsites represent campuswide initiatives or are not easily associated with a higher-level entity on campus. These subsites may have the site footer removed with approval of the Web and Web App Content Review Subcommittee.

Positioning

The site footer is located directly above the global footer. It is distinguished by a slight change in brightness.

Required Elements

  • College, division, or unit name
  • Other programs, offices, and departments within “parent” organization
  • Program portfolio link, for academic units only

Optional Elements

  • Giving button

Site Footer Updates

To ensure that students have a consistent, predictable experience navigating the Campus Web and that footer links and department names are up to date, site footers are updated by Web Services only. Changes to department information within footers can be requested via the Content Updates Support Ticket. These changes will be made free of charge and are subject to review by the Web and Web App Content Review Subcommittee.

Subfooter

General information that needs to be displayed on every page of a subsite can go in the subfooter. Office hours, contact information, navigation links, giving buttons, and other main content should remain in a subsite’s main content areas, where users expect them to be.

Positioning

The subfooter is located directly above the site footer. It is distinguished by a much lighter shade of grey.

Optional Elements

  • Accommodation statement for sites with archival content or content undergoing accessibility remediation 
  • Statement providing additional context to site content

Examples: /aaspace, /sen, /diversity

Header and Footer Exceptions

Exceptions to the “Campus Web Header & Footer Guidelines” are subject to review by the Web and Web App Content Review Subcommittee. These exceptions are rare and granted most often for sites that serve external (non-student, staff, or faculty) audiences or vendor-provided interfaces with little room for customization. (See Custom Website Guidelines for more information about websites outside of the standard campus framework.) 

These sites and apps must still meet legal and campus requirements in their nonstandard header and footer. To request an exception or visual assets for non-Cascade sites or web apps, please submit a ticket to Web Services

Was this helpful?
0 reviews

Details

Article ID: 70114
Created
Mon 1/14/19 9:32 AM
Modified
Wed 5/19/21 12:48 PM