This website uses cookies. Learn more via our web privacy policy. For questions, please email dataprivacy@columbusstate.edu.
Web Accessibility Guidelines - Columbus State University

Presidential Search Information and Updates

University Information & Technology Services

Web Accessibility Guidelines

Accessibility is a high priority for Columbus State University (CSU). By endorsing Web accessibility guidelines established by the World Wide Web Consortium (W3C), CSU enables full access to institutional information, programs, and activities offered through the Web.

Every effort is been made to design and develop webpages that comply with or exceed the W3C's Web Content Accessibility Guidelines (WCAG). In addition, CSU has been actively revising all webpages to meet or exceed W3C accessibility standards.

The UITS Web Services team conducts regular monthly web accessibility checks of the CSU website on the home page, all main secondary pages, and a spot check of lower level pages. CSU utilizes services provided by Siteimprove's platform to identify potential accessibility issues, and other similar resource may be used to perform the inspection. The Siteimprove platform will also perform weekly automated checks for accessibility issues and provides weekly reports to the UITS Web Services team. Any accessibility errors detected will be addressed as quickly as possible. If you should encounter an accessibility issue on our web site, please email us at uits_webservices@columbusstate.edu.

Columbus State University Web Accessibility Guidelines

WCAG are prioritized on a scale from 1 to 3, with Priority 1 being a set of guidelines (or checkpoints) that must be satisfied or "one or more groups will find it impossible to access information in the document." Paragraphs (a) through (k) correspond to WCAG Priority 1 guidelines; paragraphs (l) through (p) are additions that, when used in conjunction with the WCAG guides, meet accessibility standards detailed in Section 508 Subsection 1194.22 of the Rehabilitation Act.

  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.
  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.
  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 Section 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.

Web Accessibility Resources

  • Web Content Accessibility Guidelines (WCAG) - A set of guidelines explaining how to make Web content accessible to those with disabilities.
  • W3C Web Accessibility Initiative (WAI) - WAI, in coordination with organizations around the world, pursues accessibility of the Web through five primary areas of work: technology, guidelines, tools, education and outreach, and research and development.
  • Section 508 Home Page - Section 508 requires that Federal agencies' electronic and information technology is accessible to people with disabilities, including employees and members of the public.
  • Web Accessibility and Persons with Disabilities - A comprehensive site detailing accessibility guidelines and tools maintained for University System of Georgia institutions.
  • AccessGA - Georgia's Accessible ICT Initiative
Open Chatbot