If you build for the margins, you build for everyone. Identify unique needs: Work with government and project contacts to understand the demographics of users and any unique needs they might have. Consider accessibility: Proactively test for accessibility in all work. See W3C WCAG for requirements and 18F Accessibility Guide for tools to use. When collecting demographics: Follow best practices when collecting demographic/identity information via forms, demographic data collection should be optional (whenever possible) and should always explain upfront how it will be used and stored

Minimum requirements for building inclusive products (Part One)

Develop for mobile users: Mobile readiness is expected for all online resources. (Not everyone has the resources to own a computer.) Create compatibility: Products should be compatible across web browsers and versions. Build for multiple languages/locations/cultures: Apply best practices for internationalisation/localisation. Use inclusive language: Abide by plain language best practices. (Test your flesch reading level and use tools like grammarly to ensure language is optimised.)

Minimum requirements for building inclusive products (Part Two) 

<div dir="auto">U.S. Digital Response Inclusion Guidelines</div><div dir="ltr">The pandemic has impacted individuals differently based on race, income, gender, location, disability status, etc., and <a href="https://fivethirtyeight.com/features/the-young-americans-most-vulnerable-to-covid-19-are-people-of-color-and-the-working-class/" data-rnw-int-class="180064____" dir="ltr">marginalized communities have been impacted</a> <a href="https://fivethirtyeight.com/features/the-young-americans-most-vulnerable-to-covid-19-are-people-of-color-and-the-working-class/" data-rnw-int-class="180066____" dir="ltr">more severely</a>, on average. We want to be sure the COVID-19 response adequately accounts for these perspectives.</div><div dir="auto">If we incorporate more perspectives, we can have a more thorough, effective response.</div><div dir="auto">The ability to dedicate time to volunteering is a privilege. Many people do not have the resources to do so – leaving fewer perspectives reflected in our response efforts. Since no life experience can be summarized in a page, to supplement this deficit, we’ve created a quick guide to help us build with everyone in mind.</div><div dir="auto" data-rnw-media-class="207__206">​</div><div dir="auto" data-rnw-media-class="207__206">Minimum requirements for building inclusive products</div><div dir="auto">Products built by USDR volunteers keep these best practices top of mind:</div><UL><div dir="ltr">Identify unique needs: Work with government and project contacts to understand the demographics of users and any unique needs they might have. (<a href="http://s3-us-west-1.amazonaws.com/codeforamerica-cms1/documents/CfA-Digital-Outreach-Playbook-2018.pdf" data-rnw-int-class="180068____" dir="ltr">Here’s an example of how to do this</a>.)</div><div dir="ltr">Consider accessibility: Proactively test for accessibility in all work. We recommend <a href="https://www.usability.gov/what-and-why/accessibility.html" data-rnw-int-class="180070____" dir="ltr">these guidelines as best practices</a>, this <a href="https://digital.gov/topics/accessibility/" data-rnw-int-class="180072____" dir="ltr">list of resources</a> from digital.gov, and the <a href="https://accessibility.18f.gov/" data-rnw-int-class="180074____" dir="ltr">18F Accessibility Guide</a> with a long list of tools to use.</div><div dir="ltr">When collecting demographics: Follow <a href="https://academy.cultureamp.com/hc/en-us/articles/360003599179-FAQ-for-Diversity-Inclusion-Survey-Demographics" data-rnw-int-class="180076____" dir="ltr">best practices</a> when collecting demographic/identity information via forms, (referencing <a href="https://docs.google.com/spreadsheets/d/1Wlj7qBxZTPQhAr-4jRgWscXWXoAVaj43soyuWZLZmeM/edit#gid=0" data-rnw-int-class="180078____" dir="ltr">this spreadsheet for global perspectives</a>). Demographic data collection should be optional (whenever possible) and should always explain upfront how it will be used and stored. Have a concern? Consult with your USDR contact or reach out to <a href="mailto:anne@usdigitalresponse.org" data-rnw-int-class="180080____" dir="ltr">anne@usdigitalresponse.org</a>.</div><div dir="ltr">Develop for mobile users: <a href="https://services.google.com/fh/files/blogs/GoMo_Best%20Practices_GoMo%20Branded.pdf" data-rnw-int-class="180082____" dir="ltr">Mobile readiness</a> is expected for all online resources. (Not everyone has the resources to own a computer.)</div></UL>

U.S. Digital Response Inclusion Guidelines

product

Product & Design

<ul><div>Identify unique needs: Work with government and project contacts to understand the demographics of users and any unique needs they might have. ( <a href="http://s3-us-west-1.amazonaws.com/codeforamerica-cms1/documents/CfA-Digital-Outreach-Playbook-2018.pdf">Here’s an example of how to do this </a>.) </div><div>Consider accessibility: Proactively test for accessibility in all work. We recommend <a href="https://www.usability.gov/what-and-why/accessibility.html">these guidelines as best practices </a>, this <a href="https://digital.gov/topics/accessibility/">list of resources </a>from digital.gov, and the <a href="https://accessibility.18f.gov/">18F Accessibility Guide </a>with a long list of tools to use. </div><div>When collecting demographics: Follow <a href="https://academy.cultureamp.com/hc/en-us/articles/360003599179-FAQ-for-Diversity-Inclusion-Survey-Demographics">best practices </a>when collecting demographic/identity information via forms, (referencing <a href="https://docs.google.com/spreadsheets/d/1Wlj7qBxZTPQhAr-4jRgWscXWXoAVaj43soyuWZLZmeM/edit#gid=0">this spreadsheet for global perspectives </a>). Demographic data collection should be optional (whenever possible) and should always explain upfront how it will be used and stored. Have a concern? Consult with your USDR contact or reach out to <a href="mailto:anne@usdigitalresponse.org">anne@usdigitalresponse.org </a>. </div><div>Develop for mobile users: <a href="https://services.google.com/fh/files/blogs/GoMo_Best%20Practices_GoMo%20Branded.pdf">Mobile readiness </a>is expected for all online resources. (Not everyone has the resources to own a computer.) </div> </ul>

Inclusion Guidelines - USDR Policies

Minimum requirements for building inclusive products (Part One)

Minimum requirements for building inclusive products (Part Two)

CURATED BY

Related collections

More like this