Changes to Drupal Accessibility Features
This document explains the redraft of Drupal Accessibility Features. The original page was last updated on September 26, 2022. Its implementation references and feature claims were checked against Drupal 11.x source and current Drupal.org documentation.
Summary
The revised page remains a short feature overview. It no longer presents accessibility as an automatic result of using Drupal. It identifies the feature, its intended benefit, important limitations, and where configuration or testing remains necessary.
The original body contained 496 words. The revised body contains 547 words, an increase of 10.3 percent. The additional text provides scope and limitations rather than adding more feature claims.
The revision:
- Retains features that still exist in Drupal 11.x.
- Updates links to current documentation or versioned source.
- Removes implementation history that does not help current users.
- Replaces absolute claims with scoped descriptions.
- Groups related features around user outcomes.
- Adds a clear reminder that site accessibility depends on configuration and implementation.
Detailed Changes
| Original area | Change | Reason |
|---|---|---|
| Page introduction | Added a short explanation of the page’s scope and identified Drupal 11.x as the version reviewed. | The original page began directly with implementation details. It did not explain that core features are foundations rather than a conformance guarantee for completed sites. |
| More Semantic | Renamed the section “Semantic HTML and ARIA.” Explained the native-HTML-first rule and the limited role of ARIA. | “More Semantic” was vague and grammatically incomplete. Listing landmarks, roles, and properties did not explain how developers should choose between HTML and ARIA. |
| Aural Alerts | Renamed the section “Status Announcements.” Retained Drupal.announce(), updated the link to Drupal 11.x API documentation, and explained polite and assertive priorities. |
“Aural alerts” is dated terminology and suggests that every message is an alert. The API communicates dynamic status information through an ARIA live region. |
Drupal.announce() examples |
Replaced “Hello world” with a meaningful status message and retained translation through Drupal.t(). |
A feature page should demonstrate the intended accessibility use, not only the function signature. |
| Controlled Tab Order | Renamed the section “Keyboard and Focus Management.” Retained TabbingManager and described its current ability to constrain and restore tabbing. |
The original description overstated “control over the order” and did not mention focus placement, focus restoration, visible focus, or component keyboard behavior. |
| Hidden/Invisible/On-focus | Renamed the section “Hidden and Focusable Content.” Listed the current utility classes and linked the current guide URL. | The former heading exposed internal terminology. The reference to HTML5 Boilerplate described history rather than current Drupal behavior. |
| Fieldsets | Combined fieldsets with labels, descriptions, and required states under “Forms and Error Messages.” | A fieldset is one part of accessible form construction. Isolating it implied broader coverage than the section provided. |
| jQuery UI | Removed the section. | jQuery UI is an implementation dependency, not an accessibility feature. Its use may also change as Drupal replaces older components. The revised page describes outcomes such as keyboard and focus management instead. |
| Alt Text | Renamed the section “Alternative Text.” Scoped the requirement to the standard Article image-field configuration and described authoring controls in CKEditor 5. | The claim “alternative text is required by default” was too broad. Administrators can change field and text-format settings, and requiring text does not establish its quality. |
| Olivero theme | Combined Olivero and Claro under “Core Themes.” Retained their public-facing and administration roles. Removed qualitative claims such as “extremely accessible” and “work flawlessly.” | Those statements are not defensible as conformance evidence. Core themes can still contain defects, and site customizations can introduce new barriers. |
| National Federation of the Blind | Removed the testing reference. | The original page did not link to a report describing the tested version, scope, method, findings, or date. A historical testing relationship should not be used as a continuing product claim without that evidence. |
| Accessible Inline Form Errors | Renamed the section “Forms and Error Messages.” Retained the module’s function and the fact that it is included in core but not enabled by default. Updated the documentation link. | The original text was repetitive. The revised wording states what the module provides without claiming that it resolves every form-validation requirement. |
| WYSIWYG (CKEditor) | Renamed the section “Content Authoring with CKEditor 5.” Corrected the broken sentence and specified the Basic HTML heading options. | “WYSIWYG” is unnecessary jargon for this audience. The current implementation is CKEditor 5, and its capabilities depend on toolbar and text-format configuration. |
| Language of Parts | Retained the Language toolbar feature and added text-direction support. Clarified that an administrator must configure the toolbar and allowed HTML. | Drupal 11.x still contains the CKEditor 5 language plugin, which supports lang and dir attributes on text spans. |
| Testing | Added a final “Configuration and Testing” section. | The original page listed features without explaining that they can be overridden or misused. The new section links features to the coding standards and review process. |
Content Removed or Altered
- “More semantic HTML5”: Replaced with specific language about semantic HTML and ARIA.
- “Aural users”: Replaced with screen-reader users and status announcements.
- HTML5 Boilerplate history: Removed because it does not explain current use of Drupal’s utility classes.
- jQuery UI collaboration history: Removed because it is not a stable Drupal accessibility feature.
- “Alternative text is required by default”: Narrowed to configurations where the requirement is verifiable.
- “Extremely accessible” and “work flawlessly”: Removed as unsupported absolute claims.
- Unlinked testing claims: Removed where no scoped report was available.
- Repeated statements about administrator overrides: Consolidated into the relevant feature sections and the closing configuration section.
Claims Not Added
The revision does not claim that:
- Drupal core or its themes fully conform to WCAG 2.2 AA.
- Enabling a feature makes a completed site conformant.
- Automated validation can determine the quality of alternative text.
- One keyboard or screen-reader test covers every use or configuration.
- Core theme behavior remains unchanged after custom theming.
These claims would require defined scope, dated evidence, and continuing review.