Practices for embedding accessibility and inclusive design into a team’s workflow.
Each person on a team, whether you’re a manager, designer, or developer, has a role to play in making federal resources accessible and inclusive. Your responsibilities are different depending on your role. So that’s how we structured the guide, with a separate section for each of five roles:
- Product management
- Content design
- UX design
- Visual design
- Front-end development
This guide provides:
- An overview of how each team member can contribute to a product's accessibility
- A framework for thinking about accessibility and inclusive design in your role
- An understanding of the human need behind accessibility practices
We focus on the issues most likely to impact government sites. These guidelines do not provide a comprehensive list of all possible issues. Your team will need additional resources and work to conduct manual audits to conform to the standards of Section 508 (which aligns with the W3C Web Content Accessibility Guidelines (WCAG) 2.0 Level AA), a law that ensures all web content is accessible to anybody with a disability.
This guide is maintained by the Accessibility Guild in the Technology Transformation Services (TTS) at the U.S. General Services Administration (GSA).
The Accessibility for Teams runs on Jekyll. To run it locally:
- Clone the repository.
- Get Jekyll and the necessary dependencies:
bundle install
- Run the web server with
npm run start
- Visit the local site at http://localhost:4000
USWDS is updated to 3
uses SASS module syntax for USWDS packages.
You can make updates to USWDS with npm
.
Add custom styles to _custom-theme.scss
as described in the uswds repo.
This site uses custom USWDS theme settings in _src/assets/uswds-theme
. Use this if you want to include or remove utilities or update utility settings.
- Compile SASS
gulp compileSass
- Run jekyll
npm run start
For more information on contributing to the Accessibility for Teams (or even making a suggestion), see CONTRIBUTING.
This project is in the worldwide public domain. As stated in CONTRIBUTING:
This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication.
All contributions to this project will be released under the CC0 dedication. By submitting a pull request, you are agreeing to comply with this waiver of copyright interest.