Loading...

3.0 Guidelines

3.0.1 All areas of the college are encouraged to provide materials they believe will be of interest to people within and outside the college. Examples include, but are not limited to:

  • information about current offerings and services provided by the college
  • how to contact individuals and departments of the college
  • examples of student work
  • access to various public documents of the college
  • employment opportunities
  • promotional materials.

3.0.2 All IVCC pages created by college divisions, departments, programs and administrative offices are considered "official" in that they must have the approval of the college president or the appropriate vice president, director or dean before being posted to the Web. Those divisions, departments, programs and administrative offices that have web pages are responsible for posting and updating information whether or not they have direct access to the web site. It is advised that each area of the college that has web pages posted have, at minimum, one person in charge of overseeing those pages. Personal pages created by faculty follow the provisions of the academic freedom policy as outlined in the Board Policy Manual and found in Appendix A of this document.

3.0.3 Administrative and academic departments are required to develop official pages for linkage to the IVCC home page so that a comprehensive view of the college is offered. Departments wishing to put up web pages will designate a person within their unit who will be responsible for maintaining the information provided. Those designees will work closely with the Webmaster to establish their presence and will be the only individual(s) authorized to enter material onto their site. Faculty and staff may be granted server access to their individual and/or class pages.

3.0.4 Photographs of individuals placed on the IVCC web site must have a signed written permission document on file of all individuals that appear in the photograph. (This file should be kept by the individual(s) who took the photograph.)  Pictures of minors (under age 18) must have written permission from a parent or guardian before their image is place on a web page. Images created/taken by individuals must have signed permission from the copyright holder in order to be used on a web page. If the creator is a minor (under age 18), written permission for use must come from a parent or guardian. Official permission documents can be obtained from the Webmaster.  News organizations like the Student Newspaper are held by laws and rulings of federal, state, local laws and their respective press affiliation.  (Photo releases.)

3.0.5 IVCC does not grant students access to the web server(s). Access may be given to student workers on a case-by-case basis. Instructors can request temporary access (less than two weeks) for students who are working on a web site project.

3.0.6 All web pages should have the 'Text Only' link on the upper-left hand side of the web page and it should be visible.  This is done in order to help facilitate better access to those students with disabilities who view our site and to help IVCC comply with ICCB requests.  IVCC uses LIFT Text Transcoder. LIFT Text Transcoder is a software system that converts web pages into straight, plain text so that those with assistive technology to view web pages can read them easier.

 

3.1 Web Page General Guidelines

3.1.1 All college web pages will adhere to the guidelines enumerated in this section. Administrative and academic departmental pages will strictly adhere to the web page template that can be obtained from the Webmaster. The appropriate template is to be used for official college web pages only.

These standards are a digest of the Illinois Web Accessibility Standards (IWAS) and are based on Federal "Section 508" and World Wide Web Consortium accessibility guidelines.

The Illinois Web Accessibility Standards are designed to meet or exceed all Federal Section 508 requirements and all WCAG "Priority 1" Checkpoints. The Illinois Standards exceed the minimum requirements in many areas, incorporating a number of WCAG "Priority 2" and "Priority 3" Checkpoints as well as additional requirements identified through practical experience working with Illinoisans with disabilities. Each Guideline in the Illinois Standards includes a reference to the corresponding Section 508 requirements and WCAG Checkpoints.

We have further categorized the Illinois standards for ease of implementation at IVCC. Coding is consistent with the IWAS. The IWAS documentation includes detailed explanations of why each element is necessary and how it can be achieved.

 

Accessibility Needs

What you need to do if not using the Content Management System.

What you need to do if using the Content Management System.

1.1 - Use valid, standard web programming code.
WCAG 3.2, 11.1, 11.2

1.2 - Use appropriate markup to convey document structure.
WCAG 3.5, 3.6, 3.7, 5.4

1.3 - Provide meaningful page titles.
WCAG 13.2

1.4 - Use headings to introduce sections and sub-sections, and use them in the correct order.
WCAG 3.5, 12.3

1.5 - Use lists to identify series of related items, including navigation menus.
WCAG 3.6

2.1 - Use text to display text, unless formatting that cannot be achieved with CSS is required.
WCAG 3.1

2.2 - Use relative sizes for fonts.
WCAG 3.4

2.3 - Identify the language of text.
WCAG 4.1, 4.3

2.4 - Use images instead of "ASCII art."
WCAG 1.1; 508 a

3.1 - Do not convey information with color alone.
WCAG 2.1; 508 c

3.2 - Use contrasting foreground and background colors.
WCAG 2.2

4.1 - Provide appropriate "alternate text" for all images.
WCAG 1.1; 508 a

4.2 - Provide full descriptions for graphs, diagrams, and other meaningful images.
WCAG 1.1; 508 a

