Accessibility: A Cal State
Fullerton Tradition Cal State Fullerton's commitment to accessibility is a tradition that has endured for more than 35 years--it is a tradition that has historically exceeded requirements to barrier-free design. In the early 1970s, then-president L. Donald Shields emphasized this commitment when he got into a wheelchair and navigated the campus to spotlight the need for eliminating barriers.
In a letter about promoting an accessible learning environment, President Milton A. Gordon wrote:
"Our University is strongly committed to reaffirming this policy and maintaining an environment that guarantees students with disabilities full access to its educational programs, activities and facilities. In supporting our efforts to meet this commitment, I call upon the faculty and staff to be especially sensitive to the needs of this population . . . ."
Building accessible web pages is a key part of this effort, and goes beyond complying with laws. It is about maintaining an environment that is both inviting and supportive of learning--for everybody. |
Chancellor Reed Confirms Commitment to Accessibilty with Executive Order 926
By signing Excecutive Order 926 in CSU Chancellor Charles Reed confirmed the CSU's commitment to accessibilty and cited that Section 11135 of the California Government Code was amended (by Senate Bill 302,
Chapter 784, Statutes of 2003) to clarify that Section 508 of the 1973
Rehabilitation Act applies to the CSU.
Providing access to persons with disabilities has always been a serious issue for the CSU. Specifically, CSU, Fullerton has demonstrated a commitment to removing barriers and providing accommodation in numerous ways.
Cal State Fullerton will continue to build on its reputation for accessibility.
IT's web group can provide assistance to help ensure that your web sites and computer applications meet Federal standards.
Test Your Pages
Web pages must be checked and repaired, if needed, before they are posted to a production server.
Administrative web pages developed for public viewing must meet ADA 508 standards for accessibility before they can be posted. (In the case of web-based instructional materials, student access is handled on a case-by-case basis by the office of Disabled Students.) Administrative web pages will not be loaded to the production web site unless they pass automated testing and visual checks with zero exceptions.
How to Test Your Pages
There are a couple of test programs. HiSoftware's Cynthia Says is one of these and is available online at http://www.cynthiasays.com/ Only one page can be tested at a time.
AccVerify uses the same test engine as the server-level AccMonitor program now being used by Information Technology to track accessibility in the university's domain. AccVerify can test an entire site at once. AccVerify is available for download below.
Tools
Download Accessibility Tools
Testing Suite Software* (2008 Versions)
Installation instructions
AccVerifyRepair_11 Check your web pages for 508 accessibility.
AccVerify/Repair Settings: Be sure your AccVerify/Repair settings match those in this document
Hicaption: A tool for captioning video.
Link Validation: Checks for broken links.
*About these files: These applications are not compatible on Macintosh computers. These programs are not currently supported by HelpDesk. If you have questions about installation or use, please contact Web Design & Support at x5544. |
Monthly Accessibilty Scan
The entire web (fullerton.edu) is scanned once each month to monitor accessibility issues; the resulting reports list all web pages which fail to pass accessibility testing. Reports are sent to webmasters, appropriate administrators and vice presidents. Report summaries. |
If you have questions about making a page accessible, please contact Web Design & Support.
Accessibilty Report Cards
We've compiled the results of our AccMonitor automated web site testing. Follow this link to see the results.
Learning How to Make Web Pages Accessible
IT Training offers classes in web accessibilty. Contact Timothy Benbow.
Lynda.com web training modules are available online from any campus networked computer. No login is required. http://www.calstate.edu/accessibility/tutorials/lynda/
WebAIM (Web Accessibility in Mind) has a wealth of resources at http://www.webaim.org including checklists, tutorials, reading suggestions, and even a screen-reader simulation.
Coypright Information
Making audio, video and print media accessible sometimes requires getting the permission of the copyright holder or owner of the material in question. Be clear about what's required before posting material on the web. Copyright issues concerning media, textbooks, YouTube, and captioning. and other copyright concerns are covered in this Copyright FAQ compiled by the legal staff at the Chancellor's Office.
Accessibility Links
CSU Coded Memo: Access to Electronic Information Technology for Persons with Disabilities
Section 504 of the1973 Rehabilitation Act
Summary of Section 508 Standards
Americans with Disabilities Act of 1990
Section 255 of the Telecommunication Act of 1996
California Government code 11135 of 2003
Federal IT Accessibility Initiative
The 508 Web Standards
A website is in compliance with the 508 standards if it meets the following:
§1194.22 Web-based intranet and Internet information and applications
(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
(d) Documents shall be organized so they are readable without requiring an associated style sheet.
(e) Redundant text links shall be provided for each active region of a server-side image map.
(f) 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.
(g) Row and column headers shall be identified for data tables.
(h) 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.
(i) Frames shall be titled with text that facilitates frame identification and navigation.
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
(k) 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.
(l) 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.
(m) 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).
(n) 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.
(o) A method shall be provided that permits users to skip repetitive navigation links.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
Most of these rules were already embodied in the W3C's Priority 1 checkpoints, but some additions were made:
Notes on § 1194.22
1. Paragraphs (a) through (k) of this section are consistent with the following Priority 1 Checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5, 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium:
| Section 1194.22 Paragraph |
WCAG 1.0 Checkpoint |
| (a) |
1.1 |
| (b) |
1.4 |
| (c) |
2.1 |
| (d) |
6.1 |
| (e) |
1.2 |
| (f) |
9.1 |
| (g) |
5.1 |
| (h) |
5.2 |
| (i) |
12.1 |
| (j) |
7.1 |
| (k) |
11.4 |
Paragraphs (l), (m), (n), (o), and (p) of this section are different from WCAG 1.0.
Web pages that conform to WCAG 1.0, level A (i.e., all priority 1 checkpoints) must also meet paragraphs (l), (m), (n), (o), and (p) of this section to comply with this section.
WCAG 1.0 is available at http://www.w3.org/TR/WAI-WEBCONTENT.
These regulations are not difficult, but do require developers to be aware and to take the extra steps necessary. |
