Skip to content

Commit 4762846

Browse files
authored
Merge pull request #141 from joedolson/patch-1
Update accessibility.md
2 parents bdf3672 + a0e73f1 commit 4762846

1 file changed

Lines changed: 7 additions & 7 deletions

File tree

wordpress-coding-standards/accessibility.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Accessibility Coding Standards
22

3-
Code integrated into the WordPress ecosystem - including WordPress core, WordPress.org websites, and official plugins, is expected to conform to the Web Content Accessibility Guidelines (WCAG), version 2.1, at level AA.
3+
Code integrated into the WordPress ecosystem - including WordPress core, WordPress.org websites, and official plugins, is expected to conform to the Web Content Accessibility Guidelines (WCAG), version 2.2, at level AA.
44

55
New or updated interfaces are encouraged to incorporate the Authoring Tool Accessibility Guidelines (ATAG) 2.0. The most significant way that ATAG 2.0 guidelines can be incorporated is by emphasizing choices that help people make more accessible content: encouraging alternative text, captions, and semantic structures, for example.
66

@@ -10,15 +10,15 @@ The WordPress A11y team is in the process of developing a library of recommended
1010

1111
Normative Documents:
1212

13-
- [W3C WCAG 2.1](https://www.w3.org/TR/WCAG21)
13+
- [W3C WCAG 2.2](https://www.w3.org/TR/WCAG22)
1414
- [W3C ATAG 2.0](https://www.w3.org/TR/ATAG20/)
1515
- [W3C WAI ARIA 1.1](https://www.w3.org/TR/wai-aria/)
1616

1717
Informative Documents:
1818

19-
- [W3C Understanding WCAG 2.1](https://www.w3.org/WAI/WCAG21/Understanding/)
19+
- [W3C Understanding WCAG 2.2](https://www.w3.org/WAI/WCAG22/Understanding/)
2020
- [W3C Using ARIA](https://www.w3.org/TR/using-aria/)
21-
- [W3C WAI-ARIA Authoring Practices 1.1 (accessible design patterns)](https://www.w3.org/TR/wai-aria-practices-1.1/)
21+
- [W3C WAI-ARIA Authoring Practices Guide (accessible design patterns)](https://www.w3.org/WAI/ARIA/apg/)
2222
- [W3C Introduction to ATAG](https://www.w3.org/WAI/standards-guidelines/atag)
2323

2424
## About WCAG A, AA, and AAA Conformance Levels
@@ -35,7 +35,7 @@ The WordPress commitment is to conform to all WCAG 2.1 Level A and Level AA guid
3535

3636
## Applying WCAG Conformance Levels
3737

38-
WCAG 2.1 consists of 4 layers:
38+
WCAG 2.2 consists of 4 layers:
3939

4040
- Principles
4141
- Guidance
@@ -44,7 +44,7 @@ WCAG 2.1 consists of 4 layers:
4444

4545
### Principles
4646

47-
When applying WCAG 2.1, the guidance and success criteria are organized around 4 principles. These principles place emphasis on how people interact with content and must be:
47+
When applying WCAG 2.2, the guidance and success criteria are organized around 4 principles. These principles place emphasis on how people interact with content and must be:
4848

4949
- **Perceivable** - interacting with the content using the medium that they are familiar with. For example, providing text alternatives for those who are blind.
5050
- **Operable** - finding and using content is accessible. For example, being able to use a keyboard or a screen reader.
@@ -53,7 +53,7 @@ When applying WCAG 2.1, the guidance and success criteria are organized around 4
5353

5454
### Guidance
5555

56-
Each principle is supported by a list of guidelines to ensure that content is more accessible and presentable across the different devices that meet a user’s disability. The guidelines are listed below, the full detail can be found in the WCAG 2.1.
56+
Each principle is supported by a list of guidelines to ensure that content is more accessible and presentable across the different devices that meet a user’s disability. The guidelines are listed below, the full detail can be found in the WCAG 2.2.
5757

5858
#### Principle: Perceivable
5959

0 commit comments

Comments
 (0)