5.1 - Provide alternate text for each area in client-side image maps.
WCAG 1.1; 508 a

5.2 - Use client-side image maps instead of server-side image maps unless areas cannot be defined with available shapes.
WCAG 1.2, 9.1; 508 e, f

6.1 - Do not convey information with sound alone.
WCAG 1.1; 508 a

6.2 - Do not automatically play audio.

6.3 - Provide text transcripts for audio containing speech when it is provided to the public and/or required to be viewed by employees.
WCAG 1.1; 508 a

7.1 - Provide synchronized captions for all multimedia containing essential auditory information when it is provided to the public and/or required to be viewed by employees.
WCAG 1.4; 508 b

7.2 - Provide audio descriptions for all multimedia that contains essential visual information when it is provided to the public and/or required to be viewed by employees.
WCAG 1.3; 508 b

8.1 - Provide a means of pausing any moving, blinking, scrolling, or auto-updating information.
WCAG 7.1, 7.2, 7.3

8.2 - Do not include content that flashes faster than 3 times per second.
WCAG 7.1; 508 j

9.1 - Ensure that links are understandable out of context.
WCAG 13.1

9.2 - Provide a means of skipping past repetitive navigation links.
WCAG 13.6; 508 o

9.3 - Avoid using small links.

9.4 - Ensure that same-page links move keyboard focus as well as screen focus.

10.1 - Provide labels or titles for all form fields.
WCAG 12.4; 508 n

10.2 - Provide legends for groups of form fields.
WCAG 12.3; 508 n

10.3 - Ensure that form fields are in a logical tab order.
WCAG 9.4; 508 n

10.4 - Avoid placing non-focusable text between form fields.
508 n

10.5 - Ensure that text in form fields can be enlarged.

11.1 - Identify a header cell for each column and row in simple data tables.
WCAG 5.1; 508 g

11.2 - Identify relationships in complex data tables using id and headers attributes.
WCAG 5.2; 508 h

11.3 - Provide summary attributes for data tables.
WCAG 5.5

12.1 - Provide concise, unique, and understandable titles for frames.
WCAG 12.1; 508 i

12.2 - Avoid using hidden, empty, or non-essential frames.

13.1 - Ensure that scripted functions are usable with assistive technologies.
WCAG 6.2, 6.3, 6.5, 8.1; 508 l

13.2 - Ensure that significant interactions can be performed with both keyboard and mouse.
WCAG 6.4, 9.2, 9.3; 508 1194.21 a

13.3 - Avoid changing focus unexpectedly.
WCAG 8.1; 508 l

13.4 - Avoid changing content unexpectedly.
WCAG 8.1; 508 l

14.1 - Use accessible embedded objects whenever possible.
WCAG 8.1; 508 m

14.2 - If an inaccessible embedded object must be used, provide an accessible alternative that includes the same content and functionality.
WCAG 6.2, 11.4; 508 k

15.1 - Provide natively accessible downloadable documents whenever possible.

15.2 - If a downloadable document cannot be made natively accessible, provide an accessible alternative that includes the same content and functionality.
WCAG 11.1, 11.4; 508 k

16.1 - Notify users of time limits and provide a means to extend time if possible.
508 p

16.2 - Do not automatically refresh the current page.
WCAG 7.4, 7.5

17.1 - When using tables for layout, ensure that reading order is logical.
WCAG 5.3

17.2 - When using style sheets for layout, ensure that reading order is logical.
WCAG 6.1; 508 d

17.3 - Avoid horizontal scrolling.

18.1 - Use separate accessible versions only as a last resort.
WCAG 11.4; 508 k

1.2 - Use appropriate markup to convey document structure. 
WCAG 3.5, 3.6, 3.7, 5.4

1.3 - Provide meaningful page titles. 
WCAG 13.2

1.4 - Use headings to introduce sections and sub-sections, and use them in the correct order. 
WCAG 3.5, 12.3

1.5 - Use lists to identify series of related items, including navigation menus. 
WCAG 3.6

2.1 - Use text to display text, unless formatting that cannot be achieved with CSS is required. 
WCAG 3.1

2.4 - Use images instead of "ASCII art." 
WCAG 1.1; 508 a

6.1 - Do not convey information with sound alone. 
WCAG 1.1; 508 a

6.2 - Do not automatically play audio. 

6.3 - Provide text transcripts for audio containing speech when it is provided to the public and/or required to be viewed by employees.
WCAG 1.1; 508 a

7.1 - Provide synchronized captions for all multimedia containing essential auditory information when it is provided to the public and/or required to be viewed by employees.
WCAG 1.4; 508 b

7.2 - Provide audio descriptions for all multimedia that contains essential visual information when it is provided to the public and/or required to be viewed by employees.
WCAG 1.3; 508 b

8.1 - Provide a means of pausing any moving, blinking, scrolling, or auto-updating information.
WCAG 7.1, 7.2, 7.3

