All Projects → GSA → accessibility-for-teams

GSA / accessibility-for-teams

Licence: other
A ‘quick-start’ guide for embedding accessibility and inclusive design practices into your team’s workflow

Programming Languages

javascript
184084 projects - #8 most used programming language
SCSS
7915 projects
HTML
75241 projects
ruby
36898 projects - #4 most used programming language

Projects that are alternatives of or similar to accessibility-for-teams

accessibility-resources
A curated list of accessibility resources
Stars: ✭ 66 (-17.5%)
Mutual labels:  accessibility, a11y, inclusive-design
A11yproject.com
The A11Y Project is a community-driven effort to make digital accessibility easier.
Stars: ✭ 3,436 (+4195%)
Mutual labels:  accessibility, a11y, inclusive-design
aria-at
Assistive Technology ARIA Experience Assessment
Stars: ✭ 115 (+43.75%)
Mutual labels:  accessibility, a11y
jquery-accessible-simple-tooltip-aria
jQuery accessible simple tooltip window, using ARIA
Stars: ✭ 22 (-72.5%)
Mutual labels:  accessibility, a11y
accessibility-resources
Screen reader and WCAG testing resources to maintain a consistent approach to testing and documenting behaviour.
Stars: ✭ 25 (-68.75%)
Mutual labels:  accessibility, a11y
togglific
Do you find web animations distracting? Togglific provides a distraction-free web experience!
Stars: ✭ 17 (-78.75%)
Mutual labels:  accessibility, a11y
cauldron
cauldron.dequelabs.com/
Stars: ✭ 50 (-37.5%)
Mutual labels:  accessibility, a11y
accessible-name-automation-proof-of-concept
This is an experiment based on Accessibility Object Model (AOM). It tries to demonstrate that it is theoretically possible (in a certain way) to predict what the screen reader will say by focusing on semantic and non semantic elements with a bit of automated testing, thus reducing the need for manual testing.
Stars: ✭ 15 (-81.25%)
Mutual labels:  accessibility, a11y
vue-focus-loop
Vue component that helps you to to trap focus in an element.
Stars: ✭ 23 (-71.25%)
Mutual labels:  accessibility, a11y
openacr
OpenACR is a digital native Accessibility Conformance Report (ACR). The initial development is based on Section 508 requirements. The main goal is to be able to compare the accessibility claims of digital products and services. A structured, self-validated, machine-readable documentation will provide for this.
Stars: ✭ 61 (-23.75%)
Mutual labels:  accessibility, a11y
makeup-js
Mono-repo for all vanilla JavaScript utility modules and headless ui
Stars: ✭ 28 (-65%)
Mutual labels:  accessibility, a11y
lint-html-with-css
Lint HTML with CSS. A collection of CSS snippets from the hashtag #lintHTMLwithCSS on twitter. These CSS snippets intend to warn developers about common mistakes made in HTML.
Stars: ✭ 35 (-56.25%)
Mutual labels:  accessibility, a11y
eufemia
DNB Design System
Stars: ✭ 38 (-52.5%)
Mutual labels:  accessibility, a11y
ari
Accessible unstyled vue components
Stars: ✭ 22 (-72.5%)
Mutual labels:  accessibility, a11y
bones
Accessible HTML code patterns for common UI widgets such as tabs, menus, dialogs, etc.
Stars: ✭ 79 (-1.25%)
Mutual labels:  accessibility, a11y
agnostic-axe
Framework agnostic accessibility reporter, powered by axe-core
Stars: ✭ 80 (+0%)
Mutual labels:  accessibility, a11y
Tanaguru
Automated accessibility (a11y) testing tool, with emphasis on reliablity and automation
Stars: ✭ 116 (+45%)
Mutual labels:  accessibility, a11y
Design System
Open source design and front-end development resources for creating Section 508 compliant, responsive, and consistent websites.
Stars: ✭ 192 (+140%)
Mutual labels:  government, a11y
a11y-contracting
Building Accessibility Best Practices into Contracting
Stars: ✭ 43 (-46.25%)
Mutual labels:  accessibility, a11y
a11y-checker
Identifies accessibility issues in HTML markup.
Stars: ✭ 103 (+28.75%)
Mutual labels:  accessibility, a11y

Accessibility for Teams

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).

Running the site

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

Updating USWDS to a later version.

USWDS is updated to 3 uses SASS module syntax for USWDS packages. You can make updates to USWDS with npm.

Change theme settings

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.

  1. Compile SASS gulp compileSass
  2. Run jekyll npm run start

Contributing

For more information on contributing to the Accessibility for Teams (or even making a suggestion), see CONTRIBUTING.

Public domain

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.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].