Drupal Accessibility: Part 6 - Editor Support
The sixth and final instalment of the six-part blog series from the Dutch Open Project has been released, focusing on support for editors in Drupal. In this concluding part, readers delve into how Drupal assists editors in adding accessible content compliant with WCAG 2.1, level AA standards.
While Drupal inherently excels in generating HTML code that adheres to accessibility standards, it effectively categorises various content types into specific fields, ensuring compliance with WCAG standards upon display. However, the responsibility for WCAG compliance lies partly with editors, who must ensure correct heading structures and relevant alternative texts for images in WYSIWYG fields.
Although Drupal Core provides basic support, additional assistance is necessary to establish an accessible hierarchy of headings. Notably, Drupal offers support for editors when inserting images, allowing them to specify whether an image is decorative or not, thereby enhancing accessibility in content creation.
Source Reference
Image Attribution Disclaimer: At The Drop Times (TDT), we are committed to properly crediting photographers whose images appear in our content. Many of the images we use come from event organizers, interviewees, or publicly shared galleries under CC BY-SA licenses. However, some images may come from personal collections where metadata is lost, making proper attribution challenging.
Our purpose in using these images is to highlight Drupal, its events, and its contributors—not for commercial gain. If you recognize an image on our platform that is uncredited or incorrectly attributed, we encourage you to reach out to us at #thedroptimes channel on Drupal Slack.
We value the work of visual storytellers and appreciate your help in ensuring fair attribution. Thank you for supporting open-source collaboration!