4.6 Use frames and new browser windows sparingly Carefully consider your use of frames and 

new windows and use them where they are most effective.  

4.6.1 While it is sometime appropriate to create a frames based site, remember that this 

structure makes it difficult for users to link to specific sections of your site.  

4.6.2. Use frames for encapsulated presentations of information where it is appropriate. 

Frames are good for carrying a common presentation forward throughout a site visit and 

typically are faster in the perceived download and display of information. Frames don t allow 

bookmarking of pages within the frame site, and inadvertent nesting of frames creates 

problems with navigation and site display.  

4.6.3 If frames are employed, think about using the "NOFRAMES" option and name each 

frame to facilitate non visual navigation.  

4.6.4 New windows can be somewhat deceiving to the end user if they fully overlay the other 

open windows. Typically, new windows are good for interrupting an activity to present adjunct 

information, such as help, instructions, capturing feedback, exploring an option, etc, and then 

closing to return to previous work.  

5. ACCESSIBILITY  

5.1 Policy  

All electronic publications, to the extent feasible, must be accessible to people with disabilities. 

These policies apply to all Web Sites intended to accomplish the academic and administrative 

tasks of the University.  

5.2 Tips On Accessibility Based On W3 Consortium Guidelines  

Web site creators should follow the recommendations in the W3 Consortium's Web Content 

Accessibility Guidelines (http://www.w3.org/TR/WAI WEBCONTENT/) as much as possible so 

that their pages are accessible to users who use assistive technologies. See the Help page of 

InfoPath for resources on accessibility issues.  

5.3 Accessibility Tips  

5.3.1 Design for any browser. Avoid browser specific technology. Adhere to the HTML 4.0 

standard for best results for the most browsers.  

5.3.2 Try to employ browser built in supported technology for vital content (html text, gif 

images, etc) rather than proprietary formats such as Shockwave and PDF. If you do use 

proprietary formats, try to provide alternative methods to get the same content.  

_________________________________________________________________________________

Web Services Committee 

Page 48 

May 28, 2002