Anyone who has heard me speak about web accessibility knows that I typically call out two motivating factors behind accessibility: usability and regulatory compliance.
Let’s face it, usability can be a hard sell. But if an organization is being tasked with meeting certain standards/guidelines/laws, there may be no choice. The trick, therefore, is knowing if it applies.
“Section 508″ refers to a section in the Rehabilitation Act of 1973 (amended in 1998). Its purpose is stated as follows:
The purpose of this part is to implement section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d). Section 508 requires that when Federal agencies develop, procure, maintain, or use electronic and information technology, Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees who are not individuals with disabilities, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities, unless an undue burden would be imposed on the agency.
Basically, Federal agencies have an obligation only to use or buy products that are accessible. It is not readily known that this also extends to agencies such as post-secondary institutions that receive federal funding. Organizations that wish to sell to these markets must provide products that meet these standards.
Section 508 refers to all electronic technology, and there are standards for software applications, telecommunication products, and others. When looking at web accessibility, we consider section 1194.22: Web-based intranet and internet information and applications.
When an agency is evaluating products or services, it has the obligation to secure the “most accessible” solution. Yes, this acknowledges that there may be some gaps in compliance. When I attended the Access U Conference last year, the representatives from various colleges were all discussing the relative merits of different CMSes, looking for the “most accessible” solution.
To facilitate the assessment of “most compliant”, organizations will often complete a VPAT – a Voluntary Product Accessibility Template. This template allows an organization to document how they do or do not meet each standard. Filling out this template, even if it means acknowledging shortcomings, gives an organization the opportunity to show what they are doing to commit to accessibility. It also makes an organization eligible to list their products in the BuyAccessible Product and Services Directory, which may be used by agencies to find accessible solutions.
While many organizations are not obligated to comply with Section 508 standards, it may still be a good exercise to be familiar with the standards and the rationale behind them. Many of the standards map directly to the WCAG1.0 Guidelines… oh wait, that’s another post, entirely…!
Related posts:
- Subscribe to the RSS feed
- Get Email updates
- Tweet This
- Stumble It
- Add to del.icio.us
- Share on Facebook
- Email to a friend
{ 1 comment… read it below or add one }
In connection to the article, you can find an extensive VPAT directory at . Currently this directory lists over 100 companies which decided to make their VPATs public. Also, you can submit your company’s VPAT and have it listed free.
More from author