WPCampus Seeks to Raise $30K for Gutenberg Accessibility Audit

WPCampus is seeking funding to conduct an accessibility audit of WordPress’ Gutenberg editor. The non-profit organization is dedicated to helping web professionals, educators, and others who work with WordPress in higher education. Educational institutions often have stricter legal obligations that require software to be WCAG 2.0 level AA compliant and many European institutions set the bar even higher at WCAG 2.1.

WPCampus moved to spearhead an audit after Automattic decided to forego Matt MacPherson’s proposal for Gutenberg to undergo an accessibility audit. Results of the audit will help WPCampus determine any potential legal risk for institutions upgrading to WordPress 5.0 and will also identify specific challenges that Gutenberg introduces for assistive technology users and others with accessibility needs.

“A professional accessibility audit is a large expense for a small nonprofit like WPCampus,” WPCampus director Rachel Cherry said. “Accessibility is important to all of us in the WordPress community. We’re asking for your help to fund the audit and ensure this important research is completed.”

WPCampus is still evaluating proposals from vendors and will announce its selection soon, along with an updated timeline for completing the audit. The organization has set its funding goal at $30,000, an amount that falls in the mid-range of the proposals the selection committee has received. If the campaign raises more than the amount required, WPCampus plans to designate the funds for other accessibility-related efforts, such as future audits and live captioning at conferences.

Two days after launching the campaign, WPCampus has received $3,692 (12%) towards its funding goal. The organization plans to share the results of the audit and any supporting documents on its website.

The comments published on the donations page demonstrate how strongly supporters feel about getting an audit and using that information to make Gutenberg a tool that anyone can use. The topic of accessibility is close to the heart for many donating to the campaign.

“When I was navigating stores with three small children, stores which helped me with automatic doors, wide aisles, and shopping carts for a crowd often made the decision for me as to whether I could shop at all,” WordPress developer Robin Cornett said. “As we create content and build tools for the internet, we should be doing all we can to ensure the best online experience we can for everyone.”

WordPress co-founder Mike Little also donated to the campaign, with comments on how important accessibility is to fulfilling the project’s mission.

“As the platform that democratizes publishing, we can’t allow new features in WordPress to take that away from users with accessibility needs,” Little said.

“Accessibility matters to everyone — injured, encumbered, distracted, disabled, everyone,” WordPress consultant Adrian Roselli said. Accessibility in WordPress matters to my clients because some of their people require it in order to use the tool and therefore stay gainfully employed.”

The audit proposed months ago has evolved to become a community effort funded by passionate supporters working in various capacities throughout the WordPress ecosystem. If WPCampus is successful in funding its campaign, this particular approach has the benefit of making it a more cooperative effort with more people invested in the process than if it were funded by a single company. WPCampus aims to release the audit report to the community by January 17, 2019 but the dates will depend on the arrangement with the vendor.


10 responses to “WPCampus Seeks to Raise $30K for Gutenberg Accessibility Audit”

  1. It is again quite bad thought. I mean they have had years to do that audit. Actually without taking accessibility concerns SERIOUSLY into consideration they simply should not have begin coding the UI at all.

    Now as there are only some days until GB lands in core they just want money for that audit?!
    That is a complete non-sense as they will get that audit cost free from people living with accessibility problems the next day as GB ships with core.

    And by the way any audits are completely useless if they just do not listen and change their mind.

    • Read the article again. The audit was proposed months ago not just days to Gutenberg’s release, which in itself, judging by sentiments all around, it’s really good for primetime despite reaching RC status. If you follow discussions it seems as if the Gutenberg team powered ahead without really considering all community feedback.

      The effort and will has always been there for an audit but it’s like it was given a backseat by the core Gutenberg team.

  2. This really is shameful. Its the most blatant abuse of the community’s goodwill being used to line the pockets of Automattic’s investors. It’s not like there are two different WordPress applications — one for professional use and the other for home use — but even if there were, wouldn’t both need to be equally accessible? No, the only organization which should be paying to test this software is the one who stands to make the most money with it. Shame on you Matt Mullenweg.


Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: