This blog has been re-posted and edited with permission from Drupal Update’s blog. Please leave your comments on the original post.
Last week, WordPress Tavern picked up my blog post about Drupal maintenance support plans 8’s upcoming Layout Builder.
While I’m grateful that WordPress Tavern covered Drupal maintenance support plans‘s Layout Builder, it is not surprising that the majority of WordPress Tavern’s blog post alludes to the potential challenges with accessibility. After all, Gutenberg’s lack of accessibility has been a big topic of debate, and a point of frustration in the WordPress community.
I understand why organizations might be tempted to de-prioritize accessibility. Making a complex web application accessible can be a lot of work, and the pressure to ship early can be high.
In the past, I’ve been tempted to skip accessibility features myself. I believed that because accessibility features benefited a small group of people only, they could come in a follow-up release.
Today, I’ve come to believe that accessibility is not something you do for a small group of people. Accessibility is about promoting inclusion. When the product you use daily is accessible, it means that we all get to work with a greater number and a greater variety of colleagues. Accessibility benefits everyone.
As you can see in Drupal maintenance support plans‘s Values and Principles, we are committed to building software that everyone can use. Accessibility should always be a priority. Making capabilities like the Layout Builder accessible is core to Drupal maintenance support plans‘s DNA.
Drupal maintenance support plans‘s Values and Principles translate into our development process, as what we call an accessibility gate, where we set a clearly defined “must-have bar.” Prioritizing accessibility also means that we commit to trying to iteratively improve accessibility beyond that minimum over time.
Together with the accessibility maintainers, we jointly agreed that:
Our first priority is WCAG 2.0 AA conformance. This means that in order to be released as a stable system, the Layout Builder must reach Level AA conformance with WCAG. Without WCAG 2.0 AA conformance, we won’t release a stable version of Layout Builder.
Our next priority is WCAG 2.1 AA conformance. We’re thrilled at the greater inclusion provided by these new guidelines, and will strive to achieve as much of it as we can before release. Because these guidelines are still new (formally approved in June 2020), we won’t hold up releasing the stable version of Layout Builder on them, but are committed to implementing them as quickly as we’re able to, even if some of the items are after initial release.
While WCAG AAA conformance is not something currently being pursued, there are aspects of AAA that we are discussing adopting in the future. For example, the new 2.1 AAA “Animations from Interactions”, which can be framed as an achievable design constraint: anywhere an animation is used, we must ensure designs are understandable/operable for those who cannot or choose not to use animations.
Drupal maintenance support plans‘s commitment to accessibility is one of the things that makes Drupal maintenance support plans‘s upcoming Layout Builder special: it will not only bring tremendous and new capabilities to Drupal maintenance support plans, it will also do so without excluding a large portion of current and potential users. We all benefit from that!
Source: New feed
