> For the complete documentation index, see [llms.txt](https://docs.varbase.vardot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.varbase.vardot.com/developers/understanding-varbase/drupal-cms-recipes/drupal-cms-accessibility-tools.md).

# Drupal CMS Accessibility Tools

## Description

The Drupal CMS Accessibility Tools recipe provides automated accessibility checks using the Editoria11y module. It helps content editors identify and fix accessibility issues directly within the content editing interface, promoting WCAG compliance across the site.

## Recipe Dependencies

Depends on the following recipes:

| Recipe                                                                                                                   | Description                                                |
| ------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------- |
| [**Drupal CMS Content Type Base**](/developers/understanding-varbase/drupal-cms-recipes/drupal-cms-content-type-base.md) | Basic content type tools required for content integration. |

## Included Modules

Brings in the following core and contributed modules to your site:

| Module                                                        | Purpose                                                                                             |
| ------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| [**Editoria11y**](https://www.drupal.org/project/editoria11y) | Checks for accessibility in page content.                                                           |
| **Views** *(in Drupal core)*                                  | Provides a framework to fetch information from the database and to display it in different formats. |

## Installation

Apply the recipe using Drush:

```bash
ddev drush recipe ../recipes/drupal_cms_accessibility_tools
```

## Usage

After installation, Editoria11y automatically scans pages as content editors view them. Accessibility issues are highlighted with inline indicators that editors can click for detailed explanations and remediation guidance. This continuous feedback loop helps editors create accessible content as they work, rather than relying on separate auditing tools after the fact.

Common issues detected include:

* Missing or empty image alt text
* Incorrect heading hierarchy (e.g., skipping heading levels)
* Empty links or buttons
* Potential contrast issues
* Missing document language attributes


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.varbase.vardot.com/developers/understanding-varbase/drupal-cms-recipes/drupal-cms-accessibility-tools.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.