WCAG technical documents are developed by the Web Content Accessibility Guidelines Working Group (WCAG WG), which is part of the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI) and defines how to make Web content more accessible to people with disabilities. Accessibility involves a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.

How to Meet WCAG 2.0
A customizable quick reference to Web Content Accessibility Guidelines 2.0 requirements (called “success criteria”) and techniques at www.W3.org quick reference says:

• Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
• Time-based Media: Provide alternatives for time-based media.
• Adaptable: Create content that can be presented in different ways (for
• Distinguishable: Make it easier for users to see and hear content including separating foreground from background.
• Keyboard Accessible: Make all functionality available from a keyboard.
• Enough Time: Provide users enough time to read and use content.
• Seizures: Do not design content in a way that is known to cause seizures.
• Navigable: Provide ways to help users navigate, find content, and determine
• where they are.
• Readable: Make text content readable and understandable.
• Predictable: Make Web pages appear and operate in predictable ways.
• Input Assistance: Help users avoid and correct mistakes.
• Compatible: Maximize compatibility with current and future user agents, including assistive technologies.

Read the Web Content Accessibility Guidelines (WCAG) Overview for more information