WEB PAGE GUIDELINES FOR Chesapeake Public Schools. (revised April 2006)

Similar documents
ADA Compliance for Online Courses Section Rehabilitation Act of CHECKLIST --

UNIVERSITY OF NORTH CAROLINA WILMINGTON

All content published on the District Website must: 1. Comply with all State and Federal law concerning copyright and intellectual property rights.

SDCS Unit A functional structure or sub-structure of the district, such as a school, administrative unit, office, department, division or branch.

Schoology Voluntary Product Accessibility Template (VPAT)

VPAT. Voluntary Product Accessibility Template. Version 1.3

Overview... 3 Goals and Objectives... 3 Roles, Responsibility, and Protocol Calendars... 4

Agilix Buzz Accessibility Statement ( )

Web Accessibility Checklist

Voluntary Product Accessibility Template (VPAT )

Section 508 Evaluation Template

Voluntary Product Accessibility Template

Web-based Internet Information and Application Checklist

VPAT. Voluntary Product Accessibility Template. Version 1.3. Supporting Features. Not Applicable. Supported with Exceptions. Supported with Exceptions

VPAT. Voluntary Product Accessibility Template. Version 1.3

TEXAS A&M AGRILIFE EXTENSION SERVICE PROCEDURES

Adobe Experience Manager (AEM) 6.2 Forms - Output Voluntary Product Accessibility Template

Section Software Applications and Operating Systems - Detail Voluntary Product Accessibility PageCenterX

Learn Saas with the Ultra Experience Voluntary Product Accessibility Template August 2017

VPAT. Voluntary Product Accessibility Template. Version 1.3

Adobe LiveCycle PDF Generator ES4 Voluntary Product Accessibility Template

VMware vsphere Update Manager 6.0 VPAT

Adobe EchoSign Voluntary Product Accessibility Template

VMware Virtual SAN with vsan Health Check Plugin 6.0 VPAT

Information Official District information as defined herein and/or by other Board policy.

Section 508 Compliance: Ensuring Accessibility to Web-Based Information

College Website Review and Revision for Accessibility

Fusion 4 General Help VPAT

Google Forms. Summary Table. Date: 11/2014 Name of Product: Google Forms Point of Contact: Richard Wu. Criteria Supporting features Remarks

Adobe Fireworks CS6 Voluntary Product Accessibility Template

Adobe LiveCycle Digital Signatures ES3 Voluntary Product Accessibility Template

VMware vcenter Site Recovery Manager 6.1 VPAT

Adobe LiveCycle Reader Extensions ES3 Voluntary Product Accessibility Template

Adobe Experience Manager (AEM) 6.2 Forms - Digital Signatures Voluntary Product Accessibility Template

Schoolwires Manual For Department Web Editors Georgetown ISD

VPAT. Voluntary Product Accessibility Template. Version 1.3

SmartBuilder Section 508 Accessibility Guidelines

VMware vsphere Web Client 6.5 VPAT

Duke Library Website Preliminary Accessibility Assessment

For a detailed description of the parent features and benefits, please refer to the following URL:

SecurityCenter 508 Compliance

Adobe Photoshop CS6 Voluntary Product Accessibility Template

VPAT. Voluntary Product Accessibility Template. Version 1.3

Lectora 508 Compliance Document

ACCESSIBILITY POLICY Effective Date: March 20, 2017

Adobe Experience Manager (AEM) 6.2 Forms Workbench Voluntary Product Accessibility Template

Criteria Supporting Features Remarks and explanations Section Software Applications and Operating Systems. possible exceptions

Adobe FormsCentral (Desktop Application) Voluntary Product Accessibility Template

Adobe Digital Publishing Solution for Windows Voluntary Product Accessibility Template

Voluntary Product Accessibility Template (VPAT)

Adobe Contribute 6.5 Voluntary Product Accessibility Template

Adobe Experience Manager (AEM) 6.2 Forms - Reader Extensions Voluntary Product Accessibility

