Integrating Section 508 into test automation



This repository presents explanations and fully functioning code examples of several semi and fully automated open source accessibility test tools. These tools fall into multiple technical and strategic categories of use for assessing ICT for Section 508/accessibility conformance in the Software Engineering Life Cycle.

The purpose of this resource is to provide additional support and fully-functioning examples to DHS components who wish to strategically integrate accessibility test automation, and other DevOps principles, into their software engineering life cycle.


Alert: For those DHS components who do not have access to GitHub, DHS OAST maintains a mirror of this site content in Bitbucket. DHS network permissions are required.

Complexity level and testing strategy

With complexity defined as level of knowledge required for use, installation logistics involved, and level of test results feedback presented to the user, the tools presented in this repository present a wide range of complexity from the relatively simple to the highly complex. Specifically, the tools range from browser plug-ins, to command line interface (CLI) tools, to API information for full scripting, as well as a few examples that OAST developed that displays how some of these accessibility open source tools can be extended to provide greater functionality.

Regarding testing strategy, the tools presented on this resource are suitable for integrating accessibility into developer unit testing, accessibility integration testing, or Q.A./regression testing for accessibility – depending on the tool and method of integration.

Given the range of complexity of tools and range of testing approach possible, the technical team can select the type of tool and strategy for integration that works best for them.

Automated tools and rulesets

Some of the more powerful automated tools presented on this GitHub resource allow the user to pick and choose the individual, underlying rules used for testing. When automated tools have this feature, the user can exercise much more control over the quality and relevance of test results. Review the page Automated tools and rulesets for automated rules reviewed and recommended by OAST as being closer in alignment with Trusted Tester methodology.

Using the examples

To take advantage of examples, we recommend you fork the Dev-Automation repository and then focus on the example(s) of interest via the local copy of the repository you created via the fork.

Prerequisites for using the automation examples

The examples presented in this resource assumes knowledge and experience with GitHub and knowledge of any testing frameworks into which you want to integrate any of the accessibility test libraries presented in this resource.

Test automation examples

The links below point to examples for various test engines and examples on the GitHub site.

To navigate the alternative  Bitbucket mirror site, use the navigational links located HERE. DHS network permissions are required to access Bitbucket..



Google Lighthouse


Updated: Thursday 03/04/2021 3:51 PM | Template Version: 07/12/2020 02:00p