In late 2018, WPCampus released a
request for proposals
to conduct an accessibility audit of the WordPress Gutenberg editor.
The vendor was selected,
and a fundraising goal of $31,200 was met. On April 29, 2019,
Tenon LLC
provided the final audit report to WPCampus. On May 1, 2019,
WPCampus publicly shared the report documents.
What happened over the next year? Did any accessibility changes come to WordPress and the editor because of the audit?
Join Joe Dolson, a WordPress Accessibility team lead, as he shares outcomes of the WPCampus Gutenberg accessibility audit and the current state of progress
within WordPress accessibility.
Amanda Rush
NEW: @YouTube confirms it is discontinuing its community captions feature, which allowed viewers to contribute subtitles to other channels to make videos accessible to #deaf and hard of hearing people.
The tool will be retired on 28 September 2020.https://t.co/FOPGIcBcVz
— Liam O'Dell (@LiamODellUK) July 30, 2020
In this article, Harris Schneiderman walks you through the process of analyzing a wireframe and making coding decisions to optimize for accessibility.
The most efficient way to build accessible websites and apps is to “shift left” by incorporating accessibility testing into the earliest stages of your development and design process. In this article, Harris will walk you through the process of analyzing a wireframe from an accessibility perspective and making coding decisions to optimize for accessibility in both design and development phases.