Voluntary Product Accessibility Template PowerBroker Identity Services

Adobe Bridge CS5.1 Voluntary Product Accessibility Template

Accessibility Evaluation of Pearson REVEL Platform VPAT Document

Science. Voluntary Product Accessibility Template: Section 508

Adobe LiveCycle Rights Management ES3 Voluntary Product Accessibility Template

Voluntary Product Access Template (VPAT) Kronos webta 4.x

Note: This document describes normal operational functionality. It does not include maintenance and troubleshooting procedures.

Voluntary Product Accessibility Template (VPAT)

Section Web-based Internet information and applications - Incident Response Service (INRS) - Detail Voluntary Product Accessibility Template

Adobe Business Catalyst Voluntary Product Accessibility Template

Voluntary Product Accessibility Template

VPAT. Event Log Management v10 Accessibility. Version 1.3 of the VPAT Template

Wimba Voice VPAT. Date: March 25, 2008 Name of Product: Wimba Voice Tools version Contact for more Information:

Adobe CQ5.4 Voluntary Product Accessibility Template

VPAT. Voluntary Product Accessibility Template. Version 1.3. Summary Table VPAT. Voluntary Product Accessibility Template. Supporting Features

Voluntary Product Accessibility Template

Networx Universal. Supporting Features. Criteria. Remarks and explanations

Voluntary Product Accessibility Template

CBORD s Response to Voluntary Product Evaluation Template for NetNutrition

CBORD s Response to Voluntary Product Evaluation Template For GET

Adobe Acrobat.com Voluntary Product Accessibility Template

VPAT. Voluntary Product Accessibility Template. Version 1.3

Voluntary Product Accessibility Template (VPAT )

Adobe Experience Manager (AEM) 5.6 for Forms Portal Voluntary Product Accessibility Template

Rapid7 Nexpose: Voluntary Product Accessibility Template

VPAT. Voluntary Product Accessibility Template. Version 1.3

Summary Table Section 508 Voluntary Product Accessibility Template. Criteria Supporting Features Remarks and explanations Section 1194.

VPAT. Voluntary Product Accessibility Template. Version 1.3

Adobe Dreamweaver CC Voluntary Product Accessibility Template

Adobe LiveCycle Mobile Forms ES4 Voluntary Product Accessibility Template

Adobe Illustrator CS5.1 Voluntary Product Accessibility Template

VMware vcenter Orchestrator 5.5 VPAT

Networx Enterprise Proposal for Internet Protocol (IP)-Based Services. Supporting Features. Criteria. Remarks and explanations

Schedule Planner Section 508 Voluntary Product Accessibility Template

Networx Universal. Supporting Features. Remarks and explanations. Criteria

Summary Table for SolarWinds MFT Server

Section 508 Evaluation Template

Adobe Illustrator CC Voluntary Product Accessibility Template

Blackboard. Voluntary Product Accessibility Template Blackboard Learn Release 9.1 SP11. (Published January 14, 2013) Contents: Introduction

Voluntary Product Accessibility Template

VPAT. Voluntary Product Accessibility Template. Version 1.3 *

For a detailed description of the parent features and benefits, please refer to the following URL:

Adobe LiveCycle Server Administration ES3 Voluntary Product Accessibility Template

Voluntary Product Accessibility Template Retina Network Security Scanner

Adobe Photoshop Lightroom 3 Voluntary Product Accessibility Template

ELIZABETH CITY STATE UNIVERSITY Web Page Policy

Voluntary Product Accessibility Template (VPAT )

Networx Universal. Supporting Features. Remarks and explanations. Criteria

Transcription:

