WCAG — the Web Content Accessibility Guidelines — is the international standard for web accessibility. In the United States, Section 508 compliance and ADA Title III requirements both reference WCAG 2.1 AA as the applicable standard. Most higher education, government, and nonprofit organizations are legally required to meet it. Many private organizations are subject to it as well through accessibility lawsuits and settlement agreements that have been expanding WCAG’s reach across industries.
What WCAG compliance requires, and how a Drupal site achieves it, is more nuanced than passing an automated scan. This is what it actually involves.
What WCAG 2.1 AA Requires
WCAG is organized around four principles — Perceivable, Operable, Understandable, and Robust — and 50 success criteria at the AA level. The most commonly encountered requirements include:
Alternative text for images. Every image that conveys information must have descriptive alt text. Images that are purely decorative must have empty alt attributes so screen readers skip them.
Keyboard accessibility. Every function on the page must be usable with a keyboard alone. Users who cannot use a mouse must be able to navigate menus, submit forms, interact with dialogs, and access all functionality through keyboard controls.
Color contrast. Text must have sufficient contrast against its background. The WCAG 2.1 AA standard requires a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text.
Form labels and error messages. Every form field must have a programmatically associated label. Error messages must identify the field in error and describe how to fix it.
Consistent navigation. Navigation mechanisms that appear on multiple pages must appear in a consistent order and location.
Headings and structure. Page content must be structured with appropriate headings (H1, H2, H3) that reflect the content hierarchy — not used for styling purposes.
Captions for video. Pre-recorded video with audio must have captions. Live video must have captions for users who are deaf or hard of hearing.
Reflow and zoom. Content must be usable at 400% zoom without horizontal scrolling. Content must not break when text size is increased.
Focus indicators. Keyboard focus must be visible — users navigating with a keyboard must be able to see where the focus is at all times.
What Drupal Provides
Drupal’s core output is built to WCAG standards. The default themes, form rendering, navigation patterns, and HTML output of a properly configured Drupal site meet the technical requirements of WCAG 2.1 AA.
Specific Drupal capabilities that support accessibility:
Alt text fields on images. Drupal’s image media type includes an alt text field that is required by default. Content editors are prompted to provide alt text for every image. Drupal CMS includes the AI Image Alt Text module, which generates alt text suggestions using AI for editor review.
Semantic HTML. Drupal generates semantically correct HTML for headings, lists, navigation, landmarks, and form elements. A custom theme that overrides these patterns without maintaining semantic correctness reintroduces accessibility problems.
CKEditor 5 accessibility. Drupal’s rich text editor (CKEditor 5) includes accessibility tools — heading level controls, table accessibility features, link text prompts — that guide editors toward accessible content.
Editoria11y (Drupal CMS). The Editoria11y module included in Drupal CMS scans published content for accessibility issues and surfaces them to editors and administrators in real time. It checks for missing alt text, improper heading hierarchy, empty links, low contrast text, and other common content-level accessibility failures.
ARIA support. Drupal’s theme system supports ARIA attributes for dynamic content, modal dialogs, and other interactive elements.
What Drupal Does Not Do Automatically
Drupal provides a strong accessibility foundation. It does not guarantee WCAG compliance regardless of how the site is built or how content is managed.
Custom themes can introduce accessibility issues. A custom theme that uses non-semantic HTML, removes focus indicators, creates insufficient color contrast, or uses JavaScript without keyboard equivalents reintroduces the problems Drupal’s foundation avoids. Theme development for a WCAG-compliant site requires testing with screen readers and keyboard-only navigation, not just automated tools.
Content editors can introduce accessibility issues. Even on an accessible platform, content that lacks alt text, uses heading levels for styling, has poor color contrast in inline styles, or contains inaccessible PDFs creates accessibility failures. Ongoing editorial training and tools like Editoria11y are necessary to maintain compliance at the content level.
Third-party embeds must be assessed separately. Videos from YouTube, documents from Google Docs, forms from third-party tools, maps, and social media embeds all have their own accessibility characteristics that are not controlled by Drupal. Each must be assessed against WCAG requirements.
Achieving and Maintaining Compliance
Achieving WCAG 2.1 AA compliance on a Drupal site involves three phases:
Platform and theme audit. An automated accessibility scan followed by manual testing with keyboard navigation and screen readers identifies technical issues in the theme, custom modules, and platform configuration. Automated tools catch roughly 30-40% of WCAG failures; manual testing is required for the rest.
Content audit. A review of existing content for accessibility failures: missing alt text, improper heading structure, inaccessible PDFs, video without captions, and other content-level issues. For large content libraries, this is typically the most time-intensive phase.
Remediation. Addressing the issues identified in the audit — theme fixes, content updates, PDF remediation, video captioning, and editorial workflow improvements to prevent future issues.
Maintaining compliance requires ongoing attention. The Editoria11y module, editorial training, and periodic accessibility reviews prevent the gradual re-introduction of accessibility failures as content grows and the site evolves.
How Cool Fire Approaches Accessibility
Cool Fire Inc builds Drupal platforms implementation to support ongoing editorial compliance.
Frequently Asked Questions
What level of WCAG compliance is required for my organization?
Most compliance frameworks in the United States — Section 508, ADA Title III, and university or state accessibility policies — reference WCAG 2.1 Level AA as the standard. Level A is the minimum; Level AA is the practical standard for most organizational requirements. Level AAA is aspirational and is not required for most organizations.
Does Drupal automatically make my site WCAG compliant?
Drupal’s core output is built to WCAG standards, which provides a strong foundation. But compliance depends on how the theme is developed, what custom modules do, and how content is managed. A custom theme built without accessibility review and content editors who do not follow accessible content practices will produce a site that is not compliant despite running on Drupal.
How do I test my Drupal site for accessibility?
Start with automated tools: Google Lighthouse, WAVE, and Axe all identify common accessibility failures without manual testing. Follow up with keyboard-only navigation testing and screen reader testing (NVDA or JAWS on Windows, VoiceOver on Mac and iOS). Manual testing catches the failures that automated tools cannot identify, which is typically the majority of significant accessibility issues.
What are the most common accessibility failures on Drupal sites?
Missing or inadequate image alt text, improper heading hierarchy (headings used for styling rather than structure), insufficient color contrast in custom themes, form fields without associated labels, and content in PDFs or embedded documents that has not been made accessible. All of these are addressable — they require editorial attention more than technical complexity.
What is the penalty for not meeting WCAG requirements?
Organizations subject to Section 508 or Title II/III ADA requirements face legal liability for inaccessible websites. DOJ enforcement actions, private lawsuits, and settlement agreements can require remediation, monitoring, and financial penalties. Higher education institutions that receive federal funding face specific Section 508 requirements with enforcement through the Department of Education’s Office for Civil Rights.