Drupal CMS's accessibility recipe "just works"...most of the time. When you want it to work better, you find that there are more than 130 fields spread across three settings tabs! Learn how we got here from the project lead, and get practical tips on configuration and customization.

Prerequisite

None

Target Audience

Anyone who cares about quality assurance. Typically site owners, QA managers, and/or developers responsible for improving the site editing experience

Outline

Editoria11y was conceived as a deeply integrated Drupal accessibility checker in 2019:

-- v1 introduced automatic, inline alerts for accessibility issues on published pages.

-- v2 added an as-you-type checker for CKEditor and Gutenberg, as well as site-wide dismissals and reports.

-- v3 work is currently focused on building a full quality assurance suite. There are already 3x as many checks as v2, and 3x as much to configure!

We will explore what a well-configured site looks like, and present best practices for your site settings and themes:
-- Preventing false positives and annoying or repetitive alerts.
-- Splitting configuration between content authors and developers.
-- Writing custom tests.
-- Optimizing tip placement for dynamic or clipped content.
-- Using the new report maintenance tools and crawlers.
-- Adding Views relationships to customize filters, reports and exports.
-- Integrating the European Commission's new "AI: Editoria11y" module.

We will end with a look at what’s next, and how the community can guide and contribute to this project's roadmap.

Learning Objectives

Learners should:
-- Be able to optimize their checker to catch the specific issues common to their theme and editors.
-- Know where to find documentation and code samples for extending and modifying the checker.
-- Not feel overwhelmed by 130+ fields spread across 3 configuration tabs!

Experience level
Anyone