WEB PAGE GUIDELINES FOR Chesapeake Public Schools (revised April 2006) School Web pages are public documents welcoming the outside world to the school and linking students and staff to outside sources of information. Guidelines are required in the construction of school Web pages to ensure that information on the pages is appropriate for viewing by all Internet audiences. Web pages must support the educational objectives of Chesapeake Public Schools (CPS). These guidelines contain resources and documents related to publishing Web pages on the World Wide Web though Chesapeake Public Schools telecommunications network. The Office of Public Information and the Department of Information Technology along with the Web Page Guideline Committee collaboratively developed these guidelines as a key reference tool. This resource contains Chesapeake Public Schools Web site goals and specific guidelines for publishing at all levels. Questions about these guidelines or updates should be directed to the Ombudsman/Public Information Officer and the Department of Information Technology. PURPOSE Chesapeake Public Schools primary purpose for publishing Web pages is to provide information about department activities/services, schools, teachers/classes, student projects, and student extracurricular activities via Chesapeake Public Schools telecommunications network and the Internet. Educational resources for staff and the community may also be published online. PROCEDURE Pagemaster Each school and administrative department will designate a staff member to create, maintain and publish its site. This person will be designated as the school or department pagemaster. Site Content Approval When CPS Web pages are uploaded onto the Internet, the site becomes an official representative of the Chesapeake Public Schools. Because of this, the senior person in the department or school must approve the overall content, including updates and links, to ensure that it complies with CPS guidelines. In the schools, the principal approves Web pages. In an administrative department, the department head or that person s designee approves them. Signing the Web Page Approval Form indicates approval. This form must be attached to a hard copy of the page or update and sent to the Department of Information Technology. (See Appendix 1) Site Publishing All official Web pages must reside on the Chesapeake Public Schools Web server. Placing Web pages on a server is known as publishing a site. There are three possible ways for the pagemaster to accomplish this: by uploading files directly to the CPS Web server using FTP by e-mailing files to the Division Webmaster via GroupWise or Internet mail by providing all files to the Division Webmaster on a floppy disk or CD-ROM

