divider
Link to Home - Montgomery College Maryland
STANDARDS HOME WEB STANDARDS RECOMMENDED GUIDELINES TRAINING
     


MC Specific Standards

  1. Every web directory on MC live servers MUST have a file called index.htm or index.html, and this file must be the top-level navigation 'home' page for that directory.
  2. Display the name of the Content Manager, phone number, e-mail, and mailing address on the index page (home page) of each site.
  3. Use links to display important content that is managed by other college units -- especially such time-sensitive information as schedules, curriculum, and course descriptions -- in order to avoid outdated material and errors. Do not replicate or paraphrase such information directly on your pages.
  4. Review content frequently and update as needed to ensure accuracy and currency, especially near the opening of registration for each new semester.
  5. Display a standard Montgomery College banner across top of the page for all top level pages and on index (home) page for department and individual (personal) web sites. The banner must load each time from the main College website -- i.e. banner image should not simply be copied onto your local page. Please see http://www.montgomerycollege.edu/webinfo/bannerOptions.html for a list of banner images. (Note: This standard does not apply to MC Infonet website.)
  6. Name files properly. Use only non-special characters and no spaces in web site filenames.
  7. Once a set of web pages has been published, maintainers should avoid reorganizing the material in ways that change the file names of any part of the material. There is no way to judge how widely existing URL's have been book-marked or linked to from other locations. Arbitrary name changes will cause content to disappear. If a name change is unavoidable, always cover any prior file names with working pages directing the viewer to the new location.
  8. When entirely new folders are created -- even inside already existing accounts -- any shifting of previously existing links to point to material in the new folder(s) must be managed, in cooperation with IT Web Group staff, to preserve 'automatic' forwarding from the legacy URL's at least until all in-house menus and directories can be brought up to date with this new navigation. Only then will warning message be loaded at the legacy URL, for outside clients to update their bookmarks.
  9. Each document's <HEAD> element must contain a meaningful and concise <TITLE>.
  10. Use relative hyperlinks. This allows web pages to be domain name or path independent, increasing their portability.
  11. Ensure that web pages successfully function in the most commonly used Internet browsers.
  12. Content Manager or Point of Contact is responsible for maintaining back-up of web pages, and for restoring their individual sites in the event of any corruption of online data (such as accidentally loading an incorrect page, needing to restore an earlier version, etc.)
  13. Always reference 'http://www.montgomerycollege.edu' as the official URL of Montgomery College.
  14. Clearly identify the target of each link. Link text should be meaningful enough to make sense when read out of context. For example, "Follow this link for exam information" --- but NEVER "Follow this link for exam information"

Accessibility Standards

MC supports accessibility of College websites to all users, including people with disabilities using assistive technology. To promote accessibility, the College will use Federal Section 508 Standards for Electronic and Information Technology (36 CFR §1194.21-.22).Link to EXTERNAL SITE The 508 standards are listed below with links to a tutorial to assist developers in applying the Standards. Links to and examples from the US Access Board's implementation guidelines, as well as the MC .edu and Intranet websites are also provided to present a variety of approaches to meet the accessibility standards.
  1. A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).
  2. Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
  3. Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
  4. Documents shall be organized so they are readable without requiring an associated style sheet.
  5. Redundant text links shall be provided for each active region of a server-side image map. [Note: Montgomery College websites do not use server-side image maps.]
  6. Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
  7. Row and column headers shall be identified for data tables.
  8. Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.
  9. Frames shall be titled with text that facilitates frame identification and navigation.
  10. Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz (2 to 55 flashes per second).
  11. A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.
  12. When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.
  13. When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).
  14. When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
  15. A method shall be provided that permits users to skip repetitive navigation links.
  16. When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

>>Back to Top

 

divider


Further information and assistance with building accessible websites may be obtained from
the Federal Section 508 Standards for Electronic and Information Technology (36 CFR §1194.21-.22)Link to EXTERNAL SITE.
Users may also wish to consult
the MD IT NVA Regulatory Standards Link to EXTERNAL SITE
for information on recent Maryland legislation on accessible websites.

Please direct comments and suggestions to webmaster@montgomerycollege.edu.
 

divider