Accessibility
Section 508 closely maps to WCAG 1.0, Priority 1. Tom Jewitt, a Professor in Computer Engineering and Computer Science, CSU Long Beach, has written an excellent comparison of Section 508 and WCAG 1.0 that "suggests ways that developers can make their life easier while meeting both the letter and the intent of the law."
Tom's comparison of 508 and WCAG:
http://www.tomjewett.com/accessibility/section508.html
The legal requirements for Web materials accessibility are Section 508, but according to the 508 guidelines WCAG 1.0 Priority 1 may also be employed with the caveat that five additional 508 guidelines are followed. As the 508 guidelines state: "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)".
This language can be seen at:
http://www.access-board.gov/sec508/standards.htm#Subpart_b
The bottom line is that CSUN should follow the Chancellor's Office ATI in requiring adherence to state and federal law, which in turn use Section 508 guidelines, which closely map to WCAG 1.0 Priority 1 with the addition of 508 paragraphs (l), (m), (n), (o), and (p). However, since the ATI states "including but not limited to" I am going to state that if you want to also adhere to WCAG 1.0 Priority 2 and 3, that there is no reason not to do so.