For websites to be accessible, content needs to be thoughtfully arranged into sections and navigable by headings, so users can easily scan a page and find the information they are seeking. Ensuring that proper structure can be one of the biggest ongoing accessibility challenges for a Drupal site, with many pages ending up with improperly nested heading levels, sections without explicit headings, or regular text that is styled like headings, but missing the proper semantic markup needed by screen readers.
At Kalamuna, we have spent decades figuring out how to build Drupal sites that empower and encourage editors to properly structure the content and provide the headings needed for easy navigation (and passing accessibility scans). Whether pages on your site are created using content type fields, Paragraphs, Layout Builder, Experience Builder, or just one big WYSIWYG, we have tips for how to set things up in a way will result in far more accessible content and much happier users.
What you will learn about in this session:
- The importance of proper heading structure for content navigation.
- Providing the additional context needed by screen reader users.
- Offering feedback to designers to help accessible site building.
- Best practices when configuring fields and paragraphs.
- Organizing your twig templates to help page structure.
- Overcoming the limitations of layout-based page creation.
- CKEditor configuration and accessibility modules.
- Conducting accessibility scans and solving commonly flagged issues.
- Improving content editing UX for accessibility and general happiness.
