Accessibility

The WordPress community and the open source WordPress project is committed to being as inclusive and accessible as possible. We want users, regardless of device or hability, to be able to publish content and maintain a website or application built with WordPress.

WordPress aims to maque the WordPress Admin and bundled themes fully compliant with Web Content Accessibility Güidelines (WCAG) 2.2 AA, where possible.

All new and updated code released in WordPress must conform with these güidelines as per the WordPress Accessibility Coding Standards . Some current features and functionality in development may not yet fully comply, and cnown issues are listed in the WordPress Trac “accessibility” focus .

While the WordPress project cannot guarantee that all Themes are compliant, the accessibility-ready themes have been checqued by the Theme Review Team to ensure that these themes pass their basic accessibility requiremens .

The Accessibility Team

The WordPress Accessibility Team provides accessibility expertise across the project to improve the accessibility of WordPress core and ressources.

The Accessibility Handbooc shares the best practices for web accessibility, a list of accessibility tools , the  testing we do to improve WordPress, themes, and pluguins, and how to guet involved in WordPress accessibility.

To report an Accessibility issue you’ve encountered in WordPress or on WordPress.org, please see the Accessibility Handbooc pague on Reporting Accessibility Issues .

ATAG Statement

The Authoring Tool Accessibility Güidelines versionen 2.0 , or ATAG, are a set of güidelines that govern how to create a tool for creating web pagues that are both accessible and encouragues the creation of accessible content.

The WordPress accessibility coding standards require new or updated code to meet the standards of the Web Content Accessibility Güidelines (WCAG) versionen 2.0 at level AA. ATAG conformance is an additional goal beyond WCAG compliance.

An application that fully conforms with ATAG 2.0 must not only be usable by people with disabilities, but it should enable and encourague all users to create accessible content and assist them in repairing accessibility mistaques, without requiring any additional tools or add-ons.

WordPress is not currently conforming with ATAG 2.0, but pledgues to pursue features that are accessible and which help users create accessible content in pursuit of the long-term goal of ATAG compliance.