jump to content jump to navigation jump to links
IRS logo Section 508 for Software Development
Page 2 of 3    Training Previous Home Next
Help
Resources
Topic Menu
Module Introduction
Software Accessibility Guidelines
508 Conformance Evaluation Methodologies
Provision A
Provision B
Provision C
Provision D
Provision E
Provision F
Provision G
Provision H
Provision I
Provision J
Provision K
Provision L
Module Conclusion

508 Conformance Evaluation Methodologies

Manual Code Check Versus Automated Code Check

As the application developer, you should be cognizant of the functionality available to users with disabilities. It is entirely your responsibility to create code which conforms to the provisions of Section 508. As applications are designed and developed, manual reviews of the code and the application's functionality are imperative. An accepted method to accomplish this goal is the implementation of Peer Reviews.

Peer Reviews provide a means by which developers submit their designs and code to other developers, not including managers, for constructive criticism and comment. Since the emphasis of Section 508 conformance review tools currently is primarily focused on web-based applications and pages, very few tools exist which provide answers to software developers whether their application conforms to Section 508. Therefore, developers may employ the end-users' tools (e.g. screen readers) in order to assess the application and perform a pseudo-automated review. Use of such assistive technologies is only an approximation, but does provide the experience some end-users with disabilities will have with the interface of the application, and many of the associated problems nonconforming applications present. Screen readers do however, not test 508 conformance directly

Select the Next button to continue.