WCAG accessibility audit for Drupal

Drupal editors use CKEditor to create content, but the editor does not enforce accessibility best practices. Images are inserted without relevant alt text. Data tables have no headers (th). Headings are used for style (h3 everywhere) instead of logical structure. Links have generic labels. Each published page accumulates editorial non-conformities.

Drupal modules (Views, Paragraphs, Layout Builder, Webform) are developed independently and their combination creates conflicts. Views generates lists without ARIA roles. Paragraphs nests components whose heading hierarchy does not integrate with the document. Layout Builder creates regions without ARIA landmarks. Each module adds HTML that can break the page's overall accessibility structure.

Drupal displays content in blocks distributed across regions (sidebar, header, footer). Each block has its own heading (h2, h3) that inserts into the page independently of the main content hierarchy. The result is an inconsistent heading structure: sidebar h2s are interspersed between main content h2s, block h3s appear before content h2s.

Drupal's Webform module allows creating complex forms, but error handling is not always accessible. Error messages display at the top of the page without being linked to relevant fields via aria-describedby. Focus is not moved to the first field in error. Required fields are not always marked with aria-required. Conditional fields appear without announcement.