8.2 - Do not include content that flashes faster than 3 times per second.
WCAG 7.1; 508 j

9.1 - Ensure that links are understandable out of context.
WCAG 13.1

9.4 - Ensure that same-page links move keyboard focus as well as screen focus.

10.4 - Avoid placing non-focusable text between form fields.
508 n

13.2 - Ensure that significant interactions can be performed with both keyboard and mouse.
WCAG 6.4, 9.2, 9.3; 508 1194.21 a

14.1 - Use accessible embedded objects whenever possible.
WCAG 8.1; 508 m

15.1 - Provide natively accessible downloadable documents whenever possible.

15.2 - If a downloadable document cannot be made natively accessible, provide an accessible alternative that includes the same content and functionality.
WCAG 11.1, 11.4; 508 k

16.1 - Notify users of time limits and provide a means to extend time if possible.
WCAG 7.4, 7.5

17.3 - Avoid horizontal scrolling.

All individuals who have access to the Web server are responsible for backing up their web pages to their personal network drive.

To backup your web site that is not in the Content Management System:

  1. In FrontPage Explorer, click on the File Menu and choose Publish Web.
  2. In the box that pops up, give the name of the directory that you want the backup to go into preceded by u:\
  3. If the folder does not exist, it will ask if you want to create it. Click YES.

After awhile, the pages will be finished backing up to your U drive.

 

3.2 Grant Funded Programs Web Page Guidelines

3.2.1 All grant program web sites that are created after January 1, 2001 will need to follow the web site template.

 

3.3 Faculty and Staff Personal and Class web pages

3.3.1 Faculty and staff are responsible for the quality and content of their pages and student web pages that are incorporated into the college web site. Design must adhere to general guidelines (3.1). Optional templates are available upon request. Faculty are encouraged to contain the following information for usability reasons.

  • It is recommended that the first page should contain the faculty and staff member’s name, title, phone number and extension, office room number, office hours, e-mail link, last updated and an outline for each course.
  • It is recommended that all pages include regressive link(s) and last updated information.  (Regressive links are local navigation on your pages that allows visitors to easily go back to your home page or different parts of your web site.)

 

3.4 Student Organizations

3.4.1 Recognized student organizations (those that are approved by the Student Government Association) are encouraged to create web sites to provide information about their programs, services and events. Each web site must also have a faculty sponsor who is responsible for the content of the organization's pages. Design must adhere to general guidelines (3.1). Optional templates are available upon request.

 

3.5 Submitting and Posting Materials to the Web Site

3.5.1 A designee will submit departmental pages that follow policies and guidelines in this document.

3.5.2 All submissions must be completely proofread, spell-checked and fully ready for review and publishing. The author who submit(s) any material(s) must obtain copyright approval when necessary. Copies of any permission documents must accompany the submission(s).

3.5.3 Since content on the Web is considered to be "published", any content that is copyrighted by another individual or group and is posted on the Internet would be a violation of copyright laws. If you wish to post to the Internet, you must have written permission from the copyright holder. When requesting copyright permission you should include your name and how you can be contacted, including your full e-mail address. You should also include how and why you are using the materials and the information on how to contact the college Webmaster.

3.5.4 Submissions are to be provided on disk in HTML or Microsoft Word format. Submissions should include hard copies showing how the author would best like to see the documents displayed. Also submit a list of all links to, and all links from, the submitted page, so that appropriate linkages can be built.

3.5.5 Submissions can be turned into the Webmaster for posting on the web site (ten business days in advance of the date it is needed on the web site) or posted by a designated individual who has server access.  The time to create graphics, web applications or forms will be determined on a case-by-case basis.

3.5.6 Video and Audio for IVCC

  • All copyright permissions must be obtained and turned into the Community Relations office.

  • All signed consent to video and/or audio record should be held on file by the office who requested the recording.

Video and Audio Requirements for IVCC

Video

Resolution

Recommended: Original resolution of your video - for HD it is 1920x1080 (1080p) or 1280 x 720.

Bit rate

Because bit-rate is highly dependent on codec there is no recommended or minimum value. Videos should be optimized for resolution, aspect ratio and frame rate rather than bit rate.

Frame rate

The frame rate of the original video should be maintained without re-sampling. In particular pulldown and other frame rate re-sampling techniques are strongly discouraged.

Codec

H.264 or MPEG-2 preferred.

Preferred containers

FLV, MPEG-2, and MPEG-4

Audio

Codec

MP3 or AAC preferred

Preferred containers

FLV, MPEG-2, and MPEG-4

Sampling rate

44.1kHz

Channels

2 (stereo)

 

3.6 SSL Certificate Guidelines

3.6.1 Any site or page that wishes to be secured with an SSL certificate must be first reviewed by the Webmaster.