Drupal should sign the GAAD Pledge

Created on 6 May 2022, almost 3 years ago
Updated 1 April 2025, 25 days ago

Problem/Motivation

As discussed on Slack, Drupal should sign the GAAD Pledge and would really like to see that we do this. Right now the two big open source projects to have taken it are React & Ember.

Proposed resolution

Drupal signed the GAAD pledge .

This really isn’t a heavy lift for us. We are as a community already doing what is required. This would just commit us to make it a bit better over the next year.

There are 5 elements of the pledge:

  1. - Done
  2. - Done (we will need to update this document).
  3. Publish Accessibility coding standards - We should add a short standards document here.
  4. - Done (thought Improvements are always possible).
  5. s - Done (Accessibility also ATAG)

I can’t see why we wouldn’t want to commit to the GAAD Pledge. This is just a little extra incentive to do something we want to do anyways. It will make our job easier going ahead.

Feature request
Status

Fixed

Component

Approved Plan

Created by

🇨🇦Canada mgifford Ottawa, Ontario

Live updates comments and jobs are added and updated live.
  • Accessibility

    It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024