You are here:

Project Access

Question: To what extent does your project provide access and help those with various access needs?


The project access metric measures how accessible different parts of the project are for community members and new contributors. Some parts of the project may be more accessible than others. Barriers to access may be due to technology, project governance, lack of project resources, restrictions on internet access, or inattention to access concerns.


Access to open source projects is of utmost importance. Community members and maintainers want their projects to be as accessible as possible for all with an interest in contributing. This metric aims to help project members recognize and track the ease of access to a project over time. By documenting and cataloging measures to improve access taken by the project team, community members can be empowered to contribute to a project and take on leadership roles more easily and transparently.

Considerations for access may include physical ability, neurodiversity, a contributor’s location, their native language, available internet bandwidth, or other potential barriers to participating in an open source project.


Depending on the size of the project as well as the financial constraints, access considerations may include:

  • Community members’ access to project code and documentation
  • Community members’ access to the platform, tools, and technology used by the project
  • Continuous attention to and implementation of published accessibility standards as listed in the Web Content Accessibility Guidelines (see References)
  • Globally friendly meetings that are not only friendly to US and Western European community members
  • Means of connecting to online meetings in various ways (computer, phone)
  • System by which non-code contributions are supported and recognized
  • Participation in global mentorship programs
  • Regional chapters for the project where community members can work together and contribute in ways that are meaningful in different geographic regions
  • Support for translations as needed


  • Type of access provided (e.g., translation, meeting times, documentation, chat platform)
  • Goal of access (e.g., international inclusion, accessibility)

Tools Providing the Metric

Data Collection Strategies

There are several different ways to signal attention to this metric which may include:

  • Survey the community about project access. Potential survey questions for community members include:
    • [Survey Likert Item 1-x] The code and documentation are easily available to me
    • [Survey Likert Item 1-x] The project has a public-facing repository that is easy to contribute to
    • [Survey Likert Item 1-x] The project has a system for periodic accessibility audits
    • [Survey Likert Item 1-x] The project has meetings in different global locations
    • [Survey Likert Item 1-x] The project actively reaches out to a diverse, global population for contributions or support
  • Perform regular accessibility audits
  • Perform regular reviews of project Event Location Inclusivity, Documentation Accessibility, and Chat Platform Inclusivity



  • Matt Germonprez
  • Kevin Lumbard
  • Elizabeth Barron
  • Anita Ihuman
  • Sean Goggins
  • Armstrong Foundjem

To edit this metric please submit a Change Request here:

To reference this metric in software or publications please use this stable URL:

The usage and dissemination of health metrics may lead to privacy violations. Organizations may be exposed to risks. These risks may flow from compliance with the GDPR in the EU, with state law in the US, or with other laws. There may also be contractual risks flowing from terms of service for data providers such as GitHub and GitLab. The usage of metrics must be examined for risk and potential data ethics problems. Please see CHAOSS Data Ethics document for additional guidance.

Was this article helpful?
Dislike 0