The public web at UVU is a centralized system guided by standards and procedures to maintain our brand, our image, and our content at the highest standards. The standards and suggestions on this page can help guide the development of your site.
UVU strives to promote web best practices and provide a consistent, intuitive, responsive, and accessible web presence. In order to facilitate these efforts, the following standards have been determined. All UVU websites should meet these standards and may be subject to review.
These standards were adopted by SWAT on November 28, 2018. SWAT reviewed in spring 2023.
The navigation for academic departments must include the following four navigation items (and related content) in this particular order as the first navigation items listed:
The navigation for Academic Colleges and Schools must include the following four navigation
items:
The first two items should appear as the first and second items on the navigation.
The last two items may appear anywhere within the navigation.
*"Make a Gift" is optional; If a school does decide to have a '"Make a Gift" link,
it must be tightly coordinated with the Development Office.
Do not modify UVU marks or logos. Follow the guidelines for UVU marks and logos.
Do not modify the logos of social media icons, etc. in an effort to match them to your site.
UVU strives to ensure compliance with AA standards according to WCAG 2.1, as recommended by W3C. In order to facilitate these efforts, the following standards have been determined. All UVU websites should strive to meet these standards and may be subject to review.
The public website should primarily serve prospective students, parents,employees,alumni, and the broader community. Content intended specifically for employees, current students, or internal committees should be housed on secure internal platforms rather than publicly accessible web pages.
The following types of Confidential or Internal information should never appear on publicly accessible pages:
When in doubt, ask: Is this information intended for broad public access, or only for internal operational or strategic use?
Aligned with UVU Data Governance Policy
If the content supports internal planning, operations, decision-making, or reporting, it should not be posted publicly. If the primary audience is external (prospective students, parents, alumni, community), it may be appropriate. When unsure, default to internal.
Approved directory information (names, titles, departments, UVU email addresses per rules of directory system.) is appropriate. Private employee or personnel information (records, evaluations, demographics, salary, performance) should not be posted publicly.
Only if they were created and approved for external audiences. Presentations that include budget information, internal strategy, planning, draft data, or committee discussions should remain internal. Assume slide decks are internal by default. Please consult with the presentation’s presenter or slide deck’s creator before publicly posting content. Follow the share guidelines
Internal reports, dashboards, enrollment or outreach lists, and draft materials should remain internal unless explicitly approved for public release. Data solely created for internal analysis or planning should not be posted publicly—even if anonymized. Data must follow UVU's data publishing standards and be classified as public by the appropriate Business Intelligence and Research Services.
Only materials Web Strategy Groupexplicitly approve for public audiences should be posted on the public website. Official university policies are published on the university’s policy website and should be referenced there when applicable. Internal procedures, operational guidance, and employee-only reference materials should remain internal. Any data or policy changes should go through the Policy Office or Business Intelligence and Research Services.
Internal or sensitive materials should be stored on the Intranet, secure SharePoint sites, or other approved platforms with appropriate access controls. Public web pages should not be used to store internal files.
