AccessivePath

guide

EAA on Drupal: complete compliance checklist

Implementing EAA compliance on Drupal means addressing the platform's specific failure modes (custom modules introducing inaccessible markup, inaccessible wysiwyg content from editors) while applying European Accessibility Act success criteria across content, code, and editorial workflow.

Maya Ramos · IAAP CPACC · IAAP WAS · 7 years lead auditor3 min readPublished · Updated

EAA in 60 seconds

The European Accessibility Act (Directive (EU) 2019/882) is the EU's prescriptive accessibility law that takes effect 28 June 2025, requiring covered products and services — banking, e-commerce, transport, audiovisual media, ebooks and computer hardware — to meet harmonised accessibility requirements derived from EN 301 549 and WCAG 2.1 AA.

Drupal accessibility — what you are starting with

Drupal's commitment to accessibility is institutional: a dedicated accessibility maintainer, an a11y gate on core changes, and an accessibility-focused community. Drupal is the most-deployed CMS in higher education and government for this reason.

EAA setup checklist for Drupal

1. Use core themes (Olivero, Claro): Both target WCAG 2.1 AA out-of-box.

2. Audit contributed modules: Each module ships its own templates; audit before deployment.

3. Editor training: Use the Editoria11y module to catch authoring failures in CKEditor.

Common EAA failures on Drupal

• Custom modules introducing inaccessible markup

• Inaccessible WYSIWYG content from editors

• Contributed modules with weaker a11y

• Layout Builder customisations

Putting it together

Combine EAA's Level AA requirements with Drupal's native tooling. Bake accessibility into your component library and editorial workflow; instrument axe-core in CI for regression.

FAQ

Frequently asked questions

Cited answers. Sourced. Updated as standards and case law change.

  • Is Drupal EAA-compliant out of the box?

    Drupal's institutional commitment to accessibility makes it the lowest-risk choice for organisations under Section 508, ADA Title II, or WAD scrutiny.

  • What is the easiest path to EAA compliance on Drupal?

    Start with the platform's most-accessible default theme (where applicable), audit each installed plugin/extension/module, train content authors on alt text and heading hierarchy, and instrument axe-core in your CI pipeline.

  • Why is Drupal popular in government and higher-ed?

    Drupal's institutional commitment to accessibility makes it the lowest-risk choice for organisations under Section 508, ADA Title II, or WAD scrutiny.

Stop guessing. Get the audit a Fortune 500 a11y team would have written.

Free audit on your live URL. No sign-up. IAAP-format report. Ready in hours.

founders@accessivepath.com · +977 9851094056