Skip to content

Commit

Permalink
Update accessibility.md (#43)
Browse files Browse the repository at this point in the history
Switching the expected WCAG guidelines from WCAG 2.0 to WCAG 2.1 (released 2018). WAG 2.1 is now the standard in some bodies of law, and includes some important changes. See https://wordpress.slack.com/archives/C02RP4X03/p1600443262113800
  • Loading branch information
joedolson authored Sep 20, 2020
1 parent 834ce54 commit 9268dfb
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion wordpress-coding-standards/accessibility.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
# Accessibility Coding Standards

These are standards that WordPress features should meet for accessibility in order to be merged into core. All new or updated code released in WordPress must conform with the WCAG 2.0 guidelines at level AA. These basic guidelines are intended for easy reference during development, but do not cover all possible accessibility issues.
These are standards that WordPress features should meet for accessibility in order to be merged into core. All new or updated code released in WordPress must conform with the WCAG 2.1 guidelines at level AA. These basic guidelines are intended for easy reference during development, but do not cover all possible accessibility issues.

Note: further documentation for meeting WCAG 2.1 accessibility guidelines is in development, with expected publication prior to the release of WordPress 5.6.

In the [Accessibility Handbook](https://make.wordpress.org/accessibility/handbook/best-practices/) there are pages about best practices, including code examples and resources.

Expand Down

0 comments on commit 9268dfb

Please sign in to comment.