W3C Publishes Updated ARIA in HTML Recommendation

Web standards body W3C published an updated ARIA in HTML Recommendation on 11 August 2026. In its announcement, the World Wide Web Consortium said the Recommendation defines author-conformance requirements for using WAI-ARIA 1.2 and Digital Publishing WAI-ARIA 1.1 attributes with HTML. Its primary objective is to define requirements for conformance-checking tools used by web developers.

The rules are platform-neutral, but they are relevant wherever Drupal produces HTML that combines native semantics with explicit ARIA. Drupal's accessibility coding standards, last updated before this Recommendation on 4 March 2026, advise using HTML semantics where possible, using WAI-ARIA modestly, and keeping pace with W3C recommendations. The guidance also calls for automated checks and manual testing of new interactive components, including testing with assistive technology. The new Recommendation therefore provides an updated standards reference for that existing accessibility practice rather than evidence of a Drupal-specific implementation change.

The 2026 Recommendation does not present every listed rule as a change made on 11 August. W3C says it incorporates substantive changes made since the previous Recommendation of 9 December 2021. Those changes include revised requirements for summary, conditional ARIA support on unassociated label elements, support for selectedcontent in customisable selects, clarification of the html element's semantics, and adoption of image as the preferred synonym for the img role.

Drupal's issue history shows how related conformance questions can move through core independently of a standards publication date. An issue addressing redundant aria-required on fields that already used the native required attribute was opened in 2019 and committed to Drupal 11.x on 18 April 2025. A separate issue opened on 16 February 2026 cited ARIA in HTML over Drupal's use of role="button" on native summary elements. Discussion expanded to browser and assistive-technology behaviour before the issue was closed on 18 July in favour of related work.

WordPress provides a comparable interoperability example. A Gutenberg pull request opened in January 2023 documented Safari with VoiceOver failing to read URL-input combobox suggestions after the implementation had moved from aria-owns to aria-controls. The fix, merged on 1 February 2023, restored the older ARIA 1.0 pattern because testing found it more broadly supported across the browser and screen-reader combinations examined.

That history does not establish how Drupal will respond to the 2026 Recommendation. It does show why conformance questions can result in targeted markup changes, accessibility review, and interoperability testing rather than an immediate CMS-wide release. For Drupal developers, the updated Recommendation provides a current reference for reviewing custom themes, components, and other generated markup while any Drupal-specific response proceeds through its own issue and release processes.