IT Accessibility Quick Guide

This quick guide is designed to provide a high-level understanding of how to use different types of campus technologies accessibly. For more detailed information follow the links for each technology. This document can be downloaded as a single page, front and back handout.

Questions and Help

Web: go.ncsu.edu/accessibility

Email: accessibility@ncsu.edu

Our Commitment

  • Universities must provide reasonable accommodations to qualified students with disabilities. At NC State, the Disability Services Office (DSO) is authorized to make these determinations.
  • The law does not require us to waive courses or other requirements, lower academic standards, or adopt measures which fundamentally alter a course.
  • Communications with Persons with disabilities must be timely, equally effective, and in an equally integrated manner as compared with non-disabled Persons.
  • NC State has an ICT Accessibility Regulation (go.ncsu.edu/ict-accessiblity-reg) and a set of FAQs accompanying the regulation (go.ncsu.edu/ict-accessiblity-faq).
  • Creating an accessible IT environment is a shared responsibility between the institution and the content creator.

Planning

  • All content should be made accessible when delivered to a group where the functional limitations are not known, or someone in the group needs an accessible version.
  • Planning for accessibility from the beginning is an order of magnitude easier, both in time and money, than fixing it after the fact.
  • It is the responsibility of the content creator to design accessible content.
Technology Quick Guides
TechnologyOverview of How to Build it Accessibly
Video
  • include captions
  • use an accessible media player
Microsoft Word
  • use heading styles (can be customized)
  • use built-in formats for bullet lists, columns, and tables
  • avoid text boxes
  • include alternative text for images
  • DO NOT save as a Web page
Microsoft PowerPoint
  • use built-in slide layouts
  • add alternative text for images
  • DO NOT save as a Web page
Microsoft Excel
  • specify column headers
  • DO NOT use blank cells for formatting
Google Docs
  • use heading styles
  • for read-only versions of a Google Doc, export it to an MS Word document
  • DO NOT create PDF files directly from Google Docs
  • PLAN on some users not being able to edit documents online
Narrated Presentations
  • use either Camtasia Studio (Windows-only) or LecShare Pro
  • with Camtasia Studio, export to Flash/HTML player
Google Sites
  • only insert text, links, lists, and images (with alternative text)  into Google Sites
  • tables and other embedded objects cannot be made fully accessible
  • PLAN on some users not being able to edit content within Sites
Web Pages
  • design to the WCAG 2, Level AA standard
  • use freely available tools to test for Web page accessibility
PDF Documents
  • use software that creates accessible PDFs, like Microsoft Word (Windows only) or InDesign
  • use the Libraries Course Reserves for scanned articles
  • OCR must be run on scanned items
  • use Adobe Acrobat Pro Accessibility Wizard to check document
Online Surveys
  • use Qualtrics for point-and-click form creation
  • use inFORM for build-your-own HTML form creation
  • use MeToo! for informal surveys
  • DO NOT use Google Forms
Math
  • use MathType to help you write your equations in either the MathML, LaTeX, or TeX formats
  • use MathJax to insert those equations into Web pages
Clickers
  • TurningPoint clickers can be used in accessible ways
  • problems usually arise when student responses are directly tied to grades
Moodle
  • most of Moodle’s functionality is accessible
  • the Choice and Forum activities can cause problems
  • user added content must be designed accessibly
Blackboard Collaborate
  • most of Collaborate’s functionality is accessible
  • Application Sharing will cause problems for screen reader users
Mediasite
  • online recordings can be made fully accessible by adding captions
  • the WMV video player must be used

Publication date: August 14, 2012