About Us

Got Questions?

Just Ask.

508 Compliance

Teksouth supports the Government in its compliance with Section 508 throughout the development and implementation of the work to be performed. Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d) requires that when Federal agencies develop, procure, maintain, or use electronic 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 do not have 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. Applicable standards are 1194.21-1194-26.

TEKSOUTH POLICY FOR SECTION 508 COMPLIANCE

Teksouth Corporation supports the goals of Section 508, and we are committed to evaluating ways to make our products more accessible to everyone, including individuals with disabilities or age-related impairments. Our commitment allows us to assist the Federal government in making accessible technology choices.

THE GOALS OF OUR SECTION 508 COMPLIANCE POLICY ARE TO—

  • Meet U.S. Federal regulations for our public sector clients (comply with the letter of the law)
  • Produce Web based tools and applications that are universally accessible (comply with the spirit of the law)
  • Educate our staff on Section 508 requirements

WHY BE SECTION 508 COMPLIANT?

It is a law for U.S. federal government (and many state/local government) agencies, that form our current and potential customer base.
Section 508 compliance is spreading beyond the public sector, becoming an internal requirement for major corporations and non-profit organizations.

Section 508 regulations are being merged into the W3C Web Content Accessibility Guidelines (WCAG 2.0) and ISO standards, so compliance with these HTML standards help us operate on future web browsers and platforms (PDAs, phones, etc.).

Section 508 is a design standard for universal accessibility, just as PCI Compliance is a design standard for financial data security.

Following Section 508 guidelines can help multiple developers in a globally-distributed work environment produce consistent, quality HTML code.

SECTION 508 COMPLIANCE POLICY

Our policy for Section 508 compliance is:

1. 100% compliant on the registrant-facing side (i.e., Forms and Web Sites)
2. Strive for compliance with documentation and Help files, or offer a 508-compliant option
3. Strive for compliance on Admin side (intranet application), but not at the expense of harming the UI experience for sighted users.

“Strive for compliance” means that where possible on the Admin side and Help files, we should write HTML to the standards of the W3C WCAG and Section 508 guidelines. These standards are international best practices and insure maximum interoperability of HTML as the web moves to new browsers, mobile devices, kiosks, etc. So all images should have ALT tags, all form fields should have ID attributes with Label tags, all data tables should have header descriptors (as defined in the standards), all HTML should be checked for syntax errors such as end tags and tag nesting. But for areas where meeting 508 compliance would result in an inferior UI for sighted users, we can make an exception in the admin side and Help files. An example here is the Help files “Table of Contents”, which is not 508 compliant but has a much better UI for sighted readers through its dynamic interface. In cases where compliance will not be achieved, then we should try to offer a 508-compliant alternative.

Read more about 508 Compliance:

Section 508   |   Access Board   |   w3.org