University of Wisconsin-River Falls
A to Z | Calendar | Search UWRF
UWRF Home

<< Return to Home Page

Web Site Development Policy
(Full Version)

Summary and Policy Home Page

Web Site Policy Document

INTRODUCTION: WEB SITE STANDARDS AND GUIDELINES
FOR INSTITUTIONAL AND PERSONAL PAGES

REQUIRED STANDARDS FOR PERSONAL WEB PAGES

REQUIRED STANDARDS AND GUIDELINES FOR INSTITUTIONAL WEB PAGES

SITE RESPONSIBILITY AND ENFORCEMENT OF STANDARDS

I. WEB SITE ENVIRONMENTS AND TOOLS
A. Server environment
B. Desktop development environments
C. Multimedia server environment
D. Web publishing tools
E. Graphic/image files

II. CONTENT ORGANIZATION/SITE ARCHITECTURE
A. Process for Organization

III. CONTENT TEXT – WRITING/STYLE/PRESENTATION
A. Common elements and conventions
B. Structure
C. Diction
D. Correctness
E. References

IV. UWRF BRANDING REQUIREMENTS
A.& B. Common page elements
C. Page size
D. Font style and size
E. Colors
F. Breadcrumbs
G. Content terminology and usage

V. WEB PUBLISHING CONVENTIONS
A. Navigation
B. Accessibility
C. Opening new browser windows
D. Limiting file size
D1. File Management and Naming
E. Optimizing images
F. Use of HTML
G. Use of publishing elements other than HTML
H. Use of layers
I. Use of frames
J. Naming of files
K. Addressing of files
L. Use of alt tags
M. Use of motion
N. Use of meta tags
O. Use of mailto tags vs. HTML/CGI contact forms
P. Use of “under construction” links
Q. Usability by search engines
R. Usability by various browsers/versions/technologies

APPENDIX A. TERMINOLOGY, USAGE, AND SPELLING

APPENDIX B. ABOUT THIS DOCUMENT

Campus Web Development Office
21 North Hall, 425-0661
webmaster@uwrf.edu

SECTION V. Web Publications Conventions

A. Navigation

STANDARDS:

1. A UWRF Web page must use clear, consistent, “branded” navigation mechanisms.
(See Section IV: UWRF Branding Requirements).

2. Each image link or button should be accompanied by a label which clearly indicates its purpose. Image links and buttons should not blink or move. (See Section V, L: Use of motion.)

3. To ensure that no gaps exist in the search of your site, set up invisible links to anything that is referenced ONLY from image maps, JavaScript, or Flash links.

For example:
<a href=“http://www.uwrf.edu/programs.html”></a> or
<a href=“../programs.html”></a>.
There is nothing clickable on this type of link, so it is invisible to the user but readable to a search spider. This type of link can be embedded on any HTML page.

Explanation:
Search spiders and robots index a site by following links from a starting page (on the public access server this will be the UWRF home page) to all of the linked subordinate pages. However, spiders and robots cannot read image map, JavaScript, or Flash links. As a result, without invisible links, a lot of subordinate pages may not be indexed by the search engine, and the users may not find what they need.

4. ‘Jump menu go’ HTML selection boxes are the preferred method for categorizing links to avoid too many choices being displayed at one time. In creating an HTML drop down menu, make sure that the selection box is only activated by pressing a go button or other image. Use server side scripting to activate the “go” button (such as Perl).

example: of a Jump menu go

Explanation:
HTML selection boxes can be used by all browsers. JavaScript and Flash links are not readable by most search spiders and robots or by the speech synthesizers used by the visually impaired. They also don't work with some older browsers (pre-4.0 browsers).

‘Jump menu go’ – rather than ‘jump menu’ – selection boxes are preferred for accessibility and usability reasons. With ‘jump menu’ boxes, someone using a screen reader must go to each page in the list one at a time before reaching the desired page. A ‘jump menu go’ dropdown enables the user of the assistive technology to go directly to the desired link. Also, from a general usability standpoint, long menus in a ‘jump down’ box require the user to depress and move the mouse over a large list, thus increasing the chance of getting the wrong page. Requiring the pressing of a Go button placed alongside the jump menu lets users make sure that their choice is correct before the redirect is activated. As stated earlier, you should use a server side scripting such as Perl to activate the ‘Jump menu go’ instead of JavaScript.


 

 

 


 

 

 

University of Wisconsin - River Falls
410 South Third Street River Falls, WI USA 54022-5001 (715)425-3911
Copyright © 1995-2008 University of Wisconsin-River Falls