Skip to secondary navigation Skip to main content
U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.

Https

The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.


Developing Accessible Web Content

Learn how to build digital tools that conform to the Revised 508 Standards. Review the W3C’s Sufficient Techniques for examples of how to meet Success Criteria using specific technologies (relevant to HTML, CSS, server-side scripting, Flash, ARIA, etc.).

Content Authoring Guidelines

Open Source Code and Frameworks

Open source code has additional requirements to make the content accessible.

JavaScript Frameworks

Contributors to these JavaScript frameworks actively consider accessibility in development:

  • JQuery - the “grandfather” of JavaScript frameworks; this article specifically addresses how to create accessible forms
  • React.js - web application development framework from Facebook
  • Angular.js - web development framework from Google
  • Bootstrap.js - JavaScript development framework from Twitter
  • ext.js - JavaScript development framework
  • ally.js - JavaScript library to make accessibility simpler for modern web applications

Mobile

Software

Development Environments

Testing Tools

Captioning Tools and Resources

W3C WCAG 2.0 References

The W3C is an internationally recognized web standards body that identifies its approved technical specification standards as “W3C Recommendations” (such as HTML, CSS, etc.). The consortium has several Accessibility specifications that have achieved W3C Recommendation status, including WCAG, ATAG, and WAI-ARIA. Other accessibility-related W3C recommendations, such as the User Agent Accessibility Guidelines, are also relevant.

Other References

Legislation and Standards

These best practices were developed by the U.S. Federal Government Authoring and Developer Transition Working Group, with contributions from the Federal CIO Council Accessibility Community of Practice (ACoP), the U.S. Access Board, and the General Services Administration.

Reviewed/Updated: May 2018