CONTENT To ensure that content on CPS Web pages is both legal and consistent with the CPS mission, the following guidelines have been established. General Guidelines All publications must comply with the Board policies, administrative regulations, Chesapeake Public Schools Acceptable Telecommunications and Internet Use Policy, and these Web Page Guidelines. The content of Chesapeake Public Schools Web pages must be consistent with the educational objectives of Chesapeake Public Schools. All subject matter must relate to curriculum, instruction, school-authorized activities, general school-related information that is appropriate and of interest to others, or information that relates to schools within the District. Content must be reviewed carefully to ensure that nothing is inadvertently placed on Web pages that may misrepresent the school district or violate district policy. Content must be reviewed and updated on a regular basis. A revised mm/dd/yyyy line must appear at the bottom of each page. Personal information not related to education is not allowed on the Chesapeake Public Schools Web site. Copyright Web page publications must comply with all state, federal, and international laws concerning copyright, intellectual property, and use of telecommunications. A CPS copyright statement should be included on each page with a full disclaimer on the main homepage.(see Appendix 2) Pages must indicate that permission has been secured when copyrighted materials are published on them (e.g. published with permission of author. ) Advertisements Commercial use for the pursuit of personal or financial gain is prohibited. School Web pages may contain brief acknowledgements of school partnerships or sponsorships; however, any links of this nature should be linked to the official Chesapeake Public Schools Business Partnership page, not directly to the partner s or sponsor s website. Links Publications on the Chesapeake Public Schools Web site must identify affiliation with Chesapeake Public School and should link back to the main page (http://www.cps.k12.va.us) from the first page of any school or department s main page. All links to external sites must display a pop-up statement indicating that the Chesapeake Public School site is being left (see Appendix 3).

All links connecting to external sites must be approved by the school or administrative department pagemaster and are subject to approval by the principal or department head. External links should be periodically checked to ensure validity and content. Common courtesy, but not law, dictates that webmasters of externally linked sites be notified of use of such links. No Web page content should allow people accessing the page to contact any student directly. Communication must be directed either to the principal of the school or to the school pagemaster. School Web pages must include a mailto: link to the school pagemaster. The pagemaster must check electronic mail daily. Links to personal student, faculty, or staff Web pages from the Chesapeake Public Schools Web site are not permitted. Permission for Posting of Student Pictures, Names, & Work No student s email address, personal Web address, street address, or telephone number may be published at any time. Permission to publish a child s name, picture, and/or work must be obtained in any of the following situations: if a child is clearly recognizable in a picture; if a child is singled out in a picture with accompanying text that identifies him/her; if work attributed to a child is posted on a Web page. Permission may be obtained for all such situations during a school year on a single permission form. (See Appendix 4) The pagemaster must keep signed forms on files for the remainder of the school year, and references requiring permission must be removed at the close of the school year. Groups of student names, as for awards, teams, etc., may be published without permission, as long as an identifying picture of the honored individuals is not used. Filenames for web pages and images should be check to ensure that students names do not appear in the name. (e.g. johndoe.gif, johndoe.html ) Identification of Faculty or Staff Permission must be obtained from any staff or faculty member prior to displaying his/her photograph and/or work. (see Appendix 5)

School Start Page The opening school Web page contains the following information, which should be updated whenever information changes. This information can be updated through the Start Page Updater. school name school address telephone number fax number school hours grade structure principal s name link to supplies list link to lunch menu link to map mission statement notes from the principal email address for the principal and/or the principal s designee date of last modification picture of the school and principal & mascot link to return to the appropriate point in the District Web pages link to events news section Personal Home Pages Web pages containing personal information about students or staff members are not permitted. Students may create content pages under their instructor s supervision such as artwork, poetry, etc., but not personal pages about themselves. Similarly, staff members may create pages, which are education oriented. Links to external personal Web pages from the Chesapeake Public Schools Web site is not permitted. WEB PAGE DESIGN AND TECHNICAL STANDARDS Web Editor Though several Web site software packages are available for Web page management, the application of choice in Chesapeake Public Schools is Microsoft FrontPage 2000. Design: Plan the design carefully. Carry a specific color scheme or theme throughout the pages. Include empty or white space to create an uncluttered look. Use tables to organize and format content. Keep graphic sizes below 50K. Keep total page size below 500K. Avoid pages that require a visitor to scroll down excessively. Limit animated graphics. Identify or clearly mark graphic hyperlinks as links. Graphics should support and not overpower the information being presented. Use sounds only to complement content. Use small and/or compressed JPG files whenever possible.

Navigation Provide a link back to your homepage. Not all users are familiar with the back button. Visitors should be able to navigate to the most important/ frequently accessed information in less than three clicks. Content Content must be school, curriculum, or system related. Content must be approved by the school or department head prior to publishing. Include a copyright statement on every page and disclaimer on the homepage. Naming Files Testing Be consistent with file extensions decide whether you will use.htm or.html when naming all of your web pages. DO NOT use file names that contain spaces. Use a hyphen, if necessary. (e.g. gradefour.html or grade_four.html is preferred over grade four.html ). Avoid punctuation marks in file name or mixing upper and lower case. Web pages should be tested on Internet Explorer. Be sure all hyperlinks are active or current. Repeated Error 404 s (File Not Found) will annoy visitors. Many Web editors will leave local drive paths if you are not careful it is best to test with a PC that was NOT used to create the page Use the RELOAD or REFRESH button on your browser after making any changes to your Web page or you may not be seeing the latest revision.

Accessibility Requirements In an effort to ensure web page accessibility for visitors with disabilities, the General Assembly requires all state executive branch agencies and institutions of higher education to comply with Section 508. Chesapeake Public Schools web pages should be developed according to Section 508 standards so that users with disabilities can more readily access information. Chesapeake Public Schools Department of Information Technology will provide training and assistance to all pagemasters for the purpose of ensuring that school and department web pages meet Section 508 standards. Be sure to visit the following helpful websites: http://www.section508.gov (Section 508 in Depth) http://www.adainfo.org (Americans With Disabilities and Information Technology Training Center) http://bobby.watchfire.com (Offers Free Web Page Accessibility Testing) The following is a summary of Section 508 standards, as they apply to web pages. (see Appendix 7 for an expanded checklist) Provide equivalent alternatives to auditory and visual content. Color: Make meaning independent of text color. Readability: Make pages style-sheet independent. Server-Side Image Maps: Include redundant text links for server-side image maps. Client-Side Image Maps: Use client-side image maps when possible. Data Tables 1: Put row and column headers in data tables. Data Tables 2: Associate all data cells with header cells. Frames: Title all frames. Flicker Rate: Avoid screen flicker at harmful frequencies. Text-Only Alternatives: Provide and update equivalents for dynamic content. Scripts: If site utilizes scripting languages, make sure the information provided by the script is readable by assistive technology. Applets & Plug-Ins: Provide links to plug-ins or other required applications that can be used by assistive technology devices. Forms: Make electronic forms accessible via assistive technology. Navigation Links: Provide an option to skip repetitive links. Time: Give users sufficient time to complete tasks, when a timed response is required. WEB DESIGN ASSISTANCE Additional Help Pagemasters should contact Information Technology (757) 482-5635 if additional web design / publishing instruction is desired. Information Technology should be contacted to assist whenever the pagemaster is unable to make periodic revisions to a school website.

Chesapeake Public Schools Educational Services Center 369 Battlefield Boulevard S. Chesapeake, VA 23322 Appendix 1 Web Page Approval Form When web pages are placed onto the Internet, your site becomes an official Representative of the Chesapeake Public Schools. Because of this, the senior person must approve the overall content. In the schools, the principal approves web pages. In an administrative department, the department head or that person s designee approves them. Please: Fill in the blanks below. Attach web page updates. Mail or send the completed form to the: Webmaster (Mary Stinnette) Department of Information Technology/ Educational Services Center Date: School Principal/Department Head: Pagemaster Name: Pagemaster E-mail Address: Summary of changes and/or updates: I have reviewed the enclosed web page files and approved the content for publication on the Chesapeake Public School District web site. Principal/Department Head Signature: Date:

Chesapeake Public Schools Educational Services Center 369 Battlefield Boulevard S. Chesapeake, VA 23322 Appendix 2 Copyright Statement & Disclaimer Please include the following Disclaimer on your school or department homepage: The Chesapeake Public School System is an equal educational opportunity school system. The School Board of the City of Chesapeake also adheres to the principles of equal opportunity in employment and, therefore, prohibits discrimination in terms and conditions of employment on the basis of race, sex, national origin, color, religion, age, or disability. Please include the following Copyright statement with the current year at the bottom of each page: Copyright 2005 Chesapeake Public Schools All Rights Reserved.

Chesapeake Public Schools Educational Services Center 369 Battlefield Boulevard S. Chesapeake, VA 23322 Appendix 3 External Site Alert Message Copy this code into the HEAD section of your HTML code: <script language = "Javascript"> <!-- function leave() { window.alert('you are now leaving the Chesapeake Public Schools Web Site.'); } //--> </script> Copy this code into the BODY section of your HTML code where you want to post your external link: <a href="http://www.yourlink.com" onclick="leave();">your Link</a>

Chesapeake Public Schools Educational Services Center 369 Battlefield Boulevard S. Chesapeake, VA 23322 Appendix 4 Parental Release Form for Publication of Student Information on the Web In order to comply with the Chesapeake Public Schools Web Page Guidelines for site content, the following is a required parental release form for posting a students name, photo or work on the Chesapeake Public Schools web site. School Name: Child Name: Parent / Guardian Name: Parent / Guardian Phone Number:( ) The selection you choose below will appear on your child s school web site for recognition or education purposes. Your child s name and picture will not be shown together on our web site. As the parent / guardian of the student named above I give permission to use the following on his/her school s web site: Please choose one of the following: Student s Picture or Student s Name or Work created by student with or without student s name Signature Date

Chesapeake Public Schools Educational Services Center 369 Battlefield Boulevard S. Chesapeake, VA 23322 Appendix 5 Release Form for Publication of Faculty/Staff Information on the CPS Website Full Name: I authorize to publish information (School Name) as indicated below on the World Wide Web. I understand that this information will be available to anyone on the World Wide Web. Signature: Date: Please note that this does not replace the Acceptable Use Policy or imply Permission to use Internet services. Publication of this data is not required to use Internet services. Please check one: Publish my Name as shown: DO NOT publish my Name Please check one: Publish my Photo DO NOT publish my Photo Please check one: Publish my e-mail address DO NOT publish my e-mail address Other:

Chesapeake Public Schools Educational Services Center 369 Battlefield Boulevard S. Chesapeake, VA 23322 Appendix 6 School Start Page Requirements School name School address School phone number School fax number Hours of operation Grade structure Principal s name Email address for the Pagemaster or Pagemaster designee Picture of school Picture of principal Picture of school mascot Link to return to the appropriate point in the District Web pages News and events information School mission statement or notes from principal Link to school site (if one exists) Link to pertinent school lunch menu Link to map information for school location Link to SOL scores for that school General student supplies listing for school

Appendix 7 (1 of 2) SECTION 508: Web Site Accessibility Guidelines Style Sheets 1. Pages are readable and usable without style sheets (e.g., when the browser does not support them or the user has turned them off). Images and Image maps 1. All images and image maps have alternative text. 2. Graphics that present important information (especially charts, tables, and diagrams) have an associated longer description of the graphic (i.e., via a description link or the " longdesc" attribute) Furthermore, authors have included internal text in images for formats that support it. 3. Client-side image maps have been designed instead of server-side image maps. Furthermore: o For each client-side image map, each of the map's links has an associated description. o For each server-side image map, a list of the map's links are provided as text links (on the same page, on an alternative page that is accessible, or within the body of the OBJECT element). Applets and Scripts 1. All scripts have a non-script alternative (the NOSCRIPT element). 2. The user can freeze any moving or blinking text. 3. All applets have alternative text. 4. Descriptions are provided for applets that convey important information. 5. Alternative mechanisms (e.g., a form) are provided for applets that gather information. 6. Applets that require user interaction that cannot be duplicated in an alternative format are directly accessible. Audio and Video 1. All audio information has an associated transcript. 2. All video information has an associated audio description. 3. All video information has an associated transcript. 4. Transcripts and audio descriptions are synchronized with audio/video information, either directly or via a synchronization file.

Appendix 7 (2 of 2) Text, Symbols, Punctuation, Phrases, and Paragraphs 1. HTML structural elements are only used to convey meaning, not presentation. 2. HTML presentation elements are only used to convey presentation, not structure. 3. Headings are nested properly and are not used for formatting. 4. The BLINK and MARQUEE elements have not been used. Lists and Outlining 1. List structure and list items are correctly encoded with proper HTML elements. Style sheets, not markup, are used to control layout. Tables 1. Table cells are explicitly associated with row and column labels. 2. Tables are not used to arrange text documents in columns. Links 1. Link text makes sense when read out of context, but is not too verbose. Frames 1. Each frame document (the FRAMESET element) has a non-frame alternative (e.g., the NOFRAME element). 2. An image does not appear directly in a frame but is part of a document included in a frame. 3. All frames have titles. User-Input Forms 1. Image maps are not used to create graphical "submit" buttons. 2. Each label is explicitly associated with its control. 3. Images used as "submit" buttons have alternative text. If All Else Fails... If after best efforts, a page is still not accessible, provide a link to an alternative page that is accessible, has equivalent information, and is maintained with the same frequency as the inaccessible page.