For those unfamiliar with accessibility issues pertaining to web page design, consider that many users may be operating in contexts very different from your own:

They may not be able to see, hear, move, or may not be able to process some types of information easily or at all. They may have difficulty reading or comprehending text. They may not have or be able to use a keyboard or mouse. They may have a text-only screen, a small screen, or a slow Internet connection. They may not speak or understand fluently the language in which the document is written. They may have an early version of a browser, a different browser entirely, a voice browser, or a different operating system. Content developers must consider these different situations during page design. While there are several situations to consider, each accessible design choice generally benefits several disability groups at once and the Web community as a whole.

The Web Content Accessibility Guidelines (WCAG) documents explain how to make Web content more accessible to people with disabilities. Web "content" generally refers to the information in a Web page or Web application, including text, images, forms, sounds, and such.

The WCAG 2.0 techniques can be used to unambiguously meet every one of the Section 508 guidelines.

• Web content developers (page authors, site designers, etc.)